Ralink Wireless legacy drivers (rt2500 rt61 rt73 rt2570) USB/PCMCIA/PCI hangs PC

I am using a D-Link DWL-G122 (Rev B) USB WLAN Adapter with Ubuntu "Dapper Drake 6.06" Kernel 2.6.15-19-386 and experience the problem similar, only in my case the freeze occurs if I issue a "ifup rausb0" command. Better information not available, as system has to be switched off and on to get going. But I checked the Kernel-Sources, the driver distributed is the Latest BETA rt2570 driver: v1.1.0-b1 from http://rt2x00.serialmonkey.com/wiki/index.php/Downloads. If I use rt2570 USB nightly CVS tarball: rt2570-CVS
from the same page, everything works fine ( WEP as well as WPA )

Casual

I can confirm this problem too.

Using an Asus WL-167g USB adapter, the system locks up if I try to enable wireless networking.

I can use this device without a problem on Gentoo, where I am using the nightly CVS version (the 'stable' release will not compile cleanly against newer kernels).

Changing to major as this causes a complete hard lock.

I can confirm that this is still a problem on the latest Dapper Beta with kernel 2.6.15-23-686. Hard lock as soon as I activate the wl-167g.

Well seems not only the USBstick hangs up the PC. I have an Amilo A1630 Notebook with integrated rt2500 WLAN chipset. When i activate the device i can work some minutes then Notebook frezzes.

Me too, I'm running an Averatec 3715-EH1 laptop with an internal RT2500 wireless card. Worked perfectly in Breezy, then I apt-get dist-upgraded to Dapper yesterday. Now when I 'ifup ra0' or 'dhclient ra0' the system hangs.

I can confirm that the rt2500 chip also has problems if used with a router and WPA. I see this on 5 different boxes of different types.

I can confirm that this is still a problem on the latest Dapper Beta with kernel 2.6.15-23.39.
I have a rt2500 PCMCIA based card (Conceptronic C54RC).
Always work ok (since hoary) but with the latest upgrade the system hangs.

same here with a D-Link DWL-G122 b1. Complete lock-up when activating the interface on Dapper. Any drivers reported working?

I can conform this is not just a USB problem. None of the flights I tested worked. I have a Averatec 3250, with a RT2500 chip. As soon as I try to enable ra0, the whole system locks up and I have to power down.

I can do extensive testing if needed.

Here is something that may help. My Ethernet card and my Wireless card ( both built in ) were sharing IRQ 11 ) If I enabled PCI=routeirq at the kernel boot, I no longer get lockups.

I tried the pci=routeirq suggestion but that did not seem to work.

I just tried installing an older version of the rt2500 driver that I was using successfully in Breezy, but nothing changed. I used rt2500-1.1.0-b3, and followed the directions here: https://wiki.ubuntu.com/WifiDocs/RalinkRT2500/DriverAndRaconfig

The system still hangs on dhclient.

Teh problem is ubuntu probably shipped with an older version of the rt2500 driver.

See this post http://rt2x00.serialmonkey.com/phpBB2/viewtopic.php?t=1481

On Sun, 2006-06-04 at 15:26 +0000, Javier Jardón wrote:
> Teh problem is ubuntu probably shipped with an older version of the
> rt2500 driver.

We shipped with the latest stable of the legacy driver (not the rt2x00
one, which is broken on both of my rt2500's).

We also did not use the CVS version as it had it's own problems. This is
a matter of rt2x00 not being stable, IMO. The project really needs some
maturing, and really needs to be releasing more often.

Well that is indeed a valid point, but we don't have any plans to make a new release at this moment.
 This is the response of IvD (core rt2x00 developer):

> Since rt2400, rt2570 don't have SMP support, and rt2500 only has it in the latest CVS >code I would recommend to them they drop the Ralink drivers altogether untill rt2x00 is >released. The SMP issue will _not_ be solved in the legacy drivers which means that it >will _never_ work with the default Ubuntu kernel if they have SMP enabled by default.
>And rt2x00 is near a beta4 release, which will not be suited for distros yet, so they will >have to keep waiting a while before things have stabilized and are ready.

>(I am currently discussing this on the IRC channel, they will most likely update rt2500 to latest CVS version.)

See this post http://rt2x00.serialmonkey.com/phpBB2/viewtopic.php?t=1481

After the discussion on IRC, the result is that I will assist with rt2x00 related bugs filed in launchpad. That will give me a lot of testers of the rt2x00 code which helps me with debugging and stabilizing rt2x00. So rt2x00 should be stable when the next ubuntu release is made. :)

On Sun, 2006-06-04 at 18:15 +0000, IvD wrote:
> After the discussion on IRC, the result is that I will assist with
> rt2x00 related bugs filed in launchpad. That will give me a lot of
> testers of the rt2x00 code which helps me with debugging and stabilizing
> rt2x00. So rt2x00 should be stable when the next ubuntu release is made.

The other side of the coin is that I will be pulling rt2500-legacy from
CVS for dapper-updates to hopefully help with the SMP related crashes
there.

confirmed on ubuntu 6.06 final.

My friend has a very similar problem with gigabyte wp01gs.

This bug is quite high when it comes to criticalness (I found it by sorting all bugs by criticalness). I really hope to see if patched soon.

It works on the CVS of the driver:
http://rt2x00.serialmonkey.com/wiki/index.php/Downloads

This has been confirmed by a few sites I think.

Oh ya, including this one *head2desk*

And if you'll notice the bug has been marked "Fix commited", which means we have the fix, just waiting for the upload.

"Re: Ralink Wireless USB hangs PC Posted by coldsalmon at 2006-05-28 07:42:39 UTC

Me too, I'm running an Averatec 3715-EH1 laptop with an internal RT2500 wireless card. Worked perfectly in Breezy, then I apt-get dist-upgraded to Dapper yesterday. Now when I 'ifup ra0' or 'dhclient ra0' the system hangs.
"

I had the same problem, I think that it has to do with the latest via Xorg driver. When I put:
Option "DisableIRQ"
to the /etc/X11/xorg.conf file the problem went away.

Code:

Section "Device"
Identifier "VIA Technologies, Inc. S3 Unichrome Pro VGA Adapter"
Driver "via"
BusID "PCI:1:0:0"
Option "DisableIRQ"
EndSection

muadib how do you think the wifi and xorg are related to the hanging of the pc? I have suspected this but I have had no evidence to belive this. Or is it something to do with IRQ? I have had the same exact problem with Arch Linux as well, using both the native linux driver (rt2570) as well as ndiswrapper.

I also had to add irqpoll to the bootup (in /boot/grub/menu.lst, where it says "kernel ... vmlinuz ... ro". I haven't tried removing the option from xorg, but my Avaratec now works. I added the irqpoll since I got the message that IRQ185 wasn't being handled.

I think the irq "multiplexer" in the kernel confuses the display with the ralink card, or that the ralink driver is getting confused and wants to respond to display or conversely the card is pointing at the display IRQ.
I think upping the debug on the kernel module and looking which IRQ it is trying to use might isolate the problem which I might try later. I'd also look for subtle changes with the IRQ master handling between 2.6.12 and the current kernel - including #def IRQ type things.

With the new kernel (2.6.15-25) I am still getting a system lock when activating the driver.

I don't have the new kernel.

I have three changes which make it work on my Averatec for the internal rt2500 card.

I don't know if all are necessary or if just one or two are required.

1. In the driver itself, rtmp_init.c, right at the end, there is an #if which switches del_timer and del_timer_sync. I have it forced to use the _sync version.

2. In /etc/X11/xorg.conf I have the Option "DisableIRQ" line added to the driver.

3. In my boot string /boot/grub/menu.lst I've added "irqpoll" after "ro".

#1 and #2 by themselves don't work, and I think I tried #3 alone earlier.

I have a Linksys Wireless - G PCI adapter in my linux server with ubuntu dapper and kernel version 2.6.15-23-server. The driver module used seems to be "rt61". I also had the same problem with the system locking down after doing for example "iwlist ra0 scan" or any other operation using the card. And although iwconfig showed the card as ra0, executing "ifconfig ra0" just said the device doesn't exist.

After reading this thread I tried to add "irqpoll" to the kernel parameters and it worked like a charm. Thanks!

So for me, no other tricks than "irqpoll" we're necessary. Although I'm not using X windows in my server.

Confirm that I also get the system lock with a Dlink DWL-G122 (ver B1) with the -25 kernel.

Using the command

sudo dhclient rausb0

allows me to connect to the internet on a WUSB54gv4 wifi card. Using a p4 1.7ghz Desktop with 512 mb of ram. However using the GUI for networking I the computer hangs. Sometimes it hangs on it's own. This problem also happens with the ndiswrapper drivers for my card, I do not know if that is related. (Would IRQ be an issue here?) the irqpoll trick did not fix this problem.

Yea, I'm afraid I don't believe this bug is fixed - I still get a lock after doing all updates (so I have the -25 kernel)

I can confirm that this bug is still not fixed in the 2.6.15-25-686 kernel current release of dapper. I still get a complete system freeze as soon as I activate the wl-167g.

I'm using the D-Link DWL-G122 USB stick and receiving the same problem.

Could someone clarify the solution for me?

Is this bug fixed or not? I see the status changed but I have yet to see a fix commited or commented on in the notes.

The problem is in the Ubuntu patches as Debian unstable does not suffer this problem.

Is there anyway we can get a kernel that doesn't have the wifi drivers in it? I belive that has alot to do with the instability. Or could someone point me to where I can find the Ubuntu kernel patches and source?

Problem still exists.

Yes the presence of my Netgear WG511 wireless card will usually freeze my laptop at boot. Removing the card fixes the problem.
Worked very well in Breezy. Ndiswrapper is used to load driver.

I don't know if there is a solution to this bug as of yet, but I've attached a guide (borrowing heavily from the Ubuntu Wiki) that should run through the process of setting up the D-Link DWL-G122 Wireless USB Adapter using ndiswrapper.

added irqpoll to the kernel /vmlinuz ... line and my Averatec 3250 now works with kernel 2.6.15-23-386. Thanks tz

I am using a d-link WL-107g cardbus adapter connected to an IBM thinkpad 570 (Pentium 2 366). The adapter uses the ralink RT-2500 chipset.

lspci -v:
0000:06:00.0 Network controller: RaLink Ralink RT2500 802.11 Cardbus Reference Card (rev 01)
        Subsystem: ASUSTeK Computer Inc.: Unknown device 107f
        Flags: bus master, slow devsel, latency 64, IRQ 11
        Memory at 16000000 (32-bit, non-prefetchable) [size=8K]
        Capabilities: [40] Power Management version 2

I using kernel 2.6.15-26-386 with Ubuntu dapper. I have tried using dhclient, unplugging the adapter live, plugging it back in, shutting down/restarting. The card has consistently performed as expected.

I have tried using 'dhclient' 'iwlist ra0 scan' everything works as expected.

I have performed an upgrade to kernel 2.6.15-26.45 -686 and all bahaves as expected.

Correct me if I'm wrong, but first you used a kernel for a 386. The one you
used after the upgrade is for a 686-system. Is this a typing error? Because
it would be of great help if it's the 386-version

2006/7/21, Nick_Hill <email address hidden>:
>
> I am using a d-link WL-107g cardbus adapter connected to an IBM thinkpad
> 570 (Pentium 2 366). The adapter uses the ralink RT-2500 chipset.
>
> lspci -v:
> 0000:06:00.0 Network controller: RaLink Ralink RT2500 802.11 Cardbus
> Reference Card (rev 01)
> Subsystem: ASUSTeK Computer Inc.: Unknown device 107f
> Flags: bus master, slow devsel, latency 64, IRQ 11
> Memory at 16000000 (32-bit, non-prefetchable) [size=8K]
> Capabilities: [40] Power Management version 2
>
> I using kernel 2.6.15-26-386 with Ubuntu dapper. I have tried using
> dhclient, unplugging the adapter live, plugging it back in, shutting
> down/restarting. The card has consistently performed as expected.
>
> I have tried using 'dhclient' 'iwlist ra0 scan' everything works as
> expected.
>
> I have performed an upgrade to kernel 2.6.15-26.45 -686 and all bahaves
> as expected.
>
> --
> Ralink Wireless USB/PCMCIA/PCI hangs PC
> https://launchpad.net/bugs/34902
>

Hello Dimitri

I am making the point that whether using an older or newer version of the kernel, whether 386 or 686, it works for me.

Of course, this doesn't immediately help you if it isn't working for you. But at least the developer knows that there are platforms where it works perfectly, and that it isn't an issue of kernel compilation optimisation.

It also lets the developer know that the existing kernel module is very useful to those for whom it works. After all, the developer will normally get comments from those who are having a problem with this module, and is less likely to get a comment from those who are not having trouble.

This has 2 effects:
1)The developer can look at the hardware differences to help identify the bug, perhaps it is a dual cpu problem, or a cardbus bridge problem?
2)Lets the developer know not to delete the driver as doing so will inconvenience many users. I have used this driver on two other systems, and each time, it has worked perfectly. In my experience of this driver with the Asus WL107G, it appears failure is the exception rather than the rule.

