Ralink rt2400 / rt2500 / rt2570 / rt61 / rt73 do not work out of the box in Gutsy/Hardy

Thank you for taking the time to report this bug and helping to make Ubuntu better. I noticed an updated kernel, 2.6.22-11.32, was recently released. Can you try updating to this newer kernel and verify this bug is still an issue for you? Also, I just want to clarify that you do not see this problem when running Feisty correct? Thanks in advance!

The problem does not occur when running Feisty and when running Gutsy with Feisty kernel (2.6.20.x). The newest Gutsy kernel still generates problems with ralink card. The transfer rate is extremly low - 678 b/s - 1391 b/s.

I have the same problem when using gutsy. Under Feisty it's fine for me.

I have a ralink rt2500 based PCI card.

I've attached the output of lspci from feisty.

Using a WEP network set up by network manager (the first release this has 'worked' for me in - yay :)

I've a problem too.

I've tried today to install gutsy tribe 5 on my Fujitsu Siemens Amilo A 1630, with alternate iso.

But when textual installation program searches fot network interfaces, it find only the ethernet card and the IR. Feisty, instead, find and use ralink chipset during installation without any problem.

I've stopped installation of gutsy 'cause of this.

lspci command gives me this row about ralink card

00:0b.0 Network controller: RaLink RT2500 802.11g Cardbus/mini-PCI (rev 01)

If necessary, I'll install gutsy.

Will be the bug resolved in the final Gutsy release? It makes all rt2x00 cards useless with Ubuntu!

Well, it's not currently listed at https://launchpad.net/ubuntu/+milestone/ubuntu-7.10-rc
which means it will most likely not be fixed for the first release candidate.

I've finally tried gutsy.

ralink card is not recognized during installation, only cable, but when all was installed, after reboot my wireless card was correctly identified and configured.

Oh, this is just great, it's still not even worked on _and_ not on the RC list :(

Is it too late to add it to the list?

Ubuntu 7.10 released today with a serious regression - RALINK cards work no more. Great! :( And.. nothing can be done?

you can install the rt2400-source package and build the legacy driver with module-assistant. Don't forget to blacklist rt2400pci. This works for me (rt2500).

Ralink driver is under heavy development. If may be already solved, but I'm quite sure this can't be done (or is very hard to do) in this kernel version. You can try to compile newer version yourself.

The rt2x00 is not API compatible with the gutsy kernel.
I've tried recent (last week) rt2x00 kernels, the driver is still a lot slower than the legacy driver (100kB/s), although it does work with network-manager. I find myself always going back to the legacy driver.

You can also try to use ndiswrapper and Ralink's Windows drivers.
Just switched to ndiswrapper and it works (RT2500 based PCI card).

Is there legacy driver shipped with Gutsy (and blacklisted)? If so there is no problem, if not I don't get why it is not done this way. In Feisty new rt2x00 driver was present but blacklisted (brave one could try unstable driver) and every one were happy.

Hi guys,
        I finally got my onboard RT2500 card working under Gutsy on my Fujitsu-Siemens Amilo A1630. The drivers that come with gutsy didn't work and nor did ndiswrapper. However, the lastest CVS snapshot of seriualmonkey's driver (http://rt2x00.serialmonkey.com/rt2500-cvs-daily.tar.gz) worked great!

So, just download the file, untar, follow instructions in the README of the Module diretcory.

After you are done blackist the old drivers by adding these lines to /etc/modprobe.d/blacklist:

blacklist rt2500pci
blacklist rt2x00pci
blacklist rt2x00lib

Hope this helps!

I tried to install the driver for my rt2400 and was successful with the legacy. The next-generation one does not work.
http://rt2x00.serialmonkey.com/rt2400-cvs-daily.tar.gz

I would like to say that this new driver works (with rt2400 pcmcia card). Yes, it has problems like slow performance, falling connection, no signal strength reporting, errors and lockups on suspend, so it is unusable right now. But it works, it supports wireless extensions, it can scan air, it works with NetworkManager, it can handle WPA (both personal and enterprise). So please be patient, things are moving and they are on the right way. Even this is better than nothing you have when you need WPA.

Legacy driver can also be used with WPA, it's just a different manner of setting things up. You say it yourself, it's unusable right now. In the near future it will be usable, but not with Gutsy. The legacy drivers should also be included.

Anyone had any success with version 2.0.9-2 (available from the rt2x00-source package, from debian unstable)?

I've tried kernel 2.6.24-rc1 (driver is included here for first time, version 2.0.10) and there is no clearly visible progress in speed for me (I'm using WPA). But you can try to use Windows driver through ndiswrapper. It is fast, NetworkManager compatible (with WPA too) and even signal strength reporting works on rt2400 cards.

I vote for inclusion of legacy drivers in Gutsy. The user will have the choice between legacy and new driver by means of blacklisting (as in Feisty). Current status of the driver for rt2x00 cards is what makes me NOT upgrade to Gutsy.

I don't see your point. Legacy drivers ARE in Gutsy (thats what I'm using a this very moment):

rt2400-source - source for rt2400 wireless network driver: Version: 1.2.2+cvs20070219-3
rt2500-source - source for rt2500 wireless network driver: Version: 1:1.1.0-b4-4ubuntu1
rt2570-source - RT2570 wireless network drivers source: Version: 1.1.0+cvs20070219-2

I was not precise - my point is to ship both legacy and new rt2x00 modules with gutsy kernel (the way it was in feisty). By means of blacklisting user will have the choice to use NetworkManager compilant rt2x00 with poor performance (this can be default) or legacy one with weird configuration but with good performance. Compiling driver form rt2500-source with every kernel upgrade is rather unhandy.

I agree with Wodz, but I'd go one step further and say the legacy driver should be the default. There seems to be a consensus that the rt2x00 module is unusable, and I can't see any reason why users would want an unusable module as the default. It also seems to me that most users would not want to go out of their way to compile a module just so they can get wireless working properly, and many of them may not even know that option exists. I imagine that there are quite a few less experienced users out there who are not even aware that a solution is available, they just know that after the Gutsy upgrade the wireless connection on their PC is buggy and slow.

I followed the development of the rt2400/802.11b wireless drivers for a couple of years. Last I heard the drivers for the RaLink RT2400 did not work with the SMP version of any kernel and only worked with the UNI version of the kernel. Gutsy installs the SMP version of the kernel with no facility I can find to replace it with the uni kernel without connecting to the Net.....so I was screwed and had to get rid of Gutsy.

Xandros 4.0 includes/d both SMP and UNI versions of the kernel and one could switch between the two without having to download anything.

I'd rather get a good 802.11g wireless card that works well with Linux......but I have had to resort increasingly to Windows both for wireless networking and for video capture and processing. Having been on Linux exclusively for the past 6 years, moving back to Windows has been a disappointment. I just don't have time to frig around with Linux any more. ...and this issue is just one more example.

This will be retargeted towards the Hardy kernel once it is released. It's tagged this as "hardy-kernel-candidate" so that we make sure to retarget this report once the new release is out. However against the linux-source-2.6.22 package this is being marked as "Won't Fix" as it does not meet the criteria for a stable release update. To learn more about the stable release update process please refer to https://wiki.ubuntu.com/StableReleaseUpdates . Thanks!

My rt2400 card still does not work under Hardy Alpha 2. I hope the proper, WORKING driver will be set by default in the next release.

I'm guessing this is related, affects the rt73usb module also

https://bugs.launchpad.net/ubuntu/+source/linux-ubuntu-modules-2.6.24/+bug/180518

The bug affects also Ralink RT61 card. It does not work out of the box. It is needed to install another driver: http://ubuntuforums.org/showthread.php?p=3859034 to get it working.

The same problem with a slow connection with rt73 card has been reported by another user: https://bugs.launchpad.net/ubuntu/+source/linux-ubuntu-modules-2.6.22/+bug/134344 . Ralink cards should work out of the box in Hardy - it is needed to check which version of those drivers works correctly. The rt73 is known to work only with rt73-cvs-2007072709 version.

yes, I can confirm the rt73usb.ko driver does not work for "ANY RELEASE" never did, although the rt73 driver from here:
http://rt2x00.serialmonkey.com/rt73-cvs-daily.tar.gz
works fine. Wpa works great as well, unfortunately any wpa password longer than 20 characters crashes Ubuntu and locks up the box, oops, nevermind, just checked this forum thread:
http://rt2x00.serialmonkey.com/phpBB2/viewtopic.php?p=28063#28063
it seems the password length issue has been resolved for wpa with the rt73 driver from serialmonkey, basically here is how to install:
wget http://rt2x00.serialmonkey.com/rt73-cvs-daily.tar.gz
tar zxvf rt73-cvs-daily.tar.gz
cd rt73*
cd M*
make
sudo make install
sudo gedit /etc/modprobe.d/blacklist
append this to the end of the file:
# rt73 blacklisted drivers
blacklist rt2500usb
blacklist rt73usb
blacklist rt2x00usb
blacklist rt2x00lib
blacklist ipv6
now sudo /etc/init.d/networking restart and we shall be connected if /etc/network/interfaces file is configured correctly, here is an example of mine:
# WORKING STATIC AES/WPA CONFIG
#auto wlan0
#iface wlan0 inet static
#address 192.168.1.66
#netmask 255.255.255.0
#gateway 192.168.1.254
#pre-up ifconfig wlan0 up
#pre-up iwconfig wlan0 essid 2WIRE
#pre-up iwconfig wlan0 mode managed
#pre-up iwpriv wlan0 set Channel=9
#pre-up iwpriv wlan0 set AuthMode=WPAPSK
#pre-up iwpriv wlan0 set EncrypType=AES
#pre-up iwpriv wlan0 set WPAPSK=yourwpapasswd
#pre-up iwpriv wlan0 set TxRate=0

# WORKING DYNAMIC AES/WPA CONFIG
auto wlan0
iface wlan0 inet dhcp
pre-up ifconfig wlan0 up
pre-up iwconfig wlan0 essid 2WIRE
pre-up iwconfig wlan0 mode managed
pre-up iwpriv wlan0 set Channel=10
pre-up iwpriv wlan0 set AuthMode=WPAPSK
pre-up iwpriv wlan0 set EncrypType=TKIP
pre-up iwpriv wlan0 set WPAPSK=yourwpapasswd
pre-up iwpriv wlan0 set TxRate=0
mtu 1500
There we go rt73 working perfectly, now, lets watch and see if the Ubuntu developers can add this wonderful driver to Gutsy and Heron...
Kyle Weller

btw its working with this exact card:
Bus 001 Device 002: ID 050d:705a Belkin Components

oh and please stop by http://rt2x00.serialmonkey.com/phpBB2/viewtopic.php?p=28063#28063 and thank those developers for this :)

As I have stated in another bug report, 2.6.24 + rt2x00 cvs works flawlessly (good speed transfers, no lost connection, WPA encryption, working with NM) using an rt73 card. As Hardy will ship with 2.6.24 I think is just a matter of shipping with any recent build of rt2x00 and problem solved :)

