| Summary: | Laptop with AR9285 wireless chip doesn't connect to WLAN since kernel 3.3.1 | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | firefexx |
| Component: | kernel | Assignee: | John W. Linville <linville> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 16 | CC: | edu.rm.85, emailjonathananderson-fedora, gansalmon, gwendolen.lynch, harry.hieronymous.bosch, itamar, jonathan, jorenretel, kernel-maint, kybernetikkollektiv, madhu.chinakonda, nisapov, noelduffy, raidercolombia, reklov, scorpy_sk, shafi.wireless |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | kernel-3.3.2-1.fc17 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-04-18 19:30:10 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
firefexx
2012-04-08 08:47:56 UTC
Same here, after update to 3.3.1-2 (from today). Wifi on 3.3.1-2.PAE doesn't work either! Kernel commit db6a6a78d8602964c9dfb1d8ce18daefd92da0a7 seems to be the culprit, and it has also been reported on LKML: https://lkml.org/lkml/2012/4/3/26 Just to add something that I noticed: It doesn't work only for WPA networks, but works for WEP networks using kernel 3.3.1-2 (3.3.1-3 also) Identical problem with AR9285 (PCI Express) / ath9k driver. However, if I plug in my Asus N-13 usb wireless (Ralink 802.11n WLAN) using rt2800usb driver, Network Manager connects OK for 3.3.1-x kernels. http://comments.gmane.org/gmane.linux.kernel.wireless.general/88543 revert patch from Sujith, got to fix unassociated idle power save case Update to kernel-3.3.1-5.fc16.x86_64 did *not* solve this problem. Nobody said it would. But, you might try the test kernels here: http://koji.fedoraproject.org/koji/taskinfo?taskID=3980617 Same here with AR9287 on Linux 3.3.0-4.fc16.x86_64. (In reply to comment #8) > Same here with AR9287 on Linux 3.3.0-4.fc16.x86_64. Oh dear, I mean Linux 3.3.1-3.fc16.x86_64. Sry. AR9285 with kernel 3.3.1-3 on wireless network without encryption works at first boot, but after laptop goes to sleep and wakes up same problem as described. wpa_supplicant.log shows: CTRL-EVENT-DISCONNECTED bssid=00:00:00:00:00:00 reason=3 Trying to authenticate with *(routers hardware address)* (SSID='X' freq=2437 MHz) I'm seeing this on kernel 3.3.1-5, fc16, x86_64. Atheros AR9285, connecting to wireless access point using WPA2. 3.3.0-8 is the last kernel in which the wireless has worked. NetworkManager doesn't help with its constant prompting for authentication credentials. Same as #10. AR9285 with kernel 3.3.1-3 on wireless network but with encryption works at first boot, but after laptop goes to sleep and wakes up, I can't get it to connect with anything less than a reboot. This should be fixed with 3.3.2. 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. It works perfect!!! :) Awesome my friend... thanks a lot You can update your kernel version with a simple su -c 'yum update kernel' I did it on a Acer Aspire 4551 with Fedora 16 Verne X86_64, I hope it works for you :) I used to have exactly the same problem, having a Atheros AR9285. I also needed to boot into an older kernel in order to get the wireless running. As said, the last update to kernel-3.3.2-1.fc16 fixed it. Thanks. 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. Well, I installed Fedora 18 on my netbook (a MSI MS-N014) and with the default kernel (3.6.10-PAE version) the AR9285 works, but on the newer kenel 3.9.6-PAE doesn't. With the newer kernel I have to boot the system with the wireless activated if I want to get wifi and not always work. When I stop and start again the network service I have these messages. From "systemctl status network.service": ------------------------ network.service - LSB: Bring up/down networking Loaded: loaded (/etc/rc.d/init.d/network) Active: failed (Result: exit-code) since Mon 2013-06-24 14:03:55 CEST; 42s ago Process: 1726 ExecStart=/etc/rc.d/init.d/network start (code=exited, status=1/FAILURE) Jun 24 14:03:52 msi-fedora systemd[1]: Starting LSB: Bring up/down networking... Jun 24 14:03:54 msi-fedora network[1726]: Bringing up loopback interface: [ OK ] Jun 24 14:03:54 msi-fedora network[1726]: Bringing up interface Auto_WLAN_2D: Error: Connection activation failed: Device not managed by NetworkManager or unavailable Jun 24 14:03:54 msi-fedora network[1726]: [FAILED] Jun 24 14:03:54 msi-fedora network[1726]: Bringing up interface p1p1: Error: Connection activation failed: Device not managed by NetworkManager or unavailable Jun 24 14:03:54 msi-fedora network[1726]: [FAILED] Jun 24 14:03:55 msi-fedora systemd[1]: network.service: control process exited, code=exited status=1 Jun 24 14:03:55 msi-fedora systemd[1]: Failed to start LSB: Bring up/down networking. Jun 24 14:03:55 msi-fedora systemd[1]: Unit network.service entered failed state. ------------------------ From "journalctl -xn": ------------------------ -- Logs begin at Mon 2013-06-24 14:00:40 CEST, end at Mon 2013-06-24 14:03:55 CEST. -- Jun 24 14:03:54 msi-fedora network[1726]: Bringing up loopback interface: [ OK ] Jun 24 14:03:54 msi-fedora NetworkManager[576]: <warn> connection /org/freedesktop/NetworkManager/Settings/1 failed to activate: (2) Device not managed by NetworkManager or unavailable Jun 24 14:03:54 msi-fedora network[1726]: Bringing up interface Auto_WLAN_2D: Error: Connection activation failed: Device not managed by NetworkManager or unavailable Jun 24 14:03:54 msi-fedora network[1726]: [FAILED] Jun 24 14:03:54 msi-fedora NetworkManager[576]: <warn> connection /org/freedesktop/NetworkManager/Settings/0 failed to activate: (2) Device not managed by NetworkManager or unavailable Jun 24 14:03:54 msi-fedora network[1726]: Bringing up interface p1p1: Error: Connection activation failed: Device not managed by NetworkManager or unavailable Jun 24 14:03:54 msi-fedora network[1726]: [FAILED] Jun 24 14:03:55 msi-fedora systemd[1]: network.service: control process exited, code=exited status=1 Jun 24 14:03:55 msi-fedora systemd[1]: Failed to start LSB: Bring up/down networking. -- Subject: Unit network.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/be02cf6855d2428ba40df7e9d022f03d -- -- Unit network.service has failed. -- -- The result is failed. Jun 24 14:03:55 msi-fedora systemd[1]: Unit network.service entered failed state. ------------------------ And when I try to start the network service with the wireless activated it doesn't work, it simply blocked for a few seconds and after it gives me these errors: From "systemctl status network.service": ----------------------- network.service - LSB: Bring up/down networking Loaded: loaded (/etc/rc.d/init.d/network) Active: failed (Result: exit-code) since Mon 2013-06-24 14:16:49 CEST; 1min 41s ago Process: 2277 ExecStart=/etc/rc.d/init.d/network start (code=exited, status=1/FAILURE) Jun 24 14:16:49 msi-fedora network[2277]: RTNETLINK answers: File exists Jun 24 14:16:49 msi-fedora network[2277]: RTNETLINK answers: File exists Jun 24 14:16:49 msi-fedora network[2277]: RTNETLINK answers: File exists Jun 24 14:16:49 msi-fedora network[2277]: RTNETLINK answers: File exists Jun 24 14:16:49 msi-fedora network[2277]: RTNETLINK answers: File exists Jun 24 14:16:49 msi-fedora network[2277]: RTNETLINK answers: File exists Jun 24 14:16:49 msi-fedora network[2277]: RTNETLINK answers: File exists Jun 24 14:16:49 msi-fedora systemd[1]: network.service: control process exited, code=exited status=1 Jun 24 14:16:49 msi-fedora systemd[1]: Failed to start LSB: Bring up/down networking. Jun 24 14:16:49 msi-fedora systemd[1]: Unit network.service entered failed state. ----------------------- From "journalctl -xn": ----------------------- -- Logs begin at Mon 2013-06-24 14:00:40 CEST, end at Mon 2013-06-24 14:18:56 CEST. -- Jun 24 14:18:56 msi-fedora kernel: cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) Jun 24 14:18:56 msi-fedora kernel: cfg80211: Calling CRDA for country: ES Jun 24 14:18:56 msi-fedora kernel: cfg80211: Regulatory domain changed to country: ES Jun 24 14:18:56 msi-fedora kernel: cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) Jun 24 14:18:56 msi-fedora kernel: cfg80211: (2400000 KHz - 2483500 KHz @ 40000 KHz), (N/A, 2000 mBm) Jun 24 14:18:56 msi-fedora kernel: cfg80211: (5150000 KHz - 5250000 KHz @ 40000 KHz), (N/A, 2000 mBm) Jun 24 14:18:56 msi-fedora kernel: cfg80211: (5250000 KHz - 5350000 KHz @ 40000 KHz), (N/A, 2000 mBm) Jun 24 14:18:56 msi-fedora kernel: cfg80211: (5470000 KHz - 5725000 KHz @ 40000 KHz), (N/A, 2698 mBm) Jun 24 14:18:56 msi-fedora kernel: cfg80211: (57240000 KHz - 65880000 KHz @ 2160000 KHz), (N/A, 4000 mBm) Jun 24 14:18:56 msi-fedora NetworkManager[576]: <info> (wlan0): supplicant interface state: disconnected -> scanning ----------------------- And this is the last content from wpa_supplicant.log: ----------------------- wlan0: SME: Trying to authenticate with 00:22:f7:02:c2:05 (SSID='WLAN_2D' freq=2437 MHz) wlan0: Trying to associate with 00:22:f7:02:c2:05 (SSID='WLAN_2D' freq=2437 MHz) wlan0: Associated with 00:22:f7:02:c2:05 wlan0: CTRL-EVENT-DISCONNECTED bssid=00:22:f7:02:c2:05 reason=3 wlan0: SME: Trying to authenticate with 00:22:f7:02:c2:05 (SSID='WLAN_2D' freq=2437 MHz) wlan0: Trying to associate with 00:22:f7:02:c2:05 (SSID='WLAN_2D' freq=2437 MHz) wlan0: Associated with 00:22:f7:02:c2:05 wlan0: CTRL-EVENT-DISCONNECTED bssid=00:22:f7:02:c2:05 reason=3 wlan0: SME: Trying to authenticate with 00:22:f7:02:c2:05 (SSID='WLAN_2D' freq=2437 MHz) wlan0: Trying to associate with 00:22:f7:02:c2:05 (SSID='WLAN_2D' freq=2437 MHz) wlan0: Associated with 00:22:f7:02:c2:05 wlan0: CTRL-EVENT-DISCONNECTED bssid=00:22:f7:02:c2:05 reason=3 wlan0: SME: Trying to authenticate with 00:22:f7:02:c2:05 (SSID='WLAN_2D' freq=2437 MHz) wlan0: Trying to associate with 00:22:f7:02:c2:05 (SSID='WLAN_2D' freq=2437 MHz) wlan0: Associated with 00:22:f7:02:c2:05 wlan0: CTRL-EVENT-DISCONNECTED bssid=00:22:f7:02:c2:05 reason=3 wlan0: SME: Trying to authenticate with 00:22:f7:02:c2:05 (SSID='WLAN_2D' freq=2437 MHz) wlan0: Trying to associate with 00:22:f7:02:c2:05 (SSID='WLAN_2D' freq=2437 MHz) wlan0: Associated with 00:22:f7:02:c2:05 wlan0: CTRL-EVENT-DISCONNECTED bssid=00:22:f7:02:c2:05 reason=3 wlan0: SME: Trying to authenticate with 00:22:f7:02:c2:05 (SSID='WLAN_2D' freq=2437 MHz) wlan0: Trying to associate with 00:22:f7:02:c2:05 (SSID='WLAN_2D' freq=2437 MHz) wlan0: Associated with 00:22:f7:02:c2:05 wlan0: CTRL-EVENT-DISCONNECTED bssid=00:22:f7:02:c2:05 reason=3 wlan0: SME: Trying to authenticate with 00:22:f7:02:c2:05 (SSID='WLAN_2D' freq=2437 MHz) wlan0: Trying to associate with 00:22:f7:02:c2:05 (SSID='WLAN_2D' freq=2437 MHz) wlan0: Associated with 00:22:f7:02:c2:05 wlan0: CTRL-EVENT-DISCONNECTED bssid=00:22:f7:02:c2:05 reason=3 wlan0: SME: Trying to authenticate with 00:22:f7:02:c2:05 (SSID='WLAN_2D' freq=2437 MHz) wlan0: Trying to associate with 00:22:f7:02:c2:05 (SSID='WLAN_2D' freq=2437 MHz) wlan0: Associated with 00:22:f7:02:c2:05 wlan0: CTRL-EVENT-DISCONNECTED bssid=00:22:f7:02:c2:05 reason=3 wlan0: SME: Trying to authenticate with 00:22:f7:02:c2:05 (SSID='WLAN_2D' freq=2437 MHz) wlan0: Trying to associate with 00:22:f7:02:c2:05 (SSID='WLAN_2D' freq=2437 MHz) wlan0: Associated with 00:22:f7:02:c2:05 wlan0: CTRL-EVENT-DISCONNECTED bssid=00:22:f7:02:c2:05 reason=3 wlan0: SME: Trying to authenticate with 00:22:f7:02:c2:05 (SSID='WLAN_2D' freq=2437 MHz) wlan0: Trying to associate with 00:22:f7:02:c2:05 (SSID='WLAN_2D' freq=2437 MHz) wlan0: Associated with 00:22:f7:02:c2:05 wlan0: CTRL-EVENT-DISCONNECTED bssid=00:22:f7:02:c2:05 reason=3 ----------------------- |