Just to go on record and give a big thumbs-up to you guys, I'm posting this via my wireless now. Running kernel 2.6.15-26-386. I added the "irqpoll" to my boot menu and the "DisableIRQ" to my xorg.conf.

These were the only two steps necessary in order to get everything up and running like a clockwork dream.

Maybe I missed this but where do I add DisableIRQ in xorg.conf??

I reccomend that the driver be spearated from the kernel. Perhaps put the extra .deb on the cd so that it can be installed via synaptic (like the ndiswrapper driver) (for the next ubuntu release that is). This would stop the problems for those who have freezes etc. And would allow those for whom the driver works well to still have easy access to it (w/o having to be connected to the internet.

> Maybe I missed this but where do I add DisableIRQ in xorg.conf??

I used muadib's suggestion and added

Option "DisableIRQ"

as the very last thing before

EndSection

. For example, my entire entry is as follows:

Section "Device"
 Identifier "VIA Technologies, Inc. S3 Unichrome Pro VGA Adapter"
 Driver "via"
 BusID "PCI:1:0:0"
 Option "DisableIRQ"
EndSection

Thank you.

I am new to linux and ubuntu and am having the hang problem with a Gigabyte WP01GS wireless pci card. I thought I'd try adding the "irqpoll" to my boot menu and the "DisableIRQ" to my xorg.conf as suggested but I have no idea where to start. Can anyone point me in the right direction?

with email help from "tz" I made the changes but unfortunately it didn't fix the problem.

Thank you tz anyway.

I'm also having a problem with my Zonet ZEW2500P USB Wireless Adapter, which uses the rt2570 kernel module. I've compiled the latest CVS from rt2x00.serialmonkey.com, but it only lasts longer than the original module before burning out and going "kaput".

the problem is not only the driver in dapper with the pc freeze, but also the latest CVS version doesn't work properly.
For me with a Netopia USB wifi stick the cvs version is working a bit. Means after several minutes connection get lost. The driver even in cvs are not really working.

Same problem here with Belkin F5D7000 PCI wireless card. Freezes the computer if its enabled and blocks booting. Must boot with live cd to fix and disable.

I have an rt2400 and after I installed the 2.6.15-26-k7 kernel package it hangs on startup. I returned using 2.6.15-26-386 and it works fine. I had similar problems on my previous Dapper install, iwconfig used 99% percent CPU, and it can't be killed, because even sudo wasn't responding,

I had the iwlist 99% problem, which I "solved" by moving iwlist out of /sbin in recovery mode, but I have since reinstalled and my system hangs when I click "Configure" in the network settings tool. It works on the live CD, so I think it is my -23-k7 kernel. My card is PCI and uses rt61 driver. I tried compiling my own from RaLink source, but instead of crashing the system when clicking on Configure it just crashed the network settings tool.
I am confused by the different fixes suggested, since others are saying they don't work, so I don't know which to try.

I would like to fix this without changing the kernel image or GRUB config if possible, since that would require a new boot CD to be made and my CD writer isn't working.

Same problem here. I have the DLink DWL-G510 wireless card running on Dapper kernel 2.6.15-26-amd-64. I have tried compiling the rt61 driver from the website and adding the configuration files into /etc/Wireless/RT61STA but whenever I do anything to do with the adapter (ifconfig up or iwconfig ess) the program just churns and my machine becomes unusable.

If anyone can find a solution to this it would be really awesome.

Hi all,

Running Dapper 2.6.15-26-386 on an MSI 654 Ultra (MS-6547 v.1) with a Matrox G550. (The mobo BIOS has not been updated since purchase.)

I installed an Asus WL-167G USB 2.0 wifi adapter (Ralink RT2500 chipset) which initially worked fine out of the box, using default Dapper drivers. I plugged it in, configured the network settings, and it connected to my router without problems.

It ran flawlessly for several weeks until I decided to use the the System > Administration > Networking tool to change the configuration from static addressing to DHCP. I made the change, clicked OK and the system locked up, solidly. As others have reported above, all I could do was hard reboot.

I disabled the interface and tried to re-enable it, but doing so froze the system (as did each subsequent attempt). The solution (for me) turned out to be very simple. In /etc/network/interfaces I added the statement "auto rausb0" immediately above the section for my wireless interface. So, the wlan section in my interfaces file now looks like:

auto rausb0
iface rausb0 inet static
(... etc.)

After rebooting, the command did its job and auto-started the interface.

So far so good. Seems to be working fine and is a simple and benign fix. Hope this proves to be helpful to someone.

Just re-read my post above and realised that I called my solution a 'fix'. That's incorrect, it's merely a workaround as the original problem with the system freezing after configuration changes using the Gnome Networking tool persists on the machine. However, manually editing 'interfaces' has enabled me to regain connectivity.

I have similar feedback to rlancefield. I'm using an up to date dapper install with kernel 2.6.15-26-686 and an asus wl-167g usb 80211b/g adapter which uses the ralink rt2570 chip I think.

If I configure and activate my wl-167g manually using /etc/network/interfaces and calling 'ifup rausb0' or setting it to autostart everything now works.

If I configure and activate the adaptor using the Gnome networking tool I get a complete system freeze as soon as I activate. This freeze always happens if I manually specify an IP address using the networking tool, and only sometimes happens (maybe never) if I set it up to use DHCP.

Here's the lines that make it work in my /etc/network/interfaces script:

auto rausb0
iface rausb0 inet static
address 192.168.12.30
netmask 255.255.255.0
gateway 192.168.12.1
wireless-essid adf3fd
wireless-key 11112222333344445555666677

Here is some additional information:

Playing around in a text console, it appears that the "freeze" is caused by a kernel panic that occurs when we hit a BUG in a bh context at kernel/timer.c, line 411 (in cascade, an inline function that appears in __run_timers, which itself is an inline function that appears in run_timer_softirq, which is run in a bh context).

Here's the trace I was working from. The code indicates that it's line 411 of some file:

Code: ... <0f> 0b 9b 01 ee 03 30 c0 ...

It panics, so I couldn't conclusively trace which file from the panic, but I think it's clearly kernel/timer.c, given the stack trace.

 [<c01259a2>] run_timer_softirq+0x132/0x1d0
 [<c01214ff>] __do_softirq+0x4f/0xb0
 [<c0121595>] do_softirq+0x35/0x40
 [<c0121645>] irq_exit+0x35/0x40
 [<c01059cf>] do_IRQ+0x1f/0x30
 [<c010410a>] common_interrupt+0x1a/0x20

I'm doing some testing now, as to how to fix this. Since this is a double-fault, I'm curious if we can't just disable BUG()'s in the kernel (by recompiling). I don't know if the system will recover or not - it realizes something's wrong, but we panic since it reports the BUG in BH context, not necessarily because the problem is un-recoverable.

I just did a build with big-kernel-lock pre-emption (CONFIG_PREEMPT_BKL) turned off, and I didn't see any touble. So this may be a pre-emption issue. The kernel that had the problem and the one that didn't is a pretty big configuration delta, so I'm still trying to figure out what fixed it.

Still looking...

Oh, more information, for those more interested in getting their card working than in fixing kernel bugs:

I was able to get my card up by properly configuring /etc/network/interfaces manually, in the standard Ubuntu kernels, with DHCP. I can get exactly one "ifup" command through per reboot. You can also do one "ifdown" afterwards. However, on the second "ifup" the system panic's. I think the wizard does several ip-down steps, which triggers the panic. The end of my /etc/network/interfaces file, where I added wireless configs, looks like this:

iface rausb0 inet dhcp
wireless-essid <your ssid>
wireless-key <your WEP key>

*Don't* declare your interface "auto" in /etc/network/interfaces, since that tells automatic processes that they can up/down that interface, which will panic your kernel.

I have a simple script that checks if i've ever up'ed the card (by reading the ESSID from iwconfig), and only up's it once, and that is in my startup scripts:

is_wlan_up=$(iwconfig 2>/dev/null | grep '^rausb0' | sed -e 's/^.*ESSID://' | cut -d\" -f2)

[ "$is_wlan_up" ] || ifup rausb0

That was sufficient to get my D-Link DWL-g122 USB card (rt2500 based) working with Ubuntu. My network basically works at this point, but I'm curious to poke around a bit more to see what's wong.

This seems to be a bug in the rt2570 module. Since you can also use ndiswrapper to drive these cards (at least those of us on intel boxes), there is a simple workaround: disable the rt2570 module. You can compile it out, or just add these two lines to your /etc/modprobe.d/blacklist:

# use ndiswrapper instead for rt2x00 devices: rt2570 panics kernel
blacklist rt2570

With rt2570 disabled, my device works as expected, appearing as the wlan0 interface (ndiswrapper), rather than rausb0 (rt2570).

When I unplug dlink dwl-g122 or linksys wusb54 (rt2570 driver), keyboard and shutdown button stop works. Tested with latest CVS 20061103

A major source of confusion for the DLINK dwl-g122 USB WiFi dongle, I think, is that they use another chip from rev C onwards. I have a rev C dongle and had to compile the driver module from the latest CVS sources at http://rt2x00.serialmonkey.com/rt73-cvs-daily.tar.gz to get it to work. The rt73 driver isn't even released yet from what I can see. This comment is written over the WiFi connection that I just brought up manually through the network manager and by adding a few lines to the /etc/networking/interfaces with a static IP adress. I will now test further with DHCP based IP

This is strange. If I startup Dapper with eth0 deactivated and rausb0 activated I get no link over the DLINK dwl-g122 using the driver mentioned above. The interface is up but I have got no IP from the DHCP over WiFi. What makes it work hints about a startup script problem:

Open System->Administration->Networking
Deactivate the wireless (rausb0) connection
Activate the wireless (rausb0) connection

This will hang forever unless:

Open a terminal window
Issue: sudo ifup rausb0

Now it comes up! It does not work with either method alone, they seems both to be needed. My /etc/network/interfaces looks like this:

iface lo inet loopback

<snip>
iface rausb0 inet dhcp
wireless-essid myDlink524
wireless-key blablablablasecretkey

allow-hotplug rausb0
auto rausb0

iface eth0 inet dhcp
#auto eth0

I'am using Buffalo WLI-U2-KG54 usb wireless (rt2570) with Dapper in VIA epia M10000 machine. Freezing happens after few minutes. I have also tried this same adapter in Athlon XP and edgy with same results, both ndiswrapper and included drivers. Only way I can make my system stabile is boot adapter not connected, "sudo rmmod ehci_hcd" and connect adapter after that. Then of course I only have USB1 full speed, not USB 2 high speed. These "irqpoll" and Option "DisableIRQ" tricks made no difference.

My sistem d'ont crash but the conexion hangs at 29%, the wireless ca'nt connect. My machine is a targa laptop, amd64 turion mt-30. The chip is a Ralink RT2561/RT61 rev. 802.11g, Subsystem Micro Star international co. ltd. unknowm device b833.

Feisty Beta 1 will be out soon Please attach the output of dmesg and lspci from that release.

dmesg > dmesg.txt
lspci -vv > lspci.txt

Needs Info should be assigned to a person, not kernel team.

I just posted a somewhat related bug with feisty (amd64) and the rt61 module with a PCI wireless device.
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/94944

It may be related, but I will confirm this after investigation.

I'm using the newest feisty and have here a rt2570USB in my medion PC. When I try to use the serial monkey drivers feisty crashes every boot.

I testet now my WLAN RT2570USB with the feisty beta desktop CD and it still don't work. Why don't you intigrate the closed binary driver like some other one in the restricted manager or intigrate the open one? It's really bad to try get it working with long manuel installations - and this since warty and before.
Do you plan support for this chip in feisty release?

Honestly, if the license premits, then I think it would be much better to setup the Restricted Drivers manager to handle this using ndiswrapper. The ndiswrapper drivers tend to work really well for this card. I have this working myself (Linksys WUSB54gv) on feisty and I haven't had a freeze but from dapper to edgy the freezes have come. I haven't used feisty much though so it might also freeze there. My understanding is that once a few thins get worked out this will become part of the upstream kernel. I think it would be wise to wait for that, and simply provide the option for people to have this installed if they have this driver. SO that the people who this works for can use it. And for those whom this driver does not work, they can find a different method. My experiance has had this driver causeing hard freezes.( This driver being the rt2570 driver). It doesn't seem to me that there is an actual deb for this, rather it is built in with the kernel, (or as a module). Why not have it be seperate from the kernel? (If ndiswrapper is not an option that's ok the point of this was to say that this driver doesn't seem to be 100% stable, and should not be built in by default. If it were a deb uninstalling would be much easier.) No offense to anyone intended.

Yea, good idea with ndiswrapper - or maybe selectable options in restricted manager...
Can you post (or send me by mail) the link to the windows-inf-driver working with rt2570usb? (If you are using the USB variant) Thanks.

So ndiswrapper works, but that solution only helps x86, and not other supported platforms (ppc, sparc). When possible, it's better to fix a driver than to retreat to ndiswrapper.

wget http://prdownloads.sourceforge.net/rt2400/rt2570-1.1.0-b2.tar.gz?download

Preparation
If not installed already, these packages need to be installed.

Code:

sudo apt-get install build-essential linux-headers-`uname -r` gcc-3.4

At the time this was written driver was rt2570-1.1.0-b1. If driver is updated commands will need to change to that file name.

Step 1 Download and untar file

Get file
Go here and choose the rt2570beta driver. You'll get a choice of mirrors where to download from. Save it to file.

Now copy the file to /usr/src
Code:

sudo cp /path/to/file/rt2570-1.1.0-b1.tar.gz /usr/src/

Move to /usr/src
Code:

cd /usr/src

Untar file
Code:

sudo tar -xzvf rt2570-1.1.0-b1.tar.gz

Move into file
Code:

cd rt2570-1.1.0b1/Module

Step 2 Make and install file

Code:

sudo make

Code:

sudo make install

Step 3 Set up and load module

make a directory for the .ko file
Code:

sudo mkdir /lib/modules/`uname -r`/drivers/

copy file over to new directory
Code:

sudo cp /lib/modules/2.6.12/extra/rt2570.ko /lib/modules/`uname -r`/drivers/

Then insert module into kernel
Code:

sudo insmod /lib/modules/`uname -r`/drivers/rt2570.ko

Code:

sudo lsmod -a

Configure your wireless device through /etc/network/interfaces. Here is a sample file.

iface rausb0 inet dhcp
wireless-essid apname
wireless-key xxxxxxxxx
wireless-mode Managed
auto rausb0

restart the networking service

Code:

sudo /etc/init.d/networking restart

Now try to bring up your device

Code:

sudo ifconfig rausb0 up

To load module at boot add it to /etc/modules file

Code:

sudo echo rt2570 >> /etc/modules

See this problem in upstream: http://sourceforge.net/tracker/index.php?func=detail&aid=1705308&group_id=107832&atid=648844

Thanks,
I have disable the rt61 module and have uptime more than 1 day.

On 4/24/07, Javier Jardón <email address hidden> wrote:
>
> See this problem in upstream:
>
> http://sourceforge.net/tracker/index.php?func=detail&aid=1705308&group_id=107832&atid=648844
>
> --
> Ralink Wireless legacy drivers (rt2500 rt61 rt73 rt2570) USB/PCMCIA/PCI
> hangs PC
> https://bugs.launchpad.net/bugs/34902
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Well I try to resume the posible solutions fot rt61 cards (for Feisty)

Problem: (https://bugs.launchpad.net/ubuntu/+bug/34902/comments/17)
 From a ralink driver developer : "Since rt2400, rt2570 don't have SMP support, and rt2500 only has it in the latest CVS >code I would recommend to them they drop the Ralink drivers altogether untill rt2x00 is >released. The SMP issue will _not_ be solved in the legacy drivers (rt2400, rt2500, rt61, rt2570, rt73) which means that it >will _never_ work with the default Ubuntu kernel if they have SMP enabled by default."

Solutions:
1. Disable rt61 driver -> not solution for me, I need the wifi connection
1. Blacklist rt61 driver and use the rt61pci driver (comes with Feisty kernel) -> not work for me (bug #58117)
2. Compile your own driver -> not work for me, see this bug :-/
3. Install linux-image-386 which install a kernel with SMP disabled -> works for me perfect for days!!

I hope this helps.

All legacy drivers have received SMP fixes, and should now all work on SMP systems.

More and more manpower is being given to the legacy driver, so at the moment those are in better shape then rt2x00.
I hope this will be resolved in the future, but for the moment the legacy drivers seem to be the way to go.

maybe try acpi=force irqpoll https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.17/+bug/63134

Using Athero RT73 usb wireless, wireless assistant shows the routers, but the link quality stars are grayed out so it cannot connect to the routers. This has been the same on all versions of Feisty both 386 and 64. It shows everything with iwconfig, but no connection, hopefully this will be fixed soon

There should be a file somewhere on your system called rt73sta.dat (in a source install this is located in the /etc/Wireless/RT73STA). In that file you need to put the SSID and the encryption keys. If I don't do this step, I can not have a connection (independent of the settings I do with iwconfig). Once the file is properly configured, I'm able to link up with my access point. IMHO, this is quite annoying, since I'm not able to use the Network Manager to do the settings).

ok, I'm confirming that rt61 may completely hang your pc (even right after boot while or just before displaying GDM) under certain circumstances. I can't say *which*, though, what I know is that in some rooms of my university I had too boot *without* acpi=force irqpoll so that rt61 was (indirectly) disabled

I forgot: I'm using feisty with *latest* kernel update

Kubuntu 7.04, kernel 2.6.20-16-generic.

Attempting to bring up a connection with a Gigabyte GN-WP01GS PCI card (using KDE network manager, I put in the WEP key then clicked "OK") hung the machine. The mouse pointer still moved, but there was no response to mouse actions or keyboard. So I hit the power button after waiting a while to see if anything would happen "in good time". Ho hum. Machine is dual Athlon XP 1.6GHz on Tyan Tiger MPX S2466 mainboard (AMD 760MPX chipset).

Relevant bits of logs, up to last line before I hit the power button:

.....
Jun 6 22:04:34 bollard kernel: [ 25.388000] rt61 1.1.0 CVS CVS http://rt2x00.serialmonkey.com
Jun 6 22:04:34 bollard kernel: [ 25.388000] RT61: Vendor = 0x1814, Product = 0x0301
.....
Jun 6 22:06:43 bollard kernel: [ 159.908000] ADDRCONF(NETDEV_CHANGE): ra0: link becomes ready
Jun 6 22:06:53 bollard kernel: [ 170.696000] [softlockup_tick+156/240] softlockup_tick+0x9c/0xf0
Jun 6 22:06:53 bollard kernel: [ 170.696000] [update_process_times+51/128] update_process_times+0x33/0x80
Jun 6 22:06:53 bollard kernel: [ 170.696000] [smp_apic_timer_interrupt+112/128] smp_apic_timer_interrupt+0x70/0x80
Jun 6 22:06:53 bollard kernel: [ 170.696000] [apic_timer_interrupt+40/48] apic_timer_interrupt+0x28/0x30
Jun 6 22:06:53 bollard kernel: [ 170.696000] [_spin_unlock_irqrestore+13/32] _spin_unlock_irqrestore+0xd/0x20
Jun 6 22:06:53 bollard kernel: [ 170.696000] [try_to_del_timer_sync+71/80] try_to_del_timer_sync+0x47/0x50
Jun 6 22:06:53 bollard kernel: [ 170.696000] [del_timer_sync+14/32] del_timer_sync+0xe/0x20
Jun 6 22:06:53 bollard kernel: [ 170.696000] [<f8f470af>] MlmeAuthReqAction+0x5f/0x1e0 [rt61]
Jun 6 22:06:53 bollard kernel: [ 170.696000] [<f8f3bb58>] MlmeQueueFull+0x28/0x40 [rt61]
Jun 6 22:06:53 bollard kernel: [ 170.696000] [<f8f3bccc>] MlmeEnqueue+0xbc/0xf0 [rt61]
Jun 6 22:06:53 bollard kernel: [ 170.696000] [do_timer+564/2080] do_timer+0x234/0x820
Jun 6 22:06:53 bollard kernel: [ 170.696000] [<f8f469a0>] AuthTimeout+0x0/0x40 [rt61]
Jun 6 22:06:53 bollard kernel: [ 170.696000] [<f8f40ec3>] CntlWaitAuthProc+0x73/0x110 [rt61]
Jun 6 22:06:53 bollard kernel: [ 170.696000] [<f8f469a0>] AuthTimeout+0x0/0x40 [rt61]
Jun 6 22:06:53 bollard kernel: [ 170.696000] [<f8f387de>] StateMachinePerformAction+0x1e/0x30 [rt61]
Jun 6 22:06:53 bollard kernel: [ 170.696000] [<f8f3d481>] MlmeHandler+0x151/0x170 [rt61]
Jun 6 22:06:53 bollard kernel: [ 170.696000] [run_timer_softirq+303/416] run_timer_softirq+0x12f/0x1a0
Jun 6 22:06:53 bollard kernel: [ 170.696000] [timer_interrupt+89/176] timer_interrupt+0x59/0xb0
Jun 6 22:06:53 bollard kernel: [ 170.696000] [__do_softirq+130/256] __do_softirq+0x82/0x100
Jun 6 22:06:53 bollard kernel: [ 170.696000] [do_softirq+85/96] do_softirq+0x55/0x60
Jun 6 22:06:53 bollard kernel: [ 170.696000] [smp_apic_timer_interrupt+117/128] smp_apic_timer_interrupt+0x75/0x80
Jun 6 22:06:53 bollard kernel: [ 170.696000] [apic_timer_interrupt+40/48] apic_timer_interrupt+0x28/0x30
Jun 6 22:06:53 bollard kernel: [ 170.696000] [default_idle+0/96] default_idle+0x0/0x60
Jun 6 22:06:53 bollard kernel: [ 170.696000] [native_safe_ha...

Regarding comment #26, the correct syntax is:

Option "DisableIRQ" "true"

Removing Edgy task.

Removing dapper milestone.

J''ai le même problème, ma clé wifi usb (chipset ralink rt73) fige le pc
dès qu'on la branche à un port usb c'est très énervant !!!

Cela vient du driver qui est instable et gel le pc la preuve j'ai réussi à la faire fonctionné parfaitement sous la distribution BackTrack 2

Changer le driver !!-

Je suis sous Ubuntu 7.04

--------------------------------------------------------------------------------

I have the same problem, my key wifi usb (chipset ralink rt73) solidifies the PC
as soon as one connects it with a port usb it is very irritating!!!

That comes from the driver which is unstable and freezing the PC the proof I succeeded in making it functioned perfectly under the distribution BackTrack 2

To change the driver!! -

I am under Ubuntu 7.04

I can confirm this as well, I have a belkin rt73 usb card and apon insertion it freezes my pc, on reboot, it freezes with a kernel panick, I was dissapointed and removed gutsy gibbon after this problem.
I look forward to a fix soon
defcon

Confirmed. I use CNet Wireless-G PCI 54 Mbps 802.11g, WPA/AES/WPA2 which is rt2500 based. Networks are detected in network-manager, and I am able to connect to non-encrypted networks. However, connecting to encrypted networks freezes the computer totally (hard reboot is the only option, ctrl+alt+backspace does nothing). Seems not to be a network-manager bug, this also happens when using the old method of connecting to the network, using "network" in the system->administration menu. a sudo ifup wlan0 freezes the computer in the same manner.

Still buggy on encrypted wlan networks (WEP)

Hello,

in Gutsy tribe 5 no problems for me. My two cards (rt2500 and rt61 based) work 'out of the box'. Seems that the new rt2x00 driver (rt2500pci and rt61pci) are used instead legacy drivers (rt2500 and rt61).

Thank you!

Hi,

I tried Gutsy tribe 5 with Edimax - EW-7128g (rt61) and it hangs the PC.

In Feisty Fawn, Network Manager doesn't present options to set WPA AES authentication. I tried a lot of possible solutions i found in foruns and nothing work. One solution i found here (http://howto.landure.fr/gnu-linux/ubuntu-feisty-fawn-1/hardware-support-for-ubuntu-feisty-fawn/easy-wpa-with-ralink-rt2400-rt2500-rt2570-rt61-and-rt7-on-ubuntu-feisty-fawn) that basically is to use a backported kernel from Gutsy, it hangs my PC :(

Basically I can't use my brand new wireless card! :(

No net for me, except in Windows of course.

THe same problem seems to occur with the new rt2x00 drivers (or at least rt61pci) in Gutsy. See bug #68810

I have the same issue with a Linksys WMP54G connecting to a WPA access point using rt61 driver on Ubuntu Feisty.

Installing the latest serialmonkey version of rt61 appears to eliminate the lock-up issue (i.e. it looks like they have this problem fixed). However (and this could well be a serialmonkey, not Ubuntu issue) it ONLY works if I first connect to the AP with NO security, then take the connection (and router) down and back up with WPA enabled. Connecting using WPA without first connecting in unsecure mode fails (iwlist scan can see it, but signal quality is 0/100, and dhcp fails).

I just installed tribe 5 using my belkin rt73, and on boot it hangs my pc, and i am unable to log the output, and do not have a digital camera, this has nothing to do with the the serial monkey drivers, without them installed the pc still freezes apon insertion of the card and I recieve a kernel panick, since I do not have a camera and could not supply a log I uninstalled gutsy tribe 5 untill a bug fix.

This Should be marked as critical and be added to the new tribe 5 kernel, this bug effects my whole company and many friends that use the ralink chipsets

Total hang on AMD64 Gutsy Tribe 5. Only works if a hardline is inserted if i remove it and connect to any wifi network it hangs.
Syslog reports not much only that it crashes after step 3 of NetwrokManager

Iv'e been able top use the driver twice for brief periods of time, but then it stops working with the message "rt61pci->rt61pci_tx: Error - Arrived at non-free entry in the non-full queue"

Most of the time, after the card connects the computer freezes. If it's set to auto in interfaces, the system won't boot and the the last line written to syslog will be " ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready"

Another related post

[rt61] Lockups running Feisty on x86-64 https://bugs.launchpad.net/bugs/90243

This is a real pain. It sorts itself out if you change the config in 'Network Settings' but having to do it every few minutes is not feasable.

I agree, this problem needs to be fixed immediately or asap, I wonder if the
kernel team even knows how to fix it??

On 9/18/07, figjam <email address hidden> wrote:
>
> Another related post
>
> [rt61] Lockups running Feisty on x86-64
> https://bugs.launchpad.net/bugs/90243
>
> This is a real pain. It sorts itself out if you change the config in
> 'Network Settings' but having to do it every few minutes is not
> feasable.
>
> --
> Ralink Wireless legacy drivers (rt2500 rt61 rt73 rt2570) USB/PCMCIA/PCI
> hangs PC
> https://bugs.launchpad.net/bugs/34902
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Are you sure you're using legacy drivers in gutsy? AFAIK all the rt chipsets are nowadays supported by the rt2x00 project drivers instead, without eg. Network Manager wouldn't work.

The real problem as I see it is that the current 2.0.4 version from July should be upgraded to the latest 2.0.8 to have actual working functionality.

Sorry, forgot to add the link. The newest rt2x00 drivers for rt2400, rt2500, rt61, rt73 and rt2570, 2.0.8, are here:
http://git.kernel.org/?p=linux/kernel/git/linville/wireless-dev.git;a=shortlog;h=rt2x00

Currently gutsy has 2.0.4.

Timo,
Good to know, and what is the best way to implement the newest 2.0.8 since
it is not installed? Is there a patch available?

On 9/27/07, Timo Jyrinki <email address hidden> wrote:
>
> Sorry, forgot to add the link. The newest rt2x00 drivers for rt2400,
> rt2500, rt61, rt73 and rt2570, 2.0.8, are here:
>
> http://git.kernel.org/?p=linux/kernel/git/linville/wireless-dev.git;a=shortlog;h=rt2x00
>
> Currently gutsy has 2.0.4.
>
> --
> Ralink Wireless legacy drivers (rt2500 rt61 rt73 rt2570) USB/PCMCIA/PCI
> hangs PC
> https://bugs.launchpad.net/bugs/34902
> You received this bug notification because you are a direct subscriber
> of the bug.
>

yea it seems there is a USB id issue/hardware conflict or flaw in the driver, its now patched for rt73 :) yay! hopefully ubuntu gutsy will update this
http://git.kernel.org/?p=linux%2Fkernel%2Fgit%2Flinville%2Fwireless-dev.git&a=search&h=rt2x00&st=commit&s=rt73

Hi,

I tried Ubuntu 7.10 Beta with a card Edimax - EW-7128g (rt61) and it still hangs the computer :(

i can confirm this issue in Gutsy Beta, the drivers do not work at all, even the serialmonkey drivers lock up the computer completely

oot@ion:~# uname -a
Linux ion 2.6.22-10-generic #1 SMP Wed Aug 22 08:11:52 GMT 2007 i686 GNU/Linux
root@ion:~# lsusb
Bus 004 Device 003: ID 050d:705a Belkin Components

Ok I just upgraded from Ubuntu Feisty to Ubuntu Gutsy Gibbon, now I am unable to use WPA AES encryption, if I even attempt to connect with it, my system panics instantly with flashing caps/scroll lock. I am able to connect to wep perfectly with this driver, but as you know wep security is nonsecurity which id rather not get my internet stolen...

Here are the logs of the event, let me know what else is needed to figure out what the issue is to help fix it.

defcon

Here is the Gutsy modules I have blacklisted:
blacklist rt73usb
blacklist rt2500usb
blacklist rt2x00usb
blacklist rt2x00lib
blacklist rfkill
blacklist crc_itu_t
blacklist input_polldev

Here is a grep'd lsmod for rt*
root@ion:~# lsmod | grep rt
rt73 214400 0
agpgart 35016 3 drm,intel_agp
parport_pc 37412 1
parport 37448 3 ppdev,lp,parport_pc
iTCO_vendor_support 4868 1 iTCO_wdt
usbcore 137864 5 rt73,usbhid,ehci_hcd,uhci_hcd

Here is my messages log:
Sep 27 13:47:46 ion kernel: [ 28.769487] apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac)
Sep 27 13:47:46 ion kernel: [ 28.769495] apm: disabled - APM is not SMP safe.
Sep 27 13:47:46 ion kernel: [ 28.983759] AppArmor: Registered secondary security module: capability.
Sep 27 13:47:46 ion kernel: [ 28.983767] Capability LSM initialized as secondary
Sep 27 13:47:47 ion dhcdbd: Started up.
Sep 27 13:47:47 ion kernel: [ 29.171768] Bluetooth: Core ver 2.11
Sep 27 13:47:47 ion kernel: [ 29.171944] NET: Registered protocol family 31
Sep 27 13:47:47 ion kernel: [ 29.171949] Bluetooth: HCI device and connection manager initialized
Sep 27 13:47:47 ion kernel: [ 29.171954] Bluetooth: HCI socket layer initialized
Sep 27 13:47:47 ion kernel: [ 29.190285] Bluetooth: L2CAP ver 2.8
Sep 27 13:47:47 ion kernel: [ 29.190292] Bluetooth: L2CAP socket layer initialized
Sep 27 13:47:47 ion kernel: [ 29.248381] Bluetooth: RFCOMM socket layer initialized
Sep 27 13:47:47 ion kernel: [ 29.248530] Bluetooth: RFCOMM TTY layer initialized
Sep 27 13:47:47 ion kernel: [ 29.248535] Bluetooth: RFCOMM ver 1.8
Sep 27 13:47:48 ion kernel: [ 30.419827] [drm] Initialized drm 1.1.0 20060810
Sep 27 13:47:48 ion kernel: [ 30.426794] ACPI: PCI Interrupt 0000:00:02.0[A] -> GSI 16 (level, low) -> IRQ 17
Sep 27 13:47:48 ion kernel: [ 30.429668] [drm] Initialized i915 1.6.0 20060119 on minor 0
Sep 27 13:47:58 ion kernel: [ 40.906457] NET: Registered protocol family 10
Sep 27 13:47:58 ion kernel: [ 40.906752] lo: Disabled Privacy Extensions
Sep 27 13:47:58 ion kernel: [ 40.906996] ADDRCONF(NETDEV_UP): eth0: link is not ready
Sep 27 13:50:26 ion kernel: [ 188.777697] usbcore: deregistering interface driver rt2500usb
Sep 27 13:51:25 ion kernel: [ 247.787304] usbcore: deregistering interface driver rt73
Sep 27 13:51:25 ion kernel: [ 247.787495] <=== rtusb exit
Sep 27 13:52:51 ion kernel: [ 332.859548] rtusb init ====>
Sep 27 13:52:51 ion kernel: [ 332.949013] idVendor = 0x50d, idPr...

I can confirm this issue in Gutsy Beta, too.
If I try to connect to a WPA encrypted network, the whole system hangs and the computer needs a hardreboot.
This happens after a upgrade to Gutsy.

A WPA connection shouden't lockup a running system...

Confirmed here too.
Asus asus wl-107g PCMCIA with Ralink RT2500 chipset working flawlessly from breezy to feisty.

uname -a
Linux yeti 2.6.22-12-generic #1 SMP Sun Sep 23 18:11:30 GMT 2007 i686 GNU/Linux

Plugging the card in brings the system to completely hangs, no tty access, and needs a hard reboot. Relevant parts of kern.log:

Sep 29 15:44:50 yeti kernel: [ 419.828000] pccard: CardBus card inserted into slot 1
Sep 29 15:44:51 yeti kernel: [ 420.256000] PCI: Enabling device 0000:06:00.0 (0000 -> 0002)
Sep 29 15:44:51 yeti kernel: [ 420.256000] ACPI: PCI Interrupt 0000:06:00.0[A] -> GSI 18 (level, low) -> IRQ 17
Sep 29 15:44:51 yeti kernel: [ 420.256000] PCI: Setting latency timer of device 0000:06:00.0 to 64
Sep 29 15:44:51 yeti kernel: [ 420.384000] ieee80211_init: failed to initialize WME (err=-17)
Sep 29 15:44:51 yeti kernel: [ 420.396000] iwlwifi_rc80211_simple: Unknown symbol iwlwifi_ieee80211_rate_control_unregister
Sep 29 15:44:51 yeti kernel: [ 420.396000] iwlwifi_rc80211_simple: Unknown symbol iwlwifi_sta_info_put
Sep 29 15:44:51 yeti kernel: [ 420.396000] iwlwifi_rc80211_simple: Unknown symbol iwlwifi_sta_info_get
Sep 29 15:44:51 yeti kernel: [ 420.396000] iwlwifi_rc80211_simple: Unknown symbol iwlwifi_ieee80211_rate_control_register
Sep 29 15:44:51 yeti kernel: [ 420.400000] wmaster0: Selected rate control algorithm 'simple'
Sep 29 15:44:51 yeti kernel: [ 420.840000] ADDRCONF(NETDEV_UP): wlan1: link is not ready
Sep 29 15:45:57 yeti kernel: [ 486.348000] ADDRCONF(NETDEV_UP): wlan1: link is not ready
Sep 29 15:46:26 yeti kernel: [ 515.324000] r8169: eth0: link down
Sep 29 15:46:26 yeti kernel: [ 515.324000] ADDRCONF(NETDEV_UP): eth0: link is not ready
Sep 29 15:48:57 yeti kernel: Inspecting /boot/System.map-2.6.22-12-generic
Sep 29 15:48:57 yeti kernel: Loaded 25467 symbols from /boot/System.map-2.6.22-12-generic.
Sep 29 15:48:57 yeti kernel: Symbols match kernel version 2.6.22.
Sep 29 15:48:57 yeti kernel: No module symbols loaded - kernel modules not enabled.

Info towards the rt2500 problem

The rt2500 driver for a PCI card
Network controller: RaLink RT2500 802.11g is without problem under Feisty on a Desktop system,
kernel 2.6.20-16-generic

BUT is troublesome on a Avertec 3200 laptop with a AMD K7 processor support:
powernow_k8 16064 0
cpufreq_stats 7360 0
cpufreq_userspace 5408 0
cpufreq_ondemand 9228 1
freq_table 5792 3 powernow_k8,cpufreq_stats,cpufreq_ondemand
cpufreq_powersave 2688 0
cpufreq_conservative 8200 0
-------

When hald tries to configure this intermal wireless card on bootup, there is near full processor utilization, and all else slows drastically, as others have reported. This situation is cured by:
$ sudo ifconfig ra0 down
or bypassed by blacklisting rt2500 so it is not loaded on boot up.

A path to a functional work around has been accidentally discovered, through not understood at all.
To achieve some wireless support, a D-link PCMCIA wireless card was tested. Its insertion drives loading of:
(from lsmod output)
ath_rate_sample
ath_pci
wlan 204868 4 wlan_scan_sta,ath_rate_sample,ath_pci
ath_hal 192592 3 ath_rate_sample,ath_pci

Surprisingly the, blacklisted rt2500 also loaded, with
$ ifconfig
reporting both ra0, ath0 and wifi0 blocks, For reasons obscure to me wifi0 always appears with ath0,
even on Systems without a Ralink card.
If someone can explain that it might apply towards the rt2500 problem

Most IMPORTANT, the concurrent rt2500 loading does not cause the previously mentioned resource drain.
This cooperativity only appears necessary during the initial r2500 + hardware setup phase.
Because the positive effect was retained even after:
$ sudo modprobe -r ath_rate_sample
$ sudo modprobe -r ath_pci
which unloads all ath related drivers, with ifconfig showing disappearence of ath0 and wifi0 blocks
The PCMCIA card can also be removed.

Subsequently:
$ sudo ifup ra0
with specification of essid and encryption key,
DOES establish the wireless connection and services were fine.

If some further tests,
$ sudo modprobe ath_pci
$ sudo modprobe ath_rate_sample
without D-link PCMCIA card insertion had the same beneficial effects,
when done before
$ sudo modprobe rt2500

/var/log/messages provides no usefull information at all, just the expected reports on hardware activation.oot

If I try removing and reinstalling drivers during a single bootup session the freeze situation occurs.
Again this is alleviated fully once there can be entered:
$ sudo ifconfig ra0 down

To summarize, on this paricular Averatec platform, setup of the RALINK wireless using rt2500 driver is facilitated by prior loading drivers supporting the PCMCIA card:
$ cardctl ident 0
  product info: "Atheros Communications, Inc.", "AR5001-0000-0000", "Wireless LAN Reference Card", "00"
  manfid: 0x0271, 0x0012
  function: 6 (network)

THough lacking sophistication in COMM code, I would be happy to interact with someone(s) ath_pci and rt2500 driver knowledgeable, to try to unravel these interactions/problem\

Well quite a surprise for me today.

I got so fed up with it all, I decided to dump network manager and go back to the 'old way' by just hacking the configs. (since the files were already in /etc/networks) i did not touch them.

I uninstalled network-manager and network-manager-gnome and rebooted.

After a reboot, I noticed that the wireless driver had started to work again. The first time since the issue a few weeks ago.

Out of curiousity, I checked out System -> Administration -> Network and lo and behold, the network icon was back to wireless and activated. (no idea why network manager is still here..)

I had an issue with the hard wired link (eth0) though. This is back to the main issue I had when I first got the machine.

I reinstalled network-manager and network-manager-gnome and everything works for me now. Even eth0 and wlan.

Glad (for me at least) that my problem is resolved.

Now to see whether the machine locks up after a while.

http://ubuntuforums.org/showthread.php?t=563547

has anyone checked this workaround?

I can confirm this issue in Gutsy Beta, too.
 If I try to connect, the whole system hangs and the computer needs a hardreboot.

lspci: 00:0d.0 Network controller: RaLink RT2561/RT61 rev B 802.11g

this happened in the 7.04, but it stopped to give error when the package
 linux-386.deb installed.

But in the 7.10 this does not solve nothing

A status update on this fix would be appreciated to us all, and a few questions im sure we all are wondering/waiting for...
Is this being worked on?
Is there a patch/solution?
Who is in charge of the compatibility/coding of this driver?
Will it be fixed before Gutsy is released?
Why has the ralink drivers not been working well in ubuntu for the past 5-6 releases?
--
We all love Ubuntu and unfortunately us users with belkin/ralink drivers can not see the full beauty and usability of this great new os, I know it is a goal/standard to make Ubuntu run straight out of the box for anything, if we could resolve this issue it would be more than appreciated, maintainers/dev's please search for ralink, rt73, belkin, and other problems because there should be none, we want this os to be grandparent friendly/new user friendly.
Thankyou & Best Regards,
Kyle Weller

Well done Kyle.

It is not just limited to ralink, rt73 & belkin, but seems to be rt61, rt2x00 drivers too. This is a heck of a lot of hardware.

The fact that it worked perfectly roughly 2 months ago indicates that something went bad in a build somewhere.

Still patiently waiting on a fixed solution too.

-f

Should we set a collective bounty here? So many affected people, everyone might give a few bucks to someone who finally improves the upstream drivers to make them work out-of-box and easily includable in modern Linux distributions like Ubuntu. Once it's done, the developer gets paid. Saw it at https://www.bountysource.com/ recently.

Good idea, but spending ~$10 on different hardware would solve the issue too. .

Yea Matthias, the bounty idea is a good idea, if a few hundred users donate
a dollar instead of a few spending 10 that could amount up... But I agree
with figjam as well, I could take back my card which I personally love other
than the "ubuntu" compatibility. Although this would defeat the "ubuntu
always free theory" But we could donate to the process/progress of its
growth. Ubuntu wants to yet be another poineer in the opensource mobile
revolution which is indeed another wireless feature, once we get these
simple *kinks* out, we can finally call ourselves a BIG contender against
the money grubbing proprietary companies. I have heard reports of PcLinuxOS
and some other distro's already have support without problems/out of the
box, although this is completely a guess and a thing I have seen browsing
other distro forum's. Ubuntu seems to just be lacking in certain areas at
the moment, but with its growth and promise to grow with dell and other
companies backing it we should see a few jobs fill up and improvements on
there way. Id personally knock all these hardware problems out at once by
taking a view of other distro's code and learning by example, im starting to
program and excited about being a future member in the open source
development Community. I would love to help your issues as well as my own,
hopefully we can push this through, and get some stat updates because I know
the Ubuntu Community as a Strong Collective on knowledge can solve any
problem they put their minds to ;)
Thankyou & Best Regards
Kyle Weller
P.S. Lets work together and Make this OS grandma compatibile :)

On 10/3/07, figjam <email address hidden> wrote:
>
> Good idea, but spending ~$10 on different hardware would solve the issue
> too. .
>
> --
> Ralink Wireless legacy drivers (rt2500 rt61 rt73 rt2570) USB/PCMCIA/PCI
> hangs PC
> https://bugs.launchpad.net/bugs/34902
> You received this bug notification because you are a direct subscriber
> of the bug.
>

compatible*

On 10/3/07, d e f c o n <email address hidden> wrote:
>
> Yea Matthias, the bounty idea is a good idea, if a few hundred users
> donate a dollar instead of a few spending 10 that could amount up... But I
> agree with figjam as well, I could take back my card which I personally love
> other than the "ubuntu" compatibility. Although this would defeat the
> "ubuntu always free theory" But we could donate to the process/progress of
> its growth. Ubuntu wants to yet be another poineer in the opensource mobile
> revolution which is indeed another wireless feature, once we get these
> simple *kinks* out, we can finally call ourselves a BIG contender against
> the money grubbing proprietary companies. I have heard reports of PcLinuxOS
> and some other distro's already have support without problems/out of the
> box, although this is completely a guess and a thing I have seen browsing
> other distro forum's. Ubuntu seems to just be lacking in certain areas at
> the moment, but with its growth and promise to grow with dell and other
> companies backing it we should see a few jobs fill up and improvements on
> there way. Id personally knock all these hardware problems out at once by
> taking a view of other distro's code and learning by example, im starting to
> program and excited about being a future member in the open source
> development Community. I would love to help your issues as well as my own,
> hopefully we can push this through, and get some stat updates because I know
> the Ubuntu Community as a Strong Collective on knowledge can solve any
> problem they put their minds to ;)
> Thankyou & Best Regards
> Kyle Weller
> P.S. Lets work together and Make this OS grandma compatibile :)
>
> On 10/3/07, figjam < <email address hidden>> wrote:
> >
> > Good idea, but spending ~$10 on different hardware would solve the issue
> >
> > too. .
> >
> > --
> > Ralink Wireless legacy drivers (rt2500 rt61 rt73 rt2570) USB/PCMCIA/PCI
> > hangs PC
> > https://bugs.launchpad.net/bugs/34902
> > You received this bug notification because you are a direct subscriber
> > of the bug.
> >
>
>

