Bug 93341
| Summary: | Intel 7260 Hard blocked on Dell M3800 | ||
|---|---|---|---|
| Product: | Drivers | Reporter: | Fabian Kislat (fabian.kislat) |
| Component: | Platform | Assignee: | drivers_network-wireless (drivers_network-wireless) |
| Status: | CLOSED WILL_NOT_FIX | ||
| Severity: | normal | CC: | linville, szg00000 |
| Priority: | P1 | ||
| Hardware: | x86-64 | ||
| OS: | Linux | ||
| Kernel Version: | 3.19.0 | Subsystem: | |
| Regression: | No | Bisected commit-id: | |
Nothing I can do here. This is not WiFi related but platform/RFKill related. Removing Intel Wireless from this bug. Okay. I'll change component to "Platform" hoping to reach someone who might be able to help. I just made an interesting observation, the problem might not be a driver bug after all. I finally got around to installing Windows on this computer again, and I found out that now the same symptoms exist on Windows: the WiFi is unavailable until I go through one sleep (susped to RAM) / resume cycle. |
I'm running Gentoo Linux on a Dell M3800 laptop with Kernel 3.19.0-gentoo. After booting, the wireless adapter (Intel 7260) is hard blocked: localhost ~ # rfkill list 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Here is the dmesg output: localhost ~ # dmesg | grep iwlwifi [ 2.643860] iwlwifi 0000:06:00.0: enabling device (0000 -> 0002) [ 2.644539] iwlwifi 0000:06:00.0: Direct firmware load for iwlwifi-7260-12.ucode failed with error -2 [ 2.644550] iwlwifi 0000:06:00.0: Direct firmware load for iwlwifi-7260-11.ucode failed with error -2 [ 2.647279] iwlwifi 0000:06:00.0: loaded firmware version 23.11.10.0 op_mode iwlmvm [ 2.651146] iwlwifi 0000:06:00.0: Detected Intel(R) Dual Band Wireless AC 7260, REV=0x144 [ 2.651201] iwlwifi 0000:06:00.0: L1 Disabled - LTR Enabled [ 2.651411] iwlwifi 0000:06:00.0: RF_KILL bit toggled to disable radio. [ 2.651441] iwlwifi 0000:06:00.0: L1 Disabled - LTR Enabled There is no hardware wireless switch, and the key combination Fn+PrtScr, which is supposed to be the wireless switch, has no effect. It cannot be unblocked by 'rfkill unblock all', either. However, after suspending to RAM and waking the computer, the wireless is unblocked: localhost ~ # rfkill list 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no 1: hci0: Bluetooth Soft blocked: no Hard blocked: no dmesg during resume reports: [ 92.052221] iwlwifi 0000:06:00.0: L1 Disabled - LTR Enabled [ 92.052462] iwlwifi 0000:06:00.0: L1 Disabled - LTR Enabled So the RF_KILL related message is gone. Possibly related, the bluetooth is now available, which it wasn't before. It seems to me there is some initialization issue. Here are my iwlwifi related kernel configuration options: localhost ~ # grep -i iwl /usr/src/linux/.config CONFIG_IWLWIFI=m CONFIG_IWLWIFI_LEDS=y CONFIG_IWLDVM=m CONFIG_IWLMVM=m CONFIG_IWLWIFI_OPMODE_MODULAR=y # CONFIG_IWLWIFI_BCAST_FILTERING is not set # CONFIG_IWLWIFI_UAPSD is not set CONFIG_IWLWIFI_DEBUG=y # CONFIG_IWLWIFI_DEBUG_EXPERIMENTAL_UCODE is not set # CONFIG_IWLWIFI_DEVICE_TRACING is not set # CONFIG_IWL4965 is not set # CONFIG_IWL3945 is not set For completeness, here is the lspci -v output: 06:00.0 Network controller: Intel Corporation Wireless 7260 (rev 6b) Subsystem: Intel Corporation Dual Band Wireless-AC 7260 Flags: bus master, fast devsel, latency 0, IRQ 31 Memory at ec900000 (64-bit, non-prefetchable) [size=8K] Capabilities: [c8] Power Management version 3 Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [40] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [140] Device Serial Number [removed] Capabilities: [14c] Latency Tolerance Reporting Capabilities: [154] Vendor Specific Information: ID=cafe Rev=1 Len=014 <?> Kernel driver in use: iwlwifi Kernel modules: iwlwifi Please let me know if there is any other information you may need. Since this is my first kernel bug report, I may have missed something important. I tried searching the internet but couldn't find any solution to my problem. The only thing I found was that the ideapad laptop module causes the 7260 to be hard blocked, but I don't have this driver, neither as a module nor built into the kernel.