Created attachment 345165 [details] /var/log/messages Description of problem: After boot, NetworkManager tries automatically to connect to a visible wpa secured network. This takes too long and NM asks for the key. At second time, association succeeds. Version-Release number of selected component (if applicable): NetworkManager-0.7.1-4.git20090414.fc11.i586 wpa_supplicant-0.6.8-2.fc11.i586 kernel-PAE-2.6.29.3-155.fc11.i686 How reproducible: 90% Steps to Reproduce: 1. Boot, log in 2. NM tries to connect 3. Actual results: No connection is made, NM asks for key Expected results: Connection succeeds, no further assistance necessary Additional info: 0b:02.0 Ethernet controller: Atheros Communications Inc. AR5212 802.11abg NIC (rev 01) (i.e. ath5k driver)
maybe a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=463110
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: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Seems to be no problem, if using kernel 2.6.30.....
Same problem. I have not yet been able to establish a connection to a WPA router. The logs look the same as shown in the attached file. I have no trouble with a WPA2 router, though. It worked flawlessly on Fedora 10. Additional info: 0c:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02)
Seems to be fixed with the 2.6.30 (testing) kernel from koji.
Yeah, 2.6.30 (F11) kernels work pretty well with a dual-band ath5k for me with WPA-PSK as well. Closing... Final diagnosis is a kernel driver bug.