lucid wireless disconnection eee RaLink RT2860 (eee 901)

[Viesturs Zariņš]

Using Ubuntu Lucid daily build.
Wireless connects, but is disconnected after several seconds of use, repeated connections fail.
Using wpa2 setup.

The device is EEEPC 901
Lspci:
00:00.0 Host bridge: Intel Corporation Mobile 945GME Express Memory Controller Hub (rev 03)
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GME Express Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03)
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 02)
00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 02)
00:1c.2 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 3 (rev 02)
00:1c.3 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 4 (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 (rev 02)
00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 (rev 02)
00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4 (rev 02)
00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)
00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02)
00:1f.2 IDE interface: Intel Corporation 82801GBM/GHM (ICH7 Family) SATA IDE Controller (rev 02)
00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 02)
01:00.0 Network controller: RaLink RT2860
04:00.0 Ethernet controller: Attansic Technology Corp. Atheros AR8121/AR8113/AR8114 PCI-E Ethernet Controller (rev b0)

DMESG tail:
[ 3154.164186] ===>rt_ioctl_giwscan. 1(1) BSS returned, data->length = 169
[ 3214.164108] ===>rt_ioctl_giwscan. 1(1) BSS returned, data->length = 169
[ 3274.164101] ===>rt_ioctl_giwscan. 1(1) BSS returned, data->length = 169
[ 3334.161097] ===>rt_ioctl_giwscan. 1(1) BSS returned, data->length = 169
[ 3394.165158] ===>rt_ioctl_giwscan. 1(1) BSS returned, data->length = 169
[ 3454.160152] ===>rt_ioctl_giwscan. 1(1) BSS returned, data->length = 169
[ 3514.164643] ===>rt_ioctl_giwscan. 1(1) BSS returned, data->length = 169
[ 3532.976159] ===>rt_ioctl_giwscan. 1(1) BSS returned, data->length = 169
[ 3532.976694] ==>rt_ioctl_siwfreq::SIOCSIWFREQ[cmd=0x8b04] (Channel=2)
[ 3543.004182] ===>rt_ioctl_giwscan. 1(1) BSS returned, data->length = 169
[ 3543.004985] ==>rt_ioctl_siwfreq::SIOCSIWFREQ[cmd=0x8b04] (Channel=2)
[ 3553.029733] ===>rt_ioctl_giwscan. 1(1) BSS returned, data->length = 169
[ 3553.030458] ==>rt_ioctl_siwfreq::SIOCSIWFREQ[cmd=0x8b04] (Channel=2)
[ 3563.048170] ===>rt_ioctl_giwscan. 1(1) BSS returned, data->length = 169
[ 3563.048725] ==>rt_ioctl_siwfreq::SIOCSIWFREQ[cmd=0x8b04] (Channel=2)
[ 3573.065141] ===>rt_ioctl_giwscan. 1(1) BSS returned, data->length = 169
[ 3573.065873] ==>rt_ioctl_siwfreq::SIOCSIWFREQ[cmd=0x8b04] (Channel=2)
[ 3583.089126] ===>rt_ioctl_giwscan. 1(1) BSS returned, data->length = 169
[ 3583.089692] ==>rt_ioctl_siwfreq::SIOCSIWFREQ[cmd=0x8b04] (Channel=2)
[ 3593.113124] ===>rt_ioctl_giwscan. 1(1) BSS returned, data->length = 169

[Wolfgang Kufner (wolfgangkufner)]

This could be bug 496093 if and only if you are using WPA/WPA2 mixed mode (See https://bugs.launchpad.net/linux/+bug/496093/comments/21). If you are using WPA2 only mode than it is not bug 496093.

[Viesturs Zariņš (viesturs-zarins)]

Tried with another WPA2 only network, works fine there.

[Wolfgang Kufner (wolfgangkufner)]

Is the WLAN where the bug does happen WPA/WPA2 mixed mode or WPA2 only?

[Viesturs Zariņš (viesturs-zarins)]

Don't know, will check when I get home.

[Viesturs Zariņš (viesturs-zarins)]

Yap, had mixed mode at home, setting router to WPA2 only fixes the problem.

[Ulrik Mikaelsson (rawler)]

Affects me too, and changing to WPA2 only works.