[Bug 1192181] New: brightness keys mute mic instead (HP Elitebook 840 G6)
http://bugzilla.opensuse.org/show_bug.cgi?id=1192181 Bug ID: 1192181 Summary: brightness keys mute mic instead (HP Elitebook 840 G6) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs@opensuse.org Reporter: andreas_nordal_4@hotmail.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- On a HP Elitebook 840 G6 laptop, both the backlight brightness keys (F3 and F4) toggle microphone mute state instead of doing their intended thing. The good thing is that other keys, such as mute, volume and the actual microphone mute key (F5, F6, F7, F8) work as intended. No messages appear in dmesg --follow or journalctl --follow when pressing these keys. In evtest, the brightness up and down keys appear as the same identical sequence, which is also a common prefix of the actual mic mute key: Common prefix: type 4 (EV_MSC), code 4 (MSC_SCAN), value 81 type 1 (EV_KEY), code 190 (KEY_F20), value 1 -------------- SYN_REPORT ------------ type 4 (EV_MSC), code 4 (MSC_SCAN), value 81 type 1 (EV_KEY), code 190 (KEY_F20), value 0 -------------- SYN_REPORT ------------ Actual mic mute key (unique suffix part): type 4 (EV_MSC), code 4 (MSC_SCAN), value 42 -------------- SYN_REPORT ------------ Kernel: Linux 5.14.6-1-default I found similar reports about these keys not working: 1. https://bugzilla.opensuse.org/show_bug.cgi?id=1105997 2. https://bugzilla.opensuse.org/show_bug.cgi?id=1160911 The first one was about not showing it correctly, but the last one says: Update: The issue is gone in the latest BIOS update issued by HP. Version: R70 Ver. 01.04.05 Release Date: 02/18/2020 That seems to be the same version as I have (according to lshw): *-firmware description: BIOS vendor: HP physical id: 1 version: R70 Ver. 01.04.05 date: 02/18/2020 size: 64KiB capacity: 32MiB capabilities: pci pcmcia upgrade shadowing cdboot bootselect edd int5printscreen int9keyboard int14serial int17printer acpi usb smartbattery biosbootspecification netboot uefi I haven't tried updating BIOS, but it doesn't look easy. -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1192181 http://bugzilla.opensuse.org/show_bug.cgi?id=1192181#c3 Andreas Nordal <andreas_nordal_4@hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(andreas_nordal_4@ | |hotmail.com) | --- Comment #3 from Andreas Nordal <andreas_nordal_4@hotmail.com> --- Created attachment 853571 --> http://bugzilla.opensuse.org/attachment.cgi?id=853571&action=edit hwinfo | zstd hwinfo output (zstd compressed)
Which input device handles the brightness keys?
Physically, it's the keyboard (the F-key row). In evtest, "AT Translated Set 2 keyboard", is the device I selected to capture those key events. Thank you for looking into this! -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1192181 http://bugzilla.opensuse.org/show_bug.cgi?id=1192181#c4 --- Comment #4 from Takashi Iwai <tiwai@suse.com> --- Thanks. Do you any error messages from hp-wmi module when you press brightness keys? -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1192181 http://bugzilla.opensuse.org/show_bug.cgi?id=1192181#c5 --- Comment #5 from Takashi Iwai <tiwai@suse.com> --- ... or might be other way round: what happens if you blacklist hp_wmi module? -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1192181 http://bugzilla.opensuse.org/show_bug.cgi?id=1192181#c6 --- Comment #6 from Andreas Nordal <andreas_nordal_4@hotmail.com> ---
any error messages from hp-wmi module when you press brightness keys?
Nope. That would show in `dmesg --follow`, right? Nothing happens there when pressing the brightness keys. Only some other keys, which "atkbd serio0" complains about being unassigned. One of them is the WiFi key, which actually works despite being unassigned.
what happens if you blacklist hp_wmi module?
Same symptom: They still toggle the microphone instead. To test that, I did `sudo rmmod hp_wmi` and watched with `lsmod | grep hp_wmi`, both before and after, that the module was indeed loaded and got unloaded. However, this appeared in `dmesg --follow` when I modprobed it back again: [111350.270375] hp_wmi: query 0x4 returned error 0x5 [111350.276807] hp_wmi: query 0xd returned error 0x5 [111350.276931] input: HP WMI hotkeys as /devices/virtual/input/input87 [111350.292560] hp_wmi: query 0x1b returned error 0x5 -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1192181 http://bugzilla.opensuse.org/show_bug.cgi?id=1192181#c8 --- Comment #8 from Andreas Nordal <andreas_nordal_4@hotmail.com> ---
To make sure, could you do cold boot with hp_wmi module blackisted?
Yes, I like to be sure too. Did that, checked with `lsmod | grep hp_wmi` that it wasn't loaded, but the symptom was the same: The keys just toggle the microphone. -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1192181 http://bugzilla.opensuse.org/show_bug.cgi?id=1192181#c9 --- Comment #9 from Takashi Iwai <tiwai@suse.com> --- OK, thanks. So it looks like a bug in PS2 keyboard events, i.e. it's basically a BIOS bug. At least I hoped that BIOS reacts with WMI setup or such, but apparently it doesn't. One another shot would be to try some acpi_osi boot options, but I won't bet for it. Do I understand correctly that both brightness up and down trigger the very same key code? -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1192181 http://bugzilla.opensuse.org/show_bug.cgi?id=1192181#c10 --- Comment #10 from Andreas Nordal <andreas_nordal_4@hotmail.com> ---
Do I understand correctly that both brightness up and down trigger the very same key code?
Yes. I rechecked now with evtest while having hp_wmi blacklisted and not loaded.
acpi_osi boot options
Thanks for the tip! I tried a few that didn't work. Will try mor esystematically. Some good news: I can adjust the backlight by setting /sys/class/backlight/intel_backlight/brightness to 0-24000. -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1192181 http://bugzilla.opensuse.org/show_bug.cgi?id=1192181#c11 Andreas Nordal <andreas_nordal_4@hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WORKSFORME --- Comment #11 from Andreas Nordal <andreas_nordal_4@hotmail.com> --- I'm happy to report that the brightness keys are now working! Without me doing anything beyond keeping my system up to date. * The kernel is upgraded since last time: Linux 5.14.6-1-default ��� Linux 5.16.0-1-default * I didn't need to upgrade the BIOS (thank goodness, because HP doesn't make it easy): Still HP R70 Ver. 01.04.05 The 3 previously indistinguishable keys are now distinguishable in evtest: Brightness down key: Event: time 1643270483.474037, type 4 (EV_MSC), code 4 (MSC_SCAN), value 92 Event: time 1643270483.474037, type 1 (EV_KEY), code 224 (KEY_BRIGHTNESSDOWN), value 1 Event: time 1643270483.474037, -------------- SYN_REPORT ------------ Event: time 1643270483.526190, type 4 (EV_MSC), code 4 (MSC_SCAN), value 92 Event: time 1643270483.526190, type 1 (EV_KEY), code 224 (KEY_BRIGHTNESSDOWN), value 0 Event: time 1643270483.526190, -------------- SYN_REPORT ------------ Brightness up key: Event: time 1643270486.207376, type 4 (EV_MSC), code 4 (MSC_SCAN), value 97 Event: time 1643270486.207376, type 1 (EV_KEY), code 225 (KEY_BRIGHTNESSUP), value 1 Event: time 1643270486.207376, -------------- SYN_REPORT ------------ Event: time 1643270486.268492, type 4 (EV_MSC), code 4 (MSC_SCAN), value 97 Event: time 1643270486.268492, type 1 (EV_KEY), code 225 (KEY_BRIGHTNESSUP), value 0 Event: time 1643270486.268492, -------------- SYN_REPORT ------------ Mic mute key (identical for mute and unmute): Event: time 1643271216.192007, type 4 (EV_MSC), code 4 (MSC_SCAN), value 81 Event: time 1643271216.192007, type 1 (EV_KEY), code 190 (KEY_F20), value 1 Event: time 1643271216.192007, -------------- SYN_REPORT ------------ Event: time 1643271216.230921, type 4 (EV_MSC), code 4 (MSC_SCAN), value 81 Event: time 1643271216.230921, type 1 (EV_KEY), code 190 (KEY_F20), value 0 Event: time 1643271216.230921, -------------- SYN_REPORT ------------ -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1192181 http://bugzilla.opensuse.org/show_bug.cgi?id=1192181#c12 --- Comment #12 from Takashi Iwai <tiwai@suse.com> --- Thanks for the update. It's interesting. Could you check whether 5.15.x kernel also works in this regard or not? Found in my OBS home:tiwai:kernel:5.15 repo. I'd like to backport the fix to SLE15-SP4 / Leap 15.4 kernel if possible, too. -- You are receiving this mail because: You are the assignee for the bug.
participants (1)
-
bugzilla_noreply＠suse.com