Red Hat Bugzilla – Bug 494380
ath5k never associates with an AP, unless first connected to wired eth0
Last modified: 2009-11-10 20:14:38 EST
Yeah, so it's a weird one, and it's driving me nutters. I never seem to get connected to an AP running PSA2, unless I first connect to wired eth0 (or, potentially, unless I first get a kernel stack trace). I'm willing to provide any sort of data you may need to help troubleshoot this issue.
This is a Thinkpad x31 with an Atheros wireless chipset.
My dmesg is attached. Please help! :)
Created attachment 338357 [details]
And by PSA2 I mean WPA2 Personal, of course. Sorry.
Thanks for filling this bug.
Can you please provide the version of NM you use with
rpm -qa NetworkManager
and also /var/log/messages when you try to connect to your AP and need to activate the wired connection to do this. Thank you.
Fedora Bugzappers volunteer triage team
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.
More information and reason for this action is here:
Please re-open if this still happens with latest Fedora 11 update kernels. Latest should be 220.127.116.11-96.fc11. Updated kernels have fixes for various ath5k and other wifi issues. Thanks!