Currently you can't even compile the old legacy rt2500 driver with module assistent, it fails with all kinds of errors. I can't get the rt2x00 cvs to compile either, the developer said I can't compile against the kernel in Hardy, as there are some new changes in the wireless git kernel that haven't made it in the normal kernel yet.

The poll shows that most of the problems with wireless networking are problems with ralink cards in Ubuntu.

POLL: What wireless chipset are you having a problem with in Gutsy?
http://ubuntuforums.org/showthread.php?p=4178322

I think that Bug #134660 and Bug #139070 are duplicates. Is it possible to merge them, in order to get a higher priority and more attention?

There seems to be a working version in the wireless git kernel tree, but still this bug doesn't get any attention from the developers.

Piotr, thanks for bringing that poll to attention, it sheds some light on things, here is another note... The serialmonkey drivers have always worked with these cards, not flawlessly in the past as they are now but the drivers in every last ubuntu release none of the cards worked out of the box when these serialmonkey drivers have been available for a few years. I am hoping that Gutsy will get a new modules package released with these fixed drivers and Hardy and every release after will be fixed. Lets make this an issue of the past and not repeat history.

I see that this bug's importance is set to medium, when there is plenty of duplicates of this bug and thousands of people effected which should increase its importance. I think a High importance or even critical importance would be more appropriate since this bug has plagued launchpad through every release of ubuntu and can be fixed simply by implementing the serial monkey drivers

I'm with Kyle here. I can't use my laptop at University because of this problem, since everytime the connection dies and I reboot the computer I can't connect to the wi-fi net anymore because the Uni system says I didn't disconnect (I have to click a disconnect link), so I'm still logged and will be kicked out automatically in, oh, 8 hours.

I think there's seems to be a lot of people with this issue... And as Kyle says, the fix doesn't seem like such a big deal (I wouldn't know, but I'm counting on you). Please, help us :)

Ok I have faith that this will be fixed soon, seen allot of activity with marking the duplicates of this bug, thanks in advance
Kyle

 I work for a high-school in Warsaw, Poland. We have more than 20 laptops with ASUS rt2500-based PCI cards we use in classrooms and was also affected by this bug. In previous Ubuntu versions, at least since 6.06 our WiFi cards worked great. But after upgrading to Gutsy WiFi stopped working properly.

The Network Manager shows all the available networks, but when we try to connect, at least to our WPA-protected (TKIP) network, it asks for the key and than tries to connect for about 30 seconds, but than fails.

As for now we've wrote a scripts that automatically builds a rt2500 driver from source on every newly installed system.

Is there some problem with your email? I have received 27 mails from you in the last half an hour!

Thanks, Joe.

> From: <email address hidden>
> To: <email address hidden>
> Date: Thu, 24 Jan 2008 20:36:33 +0000
> Subject: [Bug 134660] Re: Ralink rt2400 / rt2500 / rt2570 / rt61 / rt73 do not work out of the box in Gutsy/Hardy
>
> ** Description changed:
>
> - Ralink drivers are under heavy development. The legacy drivers should be
> - used in Ubuntu by default or the newest (next-generation) version BUT
> - ONLY when will offer the proper connection speed. Begginers won't fix
> - that bug because they won't know how to install that drivers with
> - module-assistant. Ralink cards should work out-of the box.
> -
> - The bug affects a lot of ralink-based cards so it's very important to be
> - fixed in Hardy!
> -
> -
> ===
> The poll shows that most of the problems with wireless networking are problems with ralink cards in Ubuntu.
> POLL: What wireless chipset are you having a problem with in Gutsy?
> http://ubuntuforums.org/showthread.php?p=4178322
> +
> + The bug occurs commonly and it's very important - and will be easy - to fix it.
> + ======================================
> +
> + Cards don't work because of the invalid drivers (extremely slow
> + connection, no connection, connection lost, lack of the wpa support)
> + included in Ubuntu.
> +
> + Work-around: To install the proper driver from serialmonkey.
> +
> + SOLUTION:
> + 1. Find out which version of a serialmonkey driver works properly with each ralink card.
> + 2. Implement ralink serialmonkey drivers in Ubuntu.
> +
> + http://rt2x00.serialmonkey.com/
> +
> + Most likely the newest CVS version of each ralink driver works
> + correctly.
> +
> ===
> + Please write which drivers are known to work and which are invalid.
> + ==
>
> -
> - The rt73 is known to work only with rt73-cvs-2007072709 version.
> - rt2400-source - source for rt2400 wireless network driver: Version: 1.2.2+cvs20070219-3
> - rt2500-source - source for rt2500 wireless network driver: Version: 1:1.1.0-b4-4ubuntu1
> - rt2570-source - RT2570 wireless network drivers source: Version: 1.1.0+cvs20070219-2
> + Exemplary posts on ubuntuforums.org:
>
> Linksys WUSB54G V4 (rt2570-based card)
> http://ubuntuforums.org/showthread.php?t=588045
>
> HOWTO: RT73 (RT71) serialmonkey drivers
> http://ubuntuforums.org/showthread.php?t=400236
>
> - ======
> -
> + ====================
> + OLD BUG DESCRIPTION:
> + ====================
> I configured my rt2400 card connection in network-admin succesfully but the connection is extremely slow.
> Ping works, but I can't get into any website, download packages through Synaptic even if waiting a few minutes.
> The card was recognized by Feisty as ra0, but now it's wlan0 in Gutsy.
>
> PING onet.pl (213.180.130.200) 56(84) bytes of data.
> 64 bytes from 213.180.130.200: icmp_seq=4 ttl=52 time=93.6 ms
> 64 bytes from 213.180.130.200: icmp_seq=5 ttl=52 time=82.8 ms
> 64 bytes from 213.180.130.200: icmp_seq=6 ttl=52 time=96.9 ms
>
> The problem does not occur when running Feisty and when running Gutsy
> with Feisty kernel (2.6.20.x). ...

He was adding duplicates to this bugreport, to which you are subscribed also. (see link on the last lines of this message)

Frak, could you change the importance of this bug to high? I'm not allowed to do this.

I did that already, some developer changed it to a lower priority
because this bug doesn't prevent your system from booting or anything :/

Op 24 jan 2008, om 22:35 heeft Piotr Makowski het volgende geschreven:

> Frak, could you change the importance of this bug to high? I'm not
> allowed to do this.
>
> --
> Ralink rt2400 / rt2500 / rt2570 / rt61 / rt73 do not work out of the
> box in Gutsy/Hardy
> https://bugs.launchpad.net/bugs/134660
> You received this bug notification because you are a direct subscriber
> of the bug.

Ok here are the guidelines and they do not suggest anything to do with booting or not booting, it is a bug that impacts a large portion of ubuntu users.
Kyle
"Launchpad uses the following guidelines for assigning importance: Untriaged: the bug report has not be triaged yet. This is the default importance for new bugs. Wishlist: a request to add a new feature to one of the programs in Ubuntu. Use this for bugs which aren't really bugs but ideas for new features which do not yet exist. Low: bugs that affect functionality, but to a lesser extent than most bugs Medium: a functionality bug of the standard variety. Most bugs are of "Medium" severity. High: a bug that has a severe impact on a small portion of Ubuntu users (estimated) or has a moderate impact on a large portion of Ubuntu users (estimated) Critical: a bug which has a severe impact on a large portion of Ubuntu users."
http://209.85.173.104/search?q=cache:Gf_8tlzpcOQJ:https://docteam.ubuntu.com/repos/trunk/generic/packagingguide/C/bugs.xml+importance+launchpad&hl=en&ct=clnk&cd=3&gl=us&client=firefox-a

So this should be marked as high

I think this should be raised too. It is a shame IMHO that Gutsy was shipped with flaky drivers when the legacy ones worked perfectly well, as far as I can see simply because of a fixation with Network Manager. The Ubuntu Hardy source for rt2x00 dates back to early November; have Serialmonkey made no progress since then? The problem with Hardy as it stands 2.6.24-4 is that the legacy drivers do not work (in my experience), so we no longer have the option to compile and install a working older version. Whilst the drivers do not prevent the system booting, a laptop without a decent wireless connection is badly hamstrung.

In the case of the duplicate Bug #104743, the problem seems to be fixed in Hardy.

agreed!
a laptop without a decent wireless connection is a big problem!

this bug may not prevent anyone from booting, but it makes people have to boot every time the driver fails (at least that's how I'm dealing with it, considering I'm unable to do anything that involves compiling :-p). it's not lack of booting, it's too much booting :)

I totally agree, but that's what the dev said and only devs can set
the priority.

Op 25 jan 2008, om 00:26 heeft Olivia het volgende geschreven:

> agreed!
> a laptop without a decent wireless connection is a big problem!
>
> this bug may not prevent anyone from booting, but it makes people have
> to boot every time the driver fails (at least that's how I'm dealing
> with it, considering I'm unable to do anything that involves compiling
> :-p). it's not lack of booting, it's too much booting :)
>
> --
> Ralink rt2400 / rt2500 / rt2570 / rt61 / rt73 do not work out of the
> box in Gutsy/Hardy
> https://bugs.launchpad.net/bugs/134660
> You received this bug notification because you are a direct subscriber
> of the bug.

rt61pci actually *does* work in hardy and it almost does in gutsy

in gutsy sources are OLD and must be updated, otherwise the driver bugs after a few minutes, and you have unload/reload it, if it was to be updated it should work as in hardy: in hardy it *almost* works which means I've found I can connect using WPA via command line using

# wpa_connect -B -dwlan0 -dext ... etc etc and then issuing # dhclient wlan0

I've also recently discovered I could make it work with wifi-radar, but I can't using network-manager; wicd didn't work too, and anyway i don't like wicd

The driver seems to work perfectly with OPEN networks

bye

oh, I have to add I'd prefer to have a working rt61pci+n-m instead of rt61 legacy which doesn't work with n-m for crypted connections!

I have been successfully using one of these cards for a while now and I think the problems which I experience (much like those others experience) seem to perhaps be due to overheating. When the adapter stops working I unplug it and plug it straight back in and most of the time it kicks back into life. Occasionally it has to cool for a bit first.

Hope that helps.

JG

goodmacman, I know my problem has nothing to do with heating... It's not really a usb stick, even though it uses the rt73usb driver... Sometimes I've just turned on the computer and the driver dies because I tried to access Google Reader when GReader is in one of those bad server days...

I experienced problems especially when using bittorrent, uploading and downloading a couple of torrents at the same time. The only way to get it working again was to reboot the computer. With 2.6.24-5, the network seems to be more stable.

RT2500 PCI card working fine here!

Driver: rt2500pci
Kernel: 2.6.22-5-generic

I'm using wicd 1.4.1 rather than network-manager. I connect to a WEP secured network with a 64bit Hexa key and get a static IP. No problems!

