I've just compiled kernel 184.108.40.206 and compiled the rt61pci driver as a module. The module is loaded automatically, and the interface appears as wlan0. However, I can't get it to work. I believe this is caused by the following error I constantly see appearing in dmesg
[code2yp19hga]phy0 -> rt2x00queue_write_tx_frame: Error - Arrived at non-free entry in the non-full queue 0.
Please file bug report to http://rt2x00.serialmonkey.com.[/code2yp19hga]
Is this a known bug, and already fixed in higher kernel versions? I looked at the changelog, but could not find such a fix.
If it's a true bug, what information would I need to supply so this can be fixed?
Some information already
lspci | grep RT reports
[code2yp19hga]01:08.0 Network controller: RaLink RT2561/RT61 802.11g PCI[/code2yp19hga]
The card is an Asus PCI-G31. It's installed in an old x86 Pentium III 1GHz.
lsmod | grep rt61 reports
[code2yp19hga]rt61pci 14244 0
crc_itu_t 928 1 rt61pci
rt2x00pci 2680 1 rt61pci
rt2x00lib 16580 2 rt61pci,rt2x00pci
eeprom_93cx6 832 1 rt61pci[/code2yp19hga]
Firmware is located in /lib/firmware
With kind regards,
I've now upgraded to kernel 3.0.1 (latest stable at the moment). I still can't get the card to work, but the error is different.
While booting, the machine does a DHCP request for wlan0 (the rt61pci interface) to the DHCP server. It does not get an answer, because the card does not connect to my accesspoint. When I look at dmesg, I see the following error occurring frequently
[codeqmqnvhul]phy0 -> rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 0.[/codeqmqnvhul]
[codeqmqnvhul]wlan0 Link encap:Ethernet HWaddr bc:ae:c5:c6:df:45
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)[/codeqmqnvhul]
[codeqmqnvhul]wlan0 IEEE 802.11bg ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
lsmod | grep rt61pci
[codeqmqnvhul]rt61pci 14352 0
crc_itu_t 920 1 rt61pci
rt2x00pci 2756 1 rt61pci
rt2x00lib 18288 2 rt61pci,rt2x00pci
eeprom_93cx6 824 1 rt61pci[/codeqmqnvhul]
My question still is is the a bug? And if so what can I do to help?
I've cloned the latest rt2x00 git sources, and copied the directory 'drivers/net/wireless/rt2x00/' to my own kernel tree. Recompiling went ok, installing went ok, but the problem remains...
I've now even gone so far as to install the card temporarily in a Windows 7 machine. The card functions I can connect to an accesspoint and ping Google...
Is there no one that can give me any tips on how to proceed to tackle this?
As an alternative maybe someone can recommend another wireless PCI card that supports master mode and is fully functional in Linux?
I'm in the same boat, with same messages, on the 2.6.38 kernel.
I had been using the 2.6.35 kernel very successfully for about 6 months without these errors. I'm considering going back to 2.6.35 if that's possible.
I'm hoping that the lack of response from the dev team to this problem is due to summer vacation and that it will be addressed in the fall. Hoping.....
Thanks for posting your results with 3.0.1 - I was considering trying that but I won't after your negative report.
Thanks Robm, I'm now back to kernel 220.127.116.11 and I can confirm everything works ok. That's alright for now, I guess.