[gutsy] rt61 wireless stops working after several minutes

[Ashley Hooper]

With Gutsy I am finally able to use Network Manager to connect to WPA-protected wireless networks with my notebook's RT61 PC card. However, the connection stops working within several minutes, at which point I am not even able to ping the router. After the most recent occasion, dmesg asserted there was a duplicate address detected, however this is not possible as only this one computer is switched on and the network is WPA-protected.

Incidentally, I have the same problem with 2 different laptops, both running Gutsy. So far I've not found a way to bring the interface back to life short of rebooting the computer.

Here's the dmesg output:

[ 502.500736] wlan0: Initial auth_alg=0
[ 502.500752] wlan0: authenticate with AP 00:0f:b5:29:93:86
[ 502.502198] wlan0: RX authentication from 00:0f:b5:29:93:86 (alg=0 transaction=2 status=0)
[ 502.502209] wlan0: authenticated
[ 502.502217] wlan0: associate with AP 00:0f:b5:29:93:86
[ 502.510852] wlan0: RX AssocResp from 00:0f:b5:29:93:86 (capab=0x431 status=0 aid=1)
[ 502.510863] wlan0: associated
[ 502.511321] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 502.922237] wlan0: duplicate address detected!
[ 509.466454] wlan0: duplicate address detected!
[ 600.481524] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at non-free entry in the non-full queue 2.
[ 600.481533] Please file bug report to http://rt2x00.serialmonkey.com.

[Ondrej Huml (ondrej-huml)]

I have the same problem after upgrading from Feisty to Gutsy but using WEP.

Network controller: RaLink RT2561/RT61 802.11g PCI

dmesg:
[ 7127.812000] wlan0: Initial auth_alg=0
[ 7127.812000] wlan0: authenticate with AP 00:x:x:x:x:x
[ 7127.816000] wlan0: RX authentication from 00:x:x:x:x:x (alg=0 transaction=2 status=0)
[ 7127.816000] wlan0: authenticated
[ 7127.816000] wlan0: associate with AP 00:x:x:x:x:x
[ 7127.816000] wlan0: RX AssocResp from 00:x:x:x:x:x (capab=0x451 status=0 aid=1)
[ 7127.816000] wlan0: associated
[ 7127.820000] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 7127.884000] wlan0: duplicate address detected!

 lsmod|grep rt:
rt61pci 24576 0
rt2x00pci 11520 1 rt61pci
rt2x00lib 19712 2 rt61pci,rt2x00pci
rfkill 8208 1 rt2x00lib
mac80211 171016 4 rc80211_simple,rt61pci,rt2x00pci,rt2x00lib
input_polldev 5896 1 rt2x00lib
crc_itu_t 3072 1 rt2x00lib
eeprom_93cx6 3200 1 rt61pci

[José Dapena Paz (jdapena)]

Same problem here. After hte mentioned crash with write_tx_data, there's no new activity in wifi card. I cannot receive any new package, and I need to reboot to recover. If I try to rmmod the driver once this happens, rmmod hangs.

[Ondrej Huml (ondrej-huml)]

Is working now. Maybe fixed in 2.6.22-13.

[FernandoMilton (fernandomilton)]

It is not working for me. I'm using kubuntu gutsy, kernel 2.6.22-14-generic and it still cannot hold the connection for more than a few minutes. The message is the same of the original poster.

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

[Ashley Hooper (ash-hooper)]

Ndiswrapper has been 100% stable for me. Might be worth sticking with this until the rt2x00 et al drivers are more mature.

[José Dapena Paz (jdapena)]

Still crashing in 2.6.22-14. It's a little bit better, as I can reload the driver now (it lead to a hang). If I rmmod the driver and modprobe it again, I get connection working again.

[Philipp Meier (meier-philipp)]

I do have the same problem! It did extend the "lifetime" a bit by upgrading to 2.6.22-14, but it still lost connection after several minutes.