u should provide a verbose lspci of your card so we know exactly what works
and what doesnt

lspci

00:0b.0 Network controller: RaLink RT2500 802.11g Cardbus/mini-PCI (rev 01)

lsmod | grep rt2

rt2500pci 20352 0
rt2x00pci 11264 1 rt2500pci
rt2x00lib 22528 2 rt2500pci,rt2x00pci
rfkill 8208 1 rt2x00lib
input_polldev 5896 1 rt2x00lib
crc_itu_t 3072 1 rt2x00lib
mac80211 163480 3 rt2500pci,rt2x00pci,rt2x00lib
eeprom_93cx6 3200 1 rt2500pci

guys,

I don't know if this is relevant, but I am sucessfully using rt73usb and rt2500usb modules, and my wireless works dandy (in gutsy).

However, I can confirm that it is VITAL that they are loaded in that order.
I have an ADVENT 9112 laptop which worked "out-of the-box" with the live CD... but not after the install to hard disk.
Comparing the dmesg from the 2 setups, it struck me that those two modules were loaded in a different order.

I can now confirm, that for my setup at least, removing these modules then reinstalling in numerical order works (tested 20+times)

ie. (as root)
rmmod rt2500usb
rmmod rt73usb
modprobe rt73usb
modprobe rt2500usb.

Please don't flame me if this is of no use to you, or filed under the incorrect bug.
regards.
Neil.

Do you have two wireless cards installed? If not you should not be using two
modules.

thanks.
I've blacklisted the rt2500 one... and all works fine.
Neil.

Hi,
Read my comment on:
https://bugs.launchpad.net/ubuntu/+source/linux-ubuntu-modules-2.6.22/+bug/34902
Fernandoc

