rt2x00.serialmonkey.com

I get the following thing in my dmesg, repeated thousands of times:


Well, this is the reported bug.

lsusb | grep Ralink:


uname -a:


cat /sys/module/rt2x00*/version:

Also, maybe this is a hardware-related error, but the device only finds (the) two (closest) networks, whether I use "iwlist scanning" or "airodump-ng" makes no difference.


Thank you in advance for your response.

As mentioned in several topics: This issue has been fixed in the 2.6.26 kernel.

_________________
Regards,
Ivo van Doorn
Project Administrator
http://rt2x00.serialmonkey.com

Thank you then.


Cheers

Hi,
now I've waited a long time and now the 2.6.26.3 Kernel is out for Fedora 9.

So, I think, my problem with my ralink chipset is solved.

But today in the morning the network was once again dead.

'dmesg' told me the "old problem":

You said, this problem is fixed. Can you explain to me why I got the error messages with the new kernel?

Thanx a lot,
Stefan

same error with 2.6.27 kernel...


dmesg :




lsusb | grep Ralink :



uname -a :




cat /sys/module/rt2x00*/version :




thanks,

same here with 2.6.27-7

[ 9297.857042] phy0 -> rt2x00queue_write_tx_frame: Error - Arrived at non-free entry in the non-full queue 2.
[ 9297.857044] Please file bug report to http://rt2x00.serialmonkey.com.

$ cat /sys/module/rt2x00*/version
2.1.8
2.1.8

$ uname -a
Linux - 2.6.27-7-generic #1 SMP Tue Nov 4 19:33:06 UTC 2008 x86_64 GNU/Linux

$ lsusb | grep Ralink
Bus 002 Device 004: ID 148f:2573 Ralink Technology, Corp. RT2501USB Wireless Adapter

Same here with 2.6.27.5:

dmesg:

I also get this problem.

Running Fedora Core 10s latest kernel och associated stuff.

I temporary solve this problem by restarting NetworkManager.
I've also noticed that this problem seems to occur more often when downloading at greater speeds.
I have yet to encounter this problem when just casually browsing the web.



I suppose you could temporary "fix" this by something like..

I have the same problem using a 2.6.27 kernel:

[ 796.080885] phy0 -> rt2x00queue_write_tx_frame: Error - Arrived at non-free entry in the non-full queue 2.
[ 796.080885] Please file bug report to http://rt2x00.serialmonkey.com.
[ 796.081042] phy0 -> rt2x00queue_write_tx_frame: Error - Arrived at non-free entry in the non-full queue 2.
[ 796.081042] Please file bug report to http://rt2x00.serialmonkey.com.

# uname -a
Linux phenom 2.6.27-gentoo-r7-64 #1 SMP PREEMPT Sun Dec 21 21:10:33 PST 2008 x86_64 AMD Phenom(tm) 9950 Quad-Core Processor AuthenticAMD GNU/Linux
# cat /sys/module/rt73usb/version
2.1.8

Using a D-Link WUA-1340 wireless USB adapter:
Bus 002 Device 002: ID 07d1:3c04 D-Link System

I saw this error twice while emerging glibc via an ssh connection from another machine so the output of the emerge command was sent to the machine from where the ssh connection originated. If you need more information then please let me know exactly what. I did not have debug information compiled into this module when I saw the error, but I recompiled it with debug messages and haven't seen the error message yet.

Hello,
if I remember well, this issue has already been tackled. You may have more chances with more recent versions of the driver/kernel.

Regards,
Romain

_________________
RutilT developer

The 2.6.27 kernel was the most recent one until 2.6.28 was released just a couple of days ago. I have installed the 2.6.28 kernel and so far I haven't seen the problem yet.

I'm not sure which kernel version was used while working on this problem, but if it works on one kernel version it may not necessarily still work on subsequent versions since interfaces can change between versions. It's working now on 2.6.28, though.

This problem appeared again in Fedora 10, 2.6.27.15-170.2.24.fc10.x86_64. It was not an issue in 2.6.27.12-170.2.5.fc10.x86_64.
Starting to get a bit irritating.. Is there a bug report for this problem? What is the actual issue?

In Fedora 10, this problem is resolved in 2.6.29-0.20.rc3.git12.fc10, which can be downloaded from http://koji.fedoraproject.org/koji/buil ... ldID=82051

I posted a Fedora 10 step-by-step solution at my blog: http://blog.hacka.net/#post5

It is still a problem in 2.6.27-9-generic Ubuntu Intrepid

Well it is nice that you shout this on every topic you can find this, but if you READ the topic you could see that reported working kernel is 2.6.29-rcX... Since 2.6.27 is obviously older then that, it means that you must upgrade your kernel.

_________________
Regards,
Ivo van Doorn
Project Administrator
http://rt2x00.serialmonkey.com