the upstream rt2x00 team accept donations. i have made a donation in the past.

maybe it is worth talking to the them to see what scale of donation would be needed to speed the project up.

Kyle

Could you please just reply through the website rather than by email?
Unfortunately some of the addresses on the replies could get harvested for spam.

Keep up the enthusiasm :-)

-figjam

I had the problem that my computer stops responding when I used my D-Link DWL-G122. The kernel tried to load the rt73usb driver. My solution was to compile and install the CVS snapshot from http://rt2x00.serialmonkey.com/rt73-cvs-daily.tar.gz . After blacklisting rt73usb, I was able to access my WPA protected WLAN using the wlan0 interface (manual configuration). NetworkManager didn't work but I guess that's a different problem with an unrecognized IF name.

Fixed with today's updates here.

which is the duplicate here? see https://bugs.launchpad.net/ubuntu/+source/linux-ubuntu-modules-2.6.22/+bug/129183

Patch made two days ago:

> * System freeze when bringing up rt2500pci interface
> - LP: #129183

Not fixed with todays updates here
Linux ion 2.6.22-13-generic #1 SMP Thu Oct 4 17:18:44 GMT 2007 i686 GNU/Linux

btw, I am running Gutsy Beta, Latest Updates, and I had tried to blacklist all ralink drivers as well as leaving them all allone, still not working, I get wmaster0 and wlan0 in iwconfig and my configuration is fine when using drivers from serialmonkey,
STILL DOES NOT WORK OUT OF THE BOX
Any fix would be greatly appreciated