Oct 16 23:02:50 XXX kernel: [ 5200.140000] Please file bug report to http://rt2x00.serialmonkey.com.
Oct 16 23:02:50 XXX kernel: [ 5200.140000] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at non-free entry in the non-full queue 2.

Seems to be a serious problem.

[oxyd (georges-tupinier)]

Same problem for me.
But after crashing when i reload the driver with rmmod and modprobe the connection is stable.
Ejecting pcmcia wifi card crash the PC too.

[Kasper Meerts (kasperm-deactivatedaccount)]

I have the same problem, though not so severe, It takes hours for mine to shut-down.

[Ai1dRo0kNotBot (last-fr)]

Baga! Just why is that happening?
First time I've upgraded my Ubuntu (6.10-7.04) the TrackPoint fell off... (PS/2 mouse relative).
This time the same shoot hapend to my WiFi card... Ubuntu 7.04-7.10... It's just amazing... Does this distro started to degrade?
-----------------------
[10877.332000] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[10879.144000] wlan0: Initial auth_alg=0
[10879.144000] wlan0: authenticate with AP 00:11:95:64:eb:ac
[10879.160000] wlan0: RX authentication from 00:11:95:64:eb:ac (alg=0 transaction=2 status=0)
[10879.160000] wlan0: authenticated
[10879.160000] wlan0: associate with AP 00:11:95:64:eb:ac
[10879.168000] wlan0: RX WEP frame with unknown keyidx 1 (A1=ff:ff:ff:ff:ff:ff A2=00:11:95:64:eb:ac A3=00:11:95:64:eb:ac)
[10879.172000] wlan0: RX WEP frame with unknown keyidx 1 (A1=01:00:5e:00:01:b2 A2=00:11:95:64:eb:ac A3=00:11:95:64:eb:ac)
[10879.172000] wlan0: RX WEP frame with unknown keyidx 1 (A1=ff:ff:ff:ff:ff:ff A2=00:11:95:64:eb:ac A3=00:15:e9:3e:91:5b)
[10879.172000] wlan0: invalid aid value 1; bits 15:14 not set
[10879.172000] wlan0: RX ReassocResp from 00:11:95:64:eb:ac (capab=0x431 status=0 aid=1)
[10879.172000] wlan0: associated
[10879.172000] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[10879.452000] wlan0: duplicate address detected!

[11370.464000] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at non-free entry in the non-full queue 2.
[11370.464000] Please file bug report to http://rt2x00.serialmonkey.com.
----------------------------
Last one just before the death of wifi...
Should I mention that previous issue haven't been resolved yet?

Good luck bughunting...

[Fabio Mauri (mafabio)]

I've got this problem too. After a few minutes the rt61 generates an error, and the wifi card stops working.
Removing and inserting the rt61 module with rrmod and modprobe makes the wifi card restart working,
but neither this condition is stable: after a few minutes the problem happens again.

[Jose Padilla (sargepl)]

