FS#41316 - [linux] 3.15 RF Kill switch not detected on HP laptop
Attached to Project:
Arch Linux
Opened by Christophe Viallon (Christophe) - Wednesday, 23 July 2014, 22:00 GMT
Last edited by freswa (frederik) - Sunday, 13 September 2020, 11:30 GMT
Opened by Christophe Viallon (Christophe) - Wednesday, 23 July 2014, 22:00 GMT
Last edited by freswa (frederik) - Sunday, 13 September 2020, 11:30 GMT
|
Details
Description: the RF kill switch is not detected and thus
cannot control wifi and bluetooth since kernel 3.15
This problem affects a laptop from HP (EliteBook 840 G1) The new kernel option documented here : https://wiki.archlinux.org/index.php/HP_EliteBook_840_G1#Wireless CONFIG_HP_WIRELESS=y which appeared with the 3.14 Kernel no longer works (It was working with 3.14 kernel) I found another kernel option here : https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1303420 acpi_osi='!Windows 2012' The use of this option makes the kill switch act as a soft switch instead of hard switch. The consequence is that the switch color remain unchanged (white). The switch status is verified using the following command : $ rfkill list all 0: phy0: Wireless LAN Soft blocked: no (yes after pressing kill switch) Hard blocked: no 1: hci0: Bluetooth Soft blocked: no (yes after pressing kill switch) Hard blocked: no Additional info: * The laptop is an HP Elitebook 840 G1 * The current kernel version is 3.15.5-2-ARCH #1 SMP PREEMPT ... x86_64 GNU/Linux Steps to reproduce: To see the bug, just run the following command : $ sudo showkey -s ...pressing the RFkill switch key shows no output. dmesg detects an unknown key pressed : [ 218.076440] atkbd serio0: Unknown key released (translated set 2, code 0xf8 on isa0060/serio0). [ 218.076447] atkbd serio0: Use 'setkeycodes e078 <keycode>' to make it known. |
This task depends upon
Closed by freswa (frederik)
Sunday, 13 September 2020, 11:30 GMT
Reason for closing: Works for me
Additional comments about closing: I can't reproduce on a HP Elitebook 840 G1
Sunday, 13 September 2020, 11:30 GMT
Reason for closing: Works for me
Additional comments about closing: I can't reproduce on a HP Elitebook 840 G1
The problem is still here : the RF switch does not hard block bluetooth and wifi
I tried :
1- with the grub option CONFIG_HP_WIRELESS=y
2- with the grub option acpi_osi='!Windows 2012' instead of CONFIG_HP_WIRELESS=y
3- without any of both options
I must say that none of this 3 tests now changes anything in the behavior of the laptop.
Each time I press the RF kill switch, both bluetooth and wifi alternate between soft blocked yes/no position and the switch color remains always white, meaning that it never hard blocks bluetooth and wifi. Compared to the tests I made before, the systems seems to act as if the option 2 was now set by default in the kernel.
I hope it will help.