:~ $ uname -a
Linux yeti 2.6.22-13-generic #1 SMP Thu Oct 4 17:18:44 GMT 2007 i686 GNU/Linux

Forgot to add to my previous post that I have not been doing any tweaking of any kind (using wlan).

rt73 doesnt work at all with latest gutsy
serialmonkey drivers for rt73 crash gutsy with wpa enabled.

Later that I brought up to date the Gutsy today Beta, for kernel 2.6.22-13-generic #1 SMP, wireless this functioning correctly and did not stop more so far.
But some information, as speed, is not available.
Already laptop gives to use mine perfectly!

With the latest updates, my ASUS WL-167G now seems to work perfectly. Well done, someone.

rt73 does not work in gutsy, I am providing attachments
ifconfig
eth0 Link encap:Ethernet HWaddr 00:13:20:6A:27:51
          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
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:16436 Metric:1
          RX packets:62 errors:0 dropped:0 overruns:0 frame:0
          TX packets:62 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:5514 (5.3 KB) TX bytes:5514 (5.3 KB)

wlan0 Link encap:Ethernet HWaddr 00:17:3F:C5:BF:91
          inet addr:192.168.2.3 Bcast:192.168.2.255 Mask:255.255.255.0
          UP BROADCAST MULTICAST MTU:1454 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