Same problem here. After serveral minutes the connection is lost :(. And the same in dmesg about "duplicate IP" or "no ipv6 route to the host" messages :_((

[Fabio Mauri (mafabio)]

I encountered this issue on my laptop pc, and I noticed that it happens expecially when the notebook is overheating and the fan starts running faster.
During the last test the pc stood idle for 1 hour and half without losing connection, but after the fan had started running faster, the connection was lost in a few minutes. I hope this can help.

[oxyd (georges-tupinier)]

I think the fan goes faster because network-manager freeze (98 % cpu time) :-<

[Fabio Mauri (mafabio)]

Anyway I was tired to remove and reinsert the kernel module for rt61, so I wrote down a simple daemon in C which checks if the WLAN is connected and if not it restores the connections. I hope it will be helpful, but anyway I decline any responsibility on it.
You can download source code from my web site www.fmonline.it, the daemon name is Wlan Check. The site is in italian, but the download link is on the homepage.

[Jose Padilla (sargepl)]

I saw a spanish's tutorial replacing Network Manager with Wicd - Network
Manager and using ndiswrapper with RT61 Windows driver. The result is very
very good. I haven't the link but a file tar.gz with instructions. If
somebody want it, ask me.

On Nov 19, 2007 7:29 PM, Fabio <email address hidden> wrote:

> Anyway I was tired to remove and reinsert the kernel module for rt61, so I
> wrote down a simple daemon in C which checks if the WLAN is connected and if
> not it restores the connections. I hope it will be helpful, but anyway I
> decline any responsibility on it.
> You can download source code from my web site www.fmonline.it, the daemon
> name is Wlan Check. The site is in italian, but the download link is on the
> homepage.
>
> --
> [gutsy] rt61 wireless stops working after several minutes
> https://bugs.launchpad.net/bugs/139832
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Arnie (arne-tesdorff)]

Hi there,
I tried to fix the problem with using WICD, but (under Gutsy) networks keeps hanging after several times (both - nm or WICD). the larger the data, the shorter the runtime. Tried to use the driver from RALINK but compiling wasn't possible. Think I will throw away the WLAN and switch to LAN. :-((
to fabio: your script is clever, but doesn't solve the problem at it's roots, does it? Ciao.

[MeM (memi)]

Same problem here...I've got a motherboard with integrated wifi (ASUS P5K-E).
wifi starts and work normally about 20 minutes then i lose my connection and i can't reconnect.

[Ashley Hooper (ash-hooper)]

Just in case some here aren't aware, ndiswrapper is a 100% reliable replacement for the native rt61 driver. It simply 'wraps' the Windows XP/2000 driver in a partial Windows emulation layer, and I've been using it for several months and never lose connection or have to restart the interface.

So if you just want to get up and working with your wireless adapter, why not install ndiswrapper until the native rt61 kernel module becomes stable enough for everyday use?

There are many tutorials around on setting up ndiswrapper.

[xtsbdu3reyrbrmroezob (xtsbdu3reyrbrmroezob)]

I am confirming this bug, The native rt61 driver has become unstable between Feisty (2.6.20) and Gutsy (2.6.22). Someone from the kernel team should investigate this. Personally, I experienced the problem using the rt61pci driver...

[xtsbdu3reyrbrmroezob (xtsbdu3reyrbrmroezob)]

I forgot to also mention that I experienced this on both amd64 and i386 architectures...

[xtsbdu3reyrbrmroezob (xtsbdu3reyrbrmroezob)]

Additionally, it even occurs when not using NetworkManager. I set /etc/network/interfaces to take over the config for wlan0, so that nm would not touch it. Furthermore, this was even after I deleted the network interface entry in /etc's 70-persistent-net file which had allocated the device name 'ra0' for the card. Upon reboot, it was reassigned 'wlan0' instead, but this made no difference...

[xtsbdu3reyrbrmroezob (xtsbdu3reyrbrmroezob)]

I just called Canonical support and am utilizing one of my 10 support issues to get the resolved for all of you :-)

[oxyd (georges-tupinier)]

Thank's a lot ;->

2007/11/29, Kristian Erik Hermansen <email address hidden>:
>
> I just called Canonical support and am utilizing one of my 10 support
> issues to get the resolved for all of you :-)
>
> --
> [gutsy] rt61 wireless stops working after several minutes
> https://bugs.launchpad.net/bugs/139832
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
"Oui, oui."
Shakespeare (Richard III, Acte I, Scène IV)

[Jose Padilla (sargepl)]

I expect you achieve it and it be resolved. Thanks!

On Nov 29, 2007 7:48 AM, oxyd <email address hidden> wrote:

> Thank's a lot ;->
>
> 2007/11/29, Kristian Erik Hermansen <email address hidden>:
> >
> > I just called Canonical support and am utilizing one of my 10 support
> > issues to get the resolved for all of you :-)
> >
> > --
> > [gutsy] rt61 wireless stops working after several minutes
> > https://bugs.launchpad.net/bugs/139832
> > You received this bug notification because you are a direct subscriber
> > of the bug.
> >
>
>
> --
> "Oui, oui."
> Shakespeare (Richard III, Acte I, Scène IV)
>
> --
> [gutsy] rt61 wireless stops working after several minutes
> https://bugs.launchpad.net/bugs/139832
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Kasper Meerts (kasperm-deactivatedaccount)]