Fernando that looks suspiciously similar to the howto on the ubuntu forums (http://ubuntuforums.org/showthread.php?t=400236) apologies if I'm wrong. Compiling one of the legacy drivers does work for some people in Gutsy, me included, but not as yet in Hardy as far as I know. I never had to comment out my other interfaces in /etc/network/interfaces either..

On Jan 31, 2008 10:42 AM, _oOMOo_ wrote:
> Compiling one of the legacy drivers does work for some people
> in Gutsy, me included, but not as yet in Hardy as far as I know.

By the way using the legacy driver *is not* a solution

I don't know I, but I couldn't compile the driver using that Howto. Or maybe
I did compile it, only it didn't really work. Which is why I'm stuck waiting
for a solution for dummies :D

The easy solution for *this* dummy with an RT2500 based card, was to remove Network-Manager and install Wicd. See http://wicd.sourceforge.net. You can ad the repository or just download the latest deb file...

Hello!

My notebook (EasyNote R1907) comes with a RaLink rt2500.
I can confirm that rt2500pci/rt2x00pci/rt2x00lib modules
never connect to my access point (iwconfig) with latest Hardy.

Luckily the workaround with the serialmonkey driver (rt2500.ko)
(from CVS) that I compiled some months ago still works for me.
(ifconfig ra0 down, rmmod new rt2x00 stack, insmod rt2500.ko,
 ?run iwconfig essid/key?, ifconfig ra0 up, wait x seconds, dhclient ra0).

My rt2400 card (logs are on the top) works with the Hardy alpha 4. It is needed to choose proper network in the Network Manager... and everything works! My network does not use encryption, so I don't know if/how it works.

hi guys, here is a gutsy with hardy kernel; it seems like with kernel .24-8 there is a hang which I suspect comes from rt61pci; I could not find any clue in my logs, can anybody confirm?

hi there, running gutsy with a 2.6.24-5 hardy kernel, tested with both a rt2570 and a rt73 usb sticks with no positive outcome: both cards go off (no blinking led, no connection) after a bunch of minutes online, the only way to restore a connection is to restart the computer as simply disconnecting-reinserting the stick and/or restarting the network service does not do the trick; moreover, the serialmonkey modules would not compile, even after installing the hardy's build essential and libc etc. I've decided not to test 2.6.24-8 as I've read the post from NoWhereMan, and I'm here in nowhereland waiting for a new kernel update, in the meanwhile I'm back to gutsy's 2.6.22 kernel with serialmonkey's modules (which is not exactly working well either). These cards work quite well with both winxp sp2 and osx 10.4.9.

The RaLink RT2561/RT61 card works out of the box in the Hardy Alpha 4. Don't know anything about encryption.

Same here for me:

uname -a:
Linux laptop 2.6.22-14-generic #1 SMP Thu Jan 31 23:33:13 UTC 2008 x86_64 GNU/Linux

lspci -v:
06:00.0 Network controller: RaLink RT2500 802.11g Cardbus/mini-PCI (rev 01)
        Subsystem: Belkin F5D7000 Wireless G Desktop Network Card
        Flags: bus master, slow devsel, latency 64, IRQ 17
        Memory at 64000000 (32-bit, non-prefetchable) [size=8K]
        Capabilities: [40] Power Management version 2

It slows down the connection after reassociating at 54 mbit/s considerably. Otherwise it runs ok.

Do I understand the discussion above correctly that the next kernel will break my connectivity?

Regards,

Chris

I have tried Edimax EW-7318USg (rt73, usb) with Hardy alpha4 live cd
and it works with WEP/open using NM out of the box,
but it still doesn't work with static configuration.

Oh, yes, I forgot to add, with ralink rt2400 static configuration does not work, too.

MSI CB54G2 (rt2500pci, cardbus) works out of the box here with hardy kernels (worked with every hardy's kernel)
My config is WEP/open using NM

Since a few kernel updates, I have to manually force speed with "iwconfig wlan0 rate 54M" after associating or it runs at 1M.

I also encounter disconnections after several hours running (say at least 10 hours). I simply reconnect by clicking on my network name in NM.

Same here with a rt2500 PCI Card and WPA encrypted network. I also have to set the speed manually.

all usb dongles "DO NOT WORK"

> all usb dongles "DO NOT WORK"

That's not true:
http://www.murrayc.com/blog/permalink/2007/09/07/linux-compatible-wireless-usb-adaptor-slightly-better-in-ubuntu-gutsy/

The tested USB adaptor uses the Zydas ZD1211 chipset.

Ralink USB dongles are broken out-of-the-box for a long time.

Matthias Mailänder a écrit :
> The tested USB adaptor uses the Zydas ZD1211 chipset.
>

I got an zd1211 based usb dongle that had worked out of the box for a
long time (about 2 years).

> Ralink USB dongles are broken out-of-the-box for a long time.

I also got an rt73 based usb dongle that works out of the box correctly
with hardy. With gutsy it works only for some minutes with rt2x00usb module.

Yay!

I tested my RT2570usb with hardy in vmware - it works out of the box without any problems (fast connection).
Right now I only tested WEP 128 and only with single core cpu.

Okay, with emulated dual core cpu it works too!
I hope it works on my physical computer like in the vm...

I have a rt73usb dongle (Conceptronic C51RU) which works fast (54 Mbit/s) on Windows XP. On Linux (Hardy, writing this from 2.6.24-7) it is always at 11 Mbit/s or less. As I am dist-upgrading ubuntu and downloading many packages I notice that the mouse becomes jumpy and music playback suffers from extensive stutter. Jumpy mouse at least was not there in kernel 2.6.22 (gutsy), so I suspect the new kernel is to blame for the latency problems. But the low speed has always been there in all the kernels I tried. Well, at least it works, so I shouldn't complain so much... :P

Don't forget Bug #181320.

Hardy Heron totally ruined the ralink driver from serialmonkey, anyone else
have this issue?

No...
uname -a 2.6.24-7-generic

 [code]*-network
       description: Wireless interface
       product: RT2600 802.11 MIMO
       vendor: RaLink
       physical id: 0
       bus info: pci@0000:02:00.0
       logical name: wmaster0
       version: 00
       serial: 00:16:b6:59:90:aa
       width: 32 bits
       clock: 33MHz
       capabilities: bus_master cap_list logical ethernet physical wireless
       configuration: broadcast=yes driver=rt61pci ip=192.168.1.3 latency=64 module=rt61pci multicast=yes wireless=IEEE 802.11g[/code]

I just installed Ubuntu Hardy Alpha 4, the driver barely works, I can only get 19kbps max throughput and the driver causes 40% cpu usage, after dealing with that, I had to modprobe -r rt73usb and blacklist the ralink drivers, I headed over to http://rt2x00.serialmonkey.com/wiki/index.php/Downloads and grabbed the latest rt73 driver, compiled it, make installed it and modprobed the driver, now the serialmonkey driver is BORKED! WTF? "SIOSSIFFLAGS: Invalid argument" on ifconfig up on, so.. searched google and I landed here http://rt2x00.serialmonkey.com/phpBB2/viewtopic.php?t=4558 to find a ghetto fix for this issue by doing as follows:
modprobe rt73
ip link set wlan0 address 00:00:00:00:00:11
ifconfig wlan0 up
ifconfig wlan0
the serialmonkey will fix this driver like always but the Ubuntu dev's driver BLOWS still unfortunately....

Kyle, which kernel are you using (uname -r)? Do you use any encryption? What does dmesg say?

Andreas, I am using 2.6.24-7-generic with TKIP encryption, as for the dmesg I am running the serialmonkey driver now, do you want me to switch back over? Also when I try to use iwpriv with the rt73usb driver packaged in ubuntu I cannot use iwpriv with the driver, it says no private ioctls

it's not supposed to use iwpriv, you have to use wpa_supplicant, see
my post above and try that line

also wifi-radar is now working, but I had to hack the conf a bit (but
it might be my installation to be a little bit messed, and for you it
might just work)

bye

On Feb 12, 2008 9:04 PM, Kyle M Weller <email address hidden> wrote:
> Andreas, I am using 2.6.24-7-generic with TKIP encryption, as for the
> dmesg I am running the serialmonkey driver now, do you want me to switch
> back over? Also when I try to use iwpriv with the rt73usb driver
> packaged in ubuntu I cannot use iwpriv with the driver, it says no
> private ioctls
>
>
> --
> Ralink rt2400 / rt2500 / rt2570 / rt61 / rt73 do not work out of the box in Gutsy/Hardy
> https://bugs.launchpad.net/bugs/134660
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Everything is working great under Hardy for me here. I have an RT73 built into my laptop. Hidden essid is no longer an issue. I have not had the disconnects. I no longer need to use wlassistant for certain networks. TKIP and AES are both good on WPA networks. WEP is working fine as well. My only issue is that throughput is low. I can reliably connect at 54Mbps at home but throughput is low in comparison to when I use ndiswrapper under Gutsy and both are lower than they should be in my opinion.

The rt2x00 series are now in the upstream kernel, and appear to work (for the most part). The rt61 and rt73 adapters use different drivers, and therefore, deserve their own bug report.

You can connect with the 2.6.24 rt2x00 driver but it sets speed at 1Mbps and also throughput is horrible with it. It starts out ok and degrades after a few minutes down to no more than 100k/s a lot of time less than that. More like 20k/s. Until the latest rt2x00 gets in the kernel (linux-2.6) the speeds will be slow etc.

There are also more than 1 branch. rt2x00, linux-2.6, and wireless-2.6 i beleive are the different branches.

Tim, the rt2x00 driver supports rt61 (rt2561) and rt73 (rt2573), too, but I agree that this bug could be divided into several different bugs and that some of those bugs that are marked as duplicates aren't real duplicates.

In my opinion this bug doesn't actually make much sense anymore because it is filled up with a lot of different problems of which most of them aren't related to each other, because they deal with chipset-specific issues.

Fixing this "bug" is really difficult as the actual issues aren't _that_ clear or because it isn't fixed in latest upstream yet. Maybe some fixes that are known to improve the situation can be merged from wireless-dev, if the problem is clear.

I've noticed my rt73 setup works fine when running on AC (hours of good bandwidth), but gets flaky and disconnects when running on battery.

Anyone else had similar experience?

I would also like to chime in with a complaint that the rt2500 series drivers don't work correctly in Gutsy (2.6.22-14-generic), at least not with WPA. I'm using a Linksys WUSB56G v4 adapter.

I compiled the rt2570 legacy driver from serialmonkey and installed it. With this driver I was able to get a connection using WPA, but *only* from the command line using iwpriv or the rutilt program. This had me hopeful, except that DHCP will not work. If I manually configure my IP settings on rausb0, I can talk on the WPA network just fine. I tried both various mixtures of dhcpcd and dhclient to no avail. Requests timed out.

Uninstalled NetworkManager and installed wicd. This did not help at all. The rt2570 driver and wpa_supplicant do not jive using wext or ralink legacy (or any other driver).

I tried wifi radar. Again, no WPA.

Can't compile new rt2x00 drivers from serialmonkey against this kernel so I can't try those.

The only "solution" to this problem for me has been to use ndiswrapper with the Windows drivers for this adapter. This works well with WPA, and I can roam from network to network just fine. The problem with this solution is that there is no way to use advanced features like monitor mode. I use kismet when setting up access points, for example. When I need to use kismet I have to remove ndiswrapper and then I use the rt2500usb driver from Gutsy which doesn't work for connecting, but can sniff just fine. This is a bit of a pain in the rear, especially since these all of these ralink drivers have a tendency to lock my keyboard up when I remove them with modprobe, so I have to restart with the mouse. Thus I can switch from ndiswrapper to rt2500usb, but I can't switch back without restarting.

Frustrating!

rt61pci seems confirmed to be buggy: http://bugzilla.kernel.org/show_bug.cgi?id=9860

I just upgraded from kernel 2.6.24-3 to 2.6.24-8 and now my RT2561/RT61 will not detect any networks. I can still boot off of the Hardy Alpha4 LiveCD and connect immediately.
I included the logs I could think of. If you need others, let me know.

So if this is marked now as "Fix Released" how long will it be before that fix appears in the software updates??

Thanks.

The bug was marked "Fix Released" February 13th with regards to the rt2x00, so it should be in the archives already, and in Alpha 5 in particular. The problem is that all kind of bugs got merged into this one for some reason, and some of them are probably not fixed yet.

Apparently there is a fix for the rt2500 slow connection problem: http://rt2x00.serialmonkey.com/phpBB2/viewtopic.php?t=4579&start=0
The only problem: it's not in the mainline kernel, but in a git brach (I believe it's in the wireless branch).

RT73 (Linksys WUSB54GC) works fine in Hardy now.

Does anyone have any idea if the rt73usb is working nicely in Hardy too?

I have a quick question about the new rt73 driver for hardy, does it
have iwpriv usage and injection capability?
Thanks
defcon

Yep, confirming a RT73 based TP-Link stick works well, although I had to
configure WPA manually.

On Tue, Mar 4, 2008 at 10:04 AM, Alexander Jones <email address hidden> wrote:

> RT73 (Linksys WUSB54GC) works fine in Hardy now.
>
> --
> Ralink rt2400 / rt2500 / rt2570 / rt61 / rt73 do not work out of the box
> in Gutsy/Hardy
> https://bugs.launchpad.net/bugs/134660
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

I installed the latest hardy kernel on my gutsy i386 and my D-link
DWL-G122 H/W ver.: C1 works out of the box now.

Thanks for the fix!

On Tue, Mar 04, 2008 at 08:09:00AM -0000, Adam wrote:
> Yep, confirming a RT73 based TP-Link stick works well, although I had to
> configure WPA manually.
>
> On Tue, Mar 4, 2008 at 10:04 AM, Alexander Jones <email address hidden> wrote:
>
> > RT73 (Linksys WUSB54GC) works fine in Hardy now.
> >
> > --
> > Ralink rt2400 / rt2500 / rt2570 / rt61 / rt73 do not work out of the box
> > in Gutsy/Hardy
> > https://bugs.launchpad.net/bugs/134660
> > You received this bug notification because you are a direct subscriber
> > of a duplicate bug.
> >
>
> --
> Ralink rt2400 / rt2500 / rt2570 / rt61 / rt73 do not work out of the box in Gutsy/Hardy
> https://bugs.launchpad.net/bugs/134660
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.

Hi,

Is this fix being backported to gutsy?
There's a linux-backports-modules-2.6.22-14-generic package in the proposed updates. Is this fix in there?

My rt73 based device was working on hardy, but not with latest kernel (2.6.24-11 doesn't work). I have a problem of unknown symbol while inserting module. This is not a problem with the driver itself, that have worked great with an older alpha.

@ld2ndR, looks like an interrupt problem to me, please post full dmesg output

@NoWhereMan

Here it is (the adaptator was working with older release).

Rt2500usb will not connect to network, Gutsy (and Hardy)

In Synaptic shown installed are;- rt2500 and rt2500-source (they do not mention usb?)

hardware info = info.linux.driver rt2500usb
:~$ uname -a
Linux athlon 2.6.22-14-generic #1 SMP Tue Feb 12 07:42:25 UTC 2008 i686 GNU/Linux

The device starts up, and in 'Roaming'it collects all the wireless networks, chooses mine, the eventually asks for encryption, WEP-Ascii is entered, but it does not connect to network. The USB adapter flashes a short time, but no connection is made. After a while the encryption code is requested again with the same result. The device does work on the other OS-xp drivers, it is obviously partially working here but does not connect.

If I try manual config, set the network, encryption and DHCP I get the same result.

Are there any alternatives I could try? have I got the correct drivers installed in Synaptec?
Any help would be appreciated.

My attempts so far;

sudo /etc/init.d/networking restart

~$ lsusb

lswlan Bus 004 Device 003: ID 050d:7050 Belkin Components F5D7050 ver 1000 WiFi

:~$ ifconfig

 * Reconfiguring network interfaces...
eth1: ERROR while getting interface flags: No such device
Error for wireless request "Set Encode" (8B2A) :
    SET failed on device eth1 ; No such device.
Error for wireless request "Set ESSID" (8B1A) :
    SET failed on device eth1 ; No such device.
There is already a pid file /var/run/dhclient.eth1.pid with pid 134519120

wmaster0: unknown hardware address type 801
SIOCSIFADDR: No such device
eth1: ERROR while getting interface flags: No such device
eth1: ERROR while getting interface flags: No such device
wmaster0: unknown hardware address type 801
Bind socket to interface: No such device
Failed to bring up eth1.

wmaster0: unknown hardware address type 801
Listening on LPF/wlan0/00:11:50:4c:35:05
Sending on LPF/wlan0/00:11:50:4c:35:05
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

ifconfig

wlan0 Link encap:Ethernet HWaddr 00:11:50:4C:35:05
          UP BROADCAST MULTICAST MTU:1500 Metric:1
          RX packets:6 errors:0 dropped:0 overruns:0 frame:0
          TX packets:130 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:252 (252.0 b) TX bytes:26853 (26.2 KB)

wlan0:ava Link encap:Ethernet HWaddr 00:11:50:4C:35:05
          inet addr:169.254.2.131 Bcast:169.254.255.255 Mask:255.255.0.0
          UP BROADCAST MULTICAST MTU:1500 Metric:1

wmaster0 Link encap:UNSPEC HWaddr 00-11-50-4C-35-05-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:...

Some cards that are detected by the rt drivers are actually rt73
chips, especially USB sticks. Try loading the rt73 drivers, making
sure to unload rt2500 first.

@ld2ndR they must have changed something in their API, breaking that driver...

Thanks Adam, I deleted the rt2500 files from Synaptic but the rt2500usb is still loaded when I plug the USB in, how do I completely remove them from the system, if that is necessary. (blacklist?)

I could not find rt73 in Synaptic so I have downloaded an rt73 so will try installing that when I can delete the old driver.

Could e.vacchi explain what API is and how to fix it, bearing in mind the 'live' cd and also a fresh install of Hardy-a6 has the same problem.

Cushie wrote:
> Thanks Adam, I deleted the rt2500 files from Synaptic but the rt2500usb
> is still loaded when I plug the USB in, how do I completely remove them
> from the system, if that is necessary. (blacklist?)
>
> I could not find rt73 in Synaptic so I have downloaded an rt73 so will
> try installing that when I can delete the old driver.
>
> Could e.vacchi explain what API is and how to fix it, bearing in mind
> the 'live' cd and also a fresh install of Hardy-a6 has the same
> problem.
>
>
Cushie,
the rt2500 is a "module" which is loaded into the kernel at boot
time,they are roughly equivalent to "drivers" in windows.
you can find out which modules are currently loaded on your machine by
typing "lsmod" into a terminal

you can remove modules manually at any time using "rmmod" (as root).
example... to remove your rt2500 module.
$sudo rmmod rt2500

you can insert a module using "modprobe".
$sudo modprobe rt2500

As you allude to, it is possible to stop a module being used at any time
(including boot) by blacklisting it.
To do this you need to edit the blacklist file which lives in the folder
/etc/modprobe.d
You can edit this with any text editor (gedit, nano etc...) , but need
root level permissions to commit your changes.

$sudo gedit /etc/modprobe.d/blacklist

add these lines to the bottom of the file.

#Cushie added these lines on 11th March
#it is good practice to put in comments like this, and can save
headaches if you wish to renove your changes
#the loader will ignore any line with a hash sign at the start
#here comes the line you need
blacklist rt2500
#suggest you also blacklist the rt2500usb module
blacklist rt2500usb

now save and reboot.

good luck.
Neil.

_________________________________________________________________
Share what Santa brought you
https://www.mycooluncool.com

> Could e.vacchi explain what API is and how to fix it, bearing in mind
> the 'live' cd and also a fresh install of Hardy-a6 has the same problem.

Hi Cushie,

I'm sorry, what I meant to say is just that the kernel devs (not ubuntu devs) have broken the driver because they changed something in the internals of the kernel itself. If this were true it would mean there isn't unfortunately an easy solution to fix the problem, apart from trying to use the windows driver via "ndiswrapper"; but I can't assure it would work, and probably it isn't a thing you can try on the live cd with ease.

bye

Switch back to confirm since recent kernel updates break the driver (Unknown symbol in module).

Thank you Neil, nicely explained and all understood, I think I can manage that, first to try the Serialmonkey rt73 and then maybe ndiswrapper if there is no success. I will keep the kernels 2.6.22, and 2.6.24 (on separate systems) up to date in any case (fingers crossed it gets fixed)

Thank you too, NoWhereMan, I will eventually try that if necessary. The live cd is not any problem to me, just to help with the background info.

Cheers!

If you really are using rt2500, then the ndiswrapper solution should work.
I have it working here with a Linksys WUSB56G v4 using the XP Windows driver
from linksys and I'm connecting to a WPA network. Seems like I tried
everything else and nothing would work (connecting to encrypted networks
anyhow).

@NoWhereMan,
Linux kernel 2.6.24 was released in january. So as it is not the devel branch (which is 2.6.25), I don't think they have changed something in there API. So it might have a problem while the package of linux-image was done by Ubuntu team.

rt2x00 driver works great know, and it whould be a share that the version provided with hardy doesn't work at all wheras it was working with an older alpha.

On Thu, Mar 13, 2008 at 12:33 PM, Id2ndR <email address hidden> wrote:
> @NoWhereMan,
> Linux kernel 2.6.24 was released in january. So as it is not the devel branch (which is 2.6.25), I don't think they have changed something in there API. So it might have a problem while the package of linux-image was done by Ubuntu team.

oh, I wouldn't be so sure; I don't want to flame, but consider that
rt61pci in 2.6.24 is still going panic (in vanilla)...

bye

I do experience quite a similar problem, (Gutsy) but not that it doesn't work. It just gets an total system freeze.

(Ubuntu 8.04, Kernel 2-6.24-12,WLAN Cardbus Card: Cardbus Texas Instruments PCI 1410 rev 02, Ralink RT2561/RT61 rev B 802.11g)
Modules:

The Freeze just happens with the card. It may last for a few minutes (by heavy load) or an hour, just browsing the web.
Without the card the computer works without freeze (Longest uptime so far 2 Days, but with normal shutdown).

See also BUG:
https://bugs.launchpad.net/ubuntu/+source/linux-ubuntu-modules-2.6.24/+bug/191827

Philipp Meier wrote:
> I do experience quite a similar problem, (Gutsy) but not that it doesn't
> work. It just gets an total system freeze.
>
> (Ubuntu 8.04, Kernel 2-6.24-12,WLAN Cardbus Card: Cardbus Texas Instruments PCI 1410 rev 02, Ralink RT2561/RT61 rev B 802.11g)
> Modules:
>
> The Freeze just happens with the card. It may last for a few minutes (by heavy load) or an hour, just browsing the web.
> Without the card the computer works without freeze (Longest uptime so far 2 Days, but with normal shutdown).
>
> See also BUG:
> https://bugs.launchpad.net/ubuntu/+source/linux-ubuntu-modules-2.6.24/+bug/191827
>
>
Have you tried WICD?
my system seems much more stable under that than network-manager, but
that's obviously a VERY small sample.

Neil

_________________________________________________________________
Who's friends with who and co-starred in what?
http://www.searchgamesbox.com/celebrityseparation.shtml

Thanks for your hint!
I'll have a look at the WICD asap, just to test if networkmanager is the problem. Which would be a bit strange, because of the total system freeze. I did not even think of networkmanager as a possible threat.
I had a gentoo as well on the same laptop, with my custom kernel (development version of 2.6.24-rc5) and I did not expire that problem.

@Philip: IIRC the panic bug was introduced later with a maintenance
release (not a RC)

On Thu, Mar 13, 2008 at 4:07 PM, Philipp Meier <email address hidden> wrote:
> Thanks for your hint!
> I'll have a look at the WICD asap, just to test if networkmanager is the problem. Which would be a bit strange, because of the total system freeze. I did not even think of networkmanager as a possible threat.
> I had a gentoo as well on the same laptop, with my custom kernel (development version of 2.6.24-rc5) and I did not expire that problem.

Yeah so obviously the wicd did not solve the problem. I'm back to NetworkManager. Does anyone know if the problem is fixed in 2.6.25-rcX ??

it looks like it is, but (for me) there are bugs with keyboard
interrupts, so for now I'm still staying with the .24-4 kernel (with
no battery indication, lol) :/

On Fri, Mar 14, 2008 at 4:27 PM, Philipp Meier <email address hidden> wrote:
> Yeah so obviously the wicd did not solve the problem. I'm back to
> NetworkManager. Does anyone know if the problem is fixed in 2.6.25-rcX
> ??
>
>
>
> --
> Ralink rt2400 / rt2500 / rt2570 / rt61 / rt73 do not work out of the box in Gutsy/Hardy
> https://bugs.launchpad.net/bugs/134660
> You received this bug notification because you are a direct subscriber
> of the bug.
>

bug was reopened long after alpha-4, moving the milestone forward so that this is on the radar.

I think there is a new bug about unknow symbol, that was not the same as the original bug. This new bug appears with alpha 4 I think. Maybe someone can confirm #203758

Good: It works for me...

Not so good: ... but only if I get Network Settings to change the setup (e.g. use a static IP if previously DHCP, use DHCP or a different static IP if previously static). Then it happily connects to the wireless network it was previously ignoring.

Prior to doing this, wlan0 doesn't seem to appear in the output of dmesg, after doing it you can see the wlan0 authentication happening successfully.

Ubuntu version: 8.04 Hardy Alpha6 (also same behaviour in 7.10 Gutsy)

In an attempt to solve this, I tried installing the serialmonkey drivers, but the only difference was that it took a *lot* longer to boot up.

Hardware, lspci reports

02:00.0 Network controller: RaLink RT2600 802.11 MIMO

relevant bits of lsmod:

rt61pci 25472 0
rt2x00pci 11264 1 rt61pci
rt2x00lib 22528 2 rt61pci,rt2x00pci
rfkill 8592 1 rt2x00lib
input_polldev 5896 1 rt2x00lib
crc_itu_t 3072 1 rt2x00lib
mac80211 165652 3 rt61pci,rt2x00pci,rt2x00lib
cfg80211 15112 1 mac80211
eeprom_93cx6 3200 1 rt61pci

More details available if someone tells me where the equivalent to device manager has gone from Hardy's menus....

Install gnome-device-manager

Ah, yes, thanks. Pity that was taken out of the default menus.

Annoyingly, it won't let you copy text, but it's using the rt61pci driver having detected it as a RT2600 802.11 MIMO, product_id 1025, subsys_product_id 9825, vendor RaLink, id 6164.

.. and the actual card is a CNet Technology Inc (Taiwanese) CWC-903 "Wireless-MIMO CardBus Adapter", part no 18-1AGWC93, hardware version 1.

I can confirm that now (don't know since which kernel version but now I'm testing Hardy Beta on a real partition not only in a VM) my RT2570 USB does not work anymore. Same problem as everytime: connecting..... connecting.... no result :-/
Would be nice to have this fixed in the final release.

I upgraded to the beta of Hardy to discover that Ralink's drivers don't work. The ones that come with the kernel don't work either with my Linksys WMP54G v4.1 (rt61). dmesg turned up several lines like these:

phy3 -> rt2x00lib_request_firmware: Info - Loading firmware file 'rt2561.bin'.
phy3 -> rt2x00lib_request_firmware: Error - Failed to request Firmware.

There is a sticky in the rt2x00 forums that tells you to place the firmware files in /lib/firmware. The package linux-ubuntu-modules-2.6.24-12-generic places them in a subdirectory of /lib/firmware where the drivers can't find it.

The sticky says:

Hi,

The firmware location has changed according to new kernel firmware loading libs, from /etc/Wireless/RT61STA to /lib/firmware.
Please note that some linux distributions use /lib/firmware/<KERNEL_VERSION> as their default firmware location.

This is the first step of a few needed driver updates that unfortunately will break backward compatibility with existing user configs. Migrating to new standards will nevertheless be quite easy.

Can confirm Hardy Beta does not recognize a D-Link DWA-110 (rt73). This is a new system and new card so don't know if this is a regression (and I can't test Gutsy without pain due to an unsupported video card).