wmaster0 Link encap:UNSPEC HWaddr 00-17-3F-C5-BF-91-00-00-00-00-00-00-00-00-00-00
          UP BROADCAST RUNNING 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
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
iwconfig
$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wmaster0 no wireless extensions.

wlan0 IEEE 802.11g ESSID:"w00t31337"
          Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
          Retry min limit:7 RTS thr:off Fragment thr=2346 B
          Link Quality:0 Signal level:0 Noise level:0
          Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
          Tx excessive retries:0 Invalid misc:0 Missed beacon:0

lsusb:
Bus 004 Device 003: ID 050d:705a Belkin Components
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 001 Device 003: ID 046d:c016 Logitech, Inc. M-UV69a Optical Wheel Mouse
Bus 001 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
and an attached /var/log/messages

My system is a AMD dual core 32 bit bridge System with PCI rt2500 hardware.
Under Feisty, the wireless was fine using the rt2500 driver
the /etc/network/interfaces stanza is:
# auto ra0
iface ra0 inet dhcp
wireless-essid MyVerizonNetRouter
wireless-key 64bit_key
wireless-ap StationAddress

After performance was reliable I enabled
auto ra0
and with bootup I am usually online

Just installed Gutsy on a spare partition.
The System auto named the wireless wlan0, so I made ra0 --> wlan0
changes to the stanza above. Upon initial bootup ifconfig had both
wlan0 and wmaster0 blocks in addition to the standard lo
I could not connect to the wireless router.

