Bug 411481 - Linksys WUSB54G USB cannot get IP address with updated kernels
Linksys WUSB54G USB cannot get IP address with updated kernels
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
i686 Linux
low Severity high
: ---
: ---
Assigned To: John W. Linville
Fedora Extras Quality Assurance
Depends On:
Blocks: 427009
  Show dependency treegraph
Reported: 2007-12-04 22:56 EST by Bryan Christ
Modified: 2008-11-20 14:15 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-11-20 14:15:14 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
dmesg output from working configuration (20.02 KB, text/plain)
2007-12-13 11:53 EST, Bryan Christ
no flags Details
dmesg output from a non-working configuration (20.06 KB, text/plain)
2007-12-13 12:14 EST, Bryan Christ
no flags Details
output from lsusb (2.27 KB, text/plain)
2007-12-13 12:18 EST, Bryan Christ
no flags Details
Wireshark Capture (318.87 KB, application/octet-stream)
2008-01-04 18:32 EST, Bryan Christ
no flags Details
dmesg (23.38 KB, text/plain)
2008-03-24 10:53 EDT, Bryan Christ
no flags Details

  None (edit)
Description Bryan Christ 2007-12-04 22:56:49 EST
Description of problem:

WUSB54G USB cannot get IP address with updated kernels.  Only kernel
kernel- works correctly.

It also does not matter whether you use the NetworkManager tool or
iwconfig/dhclient manually.

Tested the failure with kernels:

Version-Release number of selected component (if applicable):

How reproducible:


Steps to Reproduce:
1.  Install F8 32-bit 
2.  Plug in Linksys WUSB54G USB adapter
3.  Configure adapter with a with a 40-bit WEP key (open system)
4.  Should work.
5.  Upgrade to newer kernel via yum.
6.  Reboot.
7.  Adapter will no longer fetch an IP address
Actual results:

Expected results:

Additional info:

Test system is an HP Compaq dc7100 usdt
Comment 1 Pete Zaitcev 2007-12-05 11:52:05 EST
I have an adapter but not the wireless infrastructure to test.
Please attach the dmesg output from both kernels (do not use the one in
/var/log/dmesg, capture it anew after the adapter fails to work).
The dmesg should also tell if it's p54u or rndis -- same hardware
different versions use different drivers.
Comment 2 Bryan Christ 2007-12-13 11:50:58 EST
Retested with updates from updates-testing:



Still no change.
Comment 3 Bryan Christ 2007-12-13 11:53:27 EST
Created attachment 287631 [details]
dmesg output from working configuration
Comment 4 Bryan Christ 2007-12-13 12:14:04 EST
Created attachment 287641 [details]
dmesg output from a non-working configuration
Comment 5 Bryan Christ 2007-12-13 12:18:12 EST
Created attachment 287651 [details]
output from lsusb
Comment 6 Bryan Christ 2007-12-27 14:36:00 EST

I thought I would mention that the adapter appears to be using the rt2x00usb
kernel module.
Comment 7 John W. Linville 2008-01-02 14:32:27 EST
The rt2500usb driver version in -42.fc8 is months old -- the jump to -49.fc8 
was too large to easily pinpoint a likely changeset.

I'm copying the main rt2x00 developer to see if he has any insight...
Comment 8 Ivo van Doorn 2008-01-02 17:05:05 EST
Ok, the problem has nothing to do with DHCP. Apparently the device is not 
authenticating and thus isn't even associated to the AP.

(This means this bug is a duplicate of [Bug 9388] Unable to associate rt25xx 
USB key with a WPA AP)

