Wireless dies and requires total shutdown rt2x00 usb

Sorry should have said I'm using Gutsy Gibbon Tribe 4

I'm now using the legacy RT73 driver from Serialmonkey as even with the CVS version of rt73usb + rt2x00 there are problems. So this isn't so much a bug as an alpha/beta module in the Gutsy kernel.

Two other bugs related to the issue (rt2x00 failure) have been reported. See bug #153718 and #154651 . Same symptoms which appear to be originated in a lost of synchronization ... Hard reboot is then required to recover the connection.

This bug is mentioned on http://rt2x00.serialmonkey.com/phpBB2/viewtopic.php?t=4347 , where someone also says "Are you using rt2x00 on a 2.6.22 kernel? This would mean you're running an old version, rt2x00 is moving a lot."

Seconding herrib, there are two duplicates.

Apparently it's been fixed upstream - http://rt2x00.serialmonkey.com/phpBB2/viewtopic.php?t=4364 ; http://comments.gmane.org/gmane.linux.kernel.wireless.general/7275 .

Oh and there may be no need to reboot - I'm using network manager, and I prod it by asking it to "connect to another network", entering the same network id with different parameters (WEP instead of WPA), then doing it again this time with the real network parameters.

I seem to be having this issue

For the benefit of an incompetent, could someone please break down how I would implement the patch mentioned above

I would use https://wiki.ubuntu.com/KernelGitGuide to get a kernel checkout and do some cherry-picking of the patch mentioned on the linux-wireless list. Requires patience, disk space, and some ability to understand the fix, its requirements, and the conflicts they will introduce. So, not for everyone!

thx - bit beyond my capabilities by the looks of it. Looks like its back to windows on the laptop which is a shame.

Same problem here. I managed to get it working with the CVS legacy version of the rt61 module.
It broke Network Manager though...

same problem here!
and like bazsal this sort of fix is way beyond my capabilities.

if anyone has an easier idiot-proof fix, I'd really appreciate it. I'm afraid of trying ndiswrapper and then something go wrong and I never be able to use my wi-fi again (even though I found a pretty easy to follow tutorial). besides, I don't really know where to find the windows driver, so there.

I use the gutsy stable release on a CCE (brazilian brand that actually uses hardware from everywhere else) laptop. the wi-fi card doesn't even show up when I try lspci, but I found that the driver is the rt73usb in the hardware information (in system, preferences). and then I saw that rt73usb is listed when I do lsmod. so I guess my problem is the same as yours.

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in linux-source-2.6.22.

Reviewing this bug report and its comments it seems that multiple people are experiencing this problem. Subsequently, I am confirming this bug report. For future reference you can manage the status of bug reports by clicking on the current status in the yellow line and then choosing a new status in the drop down box. You can learn more about bug statuses at http://wiki.ubuntu.com/Bugs/Status .

I am seeing this problem as well. Mostly just at work, I never see this happen at home on my wireless network where I am connected for entire weekends without issue.

I can confirm that I have exactly the same problem with a rt73 based (sweex LW053 usb) device. Connection drops quite quickly. its a shame because other than that it worked out of the box with both wep and wpa

Kernel version: 2.6.22-14-generic

Just for info - unplugging the usb stick and replugging and restarting networking works for me (/etc/init.d/networking restart).

A simple(ish) work around is to follow the guide on http://ubuntuforums.org/showthread.php?t=400236 to install the latest serialmonkey drivers (rt73 instead of the packaged rt73usb). Worked first time for me.

I had the same problem with gutsy.
Now I replaced the gutsy kernel with the hardy kernel (I saw in an other bug report that there is a fix released) and now it works perfectly. I don't know whether encryption works.

Thanks a lot!

I'm having the same problem with Ubuntu Serve 8.04 (Hardy Heron) kernel 2.6.24-16-server
My wireless usb is a DWL-G122.
i don't know if it might happen because i'm using with a very old notebook with 64mb ram.

The last hardy-proposed update breaks EVERYTHING. And I had the hardy-backport-modules thingy installed.

I mean, it starts dying all over again. I had a hard time downgrading everything and all, but now I'm good again. Just thought I'd let you know :)

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

The nature of this bug has changed, and a better bug to follow is #134660. The driver no longer locks up the computer, it just doesn't really work very well, even in Intrepid. The best driver for the RT73 chipset remains the legacy driver from SerialMonkey - in my 2 year experience. For details of how to install see http://ubuntuforums.org/showthread.php?t=400236
The driver is unsupported by Network Manager but there are other options, the best of which seems to be WICD - version 1.4.2 works pretty well for me.

Incidentally I reported this bug Jonno==_oOMOo_

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

With 8.10, it was working with the 2.6.24 kernel but problem came back again with the 2.6.27-x (now using the 2.6.27-7). Is there a workaround. I have a Belkin based on Ralink (rt73)

I've blacklisted rt2500usb (/etc/modprobe/blacklist for those who wonders) and it's working without any flaw.

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.

For anyone still experiencing issues, you may want to also try installing the linux-backports-modules-intrepid package to see if it helps. If the issue still persists, it would be great if you could then test the latest pre-release of Jaunty - http://cdimage.ubuntu.com/releases/jaunty/alpha-2/ . Please let us know your results. Thanks.

Leann. I'm on Intrepid and still having this problem (with rt73usb).

I was doing fine on Hardy with the backports-module package. When I tried this backports module on Intrepid it kinda made it all worse and then after an update the computer wouldn't even turn on. That was a while ago, though. Did something change in the backports package?

Leann, just installed linux-backports-modules and wicd is now at 100% instead of 78%. But all other networks around mine are also with a 100% signal, so I don't know if that means anything. So far so good. I'll let you know if I it dies. Or if it lives on :)

alright. I can confirm that apparently the backports package fixes rt73usb on Intrepid :) I've been doing some really heavy websurfing and downloading and it's all going pretty smooth, without dying. so, yay!

Thanks for testing and the feedback. Marking this Fix Released against linux-backports-modules. Thanks.