http://ndiswrapper.sourceforge.net/wiki/api.php?action=feedcontributions&feedformat=atom&user=WkirkpaNDISWrapper - User contributions [en]2026-05-02T19:58:22ZUser contributionsMediaWiki 1.26.0http://ndiswrapper.sourceforge.net/wiki/index.php?title=Linksys_WUSB600N&diff=798Linksys WUSB600N2009-12-14T08:58:00Z<p>Wkirkpa: /* Info */</p>
<hr />
<div>==Linksys WUSB600N Version 2==<br />
<br />
* Chipset: Ralink RT3572<br />
* usbid: 1737:0079<br />
* driver: Ralinktech.com driver file: USB (RT2870 /RT2770 /RT307X /RT2070 /RT3572) 09/25/09 XP 32/64 1.4.7.0<br />
<br />
==Info==<br />
Driver did not work. Bad pointer de-reference issues kernal OOPS. Kernel version 2.6.31, compiled<br />
from source. ndiswrapper version 1.55 downloaded from Sourceforge download page, compiled without<br />
issue. Device was "recognized", wlan0 created, but device otherwise unable to accept configuration commands.<br />
<br />
Update:<br />
<br />
Device shows signs of life under Unbuntu 9.1 (ndiswrapper 1.55/kernel 2.6.31-15). Device will connect and<br />
transfer data, in unsecured mode, "out of the box". Best to boot with<br />
device connected, and leave it there, else interface may hang. Haven't, yet, been able to establish a<br />
secured connection, but did notice that fiddling with thing may also cause the interface to hang. Once<br />
hung, a reboot is required to restore operation.<br />
<br />
Ok, over the last week I've discovered the device is simply flaky. At times it will connect to my <br />
WEP2 access point, other times it won't (but if I un-secure the access point, it will). No other<br />
configuration changes were made in the meantime. Also, the device always dies after a couple of<br />
minutes/hours, having it been used since re-boot, or not. ndiswrapper hangs and only a reboot<br />
will resurrect it.<br />
<br />
I'm sidelining this for now, going with a better supported, native, device. <br />
<br />
[[Category:Linksys]]<br />
[[Category:USB]]<br />
[[Category:WORKS]]</div>Wkirkpahttp://ndiswrapper.sourceforge.net/wiki/index.php?title=Linksys_WUSB600N&diff=796Linksys WUSB600N2009-12-06T05:29:57Z<p>Wkirkpa: /* Info */</p>
<hr />
<div>==Linksys WUSB600N Version 2==<br />
<br />
* Chipset: Ralink RT3572<br />
* usbid: 1737:0079<br />
* driver: Ralinktech.com driver file: USB (RT2870 /RT2770 /RT307X /RT2070 /RT3572) 09/25/09 XP 32/64 1.4.7.0<br />
<br />
==Info==<br />
Driver did not work. Bad pointer de-reference issues kernal OOPS. Kernel version 2.6.31, compiled<br />
from source. ndiswrapper version 1.55 downloaded from Sourceforge download page, compiled without<br />
issue. Device was "recognized", wlan0 created, but device otherwise unable to accept configuration commands.<br />
<br />
Update:<br />
<br />
Device shows signs of life under Unbuntu 9.1 (ndiswrapper 1.55/kernel 2.6.31-15). Device will connect and<br />
transfer data, in unsecured mode, "out of the box". Best to boot with<br />
device connected, and leave it there, else interface may hang. Haven't, yet, been able to establish a<br />
secured connection, but did notice that fiddling with thing may also cause the interface to hang. Once<br />
hung, a reboot is required to restore operation.<br />
<br />
[[Category:Linksys]]<br />
[[Category:USB]]<br />
[[Category:WORKS]]</div>Wkirkpahttp://ndiswrapper.sourceforge.net/wiki/index.php?title=Linksys_WUSB600N&diff=795Linksys WUSB600N2009-12-06T05:21:52Z<p>Wkirkpa: /* Info */</p>
<hr />
<div>==Linksys WUSB600N Version 2==<br />
<br />
* Chipset: Ralink RT3572<br />
* usbid: 1737:0079<br />
* driver: Ralinktech.com driver file: USB (RT2870 /RT2770 /RT307X /RT2070 /RT3572) 09/25/09 XP 32/64 1.4.7.0<br />
<br />
==Info==<br />
Driver did not work. Bad pointer de-reference issues kernal OOPS. Kernel version 2.6.31, compiled<br />
from source. ndiswrapper version 1.55 downloaded from Sourceforge download page, compiled without<br />
issue. Device was "recognized", wlan0 created, but device otherwise unable to accept configuration commands.<br />
<br />
Update:<br />
<br />
Device shows signs of life under Unbuntu 9.1 (ndiswrapper 1.55/kernel 2.6.31-15). Device will connect and<br />
transfer data, in unsecured mode, "out of the box". Best to boot with<br />
device connected, and leave it there, else interface may hang. Haven't, yet, been able to establish a<br />
secured connection, but did notice that fiddling with thing may also cause the interface to hang. Once<br />
hung, a reboot is required to restore operation.<br />
<br />
[[Category:Linksys]]<br />
[[Category:USB]]<br />
[[Category:WORKING]]</div>Wkirkpa