Red Hat Bugzilla – Bug 468673
rt73usb: Cold plugged USB device often does not work
Last modified: 2009-02-10 09:33:55 EST
Created attachment 321606 [details]
System log for the failed association
Description of problem:
Device ID 06f8:e010 Guillemot Corp. HWGUSB2-54-LB, which uses the rt73usb driver, often fails to associate with an access point if it was already plugged in when the computer is started.
Version-Release number of selected component (if applicable):
F9 (2.6.26-79 i686 4 core) and rawhide (F10 snap 3)
ID 06f8:e010 Guillemot Corp. HWGUSB2-54-LB
Steps to Reproduce:
1. Plug device and start computer
2. Attempt to associate with an access point
See attached log
Association works and wifi is usable.
Device works properly on Windows XP. Workaround is to unplug the device and hotplug it.
Hmm. what seems to be happening is that network manager starts talking to rt73, and suddenly the USB host decides that the hardware is gone.
This is either due to either sending an incorrect signal to the device, or bashing register values into the device. In both cases rt73usb (and rt2500usb) are known to simply shutdown immediately, and forcing the user to reinsert the device.
I'll try to find out what NetworkManager is actually doing when it prints:
NetworkManager: <info> (wlan0): supplicant connection state change
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.
More information and reason for this action is here:
Does this continue to happen with current rawhide kernels?
It appears to be fixed with kernel-2.6.29-0.22.rc4.git1.fc10 so the rt73usb stick should now be reliable.
However, my rt2500usb stick no longer works with this new kernel (it associates with the access point very quickly, but the DHCP times out). Do you want a bugzilla about this ?
Sure, please do. In the meantime, I'll close this one.