GNOME Bugzilla – Bug 595178
USB Dongle Not Detected Since Upgrade to Network Manager 0.8x
Last modified: 2009-09-18 17:02:22 UTC
Created attachment 143158 [details] DMESG with Dongle picked up with NM 0.71 Since my laptop has been u[graded from Network Manager 0.71 to 0.8x in Karmic my Edimax Wiress USB dongle has failed to be picked up by Network Manager in Gnome. Before I had no problems with it workling very robostly. Sometimes it will be picked up and listed in the network manager list, but 9 times out of 10 it is failed to be picked up. Down grading back to NM 0.71 does bring it back to life a bit, but is sitill noto as robost as it was before, it will keep dropping the connection and failing to reconnect. In the early stages of the Karmic cycle on Kernel 2.6.31 I reported another bug which was here https://bugs.launchpad.net/ubuntu/+source/linux/+bug/396417 , but iam reporting these seperatley as this was since Network Manager got upgraded. I have eaited a couple of weeks so see if a fix got released as there are other Bugs against NM but am filing this now.
Created attachment 143159 [details] DMESG with Dongle not picked up NM with 0.8x
Created attachment 143160 [details] LSUSB Output with NM 0.71
Created attachment 143162 [details] LSUSB Output with NM 0.8x
Created attachment 143163 [details] SYSLOG with NM 0.71 after Dongle dropped connection
Created attachment 143164 [details] SYSLOG with NM 0.71
Created attachment 143165 [details] SYSLOG with NM 0.8x
This actually looks like a flaky adapter. If 'lsusb' doesn't show the device, then the kernel won't know it's there, and a driver can't drive it, and NM can't find it. Basically, all those USB errors like: [ 213.494214] usb 1-5: USB disconnect, address 3 [ 213.494426] phy3 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x3040 with error -19. ... [ 214.216020] hub 2-0:1.0: unable to enumerate USB device on port 3 [ 216.656042] usb 2-3: new full speed USB device using ohci_hcd and address 3 [ 216.840035] usb 2-3: device descriptor read/64, error -62 [ 217.124032] usb 2-3: device descriptor read/64, error -62 ... indicate a hardware fault (either in the dongle or the computer) and are not an NM issue. I know it seems odd that this happened right when you updated NM, but it's most likely conincidental. You could try another wifi dongle that's known to work on another machine, or you could try plugging it into a different port on your machine. Or, you could try plugging the dongle into another machine and see if 'lsusb' shows it there, then try on your machine again. Please re-open if 'lsusb' sees the device *and* NM doesn't find it. Thanks!
Hi Dan I have tried this dongle of mine on another laptop which uses Ubuntu 9.04 kernel 2.6.28 and it works fine, and i have also reinstalled my own laptop with 9.04 and it also works fine to. Some times network manager will pickup the dongle and will work fine, but usually it will not. Andy
When it doesn't find the dongle, does 'lsusb' show the dongle? Should be able to do just 'lsusb' and see if its' there, you don't need to wade through the detailed output of 'lsusb -vv'.
Hi Dan lsusb does not show the dongle with NM 0.8x, but with 0.71 it shows as follows:- Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 148f:2573 Ralink Technology, Corp. RT2501USB Wireless Adapter Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub With Januty my dongle is picked up each time under NM 0.71, but on Karmic since the upgrade from 0.71 to 0.8x it is hardly ever picked up my NM. Downgrading to 0.71 does help alot but it is not as robost after downgrading, but using it on a Januty install not problems at all.
So you mean on Jaunty it works, but on Karmic it doesn't? If that's the case, then you should probably file a bug in Launchpad against the 'kernel' component because it's most likely a kernel problem, not a NetworkManager one. If the device doesn't show up in 'lsusb', that's a kernel & driver issue unrelated to NetworkManager. Since Karmic and Jaunty use different kernel versions, it's quite possible that a bug got into the kernel for the rt2x00 driver.