I added the following lines to /etc/modprobe.d/blacklist

blacklist intel_rng
blacklist ieee80211
blacklist iwlwifi_rc80211_simple

My problems look solved now...
Let's hope for the best.

[Arnie (arne-tesdorff)]

@ aaargh486 - i tried your suggestion but the problem is still there.
the only solution is:
sudo rmmod rt61pci
sudo modprobe rt61pci
sudo ifup wlan0
@ kristian erik: are there some news from the support?

[oxyd (georges-tupinier)]

Another way to solve this bug:

 sudo apt-get update
    sudo apt-get install build-essential linux-headers-$(uname -r)
    cd ~
    mkdir ~/rt61
    cd ~/rt61
    wget http://rt2x00.serialmonkey.com/rt61-cvs-daily.tar.gz
    tar -zxvf rt61-cvs-daily.tar.gz
    cd rt61-cvs*/Module
    make

    sudo ifconfig wlan0 down
    sudo modprobe -r rt61pci
    echo 'blacklist rt61pci' | sudo tee -a /etc/modprobe.d/blacklist

    sudo make install
    echo 'rt61' | sudo tee -a /etc/modules

And Edit the right parameters for your connexion

    sudo gedit /etc/network/interfaces

[Robert (ubuntu-10-rmn30)]

Just a quick 'me too' for this bug. Wifi is generally OK but after an hour or two it cuts out and I see the message:

[ 9619.775331] wlan0: duplicate address detected!

from dmesg. I thought that assigning a static IP address to my (unused) wired ethernet (eth0) seemed to help, but then the problem occured again.

[Ashley Hooper (ash-hooper)]

I tried using the native kernel module (rt61pci) again last night instead of NDISwrapper and I found that the signal strength was about 1/3 to 1/4 of what I get with NDISwrapper, and that it was generally unreliable. I've heard other reports of low signal strength too.

[Brian Murray (brian-murray)]

I am assigning this bug to the 'ubuntu-kernel-team' per their bug policy. For future reference you can learn more about their bug policy at https://wiki.ubuntu.com/KernelTeamBugPolicies .

[Anders Häggström (hagge)]

I can also confirm that this driver is buggy. I have D-Link DWL-G510 rev C2 (RT61) that I tried to use on a fresh Ubuntu Gutsy 7.10-i386 install (updated up to date by 2007-12-18).
The hardware is detected and scan the area just fine. It finds my wifi-network, but I can't connect to it (WPA/WPA2-protected). I read something about disabling SMP and PREEMPT, and rebuild the kernel to make the CVS-driver work correctly, but that workaround will generate a lot of work to keep the kernel up to date in the near future, I guess.

I ended up solving the problem by installing ndiswrapper and use the xp-drivers bundled with the hardware (version 5.00).
I did as follows:

$ echo 'blacklist rt61pci' | sudo tee -a /etc/modprobe.d/blacklist
$ sudo apt-get install ndiswrapper-utils-1.9 ndiswrapper-common ndisgtk

And then I started the graphical ndisgtk from "System > Administration > Windows Wireless drivers". The hardware was found automatically and I added the drivers directly from the bundled install-cd ( /cdrom/Drivers/Drivers/Win2kXP/NetRt61G.INF ).
At last I rebooted and after that it has worked 99% of the time together with network-manager (the wifi-card looses signal strength down to ~20% some short periods of time, but nothing that has affected the connectivity).

I will keep it this way until there is a working, stable, native driver available in the main repository.

I hope this can help some of you that want to get your DWL-G510-card working.

[Patrick McEvoy (patrickmcevoy)]

Following this official guide seems to have got thing working... at fast speeds too

https://help.ubuntu.com/community/WifiDocs/Driver/RalinkRT61

[Patrick McEvoy (patrickmcevoy)]

