If you are trying to get a device working with ndiswrapper, please help ndiswrapper project wiki by contributing your findings. See HowToContribute
Difference between revisions of "Linksys WUSB600N"
(→Info) |
(→Info) |
||
| Line 17: | Line 17: | ||
secured connection, but did notice that fiddling with thing may also cause the interface to hang. Once | secured connection, but did notice that fiddling with thing may also cause the interface to hang. Once | ||
hung, a reboot is required to restore operation. | hung, a reboot is required to restore operation. | ||
| + | |||
| + | Ok, over the last week I've discovered the device is simply flaky. At times it will connect to my | ||
| + | WEP2 access point, other times it won't (but if I un-secure the access point, it will). No other | ||
| + | configuration changes were made in the meantime. Also, the device always dies after a couple of | ||
| + | minutes/hours, having it been used since re-boot, or not. ndiswrapper hangs and only a reboot | ||
| + | will resurrect it. | ||
| + | |||
| + | I'm sidelining this for now, going with a better supported, native, device. | ||
[[Category:Linksys]] | [[Category:Linksys]] | ||
[[Category:USB]] | [[Category:USB]] | ||
[[Category:WORKS]] | [[Category:WORKS]] | ||
Revision as of 08:58, 14 December 2009
Linksys WUSB600N Version 2
- Chipset: Ralink RT3572
- usbid: 1737:0079
- driver: Ralinktech.com driver file: USB (RT2870 /RT2770 /RT307X /RT2070 /RT3572) 09/25/09 XP 32/64 1.4.7.0
Info
Driver did not work. Bad pointer de-reference issues kernal OOPS. Kernel version 2.6.31, compiled from source. ndiswrapper version 1.55 downloaded from Sourceforge download page, compiled without issue. Device was "recognized", wlan0 created, but device otherwise unable to accept configuration commands.
Update:
Device shows signs of life under Unbuntu 9.1 (ndiswrapper 1.55/kernel 2.6.31-15). Device will connect and transfer data, in unsecured mode, "out of the box". Best to boot with device connected, and leave it there, else interface may hang. Haven't, yet, been able to establish a secured connection, but did notice that fiddling with thing may also cause the interface to hang. Once hung, a reboot is required to restore operation.
Ok, over the last week I've discovered the device is simply flaky. At times it will connect to my WEP2 access point, other times it won't (but if I un-secure the access point, it will). No other configuration changes were made in the meantime. Also, the device always dies after a couple of minutes/hours, having it been used since re-boot, or not. ndiswrapper hangs and only a reboot will resurrect it.
I'm sidelining this for now, going with a better supported, native, device.
