Any word from the vendors on this bug? AFAICT Ralink are the ones who hired the staff engineers to work on Linux drivers, so maybe they should work on this.
What is the general process for getting new hardware supported? Unless Ralink/Linksys release open documentation on their chipsets, it is not realistic to expect that the community at large will implement a driver for this. We need the support of the companies peddling these chips. Is there any way to get Canonical to engage Linksys or Ralink asking them to help us? Also, the rt2x00 project seems to support rt2870 chips now with the rt2800usb driver. I'm not sure of the extent of modification to that driver that would be needed to support this card, if it's even a true rt2870; but it seems like any company or individual who possesses the hardware documentation and a kernel hacker would be able to get this going. That could be Canonical if they pulled the right strings. ** Description changed: I have a "Linksys By Cisco" brand WUSB600N v2. Its USB ID is 1737:0079 Rev. 0101 When the USB adapter is hotplugged (or even coldplugged) the USB bus recognizes that "something" has been plugged in, but no additional modules are loaded at all. The output of `lsmod' before and after hot insertion is identical. So no modules claim they support this card. The original of this model, WUSB600N, is supposedly an rt2870-compatible chip. I am not sure whether "v2" is an entirely different chipset, or whether it's just rt2870 with a quirk. I tried manually adding the USB ID to the rt2870sta source code and rebuilding the driver, but doing so gave me a kernel oops within that module. So apparently the fix to get it supported isn't as simple as adding that one line. But at least rt2870 seems to be partially aware of the chip -- right after the oops I ran `ifconfig' and the interface was up and I could get its MAC address (and it was correct). But since the module oopsed, I was unable to send any commands to the wireless interface via NetworkManager, iwconfig, etc. I'm not sure how fervently upstream tries to support manufacturers who buy the rt2870 chipset and put it in their own product. If Ralink is nice enough to patch their drivers for the quirks of other vendors' products (such as Linksys) then it's just a matter of waiting. But if the action is in Linksys' court, I'm not sure they would help us at all. I think we will need a volunteer kernel hacker to take a look at it and see if the fix is reasonably easy. Since these wireless USB adapters are relatively inexpensive, I am willing to donate one to a single competent individual who believes he/she can get this working well. All I ask in return is that you get it working, and return it to me when you are done with it (shipping at my expense)... unless of course you break it, which is understandable. Fragile little device. - NB: I've tested this thoroughly on both Jaunty and Karmic. The only - noticeable difference is that the rt2870sta driver seems to be better - integrated into the mainline kernel in Karmic, but the new set of rt2* - drivers still fail to automatically probe this card. I applied my patch - to the rt2870sta driver downloaded from Ralink's website and built that - on Jaunty, but did not test my naive patch against the Karmic kernel - sources, as I expected the same result. + NB: I've tested this thoroughly on both Jaunty and Karmic. In Karmic, we + have the rt2800usb driver as part of the open source rt2x00 project (now + entering mainline); but the new set of rt2* drivers still fail to + automatically probe this card. I applied my patch to the rt2870sta + driver downloaded from Ralink's website and built that on Jaunty, but + did not test my naive patch against the Karmic kernel sources, as I + expected the same result. + + UPDATE: I think the future of Ralink chipsets on Linux is the rt2x00 + project, as they are moving at a faster pace than rt2870sta and they are + integrated into mainline. Their wifi drivers are first class citizens, + with a behavior just like you'd expect from, say, iwlwifi: + NetworkManager can use them; WPA2 works without a custom supplicant; no + proprietary daemons; etc. Not sure how much code rt2x00 shares with + rt2870sta (if any), but hopefully this project will pick up support for + 1737:0079 soon. -- Linksys By Cisco WUSB600N v2 Doesn't Work https://bugs.launchpad.net/bugs/408165 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
