I have the following Wireless, according to lspci -vv: 06:00.0 Ethernet controller: Atheros Communications Inc. AR5001 Wireless Network Adapter (rev 04) (Longer output attached.) It does not work, i.e. I can see APs, but I can't connect. I get the infamous "ath5k phy0: noise floor calibration timeout (2412MHz)", which should be fixed in 2.6.28.1, according to http://wiki.debian.org/ath5k#KnownIssues, but it's still there. I have no idea whether this message is related to my problem. I also saw once or twice a "privacy configuration mismatch and mixed-cell disabled" message. I filed the bug already in Debian: http://bugs.debian.org/520622
Created attachment 22967 [details] Error message from dmesg
Created attachment 22968 [details] Output from lspci -vv
FWIW, "does not work" is the sort of phrase that makes developers ignore you... :-) Being more specific is helpful. Are you able to associate with the AP? Does the connection survive for some time before you get theses messages? Is there some activity or even that is associated with seeing these message? Does the device recover? If not, what about if you remove and reinsert the ath5k module? Any other details about the situation might be helpful as well.
> Are you able to associate with the AP? No. I can see APs with iwlist scanning, but I can't connect. I don't get an IP. Tested with both WPA2 and with encryption switched off at the AP. Also tested with two (hopefully) identical laptops (FSC Esprimo Mobile). > Does the connection survive for some time before you get theses messages? I'm under the impression, that I can't get any connection. > Is there some activity or even that is associated with seeing these message? Sorry, I didn't get the question. > Does the device recover? Do you mean, whether it works later? No, I never got this card running. Same for the other - identical - machine. > If not, what about if you remove and reinsert the ath5k module? I will try that. If you don't see any follow-up from me in the next three months, I broke my computer while trying :~)
(In reply to comment #4) > > If not, what about if you remove and reinsert the ath5k module? > > I will try that. If you don't see any follow-up from me in the next three > months, I broke my computer while trying :~) To be sure -- John wasn't asking you remove the hardware, just that you run sudo rmmod ath5k sudo modprobe ath5k or whatever equivalent.
> To be sure -- John wasn't asking you remove the hardware, just that you run > > sudo rmmod ath5k > sudo modprobe ath5k OK, I tried that - of course :~) - many, many times. No avail. I really should try with another hardware. OTOH, it is not very likely that the cards in both laptops are broken.
How are you trying to connect? Using NetworkManager? Using wpa_supplicant by itself? If you can run wpa_supplicant with "-d -t" options it may provide more clues if this is just a matter of setup. You are getting scan results, so at least we know it's RXing and probably not an rfkill type issue. What frequency is the AP on? FWIW "Noise floor calibration" likely doesn't have anything to do with it, we should just demote that message to debug only.
Created attachment 23016 [details] Output of wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant/wpa.conf -d -t
Created attachment 23017 [details] Output of iwlist wlan0 scanning
Bob, I attached the outputs of wpa_supplicant and iwlist. Does this provide you with the necessary information? Other commands to try?
Ok, are you using ap_scan or scan_ssid commands in your wpa_supplicant.conf? If so, try removing them.
Created attachment 23058 [details] Output of wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant/wpa.conf -d -t
I had ap_scan=1 in my /etc/wpa_supplicant/wpa.conf and changed it to ap_scan=0. I attached the output of wpa_supplicant to this bug report. I wonder why wpa_supplicant says "No keys have been configured - skip key clearing". Is this about the WPA PSK? I have it configured, of course...
Bob, anything more to add here? Does this problem persist w/ 2.6.33?
(In reply to comment #14) > Does this problem persist w/ 2.6.33? Yes, unfortunately.
Sorry, you do in fact want ap_scan=1, just not scan_ssid=1 commands in wpa_supplicant.conf. Are you trying to connect to "xxx" or "MYAP"? Is "xxx" really the ssid of those APs?
MYAP is my AP. For the xxx: I didn't want to show up all my neighbours in a kernel bug report :~) I just tested again with 2.6.33 from Debian experimental and, again, switched off all APs security (no WEP, no WPA2, no key), ap_scan=1, no scan_ssid, but it doesn't help.
Does this problem persist with 2.6.35 (or later) kernels?
(In reply to comment #18) > Does this problem persist with 2.6.35 (or later) kernels? No. The problem seems to be solved with 2.6.35 (Debian package from experimental). Thanks for reminding me to try it again :-) And thanks to the developers who made this work!