Re: wireless LAN problems with recent kernels
2008/8/1 Ansgar Burchardt <ansgar@2008.43-1.org>:
> Hi,
>
> I'm using a RaLink RT2500 (PCI) wireless NIC. It works without problems
> with a 2.6.20.1 kernel and the rt2500 drivers.
>
> I did try to update to the Debian 2.6.25 kernel, but there the WLAN
> connection makes problems: Sometimes the connection just drops.
> dmesg shows this message:
>
> wlan0: No ProbeResp from current AP 00:13:49:d7:ab:7c
> - assume out of range
>
> The connection is not reestablished automatically, only when I run e.g.
> `iwconfig wlan0 essid MyESSID'. This reconnection also fails sometimes
> with the following message showing up in dmesg:
>
> wlan0: authentication with AP 00:13:49:d7:ab:7c timed out
>
> I admit having sometimes connection problems running the older kernel as
> well, but the network works again after a few moments (and without any
> manual intervention). The link quality given by iwconfig is around
> 50/100, though it sometimes goes down to 30. Anyway the situation is
> much worse with the newer kernel version.
>
> A forum post [1] suggested increasing IEEE80211_MONITORING_INTERVAL in the
> kernel sources, but this didn't help much: The messages do no longer
> appear, but the connection is still flaky.
>
> Regards,
> Ansgar
>
> [1] http://rt2x00.serialmonkey.com/phpBB/viewtopic.php?f=5&t=2081&p=29255
>
> --
I'm not sure if you mean the rt2500 drivers as in the debian
packages. Also I have a rt73 so what follows may not apply.
I think the rt* series have been included in the kernel as of 2.6.24.
Prior to 2.6.24 I used the enhanced legacy drivers from serialmonkey
and have gone back to them in preference to the in-kernel package
modules as they performed much better, between 2 and 8 times the
throughput. You will need the linux-headers package to build them and
to rmmod the in-kernel modules before modprobe 'ing the legacy driver.
The legacy module name in my case is rt73, the kernel ones are rt73pci
or rt73usb.
--
rob
http://www.worldcommunitygrid.org/team/viewTeamInfo.do?teamId=82BS4ZCMFR1
Reply to: