Red Hat Bugzilla – Bug 439685
rt73usb mostly does not work after booting.
Last modified: 2009-05-05 20:50:15 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de; rv:22.214.171.124) Gecko/20080325 Fedora/126.96.36.199-1.fc8 Firefox/188.8.131.52
Description of problem:
D-Link DWL-G122 is attached to a USB 1.1 connection. I expected it,to connect to wlan by NetworkManager with WPA-PSK after booting, as it did with my previous kernel-184.108.40.206-34.fc8. However, while rt73usb is detected, when booting, there mostly does not come up any connection. Seldomly, however, it is working correcty after booting. When it is not working, I see something like the following in /var/log/messages:
Mar 29 20:20:05 localhost kernel: hub 1-0:1.0: port 2 disabled by hub (EMI?), re-enabling...
Mar 29 20:20:05 localhost kernel: usb 1-2: USB disconnect, address 3
Mar 29 20:20:05 localhost kernel: phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x3040 with error -19.
Mar 29 20:20:05 localhost kernel: phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x06 failed for offset 0x3040 with error -19.
Mar 29 20:20:05 localhost kernel: phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x06 failed for offset 0x3028 with error -19.
Mar 29 20:20:05 localhost kernel: phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x06 failed for offset 0x3064 with error -19.
Mar 29 20:20:05 localhost kernel: phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x0c failed for offset 0x0000 with error -19.
Mar 29 20:20:05 localhost kernel: phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x0a failed for offset 0x0000 with error -19.
Mar 29 20:20:11 localhost kernel:last message repeated 5 times
May be an error depending on timing, because sometimes not reproducable?
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Plug in the USB-stick
2.Boot the system and log in to Gnome as root or user.
3.Wait for an eternity. No connection and no flickering leds at the sticks.
No Wlan connection.
A Wlan connection.
NetworkManager does not show up the wlan-conection as selectable, after this happens.
Perhaps, the driver is not tested before with usb1.1 connection ??
is this a duplicate of bug #437809 ?
I'm not sure I see the connection...point it out to me?
Both are using the r73usb module. NetworkManager does not show up the wireless
connection as selectable... I thought that there's no 'enable wireless' option
on the nm-applet. My mistake?
Please try -69.fc8 (or later):
Does that help?
Created attachment 301691 [details]
bug text-file appearing after booting the requested 2.24.4-69.fc8 kernel
I installed the kernel from koji and booted as root.rt73usb did not come up.
Created attachment 301692 [details]
/var/log/dmesg after booting 2.4.24-69.fc8
Created attachment 301693 [details]
/var/log/messages after booting 2.24.4-69.fc8
Rebooting some more times with the required kernel never produced a working
wireless connection.However, the corresponding messages files differed slightly,
and the nm-applet bug file was never reproduced.
Thank you for your engagement with the problem.
Please attach the output of running 'ifconfig -a' and 'iwconfig'...thanks!
Created attachment 302035 [details]
The ifcofig -a and iwconfig outputs + the actual /var/log/messages
I think the network names are strange. Perhaps an udev and NetworkManager
Created attachment 302069 [details]
the above file
The above file is from a reboot, where the stick surprisingly worked, at least,
when believing, what NetworkManager and iwconfig (with correct name wlan0)
indicated. Slowdon because of myriads of error messages in the file prevented
more work in this system.
It has been a while, and there have been some key rt2x00 fixes...can you try
something more recent?
Created attachment 304361 [details]
/var/log/ fies, ifconfig -a and iwconfig (usb-stick attached, but no lan-cabel)
I installed kernel-220.127.116.11-87.fc8.i686.rpm and
kernel-devel-18.104.22.168-87.fc8.i686.rpm from your suggested koji site and before
that I did an automatic yum updatesd of the system (including new versions of
NetworkManager and wpasupplicant). However, after rebooting the above
kernel-devel-22.214.171.124-87.fc8 there was no success and no working leds at the
stick. Some resulting /var/log/ and /etc/ files are included in the above
Do you continue to experience problems with current kernels?
No more problems now, but I did not get the stick working with Fedora on my
labtop. I did the following:
1. I checked that stick with Windows XP, the same WPA,PSK,TKIP keying, but it
didnot work either. so I bought a new stick of the same revision level C1 and
checked that again with the same Windows, and it worked correctly.
2. I checked that new stick with th same fc8, and it did not work. I rechecked
it after a yum upgrade to fc9. It still did not work.
3. As I wanted to use the labtop during holidays, I installed a new Ubuntu 8.04
(with kernel 2.6.24 and NetworkManager). It worked with the new stick (but not
with the old one, which I then put into the waste).
Sorry about the additional hardware problem with the stick. At hte moment, I
have no more problem personally. Perhaps, I should have made a fresh install to
fc9 instead of a yum upgrade, but I was in a huury in order to get things
running before holidays. Thank you.
Sounds like you will be unavailable for further Fedora testing...
Yes, that is the case for the next year or so.
I have 3 laptops and a desktop running Fedora 10. I have an rt73usb wireless USB dongle. It works only on the 533Mhz Compaq Armada. The rest all work for a few seconds then fail with "phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x3040 with error -19." At the instance that error occurs, the lights go out on the USB stick as if it was powered off.
Even on the slowest system, it will occasionally fail (as in once every few weeks) - and refuse to work until I do a full power off. Even on the faster systems, it will occasionally work (as in once every 100 or so tries - I keep trying just for kicks). And once it gets connected the first time without the lights going out, it will continue to work until the system is powered off.
I previously submitted bug https://bugzilla.redhat.com/show_bug.cgi?id=426777