Didn't last long, had dropped the connection again by this morning.

[NoWhereMan (e.vacchi) (uncommonnonsense)]

@Arnie, the bug should be solved in git, now if only someone could pull out the sources and test... :)

[karamalz (karamalz)]

I also switched to the (disappointing) solution Ndiswrapper to get my rt61 based interface working. This is very foolish because there are two open source drivers availible for this card, but both doesn't work stable. The ndiswrapper solution works quite ok, but I hope that, at least for hardy, we find a way to get the drivers working out of the box .

By the way: Problem is still in the current version of Hardy.

[karamalz (karamalz)]

Just a short annotation:

Looks like the same bug is also discussed at the rt2x00 board.

http://rt2x00.serialmonkey.com/phpBB2/viewtopic.php?t=4250&postdays=0&postorder=asc&start=0

[NoWhereMan (e.vacchi) (uncommonnonsense)]

@karamalz, could you please tell me which version of the windriver works with this rt61? I've tried 4.1 from linksys and looked like it didn't

btw, it looks like now on my sistem both 2.6.22 and 2.6.24 have issues with WPA (probably a different bug)! I can only connect using the command line and using wpa_supplicant -B (background mode daemon); otherwise wpa_supplicant sits there and no other commands can be issued; maybe this is connected with why network-manager does not connect...

[karamalz (karamalz)]

@ NoWhereMan,

I used the drivers from the official Ralink site (ralinktech.com), which can be found in Support/Windows. The right package is called

"PCI/mPCI/CB(RT256x/RT266x)"

It is quite big, cause there a lot of windows tools in it, but i did not found the interesting rt61.inf and rt61.sys anywhere else.

good luck!

[xtsbdu3reyrbrmroezob (xtsbdu3reyrbrmroezob)]

Unfortunately, my support contract with Canonical was nuked, and I was unable to file a bug report for this problem :-( And even with the latest Hardy updates, the bug is still there. So, not even upgrading to Hardy will fix this for you guys, if some of you were wondering about that possibility. Can we put some pressure to get this bug resolved? It is quite annoying and ridiculous!!! Does anyone else have Canonical contract muscle to flex?

[IvD (ivdoorn)]

The error message:
rt2x00pci_write_tx_data: Error - Arrived at non-free entry..

has been fixed in rt2x00 for quite some time already.
I would recommend upgrading to a more recent version.
I don't know which version ubuntu is packaging, but I bet
it is quite an antique version...

[Rui Castro (rui.castro)]

Hi,

Just confirming this bug.
My wireless card is Edimax EW-7108PCg (rt61pci).
In my case the time it takes for the connection to stall is not minutes; sometimes is minutes others is hours.
I restart the connection simply clicking NetworkManager and selecting the wireless network again.

[Juergen Schroeder (js-mr)]

Hi,

I can also confirm this bug and I have a Edimax EW-7108PCg (RT2561/RT61) too.

Under 6.10 everything runs fine with the rt61 driver vom serialmonkey, a speedport W700V router and WPA2.

I upgraded to gutsy and get no link anymore. I compiled the driver from serialmonkey like oxyd describes. I see the router, but only one time a had a minute the green link led on. I tried wep, without encryption ...
Also tried wicd network manager.

This is really shit, I upgraded with no need to gutsy because someone writes the rt61(pci) runs now out of the box ...

[zorgzorg2 (mraspaud)]

This patch solved the "non-full queue" error for me:

http://<email address hidden>/msg31134.html

Hope that helps...

[Launchpad Janitor (janitor)]

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

[markus haider (markus.haider)]

I have been using the backports for Hardy which solved the problem for me. But now I tested the 8.10 Release candidate and experienced the same error:

[ 386.898504] phy0 -> rt2x00queue_write_tx_frame: Error - Arrived at non-free entry in the non-full queue 2.

Internet stopped working. But it worked with just unplugging the USB-WIFI-dongle and replugging it. Still this is annoying

[Launchpad Janitor (janitor)]

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.