rt61pci on Ubuntu Hardy fails to associate with access point

Live forum: http://rt2x00.serialmonkey.com/viewtopic.php?t=4827

mo-hog

02-06-2008 03:02:36

Hello all,

I have been working on this all (long) weekend and am still stuck. I'm sure that somebody here will call me an idiot, but I have been doing my best. I am trying to become an expert on this card overnight. I understand that the latest Ubuntu (hardy, 8.04) comes with a kernel that has the "new" 2x00 rt drivers. I'm also guessing that rt61pci is the "new" 2x00 driver for my card.

I filed this
https//answers.launchpad.net/ubuntu/+s ... tion/34884
and kept track of what I have done so far.

I am using Mythbuntu 8.04 and it comes with network-manager. Originally, I had the AP set to WPA2 and MAC address filtering, but I downgraded it to open and turned off the filtering. Clicking on the wireless AP doesn't work - it spins for a while and then reverts to the wired. I tried wicd (because somebody suggested it), but it sits on "Obtaining IP address..." until it times out.

I have read through so many webpages (some I have listed into the Launchpad report), including the FAQs, but I am concerned that a lot of them were prior to the 2x00 driver making it into the kernel and are out of date. I'm not sure whether I should be changing the driver and blacklisting the 2x00, or using the 2x00 driver with a different frontend.

I realise that you all have better things to do than support my issues, but I have donated $10 and intend to donate another $10 if someone here can help me get this working.

I deliberately chose this card because it is on the FSF page of fully-free cards. I was really hoping that it would just work with Ubuntu and network-manager, and I think that may be the case in the future (the new driver uses wireless-extensions that are needed by n-m?), but it was pretty disappointed by how difficult I have found it so far.

Thanks in advance for your help.

Aaron

--
FSF Associate Member 5632
http//www.fsf.org

dmanning

02-06-2008 05:00:01

I've got the same card running on a Hardy machine. Can't get it to connect with the 2.24 version of rt2x00 either. I haven't tried it with rt2x00.git, because I've been afraid that running a kernel without the ubuntu patches would break too many things.

I do know that the cvs version of the legacy driver works just fine, but won't support WPA through network-manager. You can use RutilT to configure WPA, but RutilT won't autoload and connect. You have to start the network manually every time you boot up.

This means you can either write a script to use iwconfig and iwpriv to connect (as is explained in the included README) or patch wpa_supplicant to work with the legacy driver. I *think* this would also get WPA to work with network-manager. Anyone know for sure?

Let me qualify the above. I assumed your chipset was an rt61 because you mentioned rt61pci. In your other thread you indicated your chipset was rt2500, which I know to work just fine with network-manager in ubuntu 8.04. Is your chipset the rt61, perhaps?

AdamBaker

02-06-2008 22:59:36

It is best to post the output of lspci to identify exactly what card you have and what driver it should be using, card model numbers can be unreliable at times. You can then use lsmod to determine what driver is actually loaded. rt61pci is indeed the rt2x00 driver for an RT61 based card.

Unfortunately the desire to push the more maintainable mac80211 wireless stack into Linux as quickly as possible to prevent a plethora of incompatible variants popping up has resulted in rt2x00 being added before it was really stable which will for a while make life difficult for end users.

Quoting some dmesg output might be helpful to indicate exactly what is going wrong and if there is likely to be a quick fix short of reverting to the older driver.

mo-hog

03-06-2008 09:19:04

Thanks so much to both of you for such quick replies!

I've got the same card running on a Hardy machine. Can't get it to connect with the 2.24 version of rt2x00 either. I haven't tried it with rt2x00.git, because I've been afraid that running a kernel without the ubuntu patches would break too many things. [...] This means you can either [...][/quote2bza8won]
I would prefer not to start compiling my own kernels, if that can be avoided. I haven't done it before and I'm not too sure how it would go. That is great news! It sounds as though I should be able to get it working with the legacy driver if all else fails ). I would prefer to use the beta drivers if I can get them working - it is probably more use to everyone to have people using the new codebase and should ease upgrading to the next Ubuntu versions. Sorry for the confusion - it is a RaLink RT2561/RT61 rev B 802.11g. I said that it was an rt2500 because this page here
http//rt2x00.serialmonkey.com/wiki/ind ... e=Hardware
listed my card under "rt2500".

