Bug 95221
| Summary: | Audio keys captured twice on HP Compaq 6735s (laptop) | ||
|---|---|---|---|
| Product: | Drivers | Reporter: | Juraj Fiala (doctorjellyface) |
| Component: | Input Devices | Assignee: | drivers_input-devices |
| Status: | ASSIGNED --- | ||
| Severity: | normal | CC: | aaron.lu, anirudhsdeshpande, dmitry.torokhov, doctorjellyface, endjekchev, jan.brummer, real86bitals, russianneuromancer, tiwai |
| Priority: | P1 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Kernel Version: | 3.19.2-1 | Subsystem: | |
| Regression: | No | Bisected commit-id: | |
| Attachments: |
Uploaded output of `sudo acpidump`
Output of evtest |
||
|
Description
Juraj Fiala
2015-03-22 15:53:36 UTC
Moved to ACPI/Power-Video. I looked at similar bugs and they were filed under this category, so I'll give it a go. Ah, sorry for another email. I mistook audio for brightness. I'll leave it in ACPI/Other and see what happens. acpidump please: # acpidump > acpidump.txt And we also need to decide which kernel module is responsible for delivering this hotkey event, I doubt it is some HP platform driver, e.g. hp-wmi. You can unload this module and see how things change. Created attachment 174681 [details]
Uploaded output of `sudo acpidump`
Tried unloading hp-wmi but it didn't help. Sounds like an input related problem, move there. What event device(s) is generating the volume up/down events? Please use evtest utility to find them (there might be just one, or several). Created attachment 174911 [details]
Output of evtest
It looks like the device is `/dev/input/event0: AT Translated Set 2 keyboard`
This is the output of evtest where I select 0, and press volume down and up.
Is there anything else I can do to help? Although showkeys and acpi_listen only shows one keypress at a time on my tablet, AT Translated Set 2 keyboard reports the key twice. Therefore i'm also effected by this issue: Event: time 1438546061.771962, type 4 (EV_MSC), code 4 (MSC_SCAN), value ae Event: time 1438546061.771962, type 1 (EV_KEY), code 114 (KEY_VOLUMEDOWN), value 1 Event: time 1438546061.771962, -------------- SYN_REPORT ------------ Event: time 1438546062.275838, type 4 (EV_MSC), code 4 (MSC_SCAN), value ae Event: time 1438546062.275838, type 1 (EV_KEY), code 114 (KEY_VOLUMEDOWN), value 0 Event: time 1438546062.275838, -------------- SYN_REPORT ------------ Event: time 1438546070.171954, type 4 (EV_MSC), code 4 (MSC_SCAN), value b0 Event: time 1438546070.171954, type 1 (EV_KEY), code 115 (KEY_VOLUMEUP), value 1 Event: time 1438546070.171954, -------------- SYN_REPORT ------------ Event: time 1438546070.675928, type 4 (EV_MSC), code 4 (MSC_SCAN), value b0 Event: time 1438546070.675928, type 1 (EV_KEY), code 115 (KEY_VOLUMEUP), value 0 Event: time 1438546070.675928, -------------- SYN_REPORT ------------ Please ignore my above comment, as it clearly states press/release events just once. As Juraj i'm also affected by sending the information twice using atkbd and acpi resulting in key captured twice. I am facing a similar issue. Instead of volume keys however, I see double key presses registered for brightness control. This issue doesn't seem restricted to HP laptops, as I'm using a Dell. Same issue on Dell 7140 and 7285. Hello. I have encountered a similar bug on Mouse MB1485UD11A-191 convertible laptop using only dedicated side volume buttons, Fn+F7/F8 worked fine. Could not find this bug at first, so came with it to an OpenSUSE Bugzilla: https://bugzilla.opensuse.org/show_bug.cgi?id=1161298 We were able to trace it back to the intel_hid driver, synopsis below. Evtest showed volume up/down events registered by: /dev/input/event0: AT Translated Set 2 keyboard /dev/input/event7: Intel HID 5 button array So it means that they both handle all of Volume Up/Down events, thus producing double input that is registered by showkey and everything else. Takashi Iwai from OpenSUSE suggested to blacklist intel_hid driver by adding a file /etc/modprobe.d/50-intel-hid.conf containing the line blacklist intel-hid You most likely need to rebuild initrd after this and then reboot. After this my volume control works as expected and I didn't find anything else affected by loss of this driver. Would ask OP and everybody affected to test this if still possible and see if we are actually having the same issue and if I need to create a separate bug report. Same issue on HP 550. |