Could you try using wireshark on a different machine to see if the 
authentication requests are leaving the device and if there is a response for 
them from the AP?
Comment 9 John W. Linville 2008-01-03 10:11:51 EST
Bryan, can you provide the information Ivo is requesting?
Comment 10 Bryan Christ 2008-01-04 15:45:29 EST
Unfortunately, this is the only machine I have configured with that adapter and
Fedora 8.  I'd be glad to capture whatever information you need from the one
machine I have, but I'll need some guidance on how to use the tool to collect
the needed info.
Comment 11 John W. Linville 2008-01-04 15:54:09 EST
The machine running wireshark can have any kind of adapter (as long as it 
supports monitoring)...does that change the picture?
Comment 12 Bryan Christ 2008-01-04 16:18:21 EST
Oh, yes indeed.  I have a laptop that participates on the same network. 
Basically, I would just need some instructions on how to capture the information
you need with wireshark.  That is not a tool I am familiar with.
Comment 13 Ivo van Doorn 2008-01-04 17:12:25 EST
Put the interface on your laptop in monitor mode (iwconfig wlan0 mode monitor)
start wireshark (As user with enough privileges)
Select Capture->Interfaces
Press the start button next to your interface.

On your machine with rt2500usb, start the network interface and let it attempt 
a few connections.

If all goes right you will see wireshark reporting a lot of frames, you can 
save those results to a file which you can attach to this bug report.
Comment 14 Bryan Christ 2008-01-04 18:32:15 EST
Created attachment 290874 [details]
Wireshark Capture
Comment 15 Bryan Christ 2008-01-04 18:33:48 EST
I tried 3 time with NetworkManager to make a connection while running Wireshark.
 The kernel on the misbehaving system is:

Comment 16 Ivo van Doorn 2008-01-09 16:40:49 EST
John, please make sure you merge the patch:
rt2x00: Corectly initialize rt2500usb MAC
which I have send to the linuxwireless mailinglist today, that should resolve 
this issue.
Comment 17 Bryan Christ 2008-01-09 16:54:35 EST
I'll be glad to test the patched kernel if someone can provide me with the rpms.
Comment 18 John W. Linville 2008-01-11 16:14:56 EST

Does this help?
Comment 19 Bryan Christ 2008-01-16 16:15:53 EST

I retested with from updates-testing and the problem still persists.
Comment 20 Bryan Christ 2008-02-01 13:01:16 EST
Retested with kernel- and problem still persists.
Comment 21 Bryan Christ 2008-02-29 18:32:11 EST

Any news on this?
Comment 22 John W. Linville 2008-03-04 14:14:27 EST
No, sorry -- nothing specific.  What is the latest F8 kernel you have tried?
Comment 23 John W. Linville 2008-03-13 11:13:05 EDT
The kernels here contain an update to rt2x00 version 2.1.4:


Could you give those kernels a try to see if they resolve this issue for you?
Comment 24 Bryan Christ 2008-03-13 11:54:49 EDT

I will try one of these sometime between now and Monday.
Comment 25 Bryan Christ 2008-03-18 13:11:30 EDT
I tried the test kernel you mentioned and it did not resolve the problem.
Comment 26 John W. Linville 2008-03-18 13:16:16 EDT
Please post a new round of dmesg output...thanks!
Comment 27 Bryan Christ 2008-03-24 10:53:06 EDT
Created attachment 298896 [details]
Comment 28 Bryan Christ 2008-04-24 20:32:16 EDT
Retested with from updates-testing and it still does not work.
Comment 29 Bryan Christ 2008-06-05 11:27:56 EDT
I retested with from the "updates-testing" repo.  The problem is
still not fixed.
Comment 30 Fedora Update System 2008-08-07 20:00:20 EDT
kernel- has been pushed to the Fedora 8 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update kernel'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F8/FEDORA-2008-7128
Comment 31 Fedora Update System 2008-08-12 14:22:32 EDT
kernel- has been pushed to the Fedora 8 stable repository.  If problems still persist, please make note of it in this bug report.
Comment 32 Bryan Christ 2008-08-12 14:30:07 EDT

I haven't forgotten about this bug.  It may be several weeks before I can test this new kernel because that machine is packed in a box until our family is moved.


Note You need to log in before you can comment on or make changes to this bug.