Red Hat Bugzilla – Bug 439924
ath5k not detecting networks
Last modified: 2008-05-05 13:12:43 EDT
Description of problem:
After installing fedora 9 beta, ath5k has seemed to stop wroking for me. I was
having very few problems in fedora 8 but now no networks show up in network
manager and "iwlist wlan0 scanning" nets no results.
Version-Release number of selected component (if applicable):
using an atheros AR5212 802.11abg NIC
Steps to Reproduce:
1.install fedora 9
2.attempt to connect to a wireless network
no wireless networks found, cannot connect manually.
a list of wireless networks, abilitiy to connect to a specific network
Created attachment 299794 [details]
Created attachment 299795 [details]
Please attach the output of running 'iwlist wlan0 scan'...thanks!
Don't know how much this will help but here it is in all its glory :-D....
[root@thinktank ~]# iwlist wlan0 scan
wlan0 No scan results
I don't think it is an issue with just NetworkManager or something since this
way doesn't find any wireless networks (and there are plenty around me).
Ah, ok...do you recall what was the last F8 kernel that worked?
Looking at https://admin.fedoraproject.org/updates/kernel it would appear that
the last kernel I used in F8 was kernel-18.104.22.168-50.fc8. If not then
kernel-22.214.171.124-34.fc8 definately worked. I only upgraded to F9 beta a few days
ago so it should be that first kernel.
Hmmm...there is a patch between -34.fc8 and -50.fc8 that touched ath5k, but
none since then.
The first rawhide kernel that had the ath5k patch in question of
And the one before that was 2.6.25-0.113.rc5.git2.fc9:
Could you test those two kernels to see if one had the problem and the other
does not? Thanks!
Sorry about the delay in getting back to you been a bit busy. Niether of those
kernels seem to solve the problem. If I have some time later today or tomorrow
I'll try some other kernels that have had changes in the ath5k driver. It
almost seems like the radio is just off or something...
Created attachment 302238 [details]
a newer dmesg
I noticed some new messages in dmesg about ath5k that I don't think were there
when I opened this bug... maybe this will provide some more clues.
It seems to be working now... I think a newer kernel took away this problem.
Ah, thanks! What kernel are you running now?
I am on 2.6.25-14.fc9.x86_64, this message is coming from my backyard wirelessly