Related to rt2570 on Hardy Beta (8.04):

Ralink 2570 as shown below connects with WEP but very poorly, signal strength of 30%. Where as 7.04 with serial monkey drivers (rt2570) work great. Currently Hardy beta uses rt2xx or something similar I believe. Is there any hope we will merge those with 8.04 final release or is it already merged in rt2xx and we are working out bugs? If there is anything to test let me know.

Bus 005 Device 003: ID 148f:2570 Ralink Technology, Corp. 802.11g WiFi

Now, that's funny. Will these open source driver ever work? For me, in gutsy they worked quite well, but everytime I've tried hardy, they just don't cut it: sometimes it works, sometimes it won't. Maybe ping works, but surfing doesn't...

Please fix this! ;)

Dear You all, I own an Asus WL-167G wi-fi dongle rt2570 based and it does not work with hardy's 2.6.24-12-generic kernel 32-bit installed on top of gutsy; I also have a D-Link DWL-G122 dongle rt73 based dongle that works very well with the very same kernel on the same computer; however a full install of hardy would not run on this box as the all usb subsystem is messed up: I have Logitech wireless usb keyboard and mouse that do not work at all with hardy ever since alpha 3, rendering my box unusable even for beta testing

More about the above post: I did test the dongles on another box, an Athlon 2800 running gutsy, I've installed hardy's 2.6.24-12 kernel and the WL-167G stick does not work as on the other machine (Intel dual core); also the D-Link DWL-G122 worked fine for a bunch of minutes and then died, I've had to reboot to get it working again for a while. The beheaviour is not the same on different hardware platforms, I hope this info helps to nail down the bug(s).

I have TP-Link TL-WN321G USB WLAN adapter. It work first try with XUbuntu 8.04 Alpha 6. Now after installing XUbuntu 8.04 beta, can not get it to work.

taleman@wally:~$ tail /var/log/kern.log
Mar 24 21:09:57 wally kernel: [ 106.454685] eth0: no IPv6 routers present
Mar 24 21:13:06 wally kernel: [ 295.404331] gdm[5478]: segfault at 7672657f eip b77e3762 esp bf859ca0 error 6
Mar 24 21:25:07 wally kernel: [ 1016.037523] usb 1-2: new full speed USB device using uhci_hcd and address 2
Mar 24 21:25:07 wally kernel: [ 1016.333721] usb 1-2: configuration #1 chosen from 1 choice
Mar 24 21:25:08 wally kernel: [ 1016.860597] phy0 -> rt2500usb_init_eeprom: Error - Invalid RT chipset detected.
Mar 24 21:25:08 wally kernel: [ 1016.860813] phy0 -> rt2x00lib_probe_dev: Error - Failed to allocate device.
Mar 24 21:25:08 wally kernel: [ 1016.862490] usbcore: registered new interface driver rt2500usb
Mar 24 21:25:08 wally kernel: [ 1017.156573] phy1: Selected rate control algorithm 'simple'
Mar 24 21:25:08 wally kernel: [ 1017.339227] usbcore: registered new interface driver rt73usb
Mar 24 21:25:09 wally kernel: [ 1017.704761] ADDRCONF(NETDEV_UP): wlan0: link is not ready