To watch kernel messages, I set:
  tail /var/log/messages &

Went through numerous trials without acquiring the wireless router,
alternately using ndiswrapper, rt2500 and rt2500pci drivers.
With each failed trial I would:
ifdown wlan0
ifconfig wlan0 down
which cleared the ifconfig blocks except lo . Unloaded
modprobe -r Driver

Then restart:
modprobe Next_Driver
because the auto setup was wrong for reasons obscure
ifdown wlan0
ifconfig wlan0 down
ifup wlan0
which usually failed to get a station offer.

With all three drivers, there was a cogent report from:
iwlist wlan0 scan
though there were following failures with:
ifup wlan0

Finally a trial worked using the rt2500pci driver,
For reasons still obscure. And there is in progress an
apt-get update

Major point, if is worth going through trial like the above several times.

MarvS

On 10/6/07, Kyle Weller <email address hidden> wrote:
> btw, I am running Gutsy Beta, Latest Updates, and I had tried to blacklist all ralink drivers as well as leaving them all allone, still not working, I get wmaster0 and wlan0 in iwconfig and my configuration is fine when using drivers from serialmonkey,
> STILL DOES NOT WORK OUT OF THE BOX
> Any fix would be greatly appreciated
>
> --
> Ralink Wireless legacy drivers (rt2500 rt61 rt73 rt2570) USB/PCMCIA/PCI hangs PC
> https://bugs.launchpad.net/bugs/34902
> You received this bug notification because you are a direct subscriber
> of the bug.
>

marvstod, same issue with me, I get wmaster0 and wlan0 and am able to
iwlist scan but not connect to anything, anyone know how to fix this
for the rt73usb driver?
my lsusb
Bus 001 Device 003: ID 050d:705a Belkin Components
Thanks
Kyle Weller

The wmaster0 seems to be a bad guess,
as it was not resident during the successful CONNECT
That is why the sequence:
=========
ifdown wlan0
ifconfig wlan0 down
which cleared the ifconfig blocks except lo . Unloaded
modprobe -r Driver

Then restart:
modprobe Next_Driver
because the auto setup was wrong for reasons obscure
ifdown wlan0
ifconfig wlan0 down
ifup wlan0
===========
is desirable.

Incidental do:
$ lsmod | grep rt
to see the zoo of supporting dependent drivers.

MarvS

On 10/10/07, Kyle Weller <email address hidden> wrote:
> marvstod, same issue with me, I get wmaster0 and wlan0 and am able to
> iwlist scan but not connect to anything, anyone know how to fix this
> for the rt73usb driver?
> my lsusb
> Bus 001 Device 003: ID 050d:705a Belkin Components
> Thanks
> Kyle Weller
>
> --
> Ralink Wireless legacy drivers (rt2500 rt61 rt73 rt2570) USB/PCMCIA/PCI hangs PC
> https://bugs.launchpad.net/bugs/34902
> You received this bug notification because you are a direct subscriber
> of the bug.
>

After the latest updates my D-Link DWL-G122 works fine. It has the hardware version C1 and firmware version 3.00.

On my computer it only hangs the computer if I enable and disable the network repeatedly.
After changing /etc/network/interfaces I have had no problems (insert some sleeps)

On my thinkpad R31 the Ralink PCI-Card (driver: rt61pci) doesn't work with Gutsy.
When get updates the connection breaks every time.

Can someone tell how to fix this problem?

greez

its really not your problem to fix, its the kernel team or module
team's and it seems they have ignored the rt73 and r61pci for quite a
while now without a decent fix

...that's not what i want to hear.
removing network-manager doesn't solve the problem.

and yes:

modprobe -r rt61pci
modprobe rt61pci
ifdown wlan0
ifup wlan0

that helps - but that's not a quiet good solution...

wubuntu, that doesnt help with rt73... its a shame rt73 works in linuxos and fedora and not ubuntu... I am about to digg these issues up or something

yeah - it's also a shame that it works well in Feisty but not in Gutsy.

I can't understand this step backwards.

Ok, there a five days til Release-Day - I hope the developers will fix it!

btw: in pclinuxos my rt61 doesn't work....what a game of hazard :-)

@Javier:

confirmed: in Gutsy Tribe 5 the rt61pci works well.

Hi,

Good news, it's working!
I'm trying Gytsy Release Candidate (https://wiki.ubuntu.com/GutsyGibbon/RC) and I connected to my home access point with WPA AES without problems. It didn't hang!!!!
My wireless card is Edimax - EW-7128g (rt61).

Good work, thanks.

cannot confirm this...

still an issue with the belkin F5D7050 ver 3002 rt73, it does not work out
of the box, driver conflict

Had the same problem.
My solution was to blacklist rt2500usb and rt2x00usb and only
load rt73, as all of these claim to support the device (Hama Wireless LAN Stick 54 MBps)

my solution:

blacklist rt61pci and load rt61 (from serialmonkey) which i have installed now.

i also had to do this on my debian etch - it's not the solution that i expect from
ubuntu but it works now.

nevertheless, it's disappointing

yea, im running serialmonkey drivers myself with rt73usb blacklisted, for
some reason wpa with serialmonkey drivers is not working any longer so now
im back to insecure wep because it causes a complete system lockup, its
truly unfortunate I have seen these opensourced drivers not work in Ubuntu
for over a year, pre-feisty, when fedora, pclinuxos, gentoo and a few other
os's work fine out of the box with our cards. The people people reporting
the bugs is not all the people who have the problem, most people wont take
the time and report such a bug and they will Trash ubuntu and talk it down..

rt61pci is working for me now

anyone have a rt73 working with this? I havnt checked mine out yet, waiting
till I get home from work

Kyle Weller a écrit :
> anyone have a rt73 working with this? I havnt checked mine out yet, waiting
> till I get home from work

rt73 (legacy from cvs) are working.

rt73usb (from rt2x00 new driver), include with gutsy, are sources of
troubles (see bug #139070).
rt2x00 cvs from serialmonkey doesn't compile anymore on gutsy (because
of changes in API, made in linux 2.6.23).

So I think we need to close this bug for rt61 (and other legacy), and
follow bug #139070 for rt73usb.

rt73usb is NOT working Bus 004 Device 003: ID 050d:705a Belkin Components
F5D7050
just tried it this morning with latest updates....

