Created attachment 21176 [details] dmesg Hi, previous versions of ath5k have worked with my wireless card (AR242x), but some update broke it, and now it cannot connect to WPA networks (possibly all networks, i do not have any WEP networks to test on, only a WPA2 personal and WPA2 enterprise Anyway, yeah, it just tries to connect and then fails. I am using network manager with gnome, the way it worked in the past. It does not work in both arch linux, and ubuntu jaunty. Attached are some log files that might help ~Mark
Created attachment 21177 [details] kern.log kern.log file
Created attachment 21178 [details] kern.log <FIXED> fixed kern.log
Created attachment 21179 [details] lspci-vvnn.log lspci -vvnn log
Created attachment 21180 [details] uname -a .log uname -a .log
Created attachment 21181 [details] version.log version .log
And one other comment, i realized that i still had ath_pci in my kernel (not loaded) because i was trying the special HAL branch of the madwifi drivers, it does not work with ath_pci or ath_5k, even after i removed ath_pci
Hello Mark, I'm not sure, but I think I've got this already within a really noisy room. Could you send us the data of /proc/net/wireless when you're trying to connect? If you can't get values different from 0 there (normally they appear when the system is ending the authentication), could you send us the values of your cell from the output of "iwlist wlan0 scan" (only as root).
Hi, i have attached what /proc/net/wirless contains when i am trying to connect (proc_net_wireless.log)
and...(sorry , i pressed commit too early) attached is iwlist_wlan0_scan.log as well, which is the output of sudo iwlist wlan0 scan. 7610-net is the network that i am trying to connect to, 'zikes' and 'actiontec' are just random network my laptop picks up
Created attachment 21204 [details] output of cat /proc/net/wireless
Created attachment 21205 [details] output of sudo iwlist wlan0 scan
In this file you have 3 ESSID: - ACTIONTEC - 7610-net - zikes Which one is yours, please?
7610-net is the network at my house
Created attachment 21233 [details] output of sudo iwlist wlan0 scan (different network) Here is another location which i cannot connect to with my laptop. The network UAWiFi is the one i am referring to. I can connect to UAPublic however, just not UAWiFi.
Does "modprobe ath5k nohwcrypt=1" help?
dear guys, I have a ar5212 chipset and i can connect to WPA personal networks but not WPA enterprise networks at my university using ath_hal/pci or ath5k. I will try the above modprobe. Is there anything else i can do to aid development of a fix? the university network i am trying to connect to is PEAP/TKIP/MSHAPV2. I'm using an ibm r31 with 2.6.28 kernel. thanks.
no, modprobe ath5k nohwcrypt=1 does not fix the problem.
still does not work with 2.6.30-ARCH
Hi, confirm this bug for my card: 03:00.0 Ethernet controller: Atheros Communications Inc. AR5212/AR5213 Multiprotocol MAC/baseband processor (rev 01) 03:00.0 0200: 168c:0013 (rev 01) I try to connect with my ap in WPA2, it connect but after few second got disconnect for ever... but led support work on this version. I try with the driver included in last compat-wireless (compat-wireless-2009-07-16) My current kernel is: 2.6.31-rc3 With the driver included in 2.6.31-rc3 it work great (only led support don't work) Good work
matrix is using a different wireless card then me (ar5252 as opposed to ar5007) but once arch gets the 2.6.31 kernel i shall try it out. Also...this is a regression.... (and i'm marking this bug as such) my wireless has worked before...and i would really like it to work now =/
Do you have a dmesg from when it did work? What userspace tools are you using to connect (network manager, wicd, wpa_supplicant)? The following looks suspect... reason 2 means previous authentication is not valid. The AP is telling you that only 3 ms after authenticating. Apr 30 15:55:55 Polygon kernel: wlan0: authenticate with AP 00:23:6c:bf:38:fb Apr 30 15:55:55 Polygon kernel: wlan0: authenticated Apr 30 15:55:55 Polygon kernel: wlan0: associate with AP 00:23:6c:bf:38:fb Apr 30 15:55:55 Polygon kernel: wlan0: RX ReassocResp from 00:23:6c:bf:38:fb (capab=0x431 status=0 aid=4) Apr 30 15:55:55 Polygon kernel: wlan0: associated Apr 30 15:55:58 Polygon kernel: wlan0: deauthenticated (Reason: 2)
(In reply to comment #21) > The following looks suspect... reason 2 means previous authentication is not > valid. The AP is telling you that only 3 ms after authenticating. Sorry can't read - that's 3 secs. A log with CONFIG_MAC80211_VERBOSE_DEBUG and iw event output may help. FWIW I can use WPA networks here without problems.
i have two atheros cards, reported like : 06:02.0 Ethernet controller: Atheros Communications Inc. AR2413 802.11bg NIC (rev 01) one is cardbus, another is pci-e or minipci (integrated in asus aspire 3690) . with same kernel (2.6.31-rc3) , same utils, etc, plugged to same machine (asus aspire in question) one card works with wpa2-aes (psk) , and the other... do not. the one not working is cardbus card (branded as tp-link) WPA2 without AES works fine on both... :S indeed confusing. i've recently tried like two other cards to make connection with wpa2-aes AP, and all failed (!) except the atheros in asus. under winXP it works with some random ralink . i've tried like : prism2 based (three different cards with three different firmware versions, latest STA was like 1.7.4) - gave up, concluding it might be somehow firmware issue (even though hostap driver does not use firmware fror WPA) rt61 - epic fail. this one also freezed during APM idle states, and driver looked unmaintained... so i got that atheros, which seemed identical to the one in asus. i would be glad to at least know what differs those atheros cards ?
ah, btw. tried also madwifi-hal with 2.6.31-rc3 and rc5 , same 'result' - on asus integrated it works, on that cardbus atheros - no luck , and after try to connect card hard-locks (it can scan networks, but not associate even to non-encrypted ones)
@bob: i don't have a dmesg from when it did work, since i have upgraded since then, but i can try booting various live cds from various distros until i find one that did work and i am using network manager to try and connect and do you mean i should try recompiling my kernel with CONFIG_MAC80211_VERBOSE_DEBUG? Im not sure what that means otherwise
Yes, recompile your kernel with that option. Mark, can you confirm WPA personal (PSK) does not work (conversely with comment #16)? I think there may be a problem with EAP and reassoc specifically.
Created attachment 22960 [details] output of iwlist wlan0 scan (working wpa network, OKMARK) output of iwlist wlan0 scan of a working wpa personal network ('OKMARK')
Hi bob, i managed to recompile my kernel with CONFIG_MAC80211_VERBOSE_DEBUG=y, and as soon as i can bring my laptop to school, i will generate the log files again. But, where is this extra output supposed to appear? kern.log? also, i guess WPA Personal networks do infact work after all. I am connected to one right now in fact, and above is the output of iwlist wlan0 scan, in case you are interested (The network that i am connecting to that does work is 'OKMARK')
Created attachment 22983 [details] dmesg file running on a kernel with CONFIG_MAC80211_VERBOSE_DEBUG=y And here is my dmesg with the custom compiled kernel with CONFIG_MAC80211_VERBOSE_DEBUG=y. let me know if you need more information or somehow i screwed up with compiling my kernel with that option enabled, and that actually isn't the verbose output =)
Ok, I replicated a similar issue recently. I haven't had time to fully troubleshoot, but I recommend trying the following: 1) disable network manager (killall -9 NetworkManager) 2) create a wpa_supplicant.conf that works with your network, e.g.: network={ ssid="my_ap" key_mgmt=WPA-EAP eap=PEAP phase2="auth=MSCHAPV2" identity="my_account" password="my_password" } 3) Make sure there is no ap_scan or scan_ssid directive in #2. 4) start the network manually: # ifconfig wlan0 down # ifconfig wlan0 up # wpa_supplicant -i wlan0 -Dwext -c wpa_supplicant.conf (in another terminal) # dhclient wlan0
Created attachment 23041 [details] dmesg output (when i successfully connected to uawifi) Hmm....it seems that did the trick, i am now connected to UAWiFi (the one with the WPA-EAP/PEAP/MSCHAPV2 Security) It took wpa_supplicant a couple minutes, and it seemed it was just doing what it was doing before (trying to associate, associate for like 3 seconds, then disconnect again) but then after a couple of minutes it associated and now i am connected to the internet. I will attach my dmesg / iwconfig wlan0 / wpasupplicant logs......but what does this mean? that this is a bug with network manager?
Created attachment 23042 [details] iwconfig wlan0 output (when connected to UAWiFi) (above post is my dmesg output) this post is the iwconfig wlan0 output
Created attachment 23043 [details] wpa_supplicant output (when it tried and eventually connected to UAWiFi) wpa_supplicant -i wlan0 -Dwext -c /etc/wpa_supplicant.conf output, when it tried and eventually connected to UAWiFi successfully.
Created attachment 23044 [details] sorry, i fail at copy/paste, this is the 'complete' wpa_supplicant when it successfully connected to UAWiFi sorry, didn't copy and paste the entire wpa_supplicant output, here is the -complete- output.
Any News? This still does not work with the latest stable Arch kernel version, "2.6.31-ARCH".
Sorry, totally swamped with school work. I think it is a bug with either the supplicant or mlme not being able to work well with the long scan times in ath5k. But I really haven't had the free cycles to pull apart nm, wpa_supplicant, and the wext code to find out what's going on (it's still on my list, though).
Hey, Bob! Any word on this? Mark, is this still an issue w/ 2.6.33?
Well, I believe the whole point of me doing the tests above was that the kernel is in fact able to use my wireless card to connect to the WPA networks, but something else along the lines (wpa_supplicant or network-manager perhaps) is causing things to break. I will have to reinstall arch linux when I have a free moment and see if the latest kernel has any other effects, as the ubuntu bug report is asking about this as well. (https://bugs.launchpad.net/bugs/344611)
Yeah, I did set up an EAP server here and didn't have problems, but I do have problems if there are a lot of servers around. I believe Jouni noticed a similar issue a month or two ago and he may have submitted related patches for cfg/mac80211.
No new info for a long time...please reopen if/when requested information becomes available...
What new info do you need? I've given everything you guys have asked for. I still cannot connect to WPA enterprise networks with the latest version of ubuntu (10.10)
I guess I should forward port the tracing patches and we can get a trace dump.