It is best to post the output of lspci to identify exactly what card you have and what driver it should be using, card model numbers can be unreliable at times. You can then use lsmod to determine what driver is actually loaded. rt61pci is indeed the rt2x00 driver for an RT61 based card. Unfortunately the desire to push the more maintainable mac80211 wireless stack into Linux as quickly as possible to prevent a plethora of incompatible variants popping up has resulted in rt2x00 being added before it was really stable which will for a while make life difficult for end users.[/quote2bza8won]
Thanks - attached and attached. Yes, I have read that in a few places. I think (knowing very little) that it was probably the best option to allow focus to be on the new drivers.

Quoting some dmesg output might be helpful to indicate exactly what is going wrong and if there is likely to be a quick fix short of reverting to the older driver.[/quote2bza8won]
I appreciate the help. I have attached this as well. It looks as though it is timing out. I read something somewhere about adding some "Sleep 20" command somewhere; could this help me?

Thanks again to both of you (and anyone else who jumps in) - I really appreciate the help.

Zi7

03-06-2008 11:20:01

Just a quick tip to share my experience there are two different versions of the rt2x00 drivers available for Hardy Heron thru its package manager at the moment
[list1vzoogno][*1vzoogno]the "standard" version is included as part of the Ubuntu kernel modules -- that's the one loading automatically on your box. This one works, although it seems it has sensitivity/rate issues. If there's a fair distance between your access point and ralink antena, it might be worth trying the next one...[/*m1vzoogno]
[*1vzoogno]the "backport" version can be installed thru the package manager linux-backports-modules-[i1vzoogno]kernel_version[/i1vzoogno]-[i1vzoogno]architecture[/i1vzoogno] (once installed, the new rt2x00 modules will replace the standard ones). The rt61pci driver included in this package has better sensibility/rate. Although it has other little problems, like a clumsy monitor mode, device will stay idle if you bring it down and back up (need to remove and reload rt61pci module), etc, it might work for your own usage[/*m1vzoogno][/listu1vzoogno]
Ubuntu's network manager then works fine with the device. It should be able to connect fine.


Your dmesg logs appear to show an authentication failure
[code1vzoogno][ 7981.017421] wlan0: Initial auth_alg=0
[ 7981.017431] wlan0: authenticate with AP 00:1b:2f:3d:c5:c6
[ 7981.215448] wlan0: authenticate with AP 00:1b:2f:3d:c5:c6
[ 7981.415410] wlan0: authenticate with AP 00:1b:2f:3d:c5:c6
[ 7981.615370] wlan0: authentication with AP 00:1b:2f:3d:c5:c6 timed out[/code1vzoogno]
Although auth_alg=0 perhaps means no encryption...? (Sorry, too lazy to look at the code)
You might want to check if Ubuntu isn't using a past config for your network (when encryption was on). Right-click on the network manager applet and select "Edit wireless networks"; see if your network is there, if it is remove it to start afresh.

Hope this helps...

mo-hog

06-06-2008 07:17:33

Thanks,

Just a follow-up question (which doesn't mean that I have solved my main problem, yet!)
If I am using the rt61pci driver, does that mean that I have a card that needs proprietary firmware, despite my selecting it from the cards listed on
http//www.fsf.org/resources/hw/net/wireless/cards.html
I should probably let them know if the CNet CWP-854 is actually not fully-free. What a shame... I thought RMS would be proud of me!

AdamBaker

06-06-2008 20:33:36

Yes rt61 and rt73 do require firmware for which we don't have source. Ralink have however allowed that firmware to be distributed. AIUI the rt2500 cards also require firmware but in that case the firmware is held in ROM on the card so is less noticeable.

It is possible that someone will in the future attempt to reverse engineer the Ralink firmware to produce a free firmware version but there is less pressure to do so than in the case of the Broadcom cards for which the firmware can't be freely distributed (for which this activity has just started).

If someone ever does try to write a free firmware they probably need a good lawyer first to work out what is an allowable starting point as Ralink have included rt61 and rt73 firmware as streams of hex data in drivers they have released under the GPL.

At the moment Ralink are being more helpful than most suppliers and there is no pressing reason to want to modify the firmware so it seems best to avoid activities which might upset them.

mo-hog

07-06-2008 03:32:33


[list3ul4no58]
[*3ul4no58]the "backport" version can be installed thru the package manager linux-backports-modules-[i3ul4no58]kernel_version[/i3ul4no58]-[i3ul4no58]architecture[/i3ul4no58] (once installed, the new rt2x00 modules will replace the standard ones). The rt61pci driver included in this package has better sensibility/rate. Although it has other little problems, like a clumsy monitor mode, device will stay idle if you bring it down and back up (need to remove and reload rt61pci module), etc, it might work for your own usage[/*m3ul4no58][/listu3ul4no58]
Ubuntu's network manager then works fine with the device. It should be able to connect fine.
[/quote3ul4no58]
I tried installing "linux-backports-modules-2.6.24-16-generic" and it had no effect.


Your dmesg logs appear to show an authentication failure
You might want to check if Ubuntu isn't using a past config for your network (when encryption was on). Right-click on the network manager applet and select "Edit wireless networks"; see if your network is there, if it is remove it to start afresh.[/quote3ul4no58]
Nope - nothing in my wireless networks list.

Still can't connect. I may have a go at the legacy drivers (cross your fingers for me!)

Thanks again for your help.

mo-hog

07-06-2008 03:36:39

Yes rt61 and rt73 do require firmware for which we don't have source. Ralink have however allowed that firmware to be distributed. AIUI the rt2500 cards also require firmware but in that case the firmware is held in ROM on the card so is less noticeable.

At the moment Ralink are being more helpful than most suppliers and there is no pressing reason to want to modify the firmware so it seems best to avoid activities which might upset them.[/quote2qj5u29h]
Thanks for clearing that up, Adam. I can see your reasoning, but when buying hardware, I make an effort to make sure it is completely free (firmware included). Not only does that mean that I can run gNewsense on the machine, it means that the company sees there completely-free products sell better than the ones with binary firmware and may encourage them to move more products that way. I'm prepared to pay a bit more for a fully-free card and thought that I had done that in this case.

mo-hog

07-06-2008 04:21:21


I do know that the cvs version of the legacy driver works just fine, but won't support WPA through network-manager. You can use RutilT to configure WPA, but RutilT won't autoload and connect. You have to start the network manually every time you boot up.
[/quote3n9uacs9]
I followed the instructions in the README and received an error when I tried to load the module - apparently it wasn't in the correct format. I realise that it is borderline off-topic, but I thought it better to keep my difficulties together for now!

Please see the attached file for a copy-paste of my terminal session.

AdamBaker was there anything in the files that I attached that could suggest a "quick fix"?

Zi7

07-06-2008 11:10:01


[list365xey5a]
[*365xey5a]the "backport" version can be installed thru the package manager linux-backports-modules-[i365xey5a]kernel_version[/i365xey5a]-[i365xey5a]architecture[/i365xey5a] (once installed, the new rt2x00 modules will replace the standard ones). The rt61pci driver included in this package has better sensibility/rate. Although it has other little problems, like a clumsy monitor mode, device will stay idle if you bring it down and back up (need to remove and reload rt61pci module), etc, it might work for your own usage[/*m365xey5a][/listu365xey5a]
Ubuntu's network manager then works fine with the device. It should be able to connect fine.
[/quote365xey5a]
I tried installing "linux-backports-modules-2.6.24-16-generic" and it had no effect.
[/quote365xey5a]
I find it doubtful you are using a [b365xey5a]generic[/b365xey5a] kernel. Aren't you using a [b365xey5a]386[/b365xey5a] one (Intel 32 bits arch) instead? Please note you should use the exact same version of linux-image and linux-header package (architecture and version number).
By the way, Ubuntu has released a new official kernel (2.6.24-18) with contains working -- afaict -- rt2x00 drivers. Why not upgrade your kernel and try these out?

I followed the instructions in the README and received an error when I tried to load the module - apparently it wasn't in the correct format. I realise that it is borderline off-topic, but I thought it better to keep my difficulties together for now!

Please see the attached file for a copy-paste of my terminal session.[/quote365xey5a]
I tried the legacy rt61 yesterday (CVS) and it worked... Perhaps your error is only the result of compiling rt61.ko with wrong header files?
I would advise updating your system (kernel, modules, headers and other compilation related packages) and trying again. Although, as i said above, this should be enough to make rt2x00 drivers work on your computer...

dmanning

07-06-2008 21:09:53


I do know that the cvs version of the legacy driver works just fine, but won't support WPA through network-manager. You can use RutilT to configure WPA, but RutilT won't autoload and connect. You have to start the network manually every time you boot up.
[/quote2br3f3u3]
I followed the instructions in the README and received an error when I tried to load the module - apparently it wasn't in the correct format. I realise that it is borderline off-topic, but I thought it better to keep my difficulties together for now!

Please see the attached file for a copy-paste of my terminal session.

AdamBaker was there anything in the files that I attached that could suggest a "quick fix"?[/quote2br3f3u3]

mo-hog,

It looks to me like your kernel-headers and your actual kernel might not be the same version. Your headers look to be 2.24.17. Type 'uname -r' to see what version your kernel is. You have to compile the module under the same version headers as the kernel image you're running.

NB I got my rt61 card working with network-manager by using ndiswrapper. I'm just going to wait until the drivers are a little more stable.

mo-hog

15-06-2008 06:05:45


It looks to me like your kernel-headers and your actual kernel might not be the same version. Your headers look to be 2.24.17. Type 'uname -r' to see what version your kernel is. You have to compile the module under the same version headers as the kernel image you're running.[/quotea6mrtmil]
$ uname -r
2.6.24-17-generic
So it looks the same...

NB I got my rt61 card working with network-manager by using ndiswrapper. I'm just going to wait until the drivers are a little more stable.[/quotea6mrtmil]
That is a little unfortunate, but it's been a while now, so I'll take whatever gets it working! Is there a good guide or some easy steps that could help me through installing with ndiswrapper?

With any luck this will get easier as the beta drivers stabilise, thanks to all of your hard work!

mo-hog

15-06-2008 07:26:01

I just tried the rt61 legacy daily again but received the error
"mythbuntu@mythbuntu-server/usr/src/rt61-cvs-2008061501/Module$ sudo modprobe -v rt61
insmod /lib/modules/2.6.24-17-generic/extra/rt61.ko
FATAL Error inserting rt61 (/lib/modules/2.6.24-17-generic/extra/rt61.ko) Invalid module format"

mo-hog

21-06-2008 02:47:42

I tried to use ndiswrapper, but the CD and Ralink site do not have the INF and SYS files available - they only have an exe file. I tried using both unzip and wine to extract the file, but neither worked. Does anyone know where a .INF for the RT61 is available?

I just tried following https//help.ubuntu.com/community/WifiD ... RalinkRT61
and managed to get the module to compile and insert. Despite what the page says, it isn't necessary to change the latest version in order to get it to compile. It seems to be loaded (it appears in iwconfig), but following all of the setup steps gets me nowhere. I've been using Gnu/Linux full-time for about 5 years now; this is really showing me how far I have left to go!

dmanning

21-06-2008 15:43:50

mo-hog,

the .exe is a self-extracting archive. If you've got a windows partition around somewhere, run it. You'll find the .inf and .sys files you need in the directories that are created. Look in the "driver" subdirectory of the Ralink folder that is created.

Sorry you're having so much trouble with this.

mo-hog

22-06-2008 05:44:01

Hahaha....

The original exe was corrupt, but downloading it again and installing on a Windows machine (someone else's, I'm proud to say) meant that I could get the required files. I installed these with the ndiswrapper GUI and it all seemed to install properly. From then on, Network-Manager appears to be working fine - except that I have the same problem that I had to begin with It scans and finds the network, but it times out when trying to connect.

This led me to pull the card out and take it to somebody else's house, where I put it into a Windows desktop and tried it with both the drivers on the CD and the ones from the Ralink website. Surprise surprise, it sees the network but times out when trying to connect. It seems that there is a problem with the actual card. The same is true when using the built-in Windows Wireless tools.

I must say that I really wasn't expecting that, seeing as it mostly seems to be working, but I can't think of any other explanation. I have contacted the company that sold it to me.

Thanks to everyone for your help so far - I will let you know if the new card works better!