Feisty regression: wifi not working (rt2500, wg54t)

Bug #82711 reported by David Gerard
8
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Incomplete
Undecided
Unassigned
linux-source-2.6.20 (Ubuntu)
Won't Fix
Undecided
Dave Morley

Bug Description

Testing on Compaq N410c and Dell Latitude D600 laptops - my wifi cards Just Work on both in Edgy, but not in Feisty. The cards are a Belkin F5D7010 (rt2500) and NetComm 54g (wg54t).

In both cases, the kernel detects the card okay and dhclient runs. However, the card doesn't seem to pull an address and gives itself a 169.254 address. e.g., from ifconfig (Belkin card on Dell):

ra0 Link encap:Ethernet HWaddr 00:11:50:66:9B:5F
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3262 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b) TX bytes:130480 (127.4 KiB)
          Interrupt:11 Base address:0xc000

ra0:avahi Link encap:Ethernet HWaddr 00:11:50:66:9B:5F
          inet addr:169.254.6.43 Bcast:169.254.255.255 Mask:255.255.0.0
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          Interrupt:11 Base address:0xc000

Kernel: Linux 2.6.20-6-generic #2 SMP Wed Jan 31 20:53:39 UTC 2007 i686 GNU/Linux

This also happened with 2.6.20-5.

Here's the console log from plugging the Belkin card into the Dell:

Feb 1 18:20:39 paris NetworkManager: <debug info>^I[1170354039.830151] nm_hal_device_added (): New device added (hal udi is '/org/freedesktop/Hal/devices/pci_1814_201').
Feb 1 18:20:39 paris NetworkManager: <debug info>^I[1170354039.842142] nm_hal_device_added (): New device added (hal udi is '/org/freedesktop/Hal/devices/net_00_11_50_66_9b_5f').
Feb 1 18:20:39 paris kernel: [ 1363.508000] pccard: CardBus card inserted into slot 0
Feb 1 18:20:39 paris kernel: [ 1363.508000] PCI: Enabling device 0000:03:00.0 (0000 -> 0002)
Feb 1 18:20:39 paris kernel: [ 1363.508000] ACPI: PCI Interrupt 0000:03:00.0[A] -> Link [LNKD] -> GSI 11 (level, low) -> IRQ 11
Feb 1 18:20:39 paris kernel: [ 1363.508000] rt2500 1.1.0 BETA4 2006/06/18 http://rt2x00.serialmonkey.com
Feb 1 18:20:39 paris kernel: [ 1363.508000] PCI: Setting latency timer of device 0000:03:00.0 to 64
Feb 1 18:20:39 paris kernel: [ 1363.664000] rt2500 EEPROM: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 Channel
Feb 1 18:20:39 paris kernel: [ 1363.664000] rt2500 EEPROM: 7 7 7 7 7 7 7 7 7 7 7 7 7 7 dBm Maximum
Feb 1 18:20:39 paris NetworkManager: <information>^Ira0: Device is fully-supported using driver 'rt2500'.
Feb 1 18:20:39 paris NetworkManager: <information>^Inm_device_init(): waiting for device's worker thread to start
Feb 1 18:20:39 paris NetworkManager: <information>^Inm_device_init(): device's worker thread started, continuing.
Feb 1 18:20:39 paris NetworkManager: <information>^INow managing wireless (802.11) device 'ra0'.
Feb 1 18:20:39 paris NetworkManager: <information>^IDeactivating device ra0.
Feb 1 18:20:56 paris dhclient: DHCPDISCOVER on ra0 to 255.255.255.255 port 67 interval 5
Feb 1 18:21:01 paris dhclient: DHCPDISCOVER on ra0 to 255.255.255.255 port 67 interval 11
Feb 1 18:21:12 paris dhclient: DHCPDISCOVER on ra0 to 255.255.255.255 port 67 interval 13
Feb 1 18:21:25 paris dhclient: DHCPDISCOVER on ra0 to 255.255.255.255 port 67 interval 2
Feb 1 18:21:27 paris dhclient: No DHCPOFFERS received.
Feb 1 18:21:27 paris dhclient: No working leases in persistent database - sleeping.
Feb 1 18:21:27 paris avahi-autoipd(ra0)[5600]: Found user 'avahi-autoipd' (UID 103) and group 'avahi-autoipd' (GID 107).
Feb 1 18:21:27 paris avahi-autoipd(ra0)[5600]: Successfully called chroot().
Feb 1 18:21:27 paris avahi-autoipd(ra0)[5600]: Successfully dropped root privileges.
Feb 1 18:21:27 paris avahi-autoipd(ra0)[5600]: fopen() failed: Permission denied
Feb 1 18:21:27 paris avahi-autoipd(ra0)[5600]: Starting with address 169.254.6.43
Feb 1 18:21:33 paris avahi-autoipd(ra0)[5600]: Callout BIND, address 169.254.6.43 on interface ra0
Feb 1 18:21:33 paris avahi-daemon[4615]: New relevant interface ra0.IPv4 for mDNS.
Feb 1 18:21:33 paris avahi-daemon[4615]: Joining mDNS multicast group on interface ra0.IPv4 with address 169.254.6.43.
Feb 1 18:21:33 paris avahi-daemon[4615]: Registering new address record for 169.254.6.43 on ra0.
Feb 1 18:21:36 paris sudo: fun : TTY=pts/2 ; PWD=/home/fun ; USER=root ; COMMAND=/usr/sbin/wifi-radar
Feb 1 18:21:37 paris dhclient: isc-dhclient-V3.0.4
Feb 1 18:21:37 paris avahi-autoipd(ra0)[5600]: Successfully claimed IP address 169.254.6.43
Feb 1 18:21:37 paris avahi-autoipd(ra0)[5600]: fopen() failed: Permission denied
Feb 1 18:26:19 paris dhclient: DHCPDISCOVER on ra0 to 255.255.255.255 port 67 interval 8
Feb 1 18:26:27 paris dhclient: DHCPDISCOVER on ra0 to 255.255.255.255 port 67 interval 12
Feb 1 18:26:39 paris dhclient: DHCPDISCOVER on ra0 to 255.255.255.255 port 67 interval 11
Feb 1 18:26:50 paris dhclient: No DHCPOFFERS received.
Feb 1 18:26:50 paris dhclient: No working leases in persistent database - sleeping.