On 10/15/07, Id2ndR <email address hidden> wrote:
>
> Kyle Weller a écrit :
> > anyone have a rt73 working with this? I havnt checked mine out yet,
> waiting
> > till I get home from work
>
> rt73 (legacy from cvs) are working.
>
> rt73usb (from rt2x00 new driver), include with gutsy, are sources of
> troubles (see bug #139070).
> rt2x00 cvs from serialmonkey doesn't compile anymore on gutsy (because
> of changes in API, made in linux 2.6.23).
>
> So I think we need to close this bug for rt61 (and other legacy), and
> follow bug #139070 for rt73usb.
>
> --
> Ralink Wireless legacy drivers (rt2500 rt61 rt73 rt2570) USB/PCMCIA/PCI
> hangs PC
> https://bugs.launchpad.net/bugs/34902
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Kyle Weller a écrit :
> rt73usb is NOT working Bus 004 Device 003: ID 050d:705a Belkin Components
> F5D7050
> just tried it this morning with latest updates....

Did you tried this ?
https://bugs.launchpad.net/ubuntu/+source/linux-ubuntu-modules-2.6.22/+bug/139070/comments/3

As I said previously, according to the title of this bug, we should add
comments about rt73usb to bug #139070 (this bug is about legacy driver).

yes I have tried this, I blacklisted those modules and renamed them, and I
still get a double wlan interface with wmaster0 and I can scan but not
connect to any access points, what could this be? serialmonkey drivers work
fine... but not the ubuntu drivers

I am wondering how one can go from a perfectly working serialmonkey set up in feisty to a totally broken (read hard lock) in gutsy ... what in the world is going on here devs. Talk to us and give us some good news about this being fixed.

With a Linux desktop under Feisty, rt2500.ko served and the channel
was automated ra0
Under Gutsy, rt2500pci proved to be functional and the channel was
automated wlan0
During testing, it is a good practice to first unload all of rt2500
rt2500pci rt61 rt73 rt2570:
$ sudo ifdown wlan0
$ sudo ifconfig wlan0 down
$ sudo modprobe -r CurrentTestDriver

Then test each one with
$ sudo modprobe TestDriver
Check auto actions with:
$ ifconfig
$ iwconfig
Even if the iwconfig default is wrong, at this point a first
functionality test can be done with:
$ iwlist wlan0 scan
You wireless router should be represented in the output.
If there are other neighboring stations with the same Address, this
can be a complication

Do
$ iwconfig --help
and
$ man iwconfig
to see how to do manually settings.
$ iwconfig
will display the default settings
You may need to do changes/choices with:
$ sudo iwconfig wlan0 essid YourRouterESSID
$ sudo iwconfig wlan0 ap WirelessStationAddress
Make sure the changes are set with:
$ iwconfig

$ sudo ifdown wlan0
just to clean any old stuff.
Check for compatibility of your settings with those in /etc/network/interfaces
Then hopefully your wireless router will pickup to:
$ sudo ifup wlan0

If it fails, try the next alternate driver.

MarvS
because the default setis sometimes wrong

On 10/19/07, sefs <email address hidden> wrote:
> I am wondering how one can go from a perfectly working serialmonkey set
> up in feisty to a totally broken (read hard lock) in gutsy ... what in
> the world is going on here devs. Talk to us and give us some good news
> about this being fixed.
>
> --
> Ralink Wireless legacy drivers (rt2500 rt61 rt73 rt2570) USB/PCMCIA/PCI hangs PC
> https://bugs.launchpad.net/bugs/34902
> You received this bug notification because you are a direct subscriber
> of the bug.
>

rt61pci crashes everytime using synaptic/apt-get...

My system is an HP Pavillion S7720 with buit-in RT73 USB wireless card.
When I installed Feisty, I downloaded and compiled the separate rt73 driver from serialmonkey and blacklisted the modules rt73usb, rt2570 and rt2x00lib that came with Ubuntu, following the advice on the Italian Ubuntu wiki. This has worked fine since. Forced by the presence of some legacy hardware, I am using WEP.

When upgrading to Gutsy, I followed the same procedure, this time using the CVS version of the legacy driver, without really thinking about it. Again, the network connection worked instantaneously, without any trouble.

Afterwards, I thought that it might have been worthwhile to try whether the drivers delivered with Gutsy would work as wel and that is why I came here - to see, that my way of working is probably still the best solution.

By the way, the firmware file (rt73.bin) delivered with the distrubution and located in /lib/firmware/2.6.20-16-generic/ is identical to the one that comes with the driver, so does not need to be replaced.

Menno Tjoelker

MennoT, yea I have the same card, usbid 050d:705a, it is a known problem
with that card that the rt2500 usb and the rt73 have the same device id, and
was a programming error on part of ralink, it is unforunate that this
problem isnt being fixed, or a simpler fix being issued.. If im wrong
please let me know or let me know what the exact issue is with these cards
and we can all work together on a fix...
Thankyou,
Kyle Weller

Bus 004 Device 003: ID 050d:705a Belkin Components still not working....
This is a tough card, there are four known versions of this card.
802.11g F5D7050 v.1xxxx Prism54
802.11g F5D7050 v.2xxxx rt2x00
802.11g F5D7050 v.3xxxx man: 050d dev: 705a rt2x00
802.11g F5D7050 v. 4001 ?
 ?
802.11g F5D7050 v.4xxxx man: 050d dev: 705c ZD1211

As you can see by the table there is only 2 known device ids. However v. 2xxxx is still believed to use the ralink chipset which is support under PCLinuxOS 2007. Version 4001of this card is unknown and the v. 40000 uses the ZD1211 chipset which is also support under PCLinuxOS 2007. If you haven't purchased this card yet but want to. Take extnreme caution in making sure there's a decent return policy at the store. As by looking at the box you may not know what version you will be stuck with.
Quick Glance Specs

Network Type: Wireless Ethernet - 11 Mbps IEEE802.11b,
Wireless Ethernet - 54 Mbps IEEE802.11g
Device Type: Network Adapter
Port Types: USB - Universal Serial Bus 1.0/1.1,
USB - Universal Serial Bus 2.0

Wireless Device
Number of Antennas: 1
Device Type: Network Adapter
Network Status Indicators: Link Status

Networking Standards
Wireless Security Features: WEP - 128-bit,
WEP - 64-bit
Features: Integrated Antenna
Speeds Supported: 54 Mbps
Network Architecture Supported: Wireless Ethernet - 11 Mbps IEEE802.11b,
Wireless Ethernet - 54 Mbps IEEE802.11g

Ports
Port Types: USB - Universal Serial Bus 1.0/1.1,
USB - Universal Serial Bus 2.0

Warranty
Warranty Information: Limited Lifetime Warranty

Yesterday i did make clean install of Gutsy using PXE, and i am trouble having to get my wireless card working. Computer where i installed is Compaq armada M700 and wireless adapter is Tekcomm NE-9428-g 54M using Ralink rt2500 chipset ( http://www.fsf.org/resources/hw/net/wireless/cards.html ). By default gutsy rt2500pci drivers the card did not work, so i tried using the old drivers (rt2500) by using this guide -> http://ubuntuforums.org/showpost.php?p=3595458&postcount=6. Still no go for the adapter. So currently i have no working wireless network connection :(

Some details:

passeli@pelikaani:/etc/default$ sudo lshw -C network
  *-network
       description: OEM
       physical id: 0
       version: 11Mbps Wireless LAN PC Card V-5
       slot: Socket 0
  *-network
       description: Ethernet interface
       product: 82557/8/9 Ethernet Pro 100
       vendor: Intel Corporation
       physical id: 9
       bus info: pci@0000:00:09.0
       logical name: eth0
       version: 09
       serial: 00:d0:59:0c:69:47
       size: 100MB/s
       capacity: 100MB/s
       width: 32 bits
       clock: 33MHz
       capabilities: pm bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=e100 driverversion=3.5.17-k4-NAPI duplex=full firmware=N/A ip=192.168.2.205 latency=66 link=yes maxlatency=56 mingnt=8 module=e100 multicast=yes port=MII speed=100MB/s

passeli@pelikaani:/etc/default$ sudo iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

irda0 no wireless extensions.

That's about all the information, because it seems that i cannot even get the driver working corretcly so that interface would show up.

If lshw indicates the device is a 11Mbs device, than it is _not_ a rt2500 device.
What does lspci indicate?

I have a rt73 and I can connect via a static address but not be able to
route to the internet, connect ping etc, when I switch the the serialmonkey
drivers I can connect fine with the same configuration

Any ideas why? and how I can make a static connection work with the rt73usb
driver?

lvD: What do you mean that it is not rt2500 device? Only information about wireless pcmcia card from Tekcomm are based on ralink rt2500 chipset.

Here is lspci info:

passeli@pelikaani:/etc/default$ lspci
00:00.0 Host bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (rev 03)
00:01.0 PCI bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge (rev 03)
00:04.0 CardBus bridge: Texas Instruments PCI1450 (rev 03)
00:04.1 CardBus bridge: Texas Instruments PCI1450 (rev 03)
00:07.0 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ISA (rev 02)
00:07.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01)
00:07.2 USB Controller: Intel Corporation 82371AB/EB/MB PIIX4 USB (rev 01)
00:07.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 03)
00:08.0 Multimedia audio controller: ESS Technology ES1978 Maestro 2E (rev 10)
00:09.0 Ethernet controller: Intel Corporation 82557/8/9 Ethernet Pro 100 (rev 09)
00:09.1 Serial controller: Agere Systems LT WinModem
01:00.0 VGA compatible controller: ATI Technologies Inc Rage Mobility P/M AGP 2x (rev 64)

Passeli:
lshw reports your device is 11Mbs, rt2500 devices are 54Mbs.
Furthermore, the reason why the driver isn't working is because even lspci cannot detect your card.
I don't know why lshw does report the card, but lspci doesn't, but the only thing I can conclude from this, is that the driver isn't to blame for this since the problem is in the hardware.
Is the device correctly plugged in? Aren't there irq conflicts?
Does your log indicate anything regarding hardware problems?

passeli@pelikaani:/etc/default$ cat /proc/interrupts
           CPU0
  0: 6172457 XT-PIC-XT timer
  1: 7074 XT-PIC-XT i8042
  2: 0 XT-PIC-XT cascade
  6: 5 XT-PIC-XT floppy
  7: 2 XT-PIC-XT parport0
  8: 3 XT-PIC-XT rtc
  9: 8 XT-PIC-XT acpi
 11: 98929 XT-PIC-XT uhci_hcd:usb1, yenta, yenta, ESS Maestro, eth0
 12: 414 XT-PIC-XT i8042
 14: 535989 XT-PIC-XT libata
 15: 0 XT-PIC-XT libata
NMI: 0
LOC: 0
ERR: 0
MIS: 0

Card is corretly plugged in, and it works in windows. Following text appears in log when ejecting and then inserting the card:
[42126.648000] pccard: card ejected from slot 0
[42133.812000] pccard: PCMCIA card inserted into slot 0
[42133.812000] pcmcia: registering new device pcmcia0.0

This is the only other information found in logs:

passeli@pelikaani:/etc/default$ dmesg | grep pcmcia
[ 47.164000] pcmcia: registering new device pcmcia0.0
[12631.004000] pcmcia: Detected deprecated PCMCIA ioctl usage from process: lshw.
[12631.004000] pcmcia: This interface will soon be removed from the kernel; please expect breakage unless you upgrade to new tools.
[12631.004000] pcmcia: see http://www.kernel.org/pub/linux/utils/kernel/pcmcia/pcmcia.html for details.
[37603.084000] pcmcia: registering new device pcmcia0.0
[42133.812000] pcmcia: registering new device pcmcia0.0
passeli@pelikaani:/etc/default$ dmesg | grep cardbus
[ 20.295662] PCI: Bus 2, cardbus bridge: 0000:00:04.0
[ 20.295718] PCI: Bus 6, cardbus bridge: 0000:00:04.1

