Comment 9 for bug 762987
Revision history for this message
| Wolfgang Kufner (wolfgangkufner) wrote | #9 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Ok, it seems clear where we must look:
phy0 -> rt2x00lib_
support detected chipset.
NetworkManager[
Let's look at what you have:
md5sum /lib/firmware/
Bug 782752 seems to be about the same problem and has identified a
working firmware. But while it would be nice if that worked for you it
might be better to look whether the newest firmware already in ubuntu
works. We want to fix this for everyone out of the box after all.
https:/
currently newest:
https:/
the changelog says this is up to date till commit:
http://
This means it includes the shiny new firmware posted to the rt2x00 mailing list:
http://
which subsequently was commited here:
http://
Maybe you could just try by extracting rt2870.bin from here:
https:/
and copy it in /lib/firmware (rename the old one to e.g. rt2870.bin.disable)
About why there are so many drivers:
Basically there are two sets of drivers, the "legacy" drivers
developed and open sourced by Ralink and those (mainly - for new
devices rt2800usb and rt2800pci) developed by the rt2x00 project
(looking a lot at the legacy sources to make up for missing specs and
getting answers from Ralink engineers and also increasingly getting
patches sent by Ralink engineers). The Ralink drivers are monoliths
(look at the size) and do not fit the linux wireless infrastructure
(mac80211 stack). For that reason they will never make it into the
kernel proper. They will stay in staging until they are deleted. There
aren't any big differences between what is in staging and what is
available directly from the Ralink website, architecturally speaking.
Resources that may or may not be interesting:
http://