David Gerard (dgerard)
description: updated
David Gerard (dgerard)
description: updated
Revision history for this message
Dave Morley (davmor2) wrote :

Thank you for your report. Could you try the following please.

open a terminal and type the following.

sudo cp /etc/network/interfaces /etc/network/interfaces.bak

then the following.

sudo gedit /etc/network/interfaces

scroll down the text till you get to the auto ra0 .....

Delete the two lines with ra0 in then save the file. then reboot your laptop. If that doesn't work you can do.

sudo rm /etc/network/interfaces

then

sudo mv /etc/network/interfaces.bak /etc/network/interfaces

and reboot that will reset to your original settings.

Revision history for this message
David Gerard (dgerard) wrote :

I got as far as editing /etc/network/interfaces - it does not contain anything about ra0 at all! Should it? Current contents are:

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto eth1
iface eth1 inet dhcp

auto eth2
iface eth2 inet dhcp

auto ath0
iface ath0 inet dhcp

auto wlan0
iface wlan0 inet dhcp

Revision history for this message
Dave Morley (davmor2) wrote :

In that case I would remove one at a time starting with eth1 as eth0 is normally wired network. Basically network manager will only manage a wifi card that isn't already managed so you need to remove the cards details from interfaces so that network manager can use it.

Revision history for this message
David Gerard (dgerard) wrote :

The rt2500 part of this bug appears to be bug 78037. The by-hand fix there works (I need to do "sudo dhclient3 ra0" afterwards, and I have to apply the bug fix again by hand if I unplug the card).

