RaLink rt2500 wireless card not seeing networks in edgy

Bug #64334 reported by seanh
30
Affects Status Importance Assigned to Milestone
linux-source-2.6.17 (Ubuntu)
Invalid
Undecided
Javier Jardón

Bug Description

Binary package hint: rt2500

Upgraded laptop to Edgy beta, RaLink rt2500 wireless card was working fine in Dapper, in Edgy, the card appears in System->Administration->Networking and can be configured, enabled, disabled, but it fails to see any wireless networks, even when they are present.

Segment from lspci:

02:00.0 Network controller: RaLink RT2500 802.11g Cardbus/mini-PCI (rev 01)

Apologies I'm not familiar with any commands that could be used to debug wireless card problems. I would be interested to know though -- if there is any more info I can provide please ask.

Revision history for this message
Chackal (chackal-jm) wrote :

It happens exactly the same here with the same card. I can configure it perfectly well if I introduce the ESSID manually.

Oh, and I also notice that the Internet can stop working for some minutes. Sometimes it comes back on its own, other times I have to deactivate and reactivate the card on the network configuration or by console.

Revision history for this message
Georg Duffner (mcduff) wrote :

i can confirm both of the described bugs (blindness and demency of the card), but the latter seems to depend on the signal strength (happens more often, when signal is low).
if anyone could tell me how to provide more infos, i'm willing to do so.

Revision history for this message
seanh (seanh) wrote :

I have found this same issue with numerous ralink-based cards on numerous different people's laptops now, in the final release of edgy. It seems like there is no way, with the new System-Administration-Networking GUI, to tell the card to scan for networks and provide a list.

I am not sure whether this is a bug with ralink chipsets in particular, or whether it's a bug in the GUI that affects all network cards (I don't have any non-ralink cards to test this with).

I can also confirm that if I enter the ESSID manually I can connect, and that if I run 'sudo dhclient ra0' from a terminal it can find dhcp networks and connect to them fine.

seanh (seanh)
Changed in rt2500:
status: Unconfirmed → Confirmed
Revision history for this message
Tarball (rjsurfing) wrote :

I can confirm the issues with Ralink/rt2500 based cards on Ubuntu 6.10. The reason is that 6.10 is shipped with a faulty driver that causes these problems. Usage of Wpa-supplicant is not possible either at this point as a workaround. Indeed the only way to get the card working with the default driver is to do 'sudo dhclient ra0' after every startup. Needless to say this is a pain. Well... there is good news. I solved this problem and it was not too hard (I am not a linux expert but I will post the steps I followed). To put it in simple words, you need to install a new (and better) driver. First you need to go to the rt2x00 webpage (http://2x00.serialmonkey.com) and go to the download section. There you look for one of the 2500-cvs-... drivers (tar) and download it. Then you follow these steps... that did it for me. After restarting the computer everything worked like a charm... internet connection at startup !!! I just used the same configuration in /etc/network/interfaces that I had in Ubuntu 6.06. Happily connected with WPA that is supported by the driver (like I said before, forget messing with wpa_supplicant, is a waste of time).

1. go to TERMINAL
2. go to directory where you downloaded the 2500-cvs...tar.gz
3. type: tar -xzf rt2500-cvs-daily.tar.gz
4. type: sudo apt-get install build-essential linux-headers-$(uname -r)
5. type: cd ./rt2500-cvs-*/Module
6. type: make
7. To test, type: sudo insmod rt2500.ko (all it does is telling me that it already exists)

Exit TERMINAL

1. Select: [System] – [Administration] – [Networking]
2. Find the wireless card, then Select  [Activate]

To finish up the install

1. go to TERMINAL
2. type: sudo ifdown ra0
3. type: sudo cp ~/rt2500-cvs-daily/Module/rt2500.ko /lib/modules/`uname -r`/kernel/drivers/net/wireless/
4. type: echo "alias ra0 rt2500" | sudo tee /etc/modprobe.d/rt2500

If you have similar success, feel free to post this on other boards or leave feedback here to help out other frustrated users. May the Force be with you :)

Revision history for this message
Chris Wagner (chris-wagner) wrote :

Hey mate, your link (http://2x00.serialmonkey.com/) does not seem to work. :,\

Revision history for this message
Tarball (rjsurfing) wrote :

You are right... it should be http://rt2x00.serialmonkey.com

Revision history for this message
revdjenk (revdjenk) wrote :

Averatec 3270-EH1 with rt2500

Edgy operates this way:
eth0 works fine in both live and installed
wifi no...
once hit 'enable connection' keyboard and mouse freeze, but not completely... I describe it as a 2-4 second stutter, with keyboard entry and mouse movements only in about a one second gap between these 'stutters.'

Feisty Herd4 (live mode)
I assume that wifi is enabled at boot - as boot-up was still in process 25 minutes later (with plain blue desktop showing and empty taskbar, and 'bouncing' K icon just beginning to show) as I have this same protracted boot (probably from the intermittant operation mentioned under Edgy) with Edgy if wifi is enabled at boot-up.

I have tried adding acpi=noirq to menu.lst in Edgy (from #48263) but that does not work.
Has anyone else had success with the above work-around?

Reporting this from another (desktop) machine...so I know that Feisty Herd4 CD is viable.

I can verify this same problem with other distros:
elive .6.1
Mepis 6.0
Knoppix 5.1.1
DreamLinux 2.2
Mandriva 2007

This wifi DOES work with elive .5... but not with Dapper...

If I can help with any testing...please contact me.

Revision history for this message
Javier Jardón (jjardon) wrote :

Hello seanh,

can you try Feisty and tell if you still have problems?

Changed in linux-source-2.6.17:
assignee: nobody → torkiano
status: Confirmed → Needs Info
Revision history for this message
Cyclops (rms) wrote :

With Feisty I can scan networks with an Asus W107-L

Revision history for this message
Javier Jardón (jjardon) wrote :

We are closing this bug report as it lacks the information, described in
the previous comments, we need to investigate the problem further.
However, please reopen it if you can give us the missing information and
feel free to submit bug reports in the future.

Changed in linux-source-2.6.17:
status: Needs Info → Rejected
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.