[Bug 831790] New: RF kill switch and LCD backlight don't work on HP EliteBook 8470p
https://bugzilla.novell.com/show_bug.cgi?id=831790 https://bugzilla.novell.com/show_bug.cgi?id=831790#c0 Summary: RF kill switch and LCD backlight don't work on HP EliteBook 8470p Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: adrien.clerc@gls-france.com QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:22.0) Gecko/20100101 Firefox/22.0 With an out of the box installation of openSuse 12.3, the kill switch for WiFi and LCD backlight don't work. According to http://comments.gmane.org/gmane.linux.kernel/1421265 The ACPI table is wrong (once again). Adding acpi_osi="!Windows 2012" on kernel command line solved the issue. Incidentally, the Bootloader YaST configuration fails to update with this parameter, I had to add it manually. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=831790 https://bugzilla.novell.com/show_bug.cgi?id=831790#c Jeff Mahoney <jeffm@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|kernel-maintainers@forge.pr |jlee@suse.com |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=831790 https://bugzilla.novell.com/show_bug.cgi?id=831790#c1 --- Comment #1 from Joey Lee <jlee@suse.com> 2013-09-27 03:39:18 UTC --- In normally case, we ill not use acpi_osi="!Windows 2012" because it's lead the acpi subsystem running to old Windows code path, e.g. Windows 7 or even Windows XP. In OEM/ODM shipping testing, they will not test the compatibility with old Windows. Back to HP machine, due to they don't release the wmi spec to kernel community. So some function key doesn't work through the Windows 8 code path is make sense. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=831790 https://bugzilla.novell.com/show_bug.cgi?id=831790#c2 Joey Lee <jlee@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX --- Comment #2 from Joey Lee <jlee@suse.com> 2013-09-27 03:41:44 UTC --- Set this issue to WONTFIX. For Bootloader YaST configuration issue, please file another bug against it. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=831790 https://bugzilla.novell.com/show_bug.cgi?id=831790#c3 --- Comment #3 from Adrien Clerc <adrien.clerc@gls-france.com> 2013-09-27 07:19:21 UTC --- OK… Is there any procedure to make it work? Beg HP? Ask ACPI subsystem maintainers? Obviously, the backlight buttons are not that important, but the RF kill switch is. For YaST, see #831791 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=831790 https://bugzilla.novell.com/show_bug.cgi?id=831790#c4 --- Comment #4 from Joey Lee <jlee@suse.com> 2013-09-27 07:52:12 UTC --- (In reply to comment #3)
OK… Is there any procedure to make it work? Beg HP? Ask ACPI subsystem maintainers? Obviously, the backlight buttons are not that important, but the RF kill switch is.
For the rfkill key, sometimes it's relate to the wifi driver. The wifi driver may need check a gpio pin to change the RF state. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=831790 https://bugzilla.novell.com/show_bug.cgi?id=831790#c5 Matt Chen <machen@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED CC| |machen@suse.com Resolution|WONTFIX | --- Comment #5 from Matt Chen <machen@suse.com> 2013-09-27 15:57:25 CST --- Which wifi you are using ? Atheros, Intel, Ralink or Realtek ? Would you please install rfkill package, zypper in rfkill. And attach the "rfkill list" result here when you duplicate the RF kill switch issue. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=831790 https://bugzilla.novell.com/show_bug.cgi?id=831790#c Matt Chen <machen@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|jlee@suse.com |machen@suse.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=831790 https://bugzilla.novell.com/show_bug.cgi?id=831790#c Matt Chen <machen@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO InfoProvider| |adrien.clerc@gls-france.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=831790 https://bugzilla.novell.com/show_bug.cgi?id=831790#c6 --- Comment #6 from Adrien Clerc <adrien.clerc@gls-france.com> 2013-09-27 08:11:28 UTC --- This is an Intel chipset: 24:00.0 Network controller [0280]: Intel Corporation Centrino Advanced-N 6205 [Taylor Peak] [8086:0082] (rev 34) With the workaround, I have the following output from rfkill : # rfkill list 0: hp-wifi: Wireless LAN Soft blocked: no Hard blocked: yes 1: hp-wwan: Wireless WAN Soft blocked: no Hard blocked: yes 2: hp-bluetooth: Bluetooth Soft blocked: no Hard blocked: yes 3: phy0: Wireless LAN Soft blocked: no Hard blocked: yes To have the output, with a bare kernel, I have to reboot. Since it's my office laptop, I'll do it later. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=831790 https://bugzilla.novell.com/show_bug.cgi?id=831790#c7 --- Comment #7 from Matt Chen <machen@suse.com> 2013-09-27 16:27:32 CST --- This looks like your devices are blocked by hard block. Generally it is blocked by WIFI hot-key or button. Can you find it and press it, see if it is able to enable the device. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=831790 https://bugzilla.novell.com/show_bug.cgi?id=831790#c8 --- Comment #8 from Adrien Clerc <adrien.clerc@gls-france.com> 2013-09-27 08:46:33 UTC --- Yes, that's exactly the point. But right now, I'm using the kernel parameter acpi_osi="!Windows 2012", so when I push the hardware button, rfkill gives me this: # rfkill list 0: hp-wifi: Wireless LAN Soft blocked: no Hard blocked: no 1: hp-wwan: Wireless WAN Soft blocked: no Hard blocked: no 2: hp-bluetooth: Bluetooth Soft blocked: no Hard blocked: no 3: phy0: Wireless LAN Soft blocked: no Hard blocked: no 4: hci0: Bluetooth Soft blocked: no Hard blocked: no This is good. However, it needs a kernel parameter. If I boot without, rfkill told me that hp-wifi is hard blocked, and the hardware button gives no result. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=831790 https://bugzilla.novell.com/show_bug.cgi?id=831790#c9 Matt Chen <machen@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |CLOSED InfoProvider|adrien.clerc@gls-france.com | Resolution| |WONTFIX --- Comment #9 from Matt Chen <machen@suse.com> 2013-09-27 17:19:13 CST --- Well, this would not be wifi driver issue. It is more likely BIOS issue. Maybe you need to update the BIOS from HP. Wifi driver either polls its register value of GPIO or receive interrupt from bus to decide block or unblock kill switch. But the role to control the hardware is from BIOS. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=831790 https://bugzilla.novell.com/show_bug.cgi?id=831790#c10 --- Comment #10 from Adrien Clerc <adrien.clerc@gls-france.com> 2013-10-01 07:03:39 UTC --- OK, I have the following output when I remove the acpi_osi kernel parameter: # rfkill list 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no As you can see, other devices are gone. The above result is the same after I push the hardware WiFi button. lspci output is the same as before. So WiFi is active, but I can't disable it with the kill switch. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com