rt61pci fails to scan for wireless networks

Live forum: http://rt2x00.serialmonkey.com/viewtopic.php?t=4801

tr333

18-05-2008 10:58:48

I'm currently testing the rt61pci driver from linuxwireless.org in the daily compat-wireless-2.6.tar.bz2 source archive. When I run "sudo iwlist scan", it repeatedly fails to find any wireless networks. I know the chipset is working, since I was able to find the AP with the ralink drivers (rt61) from their website. I looked at the dmesg output and it's giving me the line "[ 59.806358] ADDRCONF(NETDEV_UP) wlan0 link is not ready".

I have attached the outputs of dmesg, lspci -vvnn, and the regdump.txt.sh script posted on this forum.

EDIT I forgot to mention that i'm running this on Mythbuntu 8.04 with the 2.6.24 kernel.

bilek

07-08-2008 08:58:12

Hi

I have the same problem with the wireless in my notebook MSI S271X.
This is my cut out from my lspci
0509.0 Network controller RaLink RT2561/RT61 rev B 802.11g

So I investigated that the legacy driver rt61.ko is working! -) The point is that
this driver seems to be somewhat buggy because from time to time the network
freeze (stop working) and I have to restart it. (ifcofnig wlan0 down;rmmod rt61;
ifconfig wlan0 up;...), I tried to analyse the problem by running the rt61.ko driver
in debug mode, but the log are too far from my understanding.
=> If there is someone who would to spend time to help me analyse the problem
I can contribute as tester with programming knowledges.

The reason why I replied to this post is that I would to switch to the new rt6pci
driver because the new driver support some scanning function what NetworkManager
use for automatic search for APs.

Till now all my attempts to use it (the new driver) were not successful.
I suspect the driver that it do not detect the device or some part of the device (RT2561/RT61).

This is cut out from my log file

[quote39p94u4n]
Aug 7 103644 tadytudy kernel ACPI PCI Interrupt 00000509.0[A] -> GSI 22 (level, low) -> IRQ 22
Aug 7 103644 tadytudy kernel Registered led device rt61pci-phy2radio
Aug 7 103644 tadytudy kernel Registered led device rt61pci-phy2assoc
Aug 7 103644 tadytudy NetworkManager <info> wlan0 Device is fully-supported using driver 'rt61pci'.
Aug 7 103644 tadytudy NetworkManager <info> wlan0 driver supports SSID scans (scan_capa 0x01).
Aug 7 103644 tadytudy NetworkManager <info> Found new wireless (802.11) device 'wlan0'.
Aug 7 103644 tadytudy NetworkManager <info> (wlan0) exported as /org/freedesktop/Hal/devices/net_00_19_db_09_ce_79_0
Aug 7 103648 tadytudy NetworkManager <info> (wlan0) device state change 1 -> 2
Aug 7 103648 tadytudy NetworkManager <info> (wlan0) bringing up device.
Aug 7 103648 tadytudy kernel ADDRCONF(NETDEV_UP) wlan0 link is not ready
Aug 7 103648 tadytudy NetworkManager <info> (wlan0) preparing device.
Aug 7 103648 tadytudy NetworkManager <info> (wlan0) deactivating device.
Aug 7 103648 tadytudy NetworkManager <info> (wlan0) supplicant interface state change 1 -> 2.
[/quote39p94u4n]

If you ignore the NetworkManager logs than you can see that some part of the code of rt61pci.ko driver detected something.

[quote39p94u4n]
Aug 7 103644 tadytudy kernel Registered led device rt61pci-phy2radio
Aug 7 103644 tadytudy kernel Registered led device rt61pci-phy2assoc
[/quote39p94u4n]

But immediately when the NetworkManager or simply "ifconfig wlan0 up" tries to activate the device (wlan0) and assign address
it fails with following message to log file
[quote39p94u4n]
Aug 7 103648 tadytudy kernel ADDRCONF(NETDEV_UP) wlan0 link is not ready
[/quote39p94u4n]

Typically this kind of message is probably not produced by driver (rt61pci.ko) but some kernel network abstraction layer,
because I saw this message also in other cases e.g. when I unplugged ethernet cable from my PC.

Also I found one suspected line in your and also my lsmod output.
It is the line with rt61pci what looks like this

[quote39p94u4n]
Module Size Used by
rt61pci 20736 0
...
...
[/quote39p94u4n]

The reason why I thing it is not good is the number "0" in the column "Used by". Usually this column should at least number "1" if the device is used.

That is all I investigated and I would be very happy if I can find someone who can help me with this problem and of course I can help someone.

AdamBaker

07-08-2008 22:22:46

tr333 How far is your laptop from the AP. Could you be suffering from the reduced range that has been reported for a different device family in another post? Are you able to move closer to the AP nad try again?

bilek Have you tried to perform a scan with the device before trying to connect - There are lots of things that need to be set correctly for connect to work that aren't needed for scan and many of them can result in the link is not ready message A use count of 0 in lsmod is normal. The legacy driver is widely reported to be a bit unreliable in some circumstances but the code is too tangled to try to fix hence the desire to replace it.