HOWTO fix rt2500 in Hardy (bug #190515)

[HoellP]

Hi
I followed the tutorial, but I still got problems with the cvs driver.
It installed in the wrong directory, but after I copied it over manually it loads correctly. I can even scan for my ap. But when I try to establish a connection, I only get

Listening on LPF/wlan0/00:0d:f0:1b:8a:35
Sending on   LPF/wlan0/00:0d:f0:1b:8a:35
Sending on   Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
                                                                         [ OK ]

No connection at all.

lsmod |grep rt
rt2500                180704  1 
exportfs                6016  1 nfsd
parport_pc             36260  0 

dmesg
<nothing>

modinfo rt2500
filename:       /lib/modules/2.6.24-17-generic/extra/rt2500.ko
license:        GPL
description:    Ralink RT2500 802.11g WLAN driver 1.1.0 CVS 2008053108
author:         http://rt2x00.serialmonkey.com
srcversion:     DBA270178059CA932E313AE
alias:          pci:v00001814d00000201sv*sd*bc*sc*i*
depends:        
vermagic:       2.6.24.3 SMP mod_unload 586 
parm:           debug:Debug mask: n selects filter, 0 for none (int)
parm:           ifname:Network device name (default ra%d) (charp)

Any ideas what I could try?

Thanks

PS: I tried static IP as well, but no change.

[LostAndFound]

Hi and thanks for your instructions which solved the problem for me. I did have one glitch which I thought I'd point out in case it helps someone else out:

With Kernel 2.6.24-18-generic (on AMD64) I had to manually copy the module from:

/root/source/rt2500-cvs-2008060501/
to:
/lib/modules/2.6.24-18-generic/kernel/drivers/net/wireless/

I don't know why the built module didn't get placed here - it contained a version of rt2500.ko from an unsucessfully attempt to install the module the night before using method to install from https://bugs.launchpad.net/ubuntu/+s...00/+bug/183818, which gave a message to the tune of: invalid module format.

I also had problems when I first tried copying rt2500.ko to:
/lib/modules/2.6.24-18-generic/kernel/net/wireless
which was not the correct location.

Good luck! - and thanks again for the help provided in this post.

[wyley.r]

I have been using the Serialmonkey driver for the RaLink RT2500 card (lspci output: "00:09.0 Network controller: RaLink RT2500 802.11g Cardbus/mini-PCI (rev 01)") for about six months with no problems. Since upgrading to Hardy, however, the driver has behaved strangely. The rt2500 module apparently is deleted, or otherwise disappears, so that

$ sudo modprobe rt2500

reports that it can no longer find the module. This typically happens after a reboot -- but not predictably.

After re-installing via

$ sudo make install

the card works fine.

Does anyone know what changes there have been in Hardy that could produce this behavior? Why would my locally-compiled version disappear at random?

Thanks!

[Mikecore]

First I would like to thank you for providing me the solution to fix my rt2500pci "slow connection". As I was looking into the problem I found I was able to manually set the rate for my Linksys 802.11g card. And my slow connection went away. I guess I have a little different take on how to fix the issue. Instead of compiling a new driver just have the rate set before the card comes up. that does three things 1) you don't have to compile a new driver. 2) you don't have to compile the driver after every kernel upgrade. 3) its much faster to just add the lines

nano /etc/network/interfaces
and then add

pre-up ifconfig wlan1 down
pre-up iwconfig wlan1 essid "******" channel 11 rate 54M
pre-up ifconfig wlan1 up

worked really nice again thanks

[sixgun]

When trying to run make, if you receive erros, such as "no rule to make target" or "make: *** /lib/modules/2.6.24-19-generic/build: No such file or directory. Stop", you may need to create a symlink pointing to the appropriate header files. Paste and run the following code, and then try to run make.

ln -s /usr/src/linux-headers-`uname -r` /lib/modules/`uname -r`/build

[jackcy]

I had the same problem. I could manually change the wireless speed to 54M but after a reboot the connection only had 1M.

Thanks to SINternet I only added one line to the file /etc/rc.local before the exit 0:

/sbin/iwconfig wlan0 rate 54M

After a reboot the connection speed automatically was set to 54M.

[Drengur]

This does not seem to work for me. I had a flaky connection with the original driver. Now I do not seem to be able to receive DHCP offers from the router.

iwconfig seems to sometimes show me connected to the right router. However I receive no DHCP offers.

Most of the times the ESSID in iwconfig is just empty.

iwlist ra0 scanning provides me with two cells. One of which is the correct one. This tells me the wireless card works in some way.

And following these instructions I have had no luck reverting to the old driver.

I hope for a reply soon.

With regards,
Drengur

[Drengur]

Strike my last. I fiddled around with rmmod and modprobe and managed to get the old driver to work again. I followed jackcy's instructions and the connection is great and the applet works.

In my case the solution presented by parent is unnecessary, and does more harm than good, though this might not be the case with others.

Thanks jackcy

[Bert Mariën]

Have the same problem since Hardy.
I didn't try this solution (yet).

But in the mean time I can fix the bug till the next reboot with:

iwconfig wlan0 rate 54M fixed

Pity it just last till reboot.

[noname4444]

I had the same problem. I could manually change the wireless speed to 54M but after a reboot the connection only had 1M.

Thanks to SINternet I only added one line to the file /etc/rc.local before the exit 0:

/sbin/iwconfig wlan0 rate 54M

After a reboot the connection speed automatically was set to 54M.

Thank you so much. A single line added to that file fixed my internet speed!!!

I was afraid I was going to have to put windows back on there for a little bit...