The Netcomm card is actually a Netcomm 11g, and uses the prism54 driver. The same by-hand fix there works for this. Success!

So there's a workaround, if not an automatic solution. However, the same problem on different drivers suggests the cause might be at a higher level than the kernel.

Revision history for this message
Dave Morley (davmor2) wrote :

okay that's super I will pass this info onto the devs have you got the links for the solutions please? If so can you paste them here many thanks.

Revision history for this message
David Gerard (dgerard) wrote :

As I noted above, I got it from bug 78037 :-) When starting up or plugging in a card, do:

sudo ifconfig [interface] down
sudo iwconfig [interface] essid [essid] key [key]
sudo ifconfig [interface] up
sudo dhclient3 [interface]

I also listed this on the forums, with a note for people to add other chips this works for: http://ubuntuforums.org/showthread.php?p=2092813

Revision history for this message
Dave Morley (davmor2) wrote : Re: [Bug 82711] Re: Feisty regression: wifi not working (rt2500, wg54t)

Many thanks.

--
Seek That Thy Might Know

Revision history for this message
Paul Coleman (pdcoleman) wrote :

The ralink open source drivers are currently a mess in feisty. The rt2400/rt2500/rt2570 drivers are built from the legacy source and the rt61pci/rt73usb drivers are built from rt2x00 source. Both source packages date back to the first of December. The legacy rt2500 driver is known not to work with Network Manager. To avoid having to manually start my network every time I boot I had to remove NM.

Revision history for this message
melaren (me-laren) wrote :

I have a Foxconn card that uses the rt2500 driver. In Dapper and Edgy I was able to get the wireless working if I disabled my onboard NIC and manually entered the wireless network name in Network Admin. I'm currently trying Feisty Herd 5 and I have been unable to get the new network manager to connect to any wireless networks (even though it sees them). If I disable the onboard NIC and the roaming mode and select a wireless network in Network Admin, I am able to connect. ...but the new network manager icon says there is no network connection. Hopefully this is the appropriate place for this post.

Revision history for this message
chris langton (saintlangton) wrote :

Just download and installed feisty beta and my Rt2500 wifi card doesn't work with network manager. By removing network manager using System>Preferences>Sessions and manually entering details into System>Administration>Network the network does work. (This is all after I had to disable IPv6 as per http://ubuntuforums.org/showthread.php?t=87798 to get any connection - It just timed out before) both of these just annoyances for me but would be tricky for a newbie.

Revision history for this message
chris langton (saintlangton) wrote :

Just downloaded and installed feisty beta and my Rt2500 wifi card doesn't work with network manager. By removing network manager using System>Preferences>Sessions and manually entering details into System>Administration>Network the network does work. (This is all after I had to disable IPv6 as per http://ubuntuforums.org/showthread.php?t=87798 to get any connection - It just timed out before) both of these just annoyances for me but would be tricky for a newbie.

Revision history for this message
magilus (magilus) wrote :

"Supports unencrypted and WEP networks when used with NetworkManager. While the driver supports WPA, it does not use Linux Wireless Extensions for WPA support, which is required for NetworkManager."

From http://live.gnome.org/NetworkManagerHardware

I'd say, report a seperate bug about rt2500 not working with network-manager.

Also, it is important if it worked with prior Feisty kernel versions. If it did, file the bug against linux-source-2.6.20.

If it never worked with network-manager, file a bug against network-manager.

Revision history for this message
sam tygier (samtygier) wrote :

also see Bug #37120

Revision history for this message
Xavier (christian-nolasco) wrote :

Hello Folks!

I do have dwl-g122 rev B1. same story wep works fine, open network works fine, wpa it's hell on earth impossible to make it work I am using Kubuntu 7.04, so I am asuming it's the driver,
I tried wpa supplicant don't know what else to do. Zydas zd1211rw works with WPA fine...

Revision history for this message
Launchpad Janitor (janitor) wrote : This bug is now reported against the 'linux' package

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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