How to use Netgear N600 USB wireless adapter on Wary 5.3?

Post Reply
Message
Author
VictorVictor5
Posts: 131
Joined: Thu 24 May 2012, 02:52

How to use Netgear N600 USB wireless adapter on Wary 5.3?

#1 Post by VictorVictor5 »

Greetings all,

So I abandoned my Cisco card and am going to work with USB - probably better in the long run.

I have a Netgear N600 for the Gateway Solo 9100 that I am going to use with Wary 5.3 (and possible RetroPrecise).

Now I tried several of the network setup utilities, but it doesn't detect my USB adapter. Strangely, Wary had no problem picking up my Netgear USB Ethernet converter.

Now I did try "ndiswrapper" and I didn't see any modules for my piece of equipment. Plus I couldn't find any .inf files either.

When I tried to type in "lsusb" I just get "NetGear, Inc." on the bus where the wireless adapter is.

Can someone walk me through the process? I did a search but I'm still not clear on what to do.

Thanks!
VV5
Last edited by VictorVictor5 on Fri 22 Mar 2013, 02:41, edited 1 time in total.

User avatar
pemasu
Posts: 5474
Joined: Wed 08 Jul 2009, 12:26
Location: Finland

#2 Post by pemasu »

Start with pristine fresh install. Ndiswrapper trial disturbs too much so you have to start with fresh install without savefile. Plug in your usb wireless.
Install this pet:
http://distro.ibiblio.org/quirky/pet_pa ... 130207.pet

In console run: pdiag
Post the created tarball here. It creates the tar ball to the /root

We dont know the chip id...or the wireless driver your usb wireless should use, if it would need firmware and if that firmware is in place....or does the wary all together lack the support for your usb wireless. Are there any error messages from the kernel in dmesg and so on.....

Too many questions to try to answer without sufficient data.

VictorVictor5
Posts: 131
Joined: Thu 24 May 2012, 02:52

#3 Post by VictorVictor5 »

Pemasu,

Will do all tonight when I get home. But before I do I am running Live CD right now before I commit to a final install (debating full vs. frugal installs still :roll: ).

Can I still do your tests with a live CD? Would the instructions change?

Thanks!
VV5

User avatar
pemasu
Posts: 5474
Joined: Wed 08 Jul 2009, 12:26
Location: Finland

#4 Post by pemasu »

Live CD without savefile ie using for example boot parameter: puppy pfix=ram is ok. Main thing is that you reboot without any ndiswrapper or any other manual attempts.

Install the pet and plug in the usb wireless.

VictorVictor5
Posts: 131
Joined: Thu 24 May 2012, 02:52

#5 Post by VictorVictor5 »

Pemasu,

That's pdiag pet is pretty damn cool!

File attached - please let me know what you think and if you need me to do anything else!

VV5
Attachments
pdiag-20130227.tar.gz
(91.05 KiB) Downloaded 346 times

User avatar
pemasu
Posts: 5474
Joined: Wed 08 Jul 2009, 12:26
Location: Finland

#6 Post by pemasu »

Manufacturer=Broadcom
Product=Remote Download Wireless Adapter
SerialNumber=0
VendorID=0846 ProductID=9011 KERNEL-DRIVER(builtin)=(none)

It means it has broadcom chip inside.

Chasing with 0846:9011 I found these pages:
http://www.wikidevi.com/wiki/Netgear_WNDA3100v2

http://ubuntuforums.org/showthread.php?t=2052594

It looks like none of the broadcom drivers support your broadcom chip.

And that there is solution by using ndiswrapper. For it you need working .inf file.

I found one and you can try it. I cant attach the package here, due to new restrictions of the file size.
http://ubuntuforums.org/archive/index.p ... 32025.html
http://av3ngr.wikispaces.com/file/view/0846_9011.tar.gz

Launch ndiswrapper with the network wizard. It should be quite straightforward to use the gui. It will ask the .inf file at some step. Point it to that .inf file. There seems to be to 2 to test. It should load it and maybe you get your wireless working. If not, I suppose you need to hunt other .inf file.

VictorVictor5
Posts: 131
Joined: Thu 24 May 2012, 02:52

#7 Post by VictorVictor5 »

pemasu,

Apologies on the delay, I was on business travel.

Out of courtesy, I did try ndiswrapper with the links you provided, but I was unable to get the adapter to work. It's a Broadcom issue.

Thanks for all of your help.

VV5

Post Reply