Bug 1009241
| Summary: | [asus_laptop] rfkill not correctly handled on ASUS X550C | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Yi Li <lovelylich> |
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | urgent | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 20 | CC: | dcbw, gansalmon, gergely, itamar, jklimes, jonathan, jon.dufresne, jones.peter.busi, kernel-maint, madhu.chinakonda |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-02-26 02:16:02 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: | |
| Embargoed: | |||
|
Description
Yi Li
2013-09-18 04:10:58 UTC
The same goes for me; same network adapter, NM is 0.9.8.8, the machine is an ASUS X550C. I'm running the latest available kernel as of date (3.11.6-200.fc19.x86_64). Fedora is freshly installed from networkless DVD, this is my first attempt to connect to a network. Secure boot is on, and I'm unwilling to disable it due to company policy. The only difference between original report and my problem, is that NM reports to me that WiFi hardware is disabled. As I think NM doesn't have anything to do with this problem, I issued rfkill: $ sudo rfkill list 2: phy0: Wireless LAN Soft blocked: no Hard blocked: yes 17: asus-wlan: Wireless LAN Soft blocked: no Hard blocked: no 18: asus-bluetooth: Bluetooth Soft blocked: no Hard blocked: no WiFi hardware switch key (Fn-F2) doesn't seem to do anything (no output in dmesg, nor in syslog), the WiFi status LED is constantly on (it is initially off, and gets turned on after the kernel is loaded). WiFi is working well in dual-booted Windows 8, and it is not turned off before reboot. (Seemingly) relevant comment on an Ubuntu bug: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1172151/comments/28 The solution (reloading the wmi module with wapf=4) didn't help. Does pressing (Fn-F2) influence rfkill list output? Are you able to unblock the Wi-Fi with 'sudo rfkill unblock all'? Does 'rmmod asus-wlan' influence the behaviour? As the card is hard blocked, rfkill unblock can do nothing. As I mentioned in my comment, pressing Fn-F2 does nothing, and I can't even see anything in the logs. Since then, however, it turned out that if I blacklist the asus-nb-wmi kernel module, the problem disappears (simply doing rmmod doesn't help). In Fedora-Live-Jam-KDE-x86_64-20-Beta-5.iso, when I go to the Network Manager toolbox and enable networking, I get a message saying something like "Network Manager 0.8.8 needed, found", and the end seems cut off. I don't see the wireless networks there, but I do with iwlist scan. rpm -qa | grep Network gives: NetworkManager-openswan-0.9.8.0-1.fc20.x86_64 NetworkManager-pptp-0.9.8.2-3.fc20.x86_64 NetworkManager-glib-0.9.9.0-14.git20131003.fc20.x86_64 NetworkManager-openvpn-0.9.8.2-3.fc20.x86_64 NetworkManager-l2tp-0.9.8-2.fc20.x86_64 NetworkManager-0.9.9.0-14.git20131003.fc20.x86_64 NetworkManager-openconnect-0.9.8.0-2.fc20.x86_64 KNetworkKManager-vpnc-0.9.8.2-2.fc20.x86_64 So, Network is 0.9.9, not 0.9.8 (In reply to Gergely Polonkai from comment #3) > As the card is hard blocked, rfkill unblock can do nothing. As I mentioned > in my comment, pressing Fn-F2 does nothing, and I can't even see anything in > the logs. > > Since then, however, it turned out that if I blacklist the asus-nb-wmi > kernel module, the problem disappears (simply doing rmmod doesn't help). If 'rfkill list' shows that the wifi is hardblocked and you cannot unblock it, that's a kernel problem that needs to be fixed in the drivers for your laptop, like you've found. NetworkManager is simply reporting what the kernel says. Sometimes the kernel is wrong, and the rfkill "switch" it shows has no relation to the wifi card you've installed, which is often true of you have changed the wifi card in your machine. Unfortunately the kernel does not tell NetworkManager about this (and it cannot do so easily), so there's no way to override the kernel here. Even if there was, we'd rather have the kernel fixed than hack around it in userspace. So the core problem here is likely that the platform/laptop drivers for your machine are not working correctly, and that needs to be fixed in the kernel. I am running into the same issue. I have discovered a workaround to get the wireless device into a working state. 0. Do a cold boot (wifi not working) 1. Close lid to put laptop to sleep 2. Open lid and restore session (wifi working) After bringing the laptop back from sleep, the wifi begins to work. This is my rfkill after resume from sleep: $ sudo rfkill list 0: asus-wlan: Wireless LAN Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no So it appears the driver can work with the wireless device, just not on initial boot. This looks like it may be a duplicate of bug 954070 *********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs. Fedora 20 has now been rebased to 3.13.4-200.fc20. Please test this kernel update and let us know if you issue has been resolved or if it is still present with the newer kernel. If you experience different issues, please open a new bug report for those. *** This bug has been marked as a duplicate of bug 954070 *** |