rt2x00 kernel support

Bug #110590 reported by Matevž Jekovec
8
Affects Status Importance Assigned to Milestone
linux-source-2.6.20 (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Binary package hint: linux-source

Support for rt2x00 driver is currently a must. Bug 37120 describes the currently Ubuntu provided rt2500 driver not working with networkmanager (wpasupplicant not supported at all) and therefore doesn't work for any users who want to have a frontend for their 2500 network card.

rt2x00 supports any wpasupplicant encryption using wext for more than two years now and IMO is stable enough for inclusion into the main Ubuntu kernel and should superseed the current legacy rt2500, rt2600, rt2650 and rt2700usb drivers.

The problem I see with the latest rt2x00 source and Ubuntu kernel is that the kernel headers are already patched with the legacy ieee80211 drivers and you can't compile rt2x00 on Ubuntu out of the box anymore. It does compile fine with vanilla kernel.

Homepage:
http://rt2x00.serialmonkey.com/

Revision history for this message
Ben Collins (ben-collins) wrote :

That's all fine and dandy, and to be honest, I would have switched us over a year ago to rt2x00, except that the two machines I have with rt2500 cards in them do not work with rt2x00, only with the rt2500 legacy driver.

If they fix that, then I'll feel comfortable making the move.

In addition, reality is, we already have the modules:

echo blacklist rt2500 | sudo tee /etc/modprobe.d/rt2500-blacklist
echo rt2500pci | sudo tee /etc/modules

After rebooting, you should be using the rt2x00 version of the driver, although I cannot confirm it works.

Changed in linux-source-2.6.20:
assignee: nobody → ubuntu-kernel-team
importance: Undecided → Low
status: Unconfirmed → Rejected
Revision history for this message
Matevž Jekovec (matevz-jekovec) wrote :

You are correct - rt2500 should be more stable than rt2x00 as they were officially developed by the chipset manufacterer as well. But currently, rt2500 brokes the wireless net on *all* the machines out there running feisty and try to use networkmanager for the network (there is no way to connect to any encrypted network because it doesn't support wpasupplicant and the new networkmanager uses wpasupplicant only AFAIK). Is this really what we want?

Thanks for the recipe - I'll test rt2x00 with networkmanager and report back.

Revision history for this message
Matevž Jekovec (matevz-jekovec) wrote :

I tested rt2x00 and I was unable to connect to any network let it be using iwconfig or wpasupplicant, encrypted or non-encrypted. Even scan didn't work, so I can only assume that the current rt2x00 driver is really broken and not usable. However, wpasupplicant on my card worked fine half a year ago fine with 2.6.15 kernel on Edgy. I could say that the whole thing regressed a bit. So... we should probably wait for rt2x00 to stabilize. Until then, the GUI and wpasupplicant for rt cards is useless as we use the legacy driver.

Revision history for this message
wodz (wodz) wrote :

rt2x00 drivers shipped with feisty does not work for me either but I tried rt2x00 from git repository (wireless-dev kernel tree) and this works correctly. I was able to connect to my WPA protected AP. So it is a matter of time to see this drivers in mainline kernel.

Revision history for this message
Sniper Fox (sniperfox-gvc) wrote :

This bug may be a dupe of bug #78037

Revision history for this message
SkyScrap (andreas-ebbert) wrote :

@wodz

Could you please write some instructions how to do that? I think there are many, many people currently out there, who would like to use RT based cards and sticks with WPA, and the rt2x00 drivers are the only solution to that.

Revision history for this message
wodz (wodz) wrote :

Three first steps of this instruction was sufficient for me:
http://rt2x00.serialmonkey.com/wiki/index.php?title=Rt2x00_GIT_instructions

Than You have to compile obtained kernel sources. But beware that you will lose all patches applied in standard ubuntu kernel.

Revision history for this message
Peter Makowski (petermakowski) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote : Kernel team bugs

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.