taleman@wally:~$ lsusb
Bus 002 Device 002: ID 058f:9254 Alcor Micro Corp. Hub
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 002: ID 148f:2573 Ralink Technology, Corp.
Bus 001 Device 001: ID 0000:0000
taleman@wally:~$

I can confirm also that my Linksys WUSB54G v4 is not at all recognized
by the Hardy Beta. It seems that the issue has gotten worse, and
using ndiswrapper is the only solution, again.

I am personally giving up on this issue. I have found no reliable way
to use this card with native drivers that support both WPA and monitor
mode. Similar issue with an older Orinoco Gold (atmel Hermes I).
I've got a different card on the way but am trying out other distros
regardless because of other issues (ATI video, namely).

On 3/22/08, Barrakketh <email address hidden> wrote:
> I upgraded to the beta of Hardy to discover that Ralink's drivers don't
> work. The ones that come with the kernel don't work either with my
> Linksys WMP54G v4.1 (rt61). dmesg turned up several lines like these:
>
> phy3 -> rt2x00lib_request_firmware: Info - Loading firmware file
> 'rt2561.bin'.
> phy3 -> rt2x00lib_request_firmware: Error - Failed to request Firmware.
>
> There is a sticky in the rt2x00 forums that tells you to place the
> firmware files in /lib/firmware. The package linux-ubuntu-
> modules-2.6.24-12-generic places them in a subdirectory of /lib/firmware
> where the drivers can't find it.
>
> The sticky says:
>
> Hi,
>
> The firmware location has changed according to new kernel firmware loading
> libs, from /etc/Wireless/RT61STA to /lib/firmware.
> Please note that some linux distributions use /lib/firmware/<KERNEL_VERSION>
> as their default firmware location.
>
> This is the first step of a few needed driver updates that unfortunately
> will break backward compatibility with existing user configs. Migrating
> to new standards will nevertheless be quite easy.
>
> --
> Ralink rt2400 / rt2500 / rt2570 / rt61 / rt73 do not work out of the box in
> Gutsy/Hardy
> https://bugs.launchpad.net/bugs/134660
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Source Package "linux-ubuntu-modules-2.6.22" in Ubuntu: Won't Fix
> Status in Source Package "linux-ubuntu-modules-2.6.24" in Ubuntu: Confirmed
>
> Bug description:
> ===
> The poll shows that most of the problems with wireless networking are
> problems with ralink cards in Ubuntu.
> POLL: What wireless chipset are you having a problem with in Gutsy?
> http://ubuntuforums.org/showthread.php?p=4178322
>
> The bug occurs commonly and it's very important - and will be easy - to fix
> it.
> ======================================
>
> Cards don't work because of the invalid drivers (extremely slow connection,
> no connection, connection lost, lack of the wpa support) included in Ubuntu.
>
> Work-around: To install the proper driver from serialmonkey.
>
> SOLUTION:
> 1. Find out which version of a serialmonkey driver works properly with each
> ralink card.
> 2. Implement ralink serialmonkey drivers in Ubuntu.
>
> http://rt2x00.serialmonkey.com/
>
> Most likely the newest CVS version of each ralink driver works correctly.
>
> ===
> Please write which drivers are known to work and which are invalid.
> ==
>
> Exemplary posts on ubuntuforums.org:
>
> Linksys WUSB54G V4 (rt2570-based card)
> http://ubuntuforums.org/showthread.php?t=588045
>
> HOWTO: RT73 (RT71) serialmonkey drivers...

Taleman: Are you sure the right module is loaded?
Your device has a USB ID which is known to be abused by hardware manufacturers to be either rt2500usb or rt73usb.
If rt2500usb fails, try to blacklist it to give rt73usb a chance of recognizing it.

I can verify that the rt61pci driver included with the latest hardy kernel doesn't work properly with my D-Link DWL-G510 rev. C2 PCI card. The driver detects the card, but will not connect to a hidden WPA2-Personal (AES-CCMP) network.

>> luca.mg wrote on 2008-03-24: (permalink)

>>Dear You all, I own an Asus WL-167G wi-fi dongle rt2570 based and it does not work with hardy's 2.6.24-12-generic kernel 32-bit installed on top of gutsy; I also have a D-Link DWL-G122 dongle rt73 based dongle that works very well with the very same kernel on the same computer; however a full install of hardy would not run on this box as the all usb subsystem is messed up: I have Logitech wireless usb keyboard and mouse that do not work at all with hardy ever since alpha 3, rendering my box unusable even for beta testing<<

Logitech 'Cordless Internet Pro' wireless keyboard & mouse never been a problem here Hardy Alpha6. (RT2500 USB is a problem still)

There seems to be different issues. I am affected by the 'slow rt2500' one, others seems to have symbols problems, firmware problems, etc.

Maybe we should 'clear' this bug and create 3 o 4 new bugs treating the different issues.

By the way, my report:

uname -a:
Linux baenre 2.6.24-12-generic #1 SMP Wed Mar 12 23:01:54 UTC 2008 i686 GNU/Linux

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

lsmod:
rt2500pci 20352 0
rt2x00pci 11264 1 rt2500pci
rt2x00lib 22528 2 rt2500pci,rt2x00pci
rfkill 8592 1 rt2x00lib
input_polldev 5896 1 rt2x00lib
crc_itu_t 3072 1 rt2x00lib
mac80211 165652 3 rt2500pci,rt2x00pci,rt2x00lib
eeprom_93cx6 3200 1 rt2500pci

After setting manually the interface speed ($sudo iwconfig wlan0 rate 54M) it seems to work normally (ie, like in gutsy, where this card works for me like a charm, without leds).

For what it's worth:

Linksys WUSB54GC (USB ID 13b1:0020, driver rt73usb) works fine with Network
Manager, and almost fine with static configuration (you just have to issue
ifup wlan0 after startup.)

It definitely works "out of the box"!

Alexander, and it's not dying all of a sudden from time to time? With Hardy? :D

No, it's absolutely fine, and it has been pretty much since I started using
Hardy in January.

Gutsy, on the other hand, would constantly die with lots of errors in the
kernel log, forcing me to reload the module and reload networkmanager.

Both Gutsy and the Hardy beta can't make my card function. Under feisty it works when setup manually (wireless networks are not detected). My card is detected as a ralink RT2400/2460 under feisty.

can someone tell my why I cannot use iwpriv with the rt73 driver? I
can with the serialmonkey driver. Also is monitor/injection
supported?

On Thu, Mar 27, 2008 at 09:21:08PM -0000, Kyle M Weller wrote:
> can someone tell my why I cannot use iwpriv with the rt73 driver? I
> can with the serialmonkey driver. Also is monitor/injection
> supported?

iwpriv is an interface to "private" -- i.e., per-driver -- controls. So
that's not going to work with all drivers, and those drivers it does work
with won't expose an identical set of controls.

After saying how well my rt73usb device was working in Hardy, I noticed my connection kept dropping a lot.

Mar 28 01:26:42 flash kernel: [ 276.757545] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x06 failed for offset 0x3038 with error -110.
Mar 28 01:26:42 flash kernel: [ 276.770664] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Mar 28 01:26:56 flash kernel: [ 291.065500] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x06 failed for offset 0x3020 with error -110.
Mar 28 01:26:59 flash NetworkManager: <WARN> request_and_convert_scan_results(): card took too much time scanning. Get a better one.

However, I have experimentally determined that this is only a problem when I have my Seagate FreeAgent external USB hard disk plugged in. Removing it caused all the problems to go away instantly.

I'm using the Ubuntu 8.04 Beta AMD64 and have some problem with my rt73 usb device. First it all works fine, but after some I get disconnected. Dmesg gives a lot of the following lines...
[ 7128.759353] phy0 -> rt2x00usb_write_tx_data: Error - Arrived at non-free entry in the non-full queue 2.
[ 7128.759357] Please file bug report to http://rt2x00.serialmonkey.com.
[ 7128.789562] phy0 -> rt2x00usb_write_tx_data: Error - Arrived at non-free entry in the non-full queue 2.
[ 7128.789564] Please file bug report to http://rt2x00.serialmonkey.com.
[ 7128.817796] phy0 -> rt2x00usb_write_tx_data: Error - Arrived at non-free entry in the non-full queue 2.
[ 7128.817799] Please file bug report to http://rt2x00.serialmonkey.com.
[ 7128.873371] phy0 -> rt2x00usb_write_tx_data: Error - Arrived at non-free entry in the non-full queue 2.
[ 7128.873374] Please file bug report to http://rt2x00.serialmonkey.com.
[ 7128.894857] phy0 -> rt2x00usb_write_tx_data: Error - Arrived at non-free entry in the non-full queue 2.
[ 7128.894861] Please file bug report to http://rt2x00.serialmonkey.com.

after shuting down, and booting up, it works again. Anybody experiences the same problem?

Hi,

As discussed on the forum, bugzilla and mailinglists:
This issue has been resolved in rt2x00 2.1.0
Current rt2x00 version is 2.1.4

Ivo

> I'm using the Ubuntu 8.04 Beta AMD64 and have some problem with my rt73 usb device. First it all works fine, but after some I get disconnected. Dmesg gives a lot of the following lines...
> [ 7128.759353] phy0 -> rt2x00usb_write_tx_data: Error - Arrived at non-free entry in the non-full queue 2.
> [ 7128.759357] Please file bug report to http://rt2x00.serialmonkey.com.
> [ 7128.789562] phy0 -> rt2x00usb_write_tx_data: Error - Arrived at non-free entry in the non-full queue 2.
> [ 7128.789564] Please file bug report to http://rt2x00.serialmonkey.com.
> [ 7128.817796] phy0 -> rt2x00usb_write_tx_data: Error - Arrived at non-free entry in the non-full queue 2.
> [ 7128.817799] Please file bug report to http://rt2x00.serialmonkey.com.
> [ 7128.873371] phy0 -> rt2x00usb_write_tx_data: Error - Arrived at non-free entry in the non-full queue 2.
> [ 7128.873374] Please file bug report to http://rt2x00.serialmonkey.com.
> [ 7128.894857] phy0 -> rt2x00usb_write_tx_data: Error - Arrived at non-free entry in the non-full queue 2.
> [ 7128.894861] Please file bug report to http://rt2x00.serialmonkey.com.
>
> after shuting down, and booting up, it works again. Anybody experiences
> the same problem?
>

