WNDA 4100 (NetGear N900) Wireless Dual Band USB Adapter

Quote:

---

Originally Posted by feardotcom

Thats the thing...it is inserted but the adapter doesn't have any of the lights on. I noticed when i compiled the drivers the first time that the lights on the adapter didn't come on till after the driver was compiled.

---

We don't see it here:

Quote:

---

lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 0bb4:0ffe High Tech Computer Corp. Desire HD (modem mode)
Bus 004 Device 002: ID 046d:c517 Logitech, Inc. LX710 Cordless Desktop Laser
Bus 003 Device 002: ID 046d:c043 Logitech, Inc. MX320/MX400 Laser Mouse

---

I wonder if the device or the USB port is defective.

I noticed that too... but i've tried multiple usb ports and still nothing. maybe i'll try not using the extension cord it came with when i get home and see what happens. But, before i compiled the driver the first on kernel 3.2.0-29-generic i noticed the computer wasn't even recognizing the adapter was plugged in. After i compiled the driver on kernel 3.2.0-29 generic the adapter come right up and was recognized. I've checked the 2 files i had to modify and they are still what i changed them to from your instructions.

Does anyone have instructions installing the drivers without an internet connection? Would I be able to download the files and put them on my USB, than boot into Ubuntu and compile them?

With or without a driver, it ought to appear in lsusb. Is there any recognition if you unplug the device and then run:

Code:

---

sudo tail -f /var/log/syslog

---

Plug it in. Any interesting messages?

Close out of tail with Ctrl+c.

@Chili: So when i got home from work this morning i unplugged the adapter from the extension cord that was plugged up to the back of the computer and then plugged the adapter into the front usb directly(without the extension cord) and it came right up and worked, so i unplugged from the front and plugged it back into the extension cord and it came right up and connected again. So weird, maybe a short in the extension cord, idk.

@Andy: If you have build essentials installed then yes you can install the drivers without the internet. The drivers just come in a zip file. If you dont have build essentials i think Chili added a link somewhere to get instructions on how to download it from a different computer.

Quote:

---

Originally Posted by chili555

Booted into the new kernel, please run and post:

Code:

---

sudo modprobe rt3573sta
dmesg | grep -e rt3 -e wlan

---

Thanks.

---

OK ... finally tried it and here's the output:

cecilieaux@CM-Workstation:~$ modinfo rt3573sta | head -n5
filename: /lib/modules/3.2.0-30-generic-pae/kernel/drivers/net/wireless/rt3573sta.ko
version: 2.5.0.0
license: GPL
description: RT2870 Wireless Lan Linux Driver
author: Paul Lin <paul_lin@ralinktech.com>
cecilieaux@CM-Workstation:~$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 004: ID 0846:9012 NetGear, Inc.
Bus 002 Device 002: ID 413c:3200 Dell Computer Corp. Mouse
Bus 002 Device 003: ID 413c:2003 Dell Computer Corp. Keyboard
cecilieaux@CM-Workstation:~$ dmesg | tail -n10
[ 3565.436065] EDAC MC0: CE page 0x16cbe, offset 0xb00, grain 64, syndrome 0xc1, row 0, channel 1, label "DIMM B1": i82975x CE
[ 3566.436083] EDAC MC0: CE page 0x16ebe, offset 0xf00, grain 64, syndrome 0xc1, row 0, channel 1, label "DIMM B1": i82975x CE
[ 3567.436055] EDAC MC0: CE page 0x16cbe, offset 0xb00, grain 64, syndrome 0xc1, row 0, channel 1, label "DIMM B1": i82975x CE
[ 3568.436088] EDAC MC0: CE page 0x16cbe, offset 0xf00, grain 64, syndrome 0xc1, row 0, channel 1, label "DIMM B1": i82975x CE
[ 3569.436086] EDAC MC0: CE page 0x16cbe, offset 0xb80, grain 64, syndrome 0xc1, row 0, channel 1, label "DIMM B1": i82975x CE
[ 3571.436068] EDAC MC0: CE page 0x16cbe, offset 0xb80, grain 64, syndrome 0xc1, row 0, channel 1, label "DIMM B1": i82975x CE
[ 3572.436141] EDAC MC0: CE page 0x16cbe, offset 0xb00, grain 64, syndrome 0xc1, row 0, channel 1, label "DIMM B1": i82975x CE
[ 3573.436065] EDAC MC0: CE page 0x16cbe, offset 0xf00, grain 64, syndrome 0xc1, row 0, channel 1, label "DIMM B1": i82975x CE
[ 3574.440044] EDAC MC0: CE page 0x16cbe, offset 0xb80, grain 64, syndrome 0xc1, row 0, channel 1, label "DIMM B1": i82975x CE
[ 3575.440067] EDAC MC0: CE page 0x16ebe, offset 0xf00, grain 64, syndrome 0xc1, row 0, channel 1, label "DIMM B1": i82975x CE
cecilieaux@CM-Workstation:~$

Looks to me like it recognizes the gizmo. Why the eff doesn it work with it like 3.2.0-29-generic-pae, which I am writing to you from, does.

Cecilieaux

I assume you made the changes here: http://ubuntuforums.org/showpost.php...8&postcount=19

I also assume you re-compiled for the later kernel as outlined here: http://ubuntuforums.org/showpost.php...2&postcount=41

Yes? No?

Quote:

---

Originally Posted by chili555

I assume you made the changes here: http://ubuntuforums.org/showpost.php...8&postcount=19

I also assume you re-compiled for the later kernel as outlined here: http://ubuntuforums.org/showpost.php...2&postcount=41

Yes? No?

---

The answer was No, but I am now connected via the new kernel, so I looked through and fixed what was wrong.

I have two questions left and Iĺl leave you alone with enormous gratitude for teaching me something that is still almost magic to me.

1. I am still confused about common/rtusb_dev_id.c. I had edited it before for the previous kernel (else it wouldn't have worked, I assume). But when I went to check, the device-specific line (in my case {USB_DEVICE(0x0846,0x9012)}, /* Netgear */) was not there. It somehow returns to the original?

2. In future, then, every time a new kernel is installed, I should, BEFORE recompiling

a) check the file
Desktop/Linux/DPO_RT3573_LinuxSTA_V2.5.0.0/os/linux/config.mk to make sure HAS_WPA_SUPPLICANT= is set to y

b) Desktop/Linux/DPO_RT3573_LinuxSTA_V2.5.0.0/check common/rtusb_dev_id.c to make sure that everything is as indicated in http://ubuntuforums.org/showpost.php...8&postcount=19 (msg #19 of this thread)

Then, if all is well I shoud recompile per d here: http://ubuntuforums.org/showpost.php...2&postcount=41 (msg #41 of this thread)

Anyway, that's what I did and it worked. Correct?

If this is correc, I'll put the instructions together in one "cheat sheet" file.

Again, thank you so very much!!!!

Yes chili, thank you very much, you turned our $60 paper weight back in a wifi adapter

Here is my complete "cheat sheet." Attached.

Attachment 224599