System freeze (caps lock blinks) using wireless (rt61)

[bgc]

The system completely freezes with any wireless activity (particularly downloads, but also with normal surfing). This issue has been reported before for other versions of Ubuntu. I'm using Hardy alpha 4 (including updates until today (14 Feb)), and use a Belkin wireless PCMCIA card (rt61 chipset).

I have had many problems with this card with Feisty and Gutsy. Got it working eventually on Feisty, but never managed on Gutsy (would not even recognise the network, etc.), even after numerous workaround attempts. Hardy recognises the card and network, connects fine, but freezes after about 2-5mins, with a blinking caps lock. The only way out then is a hard reboot.

Thanks!

[Philipp Meier (meier-philipp)]

On my Computer
(Ubuntu 8.04, Kernel 2-6.24-11,WLAN Cardbus Card: Cardbus Texas Instruments PCI 1410 rev 02, Ralink RT2561/RT61 rev B 802.11g)

The Freeze just happens with the card. It may last for a few minutes (by heavy load) or an hour, just browsing the web.
It seems that it is related to data transfered through the card. (Not proffed)
Without the card the computer works without freeze (Longest uptime so far 2 Days, but with normal shutdown).

System Freeze approx 11:22:39 (locale time)

[Philipp Meier (meier-philipp)]

As this bug is related to rt61pci, rt2x00pci, rt2x00lib, mac80211

[Magnes (magnesus2)]

8.04 with rt61, the same problem here. System freezes during heavy transfer through WiFi - caps lock and scroll lock leds are blinking.

[NoWhereMan (e.vacchi) (uncommonnonsense)]

please install the backport modules package

On Sun, May 4, 2008 at 9:56 AM, Magnes <email address hidden> wrote:
> *** This bug is a duplicate of bug 134660 ***
> https://bugs.launchpad.net/bugs/134660
>
> 8.04 with rt61, the same problem here. System freezes during heavy
> transfer through WiFi - caps lock and scroll lock leds are blinking.
>
> --
> System freeze (caps lock blinks) using wireless (rt61)
> https://bugs.launchpad.net/bugs/191827
> You received this bug notification because you are a direct subscriber
> of the bug (via bug 134660).
>