Description of problem:
WUSB54G USB cannot get IP address with updated kernels. Only kernel
kernel-220.127.116.11-42.fc8 works correctly.
It also does not matter whether you use the NetworkManager tool or
Tested the failure with kernels:
Version-Release number of selected component (if applicable):
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.
7. Adapter will no longer fetch an IP address
Test system is an HP Compaq dc7100 usdt
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.
Retested with updates from updates-testing:
Still no change.
Created attachment 287631 [details]
dmesg output from working configuration
Created attachment 287641 [details]
dmesg output from a non-working configuration
Created attachment 287651 [details]
output from lsusb
I thought I would mention that the adapter appears to be using the rt2x00usb
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...
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?
Bryan, can you provide the information Ivo is requesting?
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.
The machine running wireshark can have any kind of adapter (as long as it
supports monitoring)...does that change the picture?
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.
Put the interface on your laptop in monitor mode (iwconfig wlan0 mode monitor)
start wireshark (As user with enough privileges)
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.
Created attachment 290874 [details]
I tried 3 time with NetworkManager to make a connection while running Wireshark.
The kernel on the misbehaving system is: 18.104.22.168-85
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
I'll be glad to test the patched kernel if someone can provide me with the rpms.
Does this help?
I retested with 22.214.171.124-105 from updates-testing and the problem still persists.
Retested with kernel-126.96.36.199-107 and problem still persists.
Any news on this?
No, sorry -- nothing specific. What is the latest F8 kernel you have tried?
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?
I will try one of these sometime between now and Monday.
I tried the test kernel you mentioned and it did not resolve the problem.
Please post a new round of dmesg output...thanks!
Created attachment 298896 [details]
Retested with 188.8.131.52-85 from updates-testing and it still does not work.
I retested with 184.108.40.206-10 from the "updates-testing" repo. The problem is
still not fixed.
kernel-220.127.116.11-69.fc8 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
kernel-18.104.22.168-69.fc8 has been pushed to the Fedora 8 stable repository. If problems still persist, please make note of it in this bug report.
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.