How do i find out what chipset i have in my wireless network card?

What is the name of the windows driver?

Don't remember windows driver name, something generic mumbo jumbo. But went the hard way and opened the adapter casing :) Chipset inside is Atmel AT76C502A. It seems that it has linux drivers, but gutsy doesn't work out of box with the adapter card.

My Linksys WMP54G v4.1 (rt61) is now working perfectly on 7.10 using the instructions in the link below.

http://ubuntuforums.org/showthread.php?p=3830958#post3830958

Hope the rest of you see progress soon!

Bye!

My wireless worked fine under 2.6.20 kernels with the rt2500 driver.
Upon update to Gutsy, service was very poor with the recommended rt2500pci

So I installed the Feisty linux-image-2.6.20-16-generic package under Gutsy ,
and am connecting fine using its rt2500 driver under 2.6.20-16-generic bootups

MarvS

On Nov 24, 2007 2:38 PM, Mark Tiffany <email address hidden> wrote:
> My Linksys WMP54G v4.1 (rt61) is now working perfectly on 7.10 using the
> instructions in the link below.
>
> http://ubuntuforums.org/showthread.php?p=3830958#post3830958
>
> Hope the rest of you see progress soon!
>
> Bye!
>
>
> --
> Ralink Wireless legacy drivers (rt2500 rt61 rt73 rt2570) USB/PCMCIA/PCI hangs PC
> https://bugs.launchpad.net/bugs/34902
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Confirming issue on Gutsy 32bit & 64bit Ubuntu and kbuntu

Chpset Network controller: RaLink RT2561/RT61 rev B 802.11g

I also can confirm on Ubuntu Gutsy 32 bit:
Linux version 2.6.22-14-generic (buildd@terranova) (gcc version 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)) #1 SMP Tue Dec 18 08:02:57 UTC 2007
Using Linksys WUSB54GR with rt73 chipset.

I solved my problem downloading the cvs driver directly from serailmonkey:
http://rt2x00.serialmonkey.com/wiki/index.php/Downloads

Then i recompiled the dirver and reloaded the rt73 module, now it seems to work fine.

Hola,
FINALLY... this applies to RT73 based dongles or similar (my case: TP-LINK TL_WN321g)
Thanks to all of you, after months of trial and error, and so many pages read:
This is based on:
http://generacionlibre.es/?p=11#comments who based on:
http://terminusblog.wordpress.com/2007/08/04/instalacion-de-dispositivo-wifi-linksys-wusb54gc-en-ubuntu-feisty/

So this goes in English and adapted, sort of a HOWTO:
1) Install:
    sudo apt-get install build-essential linux-headers-`uname -r`
2)Download:
    sudo wget http://rt2×00.serialmonkey.com/rt73-cvs-daily.tar.gz
3) Unpack the previous tar.gz ("home" would be perfect)
3) Change to the following directory:
    cd /rt73-cvs-yyyymmddhh/Module (based on where you unpacked it)
4) Make:
   sudo make
      Just ignore the message:
    !!! WARNING: Module file much too big (>1MB)
    !!! Check your kernel settings or use ’strip’
5) sudo strip -S rt73.ko
6) sudo make install
7) Get rid off network manager:
    sudo aptitude purge network-manager
8) May or may not be necessary, to ease things??????
    sudo apt-get install rutilt
9) Turn off the wlan0 for a while:
    sudo ifconfig wlan0 down
10) Remove the following troublemakers:
    sudo modprobe -r rt73usb
    sudo modprobe -r rt2570
    sudo modprobe -r rt2500usb
    sudo modprobe -r rt2×00lib
11) Blacklist the above, this is a must, as pointed out by some of you, open an editor:
    sudo gedit /etc/modprobe.d/blacklist
12) Add to the end of the file:
    # Blacklist rt73usb, as it is a non-functional beta module which conflicts with the working rt73 module.
    blacklist rt73usb
    # Blacklist rt2570, as it causes conflicts with rt73
    blacklist rt2570
    # Other modules that break rt73
    blacklist rt2500usb
    blacklist rt2×00lib
13) Load the module:
    sudo modprobe -v rt73
14) Now you can play with RutilIT, click on menu: Applications/Internet/RutilIT...
or
15) Even better open interfaces:
      sudo gedit /etc/network/interfaces
16)Add the following lines (for auto DHCP) according to your personal set-ups, but make sure to block (mask using #) all other references to eth0 or similar, if not this WON'T work:
     #auto eth0
     #iface eth0 inet dhcp
    auto wlan0
    iface wlan0 inet dhcp
    pre-up ifconfig wlan0 up
    pre-up iwconfig wlan0 essid YOUR_SSID
    pre-up iwconfig wlan0 mode managed
    pre-up iwpriv wlan0 set AuthMode=WPAPSK
    pre-up iwpriv wlan0 set EncrypType=TKIP
    pre-up iwpriv wlan0 set WPAPSK=YOUR_PASS_KEY_IN_HEXADEC
Or (for manual DHCP)
    #auto eth0
    #iface eth0 inet dhcp
    auto wlan0
    iface wlan0 inet static
    address 192.168.1.2 (or what ever yours is)
    netmask 255.255.255.0 (or what .....)
    gateway 192.168.1.1 (or what .....)
    pre-up ifconfig wlan0 up
    pre-up iwconfig wlan0 essid YOUR_SSID
    pre-up iwconfig wlan0 mode managed
    pre-up iwpriv wlan0 set AuthMode=WPAPSK
    pre-up iwpriv wlan0 set EncrypType=TKIP
    pre-up iwpriv wlan0 set WPAPSK=YOUR_PASS_KEY_IN_HEXADEC
17) Save the file,
18) Reboot and you should be connected

Hasta pronto, let me know,
Fernando

I had terrible problems with my Edimax rt73 USB dongle (Bus 003 Device 002: ID 148f:2573 Ralink Technology, Corp.).

First I tried the trick of sudo modprobe -rv rt2500usb; sudo modprobe -rv rt73usb; sudo modprobe rt73usb

This got the networking working but it would then stop after a few minutes and then go into a stuck state if I tried to repeat the modprobe trick.

I have followed the instructions from https://bugs.launchpad.net/ubuntu/+bug/34902/comments/177 and it seems to have fixed it! The only oddity is that dmesg gives me a dozen or so lines that say NOHZ: local_softirq_pending 08 now. Any idea what this means?

I also miss nm-applet and it's nice graphical wireless strength meter :)

Raphael

Hola,
You may use RutilT instead of nm-applet...
Works the same way

you have a typo there, you use character × instead of x. rt2×00lib doesn't exist, so that should be rt2x00lib :)

you are right Savvas, it should have been:
 http://rt2x00.serialmonkey.com/rt73-cvs-daily.tar.gz
Sorry for the mistake.
Hasta pronto,
Fernando

already filed against the kernel, no need to keep open for Ubuntu.

Hola,
There was a typo, it should be:
http://rt2x00.serialmonkey.com/rt73-cvs-daily.tar.gz

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.

Hi Fernando,
I'm a new joiner and I would ask some help on your HowTo procedure. I've tried to apply it but unfortunately it doesn't work
in my case (TL-WN321G).
Maybe the problem is related to my /etc/network/interfaces file. Hereafter the content of my file:

#auto lo
#iface lo inet loopback
#auto eth0
#iface eth0 inet dhcp
auto wlan0
iface wlan0 inet dhcp
pre-up ifconfig wlan0 up
pre-up iwconfig wlan0 essid OmarWiFi
pre-up iwconfig wlan0 mode managed
pre-up iwpriv wlan0 set AuthMode=WPAPSK
pre-up iwpriv wlan0 set EncrypType=TKIP
pre-up iwpriv wlan0 set WPAPSK=***MY_PSWD_CODE_IN_HEXADEC***

As you can see I blocked entries according to your suggestions, but unfortunately it doesn't solve my problem.
Could you please help me on this?

Many thanks

This bug is still in Ubuntu 9.04. Common, just add rt2x00 from serialmonkey to the repository and ditch this stupid driver.

> This bug is still in Ubuntu 9.04. Common, just add rt2x00 from
> serialmonkey to the repository and ditch this stupid driver.

Well the in-kernel driver _is_ the rt2x00 driver.

But I assume you mean the deprecated legacy drivers instead,
those drivers have been removed from the rt2x00 project.
There was a call for maintainers for those drivers, but nobody
was interested in that job.

Ivo

The 18 month support period for Gutsy Gibbon 7.10 has reached its end of life -
http://www.ubuntu.com/news/ubuntu-7.10-eol . As a result, we are closing the
linux-ubuntu-modules-2.6.22 task.

For anyone still experiencing an issue with Jaunty could you run the following apport-collect command from a Terminal. It will gather and attach updated debug information to this report. Thanks.

apport-collect -p linux-image-2.6.28-11-generic 34902

Architecture: amd64
Dependencies:

DistroRelease: Ubuntu 9.04
HibernationDevice: RESUME=UUID=9e717d36-d848-40fe-beaa-78e240e0b20c
MachineType: Unknow Unknow
NonfreeKernelModules: nvidia
Package: linux-image-2.6.28-11-generic None [modified: /var/lib/dpkg/info/linux-image-2.6.28-11-generic.list]
PackageArchitecture: amd64
ProcCmdLine: root=UUID=e8f59002-8dbe-4f68-9454-1078c7c965b1 ro quiet splash
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.28-15.52-generic
Uname: Linux 2.6.28-15-generic x86_64
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin netdev plugdev powerdev pulse pulse-access pulse-rt scanner tape video

Architecture: amd64
Dependencies:

DistroRelease: Ubuntu 9.04
HibernationDevice: RESUME=UUID=9e717d36-d848-40fe-beaa-78e240e0b20c
MachineType: Unknow Unknow
NonfreeKernelModules: nvidia
Package: linux-image-2.6.28-11-generic None [modified: /var/lib/dpkg/info/linux-image-2.6.28-11-generic.list]
PackageArchitecture: amd64
ProcCmdLine: root=UUID=e8f59002-8dbe-4f68-9454-1078c7c965b1 ro quiet splash
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.28-15.52-generic
Uname: Linux 2.6.28-15-generic x86_64
UserGroups:

Hrm, the apport-collect command didn't seem to attach what I expected it to. Care to instead test the latest Karmic release since it contains a newer 2.6.31 based kernel and let us know your results. Assuming the issue remains, could you then try re-running apport-collect but use:

apport-collect -p linux 34902

Also, ISO CD images for Karmic can be found at http://cdimage.ubuntu.com/releases/karmic/ . Thanks!

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

Am Sa, 9.01.2010, 22:50 schrieb papukaija:
> We'd like to figure out what's causing this bug for you, but we haven't
> heard back from you in a while. Could you please provide the requested
> information? Thanks!
>
> ** Changed in: linux-source-2.6.22 (Baltix)
> Status: New => Incomplete
>
> --
> Ralink Wireless legacy drivers (rt2500 rt61 rt73 rt2570) USB/PCMCIA/PCI
> hangs PC
> https://bugs.launchpad.net/bugs/34902
> You received this bug notification because you are a direct subscriber
> of the bug.
>
>

I do not have a similar setup right now,
so I can no longer help you here.

--
MfG,

Stefan Sonnenberg-Carstens

IT Architect
- Project management
- System analysis, design and build
- Security and business continuity
- IT risk management

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!