The Hardy kernel uses the rt2x00 driver that is in the kernel upstream. There have been several fixes since 2.6.24 release and I got a test kernel with most of them at:

http://people.ubuntu.com/~smb/rt2x00-test/

There is a chance this patchset might make it into the final Hardy release but we need feedback, whether this is an improvement. So please, any volunteers to try this are welcome.

@IvD
As far as I can tell the version in Linus tree is 2.0.14. I am not expert in that field but it seems the more recent driver cannot be built easily for the Hardy kernel since it uses quite a lot mac80211 functionality that isn't in Hardy. A solution would be to put the advanced driver into linux-backport-modules. But this requires a codebase that can be compiled and used with the current Hardy code. But this requires more time (and knowledge) than I have.

What might be interesting is the wireless-compat package on linuxwireless.org.
They provide the latest mac80211 versions including all mac80211 drivers for "older" kernels.

Unfortunately the patch that fixed above problems was not a single patch, in fact it were about 80 patches that fixed most issues. And that makes backporting the fix too complex.

I tested the Kernel on http://people.ubuntu.com/~smb/rt2x00-test/ with Network controller: RaLink RT2500 802.11g Cardbus/mini-PCI (rev 01).

None of my problems is resolved. The connection ist very slow and unstable. I can speed it up with iwconfig wlan0 rate 54M, without setting the rate manual it is Bit Rate=1 Mb/s, it is faster than, but not stable.

I do not know how to give a better feedback, so please tell me, if you need more information.

if you people here want to solve your problems with rt61pci, the only
fix i found was to compile 2.6.25-rc7; at least there it's fixed

On Tue, Apr 1, 2008 at 11:33 PM, Christian Mangold
<email address hidden> wrote:
> I tested the Kernel on http://people.ubuntu.com/~smb/rt2x00-test/ with
> Network controller: RaLink RT2500 802.11g Cardbus/mini-PCI (rev 01).
>
> None of my problems is resolved. The connection ist very slow and
> unstable. I can speed it up with iwconfig wlan0 rate 54M, without
> setting the rate manual it is Bit Rate=1 Mb/s, it is faster than, but
> not stable.
>
> I do not know how to give a better feedback, so please tell me, if you
> need more information.
>
>
>
> --
> Ralink rt2400 / rt2500 / rt2570 / rt61 / rt73 do not work out of the box in Gutsy/Hardy
> https://bugs.launchpad.net/bugs/134660
> You received this bug notification because you are a direct subscriber
> of the bug.
>

@Christian

Thanks, for testing. I guess this is feedback enough. Your results, together with IvD's comments sound like this will not be fixable within the kernel code. The linuxwireless compat package might be interesting for l-b-m but this has to be carefully evaluated.

I also tested the kernel at http://people.ubuntu.com/~smb/rt2x00-test/ with a D-Link DWL-G510 rev. c2 (rt61pci driver) and it didn't resolve any problems. I tested this on the latest hardy updates with NetworkManager.

I tested the kernel at http://people.ubuntu.com/~smb/rt2x00-test/ on my updated Hardy too.
I have an ASUS WL-167G usb dongle (rt73usb) and it's not working. I'm not able to connect to any network, open or wpa-protected.

Ok, the kernel driver itself does not work. So an external version seems to be the only solution. I finally managed to (hopefully) solve the dependencies and have placed a tarball into http://people.ubuntu.com/~smb/rt2x00-test/ which does build on my machine and also provides modules I can load (but lacking the real hardware I could not do any real testing). To build the modules, unpack the tarball run "make" and "make install". This will place the modules in the /lib/modules into updates. After depmod -ae an modprobe -l for the module should return the updates path. To boot with the modules an additional update-initramfs would be required.
If anybody can give that a try and feedback, that would be much appreciated.

Hopefully I tested it. I compiled the driver and it was present in /lib/modules/2.6.24-15-generic/updates. I did a "sudo depmod -ae" and "sudo modprobe -l". Than a reboot. WLAN was broken after that, "sudo iwconfig" did not list the rt2500 pci Card anymore. I deleted rt2xx0 in ./updates and depmod + modprobe and did another reboot, and here I am again. Slow, but online ;)

I can do another test, if you like to get a faster way to contact me, I am neversfelde on freenode, mostly online in #kubuntu-de.org or #kubuntu-devel. Jabber is <email address hidden>.

Thanks for your efforts. I am sure that Ralink will work again in Ubuntu :)

Hi Stefan,

I've got a few minutes so I booted back in 2.6.24-11 (yes, 11, I'm the
one on a gutsy with hardy kernel, and at the moment really I'm running
a very custom .25-rc7; btw I'm sure it doesn't make any difference)

I'm afraid there is still a little problem I can't figure out how to
fix myself, which prevents the driver to load successfully (so we
still don't know if it will even work)

dmesg reports a failure in initialization because it can't load rate algorhithm

Apr 4 23:58:18 localhost kernel: [ 40.189338] phy0: Failed to
select rate control algorithm
Apr 4 23:58:18 localhost kernel: [ 40.189344] phy0: Failed to
initialize rate control algorithm
Apr 4 23:58:18 localhost kernel: [ 40.256640] phy0 ->
rt2x00lib_probe_dev: Error - Failed to initialize hw.
Apr 4 23:58:18 localhost kernel: [ 40.256682] ACPI: PCI interrupt
for device 0000:00:06.0 disabled
Apr 4 23:58:18 localhost kernel: [ 40.256695] rt61pci: probe of
0000:00:06.0 failed with error -2

the directives i have in my working .config looks the same that you
pass via config so I don't know where the problem might be, otherwise
I would provide a patch

I hope this helps

Sorry to report a negative but on my H/W (rt2500) this fails with:

[ 31.651333] phy0 -> rt2x00lib_probe_dev: Error - Failed to initialize hw.
[ 31.651419] rt2500pci: probe of 0000:00:0e.0 failed with error -2

        *-network:1
             description: Wireless interface
             product: RT2500 802.11g Cardbus/mini-PCI
             vendor: RaLink
             physical id: e
             bus info: pci@0000:00:0e.0
             logical name: wmaster0
             version: 01
             serial: 00:11:2f:81:38:ea
             width: 32 bits
             clock: 33MHz

as i've said, guys, the relevant line is
> Failed to select rate control algorithm
it's unlikely that if it didn't work for me it would for you ;)

@Stefan,

there is something funky in your Makefiles, without wasting too much time I just hardcoded a couple of changes so that it would install and at least initialise (see attached patch).

Apr 5 19:15:13 desktop kernel: [ 1987.808748] ACPI: PCI Interrupt 0000:00:0e.0[A] -> GSI 19 (level, low) -> IRQ 19
Apr 5 19:15:13 desktop kernel: [ 1987.808755] PCI: Disallowing DAC for device 0000:00:0e.0
Apr 5 19:15:13 desktop kernel: [ 1987.819500] phy0: Selected rate control algorithm 'pid'
Apr 5 19:15:13 desktop kernel: [ 1987.881851] udev: renamed network interface wmaster0 to eth1

The bad news is that it still doesn't solve my wireless problem:

Apr 5 19:17:50 desktop dhclient: There is already a pid file /var/run/dhclient.wlan0_rename.pid with pid 12743
Apr 5 19:17:50 desktop dhclient: killed old client process, removed PID file
Apr 5 19:17:50 desktop dhclient: Internet Systems Consortium DHCP Client V3.0.6
Apr 5 19:17:50 desktop dhclient: Copyright 2004-2007 Internet Systems Consortium.
Apr 5 19:17:50 desktop dhclient: All rights reserved.
Apr 5 19:17:50 desktop dhclient: For info, please visit http://www.isc.org/sw/dhcp/
Apr 5 19:17:50 desktop dhclient:
Apr 5 19:17:50 desktop dhclient: eth1: unknown hardware address type 801
Apr 5 19:17:50 desktop dhclient: eth1: unknown hardware address type 801
Apr 5 19:17:50 desktop dhclient: Listening on LPF/wlan0_rename/00:11:2f:81:38:ea
Apr 5 19:17:50 desktop dhclient: Sending on LPF/wlan0_rename/00:11:2f:81:38:ea
Apr 5 19:17:50 desktop dhclient: Sending on Socket/fallback
Apr 5 19:17:50 desktop dhclient: DHCPRELEASE on wlan0_rename to 192.168.1.1 port 67
Apr 5 19:17:50 desktop dhclient: send_packet: Network is unreachable
Apr 5 19:17:50 desktop dhclient: send_packet: please consult README file regarding broadcast address.
Apr 5 19:17:50 desktop avahi-autoipd(wlan0_rename)[12732]: Got SIGTERM, quitting.
Apr 5 19:17:50 desktop avahi-autoipd(wlan0_rename)[12732]: Callout STOP, address 169.254.7.101 on interface wlan0_rename
Apr 5 19:17:50 desktop avahi-autoipd(wlan0_rename)[12733]: client: RTNETLINK answers: Numerical result out of range
Apr 5 19:17:50 desktop avahi-autoipd(wlan0_rename)[12733]: Script execution failed with return value 2
Apr 5 19:17:51 desktop kernel: [ 2060.636594] ADDRCONF(NETDEV_UP): wlan0_rename: link is not ready
Apr 5 19:17:51 desktop kernel: [ 2060.638025] wlan0_rename: Initial auth_alg=0
Apr 5 19:17:51 desktop kernel: [ 2060.638028] wlan0_rename: authenticate with AP 00:18:39:90:ba:7c
Apr 5 19:17:51 desktop kernel: [ 2060.652193] wlan0_rename: Initial auth_alg=0
Apr 5 19:17:51 desktop kernel: [ 2060.652197] wlan0_rename: authenticate with AP 00:18:39:90:ba:7c
Apr 5 19:17:51 desktop dhclient: There is already a pid file /var/run/dhclient.wlan0_rename.pid with pid 0
Apr 5 19:17:51 desktop dhclient: Internet Systems Consortium DHCP Client V3.0.6
Apr 5 19:17:51 desktop dhclient: Copyright 2004-2007 Internet Systems Consortium.
Apr 5 19:17:51 desktop dhclient: All rights reserved.
Apr 5 19:17:51 desktop dhclient: For info, please visit http://www.isc.org/sw/dhcp/
Apr 5 19:17:51 desktop dhclient:
Apr 5 19:17:51 desktop dhclient: eth1: unknown ha...

Just would like to :

[ 1 ] Confirm this bug

[ 2 ] The solution : install the latest driver :
http://backports.ubuntuforums.com/showpost.php?p=2395871&postcount=1

The solution is very simple, there was even no need to reboot. It works straight away.

Hope it helps somone.

@harry: actually that's not the latest driver, but it's still the old
legacy, which was already reported to (usually) work; still no support
for network manager, though (even though I actually still don't have
it with the new driver either)

Hardy broke my wireless setup (using serial monkey's rt2570), I have attempted to resolve this issue using the gutsy solutions, however none of them have worked. Some how the device can pick up SSIDs.

When I start and stop network manager, it fails to load up rausb0.

I think it may have defaulted back to RT2500USB, because when I ran iwconfig, it shows it as rt2500usb, but I do not know where to change the rt25000, and I'm quite postive I blacklisted it in modprobe.d

rt73 works fine for me in Hardy. I got "unknow symbol" errors that was due to iwl3945 module, that was in conflict with rt2x00. This is not a trouble with rt2x00 itself. Explanation in bug #203758.

Tried Kubuntu Hardy and my rt2570 (Linksys WUSB54G V4) could not establish a connection with my WPA2 secured network. It fails badly although it recognizes it.

I will once again revert to using 'ndiswrapper'. How sad.

@Caesare:
Thanks for the feedback. Sorry I still had some glitches in the scripts that convert the driver. I just put an updated version of the external driver to http://people.ubuntu.com/~smb/rt2x00-test/ which removes the double prefix issues and hopefully also fixes the uninitialized pid algo. BTW, I try to get the init function named differently from the standard kernel mac80211 so it might co-exist with the kernel module. I also enabled the mesh code in this version.

@IvD:
Maybe you could have a glimpse at that package and check for obvious mistakes. That would be very much appreciated.

second Version of rt2x00-test did not work here. I do not know how to give a better feedback, so let me know, if I can attach some logs etc.

See my comment in bug #203758

@Stefan,

first of all thanks for the terrific job you are doing!
Re. the still failing initialisation, I think we are missing the initialisation call (rt2x_rc80211_pid_init) in ieee80211.c. If we don't define RC80211_PID_COMPILE when we compile it then the wrong path will be taken by the preprocessor in ieee80211.h. It should be enough to add a CFLAGS_ieee80211.o += -DRC80211_PID_COMPILE in Makefile.

@IvD
Thanks. I hope this does not cause confusion for the other bug since everything with rt2x_ prefix is just currently done by me for testing purposes. The reason for not using the native mac80211 is because with the version of mac80211 that is in Hardy the compile of the latest driver (which is supposed to fix a lot of bugs) fails. So I need the versions kernel that comes with the git repository of the rt2x00 project but have to somehow get it working while the older modules are still around.

@Cessare
Youre right. It is only defined for rc80211_pid_algo but would be defined as a function doing nothing for ieee80211.c. If you change that. Do you get further in activation?

@Stefan,

yes, adding CFLAGS_ieee80211.o += -DRC80211_PID_COMPILE to the mac80211 Makefile allows me to initialise, I still fail the association though.

@Cesare,

ok, so I put that change in and update package so others can try. Is the output currently the same as in https://bugs.launchpad.net/ubuntu/+source/linux-ubuntu-modules-2.6.22/+bug/134660/comments/178?
Otherwise the syslog output might be helpful.

@Stefan,

yes, exactly the same.
One question I forgot to ask, I see you have renamed some rt2x_ prefixes to rt2x__ or rt2x___, or perhaps its just a problem of the script you are using?

@Cesare,

ok, I try to find out more. For the prefix issue: that might be coincidence, some functions begin with one or two underscores and just get prefixed with rt2x_. So in the end they have several underscores in them.

I can report success with your rt2x00-test-v3.tgz. This was on a fresh hardy beta install and a D-Link DWA-110 USB Stick (r73).

make
sudo make install
sudo depmd -ae
sudo modprobe -l
sudo update-initramfs -u

Turns out I'm only able to connect to unsecured networks with the DWA-110, and am unable to connect to my local 128bit WEP netework. I have no idea if this is a seperate bug.

Version 3 works here and it seems to be a stable connection with 54mb/s :).
I am using a wpa encrypted wlan network, so I cannot confirm general problems with encryption.

Here it is quite broken: the problem is that the tx-power output before was 27dB, and now it's 18... and my dd-wrt flashed router reports lower signal. Using iwconfig to set the txpower won't let me go above 18dB. Ah, the 1MB/s connection seems fixed.

I don't get any connection - rt2x00usb does not detect by card (rt2570 usb) and rt2500usb detects it but there I unable to establish a connection... You updated packages does not work as well.

Re: the D-Link DWA-110 (rt73), with the v3 test I can connect happily to a WPA2 network. Probably worth ignoring the WEP problem - other people have had difficulty connecting to that network so might be an issue with the Airport Extreme base station.

same problem here: TP-LINK WN321G is recognized and it sees networks, but the connection is very slow and incostant.

Wicd solved the problem for me, I'm using rt61. See my duplicate bug:
https://bugs.launchpad.net/ubuntu/+bug/211443

I tested both rt2x00-test-v3 and -v4 on http://people.ubuntu.com/~smb/rt2x00-test/ and neither managed to get my rt61 pci card connecting to a hidden WPA2-AES network.

v4 works with my rt2500 card and wpa encrypted network.

and no problems with 2.6.24-16-generic.

Hi,

I have 2 Edimax EW-7108PCg cards (rt61pci driver), one in gutsy with hardy kernel and another in hardy beta with all updates.

Both systems are connected to the same access point (with WPA1/AES) and the connection doesn't fall as it did with the gutsy kernel, but it's still inconstant in signal detection and performance.

The information about the connection is also wrong, I think.
This is what i see with iwconfig:

wlan0 IEEE 802.11g ESSID:"Casa"
          Mode:Managed Frequency:2.412 GHz Access Point: 00:18:F3:98:D3:C4
          Bit Rate=1 Mb/s Tx-Power=27 dBm
          Retry min limit:7 RTS thr:off Fragment thr=2346 B
          Link Quality=48/100 Signal level=-40 dBm
          Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
          Tx excessive retries:0 Invalid misc:0 Missed beacon:0

the quality is varies from 50% to 90% with the wireless card and the access point in the same room and the bit rate is always 1Mb/s!!!
Copying a music album (~100Mb) from one computer to the other takes arround 15 min. Too slow!

So, for me rt61pci from hardy is more stable, but much more slow than in gutsy.

For those people with speed problems:
Try setting the rate manually to 54Mbs

I have a rt2500 card and with rt2x00-test-v4 and kernel 2.6.24-16-generic works for me, too. also the speed problem is gone. :)

Still the same problem: worse range because of Tx-power is 18dB instead of 27 with the kernel drivers! Other than that, it seems to work fine, sad I need those extra dB so that it works reliable.

2.1.4 is in linux-backports-modules, I think we should close this, as soon as this version proves to work or at least work better.

This bug doesn't make any sense anyway because it's deals with several completely different problems...

The driver included in the backports package has worse signal, because of Tx-power is 18dB instead of the 27dB I get with the stock kernel drivers. Should I fill a new bug report about that?

Hey, can anyone draw this for me? I'm a bit lost :) My card uses rt73usb, can I expect it to work when the final version of Hardy is released? (I'm sure I wouldn't be able to compile anything anyway).

Hopefully I am not promising too much, but the current intention is to have two possible choices:
1. The kernel driver at the stage of 2.6.24. If this works, good. :)
2. The more recent version of the rt2x00 driver with some modifications to make it compile and load outside
    of the kernel. This will then be part of the linux-backport-modules package.
So everyone would have the freedom of either using one or the other.

Is there any hope of getting the backport on the install CD somewhere in time for hardy release?

If not, is this suitable for mentioning in the release notes or install guide?

Realtek RT61 finally works. It didn't work in Gutsy so my acknowledgemente
for the developers team.

On Tue, Apr 15, 2008 at 4:45 AM, Stuart Bishop <email address hidden>
wrote:

> Is there any hope of getting the backport on the install CD somewhere in
> time for hardy release?
>
> If not, is this suitable for mentioning in the release notes or install
> guide?
>
> --
> Ralink rt2400 / rt2500 / rt2570 / rt61 / rt73 do not work out of the box
> in Gutsy/Hardy
> https://bugs.launchpad.net/bugs/134660
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

Jose R. Padilla,

Does it work with full WPA2 support and Network Manager?

No, it doesn't. It works with WEP 128 encryption and network manager in
Kubuntu, but I will test with WPA2 support and I will report it.

On Tue, Apr 15, 2008 at 2:27 PM, wieman01 <email address hidden> wrote:

> Jose R. Padilla,
>
> Does it work with full WPA2 support and Network Manager?
>
> --
> Ralink rt2400 / rt2500 / rt2570 / rt61 / rt73 do not work out of the box
> in Gutsy/Hardy
> https://bugs.launchpad.net/bugs/134660
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

I thought so. Let us know if there is any progress. WEP is pointless as it is highly insecure.

Anyway, thanks for responding quickly. :-)

Hi everybody, I took a test drive on gutsy with hardy's 2.6.24-16 generic 32-bit kernel: my rt73 dongle works (wep 128, no network manager); the other dongle I own wich is rt2570 based does not work at all as usual; I could not test on a fresh install of hardy as trying to open the network configuration app would stall the computer with a suspicious repeated clicking of the hard drives (?!) I'll try wpa as soon as I can spare some time and report back. ciao luca

More on the previous post: I booted hardy and did not bother to try manual network configuration but went the network manager route; I can now confirm that the rt73 stick works (it's on right now) while the rt2570 does not (still talking of wep as wpa has never been an option with my hardware), there's an improvement however, as the rt2570 dongle now connects via network manager even if the connection itself is very bad and unfit for normal use; I'll try to set up a wpa network and doing tests in such an environment as soon as I can. ciao again luca

on 2.6.25 (from which the driver comes) n-m doesn't work with wpa,
however I can connect via wifi-radar

On Tue, Apr 15, 2008 at 6:42 PM, luca.mg <email address hidden> wrote:
> Hi everybody, I took a test drive on gutsy with hardy's 2.6.24-16
> generic 32-bit kernel: my rt73 dongle works (wep 128, no network
> manager); the other dongle I own wich is rt2570 based does not work at
> all as usual; I could not test on a fresh install of hardy as trying to
> open the network configuration app would stall the computer with a
> suspicious repeated clicking of the hard drives (?!) I'll try wpa as
> soon as I can spare some time and report back. ciao luca
>
>
>
> --
> Ralink rt2400 / rt2500 / rt2570 / rt61 / rt73 do not work out of the box in Gutsy/Hardy
> https://bugs.launchpad.net/bugs/134660
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Hi all,

just to report that an ASUS USB dongle (rt73) runs without problem
under Hardy beta with WEP 64 bit encryption. Out of the box, with
network manager.

Ta

Hey,
I'm with rt73usb under the latest Hardy beta live cd, and the connection seems alright :) Didn't die on me, and I was daring (opening all sorts of tabs at once)! The signal is a bit unstable though. I'm right next to the router and it shows 52% of signal, and then 83%, and then 68%. That's not such a big problem for me (as long as it stays alive), but thought I should let you know.
Either way, I'm installing Hardy beta right now!
~o.