rt2500 module keeps losing connection with AP.

[Shkodran Gerguri]

After last kernel update, the rt2500 wireless card and its module returned to its erroneous state which was present in a fresh install of feisty.

I use the card to connect to a home AP which "distributes" access to internet. After the last update, the internet often drops dead, even if the AP is running fine. This is purely the issue of rt2500 module, since I had two machines connected to the AP and browsing the web happily, with the desktop sometimes suddenly dropping dead, even though the iwconfig command states that it is connected with 27 % signal strength.

As I wrote, everything was ok till the last kernel update, so the rt2500 module probably ended in an erroneous state after it.

Output of "uname -a":
Linux Tomahna 2.6.20-16-generic #2 SMP Sun Sep 23 19:50:39 UTC 2007 i686 GNU/Linux

[Brian Murray (brian-murray)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description doesn't yet have enough information.
Please include as attachments the following additional information, if you have not already done so (please pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command 'uname -a' in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command 'dmesg > dmesg.log' and attach the resulting file 'dmesg.log' to this bug report.
3. Please run the command 'sudo lspci -vvnn > lspci-vvnn.log' and attach the resulting file 'lspci-vvnn.log' to this bug report.
For your reference, the full description of procedures for kernel-related bug reports is available at https://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks in advance!

[Shkodran Gerguri (s-gerguri)]

My apologies for filing in an incomplete report. It was my first report whatsoever and I should have read the bug reporting policies prior to posting it.

[Shkodran Gerguri (s-gerguri)]

After a clean install and update of feisty, the module stopped exhibiting the behavior. Since I haven't experienced the issue again yet, I'm changing the status to Invalid.

[Shkodran Gerguri (s-gerguri)]

Switched status back to "confirmed", as the card exhibited the behavior again.

[Steven Brown (steven-w-j-brown)]

I am getting this behaviour, as well, in updated Gutsy.

$ uname -a
Linux semper 2.6.22-14-generic #1 SMP Wed Oct 10 06:00:47 GMT 2007 i686 GNU/Linux

output of dmesg and lspci attached.

[TomLottermann (tomlottermann)]

I am having this problem as well, but in new installed Gutsy Server (Final)

$ uname -a
Linux zion 2.6.22-14-server #1 SMP Sun Oct 14 23:34:23 GMT 2007 i686 GNU/Linux

dmesg and lspci attached.

[TomLottermann (tomlottermann)]

Also appeared before -> Confirmed!

[TomLottermann (tomlottermann)]

Sorry for posting so many different things, but I just found out that it also happens using my cable lan card... So it's no rt2x00 issue, but a MORE SEVERE network problem. (at least on my mashine)

[TomLottermann (tomlottermann)]

Please delete my last post! I'm extremely sorry... I just noticed a really stupid mistake... My last post is completely WRONG! I'm so sorry...

[Juergen Scholz (juergen.scholz)]

Hello!

I can confirm this behaviour. The wireless connection on an rt2500 device is losing the connection after about 20 minutes and will not reconnect to the wireless access point until the machine is rebooted.

$lspci
00:0c.0 Network controller: RaLink RT2500 802.11g Cardbus/mini-PCI (rev 01)

$lsmod
rt2500pci 19072 0
rt2x00pci 11520 1 rt2500pci
rt2x00lib 19584 2 rt2500pci,rt2x00pci

Is any further information needed?

goddbye!

[Javier Jardón (jjardon)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 134660, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

[Launchpad Janitor (janitor)]

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.