Description of problem: kernel-3.3.1-3.fc16.i686 - no wireless kernel-3.3.0-8.fc16.i686 - no problem Network manager prompts for passphrase for wireless network endlessly (correct phrase is given). Log messages shown: Apr 12 21:23:42 bishop NetworkManager[511]: <info> Config: added 'ssid' value 'Nostromo' Apr 12 21:23:42 bishop NetworkManager[511]: NetworkManager[511]: <info> Config: added 'ssid' value 'Nostromo' Apr 12 21:23:42 bishop NetworkManager[511]: <info> Config: added 'scan_ssid' value '1' Apr 12 21:23:42 bishop NetworkManager[511]: <info> Config: added 'key_mgmt' value 'WPA-PSK' Apr 12 21:23:42 bishop NetworkManager[511]: <info> Config: added 'psk' value '<omitted>' Apr 12 21:23:42 bishop NetworkManager[511]: <info> Config: added 'proto' value 'WPA RSN' Apr 12 21:23:42 bishop NetworkManager[511]: NetworkManager[511]: <info> Config: added 'scan_ssid' value '1' Apr 12 21:23:42 bishop NetworkManager[511]: NetworkManager[511]: <info> Config: added 'key_mgmt' value 'WPA-PSK' Apr 12 21:23:42 bishop NetworkManager[511]: NetworkManager[511]: <info> Config: added 'psk' value '<omitted>' Apr 12 21:23:42 bishop NetworkManager[511]: NetworkManager[511]: <info> Config: added 'proto' value 'WPA RSN' Apr 12 21:23:42 bishop NetworkManager[511]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete. Apr 12 21:23:42 bishop NetworkManager[511]: NetworkManager[511]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete. Apr 12 21:23:42 bishop NetworkManager[511]: <info> Config: set interface ap_scan to 1 Apr 12 21:23:42 bishop NetworkManager[511]: NetworkManager[511]: <info> Config: set interface ap_scan to 1 Apr 12 21:23:42 bishop NetworkManager[511]: <info> (wlan0): supplicant interface state: disconnected -> scanning Apr 12 21:23:42 bishop NetworkManager[511]: NetworkManager[511]: <info> (wlan0): supplicant interface state: disconnected -> scanning Apr 12 21:23:43 bishop NetworkManager[511]: <info> (wlan0): supplicant interface state: scanning -> authenticating Apr 12 21:23:43 bishop NetworkManager[511]: NetworkManager[511]: <info> (wlan0): supplicant interface state: scanning -> authenticating Apr 12 21:24:07 bishop NetworkManager[511]: <warn> Activation (wlan0/wireless): association took too long. Apr 12 21:24:07 bishop NetworkManager[511]: <info> (wlan0): device state change: config -> need-auth (reason 'none') [50 60 0] Apr 12 21:24:07 bishop NetworkManager[511]: NetworkManager[511]: <warn> Activation (wlan0/wireless): association took too long. Apr 12 21:24:07 bishop NetworkManager[511]: NetworkManager[511]: <info> (wlan0): device state change: config -> need-auth (reason 'none') [50 60 0] Apr 12 21:24:07 bishop NetworkManager[511]: NetworkManager[511]: <warn> Activation (wlan0/wireless): asking for new secrets Apr 12 21:24:07 bishop NetworkManager[511]: <warn> Activation (wlan0/wireless): asking for new secrets Apr 12 21:24:07 bishop NetworkManager[511]: NetworkManager[511]: <info> (wlan0): supplicant interface state: authenticating -> disconnected Apr 12 21:24:07 bishop NetworkManager[511]: <info> (wlan0): supplicant interface state: authenticating -> disconnected Apr 12 21:24:07 bishop NetworkManager[511]: NetworkManager[511]: <warn> Couldn't disconnect supplicant interface: This interface is not connected. Apr 12 21:24:07 bishop NetworkManager[511]: <warn> Couldn't disconnect supplicant interface: This interface is not connected. Version-Release number of selected component (if applicable): As above How reproducible: 100% Steps to Reproduce: 1.update kernel with yum 2.reboot Actual results: Wireless does not connect, log messages are seen and NM prompts for passphrase Expected results: Wireless should connect based on remembered passphrase Additional info: Using initrdless boot for both successful and failed case. grub2 reinstalled manually after updates.
we'd need to know what kind of network card and driver are being used here. ath9k?
How did you guess? Any more info needed? 03:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01) Subsystem: Hewlett-Packard Company Device 3040 Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at d3000000 (64-bit, non-prefetchable) [size=64K] Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit- Capabilities: [60] Express Legacy Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [140] Virtual Channel Capabilities: [160] Device Serial Number 00-15-17-ff-ff-24-14-12 Capabilities: [170] Power Budgeting <?> Kernel driver in use: ath9k Kernel modules: ath9k
Please try the test kernels here: http://koji.fedoraproject.org/koji/taskinfo?taskID=3980617 Do they resolve the issue for you?
(In reply to comment #3) > Please try the test kernels here: > > http://koji.fedoraproject.org/koji/taskinfo?taskID=3980617 > > Do they resolve the issue for you? I'm pleased to report that 3.3.1-5.bz810796.fc16.i686 does not have the problem, it seems to work normally. Thanks very much :)
kernel-3.3.2-1.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/kernel-3.3.2-1.fc16
kernel-3.3.2-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/kernel-3.3.2-1.fc17
Package kernel-3.3.2-1.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing kernel-3.3.2-1.fc17' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-5994/kernel-3.3.2-1.fc17 then log in and leave karma (feedback).
kernel-3.3.2-1.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.
kernel-3.3.2-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.