Skip to contentSkip to conversation

hp-wmi: info hotkey has no keycode or scancode

DISCUSSION Dennis Nezic 3 participants 18 messages Jan 20, 2024 – Mar 26, 2024 2 messages not in the archive

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

Guys, the "info" illuminated touch-key (hotkey?) on my laptop "doesn't work", showkey doesn't report any keycode or scancode. I don't see any wmi related error messages from dmesg. All the other illuminated "hotkeys" work fine, although confusingly evtest and "libinput debug-events" report that they're coming through the event interface associated with "AT Translated Set 2 keyboard" instead of "HP WMI hotkeys", but hey, as long as I receive them I'm okay :p.

hp-wmi.c does seem to reference it:
{ KE_KEY, 0x213b, { KEY_INFO } },

How can I go about troubleshooting this? (I'm using kernel 6.6.8)

#1 lore raw

Am 20.01.24 um 19:58 schrieb Dennis Nezic:

Quoted 8 lines

Guys, the "info" illuminated touch-key (hotkey?) on my laptop "doesn't work", showkey doesn't report any keycode or scancode. I don't see any wmi related error messages from dmesg. All the other illuminated "hotkeys" work fine, although confusingly evtest and "libinput debug-events" report that they're coming through the event interface associated with "AT Translated Set 2 keyboard" instead of "HP WMI hotkeys", but hey, as long as I receive them I'm okay :p.

Quoted 5 lines

hp-wmi.c does seem to reference it:

   { KE_KEY, 0x213b,  { KEY_INFO } },

How can I go about troubleshooting this? (I'm using kernel 6.6.8)

Hello,

it can be possible that you machine does not use hp-wmi to deliver keycodes to the operating system, but instead emulates a standard keyboard controller.

Can you check with "kacpimon" that events concerning a PNP0C14 device are being received?

Thanks,
Armin Wolf

#2 lore raw
Quoted 13 lines · Armin Wolf

Am 20.01.24 um 19:58 schrieb Dennis Nezic:

Quoted 11 lines

Guys, the "info" illuminated touch-key (hotkey?) on my laptop "doesn't work", showkey doesn't report any keycode or scancode. I don't see any wmi related error messages from dmesg. All the other illuminated "hotkeys" work fine, although confusingly evtest and "libinput debug-events" report that they're coming through the event interface associated with "AT Translated Set 2 keyboard" instead of "HP WMI hotkeys", but hey, as long as I receive them I'm okay :p.

hp-wmi.c does seem to reference it:

   { KE_KEY, 0x213b,  { KEY_INFO } },
Quoted 7 lines
Quoted 1 line

How can I go about troubleshooting this? (I'm using kernel 6.6.8)

it can be possible that your machine does not use hp-wmi to deliver keycodes to the operating system, but instead emulates a standard keyboard controller.

Can you check with "kacpimon" that events concerning a PNP0C14 device are being received?

Very possible indeed. "kacpimon" doesn't show anything when I press that touchkey, but it does when I press all the other touchkeys. (I do get lots of accelerometer noise.)

#3 lore raw

Am 20.01.24 um 22:39 schrieb Dennis Nezic:

Quoted 15 lines · Armin Wolf
Quoted 14 lines

Am 20.01.24 um 19:58 schrieb Dennis Nezic:

Quoted 12 lines

Guys, the "info" illuminated touch-key (hotkey?) on my laptop "doesn't work", showkey doesn't report any keycode or scancode. I don't see any wmi related error messages from dmesg. All the other illuminated "hotkeys" work fine, although confusingly evtest and "libinput debug-events" report that they're coming through the event interface associated with "AT Translated Set 2 keyboard" instead of "HP WMI hotkeys", but hey, as long as I receive them I'm okay :p.

hp-wmi.c does seem to reference it:

    { KE_KEY, 0x213b,  { KEY_INFO } },

How can I go about troubleshooting this? (I'm using kernel 6.6.8)

Quoted 9 lines
Quoted 5 lines

it can be possible that your machine does not use hp-wmi to deliver keycodes to the operating system, but instead emulates a standard keyboard controller.

Can you check with "kacpimon" that events concerning a PNP0C14 device are being received?

Very possible indeed. "kacpimon" doesn't show anything when I press that touchkey, but it does when I press all the other touchkeys. (I do get lots of accelerometer noise.)

Interesting, can you please share the output of:
- "kacpimon" while you where pressing the buttons
- "acpidump"

Thanks,
Armin Wolf

#4 lore raw
Quoted 22 lines · Armin Wolf

Am 20.01.24 um 22:39 schrieb Dennis Nezic:

Quoted 20 lines · Armin Wolf
Quoted 19 lines

Am 20.01.24 um 19:58 schrieb Dennis Nezic:

Quoted 8 lines

Guys, the "info" illuminated touch-key (hotkey?) on my laptop "doesn't work", showkey doesn't report any keycode or scancode. I don't see any wmi related error messages from dmesg. All the other illuminated "hotkeys" work fine, although confusingly evtest and "libinput debug-events" report that they're coming through the event interface associated with "AT Translated Set 2 keyboard" instead of "HP WMI hotkeys", but hey, as long as I receive them I'm okay :p.

Quoted 4 lines

hp-wmi.c does seem to reference it:

    { KE_KEY, 0x213b,  { KEY_INFO } },

How can I go about troubleshooting this? (I'm using kernel 6.6.8)

it can be possible that your machine does not use hp-wmi to deliver keycodes to the operating system, but instead emulates a standard keyboard controller.

Can you check with "kacpimon" that events concerning a PNP0C14 device are being received?

Quoted 7 lines
Quoted 4 lines

Very possible indeed. "kacpimon" doesn't show anything when I press that touchkey, but it does when I press all the other touchkeys. (I do get lots of accelerometer noise.)

Interesting, can you please share the output of:
- "kacpimon" while you where pressing the buttons
- "acpidump"

Actually I was finally able to detect something via kacpimon, but it was elusive, and it's scaring me now! It wouldn't immediately show on live stdout (the way the other touch-hotkeys, and normal keys, do), and I even had trouble seeing it when trying to redirect stdout to a file! Ctrl-C'ing would prematurely truncate the output, sometimes not capturing it, even the more graceful Escape-exit wouldn't capture it unless I waited or padded it with mouse movements. Ie. there is some very weird delay going on, and maybe repetition, or something.

For example, I swear I only touched that info key 5 times here, and then AFTERWARDS pressed the 'A' key twice, and then Esc. grep'ing for 'Type: 1' I was able to catch:

Input Layer:  Type: 1  Code: 28  Value: 0
Input Layer:  Type: 1  Code: 325  Value: 1
Input Layer:  Type: 1  Code: 330  Value: 1
Input Layer:  Type: 1  Code: 330  Value: 0
Input Layer:  Type: 1  Code: 325  Value: 0
Input Layer:  Type: 1  Code: 325  Value: 1
Input Layer:  Type: 1  Code: 330  Value: 1
Input Layer:  Type: 1  Code: 330  Value: 0
Input Layer:  Type: 1  Code: 325  Value: 0
Input Layer:  Type: 1  Code: 325  Value: 1
Input Layer:  Type: 1  Code: 330  Value: 1
Input Layer:  Type: 1  Code: 330  Value: 0
Input Layer:  Type: 1  Code: 325  Value: 0
Input Layer:  Type: 1  Code: 30  Value: 1
Input Layer:  Type: 1  Code: 30  Value: 0
Input Layer:  Type: 1  Code: 325  Value: 1
Input Layer:  Type: 1  Code: 330  Value: 1
Input Layer:  Type: 1  Code: 330  Value: 0
Input Layer:  Type: 1  Code: 325  Value: 0
Input Layer:  Type: 1  Code: 325  Value: 1
Input Layer:  Type: 1  Code: 330  Value: 1
Input Layer:  Type: 1  Code: 330  Value: 0
Input Layer:  Type: 1  Code: 325  Value: 0
Input Layer:  Type: 1  Code: 325  Value: 1
Input Layer:  Type: 1  Code: 330  Value: 1
Input Layer:  Type: 1  Code: 330  Value: 0
Input Layer:  Type: 1  Code: 325  Value: 0
Input Layer:  Type: 1  Code: 330  Value: 1
Input Layer:  Type: 1  Code: 325  Value: 1
Input Layer:  Type: 1  Code: 330  Value: 0
Input Layer:  Type: 1  Code: 325  Value: 0
Input Layer:  Type: 1  Code: 30  Value: 1
Input Layer:  Type: 1  Code: 30  Value: 0
Input Layer:  Type: 1  Code: 1  Value: 1

A more weird example, again I *swear* I first only touched that info key *5* times, and then moved the mouse for a few seconds between 2 'A' key presses, and finishing with Escape, but although it showed the two 'A' key events properly, it also showed *11* "code 325" and 11 "code 330" value1 events, out of order!?

Input Layer:  Type: 1  Code: 28  Value: 0
Input Layer:  Type: 1  Code: 325  Value: 1
Input Layer:  Type: 1  Code: 330  Value: 1
Input Layer:  Type: 1  Code: 330  Value: 0
Input Layer:  Type: 1  Code: 325  Value: 0
Input Layer:  Type: 1  Code: 325  Value: 1
Input Layer:  Type: 1  Code: 330  Value: 1
Input Layer:  Type: 1  Code: 330  Value: 0
Input Layer:  Type: 1  Code: 325  Value: 0
Input Layer:  Type: 1  Code: 325  Value: 1
Input Layer:  Type: 1  Code: 330  Value: 1
Input Layer:  Type: 1  Code: 330  Value: 0
Input Layer:  Type: 1  Code: 325  Value: 0
Input Layer:  Type: 1  Code: 30  Value: 1
Input Layer:  Type: 1  Code: 30  Value: 0
Input Layer:  Type: 1  Code: 325  Value: 1
Input Layer:  Type: 1  Code: 330  Value: 1
Input Layer:  Type: 1  Code: 330  Value: 0
Input Layer:  Type: 1  Code: 325  Value: 0
Input Layer:  Type: 1  Code: 325  Value: 1
Input Layer:  Type: 1  Code: 330  Value: 1
Input Layer:  Type: 1  Code: 330  Value: 0
Input Layer:  Type: 1  Code: 325  Value: 0
Input Layer:  Type: 1  Code: 330  Value: 1
Input Layer:  Type: 1  Code: 325  Value: 1
Input Layer:  Type: 1  Code: 330  Value: 0
Input Layer:  Type: 1  Code: 325  Value: 0
Input Layer:  Type: 1  Code: 330  Value: 1
Input Layer:  Type: 1  Code: 325  Value: 1
Input Layer:  Type: 1  Code: 330  Value: 0
Input Layer:  Type: 1  Code: 325  Value: 0
Input Layer:  Type: 1  Code: 30  Value: 1
Input Layer:  Type: 1  Code: 30  Value: 0
Input Layer:  Type: 1  Code: 325  Value: 1
Input Layer:  Type: 1  Code: 330  Value: 1
Input Layer:  Type: 1  Code: 330  Value: 0
Input Layer:  Type: 1  Code: 325  Value: 0
Input Layer:  Type: 1  Code: 325  Value: 1
Input Layer:  Type: 1  Code: 330  Value: 1
Input Layer:  Type: 1  Code: 330  Value: 0
Input Layer:  Type: 1  Code: 325  Value: 0
Input Layer:  Type: 1  Code: 325  Value: 1
Input Layer:  Type: 1  Code: 330  Value: 1
Input Layer:  Type: 1  Code: 330  Value: 0
Input Layer:  Type: 1  Code: 325  Value: 0
Input Layer:  Type: 1  Code: 325  Value: 1
Input Layer:  Type: 1  Code: 330  Value: 1
Input Layer:  Type: 1  Code: 330  Value: 0
Input Layer:  Type: 1  Code: 325  Value: 0
Input Layer:  Type: 1  Code: 1  Value: 1

(Thank you for your guidance btw! Will an acpidump still be necessary?)

#5 lore raw

Am 22.01.24 um 08:05 schrieb Dennis Nezic:

Quoted 78 lines · Armin Wolf
Quoted 22 lines

Am 20.01.24 um 22:39 schrieb Dennis Nezic:

Quoted 20 lines · Armin Wolf
Quoted 19 lines

Am 20.01.24 um 19:58 schrieb Dennis Nezic:

Quoted 8 lines

Guys, the "info" illuminated touch-key (hotkey?) on my laptop "doesn't work", showkey doesn't report any keycode or scancode. I don't see any wmi related error messages from dmesg. All the other illuminated "hotkeys" work fine, although confusingly evtest and "libinput debug-events" report that they're coming through the event interface associated with "AT Translated Set 2 keyboard" instead of "HP WMI hotkeys", but hey, as long as I receive them I'm okay :p.

Quoted 4 lines

hp-wmi.c does seem to reference it:

     { KE_KEY, 0x213b,  { KEY_INFO } },

How can I go about troubleshooting this? (I'm using kernel 6.6.8)

it can be possible that your machine does not use hp-wmi to deliver keycodes to the operating system, but instead emulates a standard keyboard controller.

Can you check with "kacpimon" that events concerning a PNP0C14 device are being received?

Quoted 7 lines
Quoted 4 lines

Very possible indeed. "kacpimon" doesn't show anything when I press that touchkey, but it does when I press all the other touchkeys. (I do get lots of accelerometer noise.)

Interesting, can you please share the output of:
- "kacpimon" while you where pressing the buttons
- "acpidump"

Actually I was finally able to detect something via kacpimon, but it was elusive, and it's scaring me now! It wouldn't immediately show on live stdout (the way the other touch-hotkeys, and normal keys, do), and I even had trouble seeing it when trying to redirect stdout to a file! Ctrl-C'ing would prematurely truncate the output, sometimes not capturing it, even the more graceful Escape-exit wouldn't capture it unless I waited or padded it with mouse movements. Ie. there is some very weird delay going on, and maybe repetition, or something.

For example, I swear I only touched that info key 5 times here, and then AFTERWARDS pressed the 'A' key twice, and then Esc. grep'ing for 'Type: 1' I was able to catch:

Input Layer:  Type: 1  Code: 28  Value: 0
Input Layer:  Type: 1  Code: 325  Value: 1
Input Layer:  Type: 1  Code: 330  Value: 1
Input Layer:  Type: 1  Code: 330  Value: 0
Input Layer:  Type: 1  Code: 325  Value: 0
Input Layer:  Type: 1  Code: 325  Value: 1
Input Layer:  Type: 1  Code: 330  Value: 1
Input Layer:  Type: 1  Code: 330  Value: 0
Input Layer:  Type: 1  Code: 325  Value: 0
Input Layer:  Type: 1  Code: 325  Value: 1
Input Layer:  Type: 1  Code: 330  Value: 1
Input Layer:  Type: 1  Code: 330  Value: 0
Input Layer:  Type: 1  Code: 325  Value: 0
Input Layer:  Type: 1  Code: 30  Value: 1
Input Layer:  Type: 1  Code: 30  Value: 0
Input Layer:  Type: 1  Code: 325  Value: 1
Input Layer:  Type: 1  Code: 330  Value: 1
Input Layer:  Type: 1  Code: 330  Value: 0
Input Layer:  Type: 1  Code: 325  Value: 0
Input Layer:  Type: 1  Code: 325  Value: 1
Input Layer:  Type: 1  Code: 330  Value: 1
Input Layer:  Type: 1  Code: 330  Value: 0
Input Layer:  Type: 1  Code: 325  Value: 0
Input Layer:  Type: 1  Code: 325  Value: 1
Input Layer:  Type: 1  Code: 330  Value: 1
Input Layer:  Type: 1  Code: 330  Value: 0
Input Layer:  Type: 1  Code: 325  Value: 0
Input Layer:  Type: 1  Code: 330  Value: 1
Input Layer:  Type: 1  Code: 325  Value: 1
Input Layer:  Type: 1  Code: 330  Value: 0
Input Layer:  Type: 1  Code: 325  Value: 0
Input Layer:  Type: 1  Code: 30  Value: 1
Input Layer:  Type: 1  Code: 30  Value: 0
Input Layer:  Type: 1  Code: 1  Value: 1
Quoted 5 lines

A more weird example, again I *swear* I first only touched that info key *5* times, and then moved the mouse for a few seconds between 2 'A' key presses, and finishing with Escape, but although it showed the two 'A' key events properly, it also showed *11* "code 325" and 11 "code 330" value1 events, out of order!?

Those events are touchscreen events, maybe your mouse is responsible for them.

Quoted 52 lines
Input Layer:  Type: 1  Code: 28  Value: 0
Input Layer:  Type: 1  Code: 325  Value: 1
Input Layer:  Type: 1  Code: 330  Value: 1
Input Layer:  Type: 1  Code: 330  Value: 0
Input Layer:  Type: 1  Code: 325  Value: 0
Input Layer:  Type: 1  Code: 325  Value: 1
Input Layer:  Type: 1  Code: 330  Value: 1
Input Layer:  Type: 1  Code: 330  Value: 0
Input Layer:  Type: 1  Code: 325  Value: 0
Input Layer:  Type: 1  Code: 325  Value: 1
Input Layer:  Type: 1  Code: 330  Value: 1
Input Layer:  Type: 1  Code: 330  Value: 0
Input Layer:  Type: 1  Code: 325  Value: 0
Input Layer:  Type: 1  Code: 30  Value: 1
Input Layer:  Type: 1  Code: 30  Value: 0
Input Layer:  Type: 1  Code: 325  Value: 1
Input Layer:  Type: 1  Code: 330  Value: 1
Input Layer:  Type: 1  Code: 330  Value: 0
Input Layer:  Type: 1  Code: 325  Value: 0
Input Layer:  Type: 1  Code: 325  Value: 1
Input Layer:  Type: 1  Code: 330  Value: 1
Input Layer:  Type: 1  Code: 330  Value: 0
Input Layer:  Type: 1  Code: 325  Value: 0
Input Layer:  Type: 1  Code: 330  Value: 1
Input Layer:  Type: 1  Code: 325  Value: 1
Input Layer:  Type: 1  Code: 330  Value: 0
Input Layer:  Type: 1  Code: 325  Value: 0
Input Layer:  Type: 1  Code: 330  Value: 1
Input Layer:  Type: 1  Code: 325  Value: 1
Input Layer:  Type: 1  Code: 330  Value: 0
Input Layer:  Type: 1  Code: 325  Value: 0
Input Layer:  Type: 1  Code: 30  Value: 1
Input Layer:  Type: 1  Code: 30  Value: 0
Input Layer:  Type: 1  Code: 325  Value: 1
Input Layer:  Type: 1  Code: 330  Value: 1
Input Layer:  Type: 1  Code: 330  Value: 0
Input Layer:  Type: 1  Code: 325  Value: 0
Input Layer:  Type: 1  Code: 325  Value: 1
Input Layer:  Type: 1  Code: 330  Value: 1
Input Layer:  Type: 1  Code: 330  Value: 0
Input Layer:  Type: 1  Code: 325  Value: 0
Input Layer:  Type: 1  Code: 325  Value: 1
Input Layer:  Type: 1  Code: 330  Value: 1
Input Layer:  Type: 1  Code: 330  Value: 0
Input Layer:  Type: 1  Code: 325  Value: 0
Input Layer:  Type: 1  Code: 325  Value: 1
Input Layer:  Type: 1  Code: 330  Value: 1
Input Layer:  Type: 1  Code: 330  Value: 0
Input Layer:  Type: 1  Code: 325  Value: 0
Input Layer:  Type: 1  Code: 1  Value: 1
Quoted 1 line

(Thank you for your guidance btw! Will an acpidump still be necessary?)

I have to apologize, the events send by ACPI WMI to kacpimon do not contain a "PNP0C14" string or the name WMI at all.

Instead they look like this:

	netlink:  9DBB5994-A997- 000000d0 00000000

Can you try to use kacpimon again but without root privileges? This way only netlink events show up. You might also stop acpid while you are using kacpimon.

If you still cannot receive any netlink events, then i might need to take a look at your ACPI tables via acpidump.

Thanks,
Armin Wolf

A message that is not in the archive (sent off-list or not yet received): Za8xL39m1X22f2Bb@panther

A message that is not in the archive (sent off-list or not yet received): Za9DQdLg2d_CnrZG@panther

#8 lore raw

Am 23.01.24 um 05:40 schrieb Dennis Nezic:

Quoted 76 lines · Dennis Nezic
Quoted 58 lines · Armin Wolf
Quoted 32 lines

Am 22.01.24 um 08:05 schrieb Dennis Nezic:

Quoted 30 lines · Armin Wolf
Quoted 29 lines

Am 20.01.24 um 22:39 schrieb Dennis Nezic:

Quoted 15 lines · Armin Wolf
Quoted 14 lines

Am 20.01.24 um 19:58 schrieb Dennis Nezic:

Quoted 12 lines

Guys, the "info" illuminated touch-key (hotkey?) on my laptop "doesn't work", showkey doesn't report any keycode or scancode. I don't see any wmi related error messages from dmesg. All the other illuminated "hotkeys" work fine, although confusingly evtest and "libinput debug-events" report that they're coming through the event interface associated with "AT Translated Set 2 keyboard" instead of "HP WMI hotkeys", but hey, as long as I receive them I'm okay :p.

hp-wmi.c does seem to reference it:

      { KE_KEY, 0x213b,  { KEY_INFO } },

How can I go about troubleshooting this? (I'm using kernel 6.6.8)

Quoted 9 lines
Quoted 5 lines

it can be possible that your machine does not use hp-wmi to deliver keycodes to the operating system, but instead emulates a standard keyboard controller.

Can you check with "kacpimon" that events concerning a PNP0C14 device are being received?

Very possible indeed. "kacpimon" doesn't show anything when I press that touchkey, but it does when I press all the other touchkeys. (I do get lots of accelerometer noise.)

Interesting, can you please share the output of:
- "kacpimon" while you where pressing the buttons
- "acpidump"

Quoted 6 lines
Quoted 5 lines

...

Input Layer:  Type: 1  Code: 325  Value: 1
Input Layer:  Type: 1  Code: 330  Value: 1
Input Layer:  Type: 1  Code: 330  Value: 0
Input Layer:  Type: 1  Code: 325  Value: 0

Those events are touchscreen events, maybe your mouse is responsible for them.

Right, of course, woops, these must have been the touchpad press events, as I was moving the mouse around :P

Quoted 3 lines

Instead they look like this:

	netlink:  9DBB5994-A997- 000000d0 00000000

I'm definitely not seeing anything like that, just "^Input Layer: Type"'s

Quoted 2 lines

Can you try to use kacpimon again but without root privileges? This way only netlink events show up. You might also stop acpid while you are using kacpimon.

0 output from/with netlink, even though kacpimon said:

Netlink ACPI Family ID: 24
Netlink ACPI Multicast Group ID: 5
netlink opened successfully

Remember all my other fancy hotkeys "work", but they appear as regular keypress events from an "AT Translated Set 2 keyboard".

Quoted 7 lines
Quoted 2 lines

If you still cannot receive any netlink events, then i might need to take a look at your ACPI tables via acpidump.

https://dennisn.mooo.com/stuff/dump.txt

Quoted 2 lines

Thanks,
Armin Wolf

Thank you again sir!

I'm not sure if this is helpful, "dmesg | grep -i wmi" ...

[    0.352634] wmi_bus wmi_bus-PNP0C14:00: [Firmware Info]: A1799AC3-9429-4529-927E-DFE13736EEBA has zero instances
[    0.352634] wmi_bus wmi_bus-PNP0C14:00: [Firmware Info]: A1799AC5-9429-4529-927E-DFE13736EEBA has zero instances
[    0.352634] wmi_bus wmi_bus-PNP0C14:00: [Firmware Info]: A1799ACA-9429-4529-927E-DFE13736EEBA has zero instances
[    0.352634] wmi_bus wmi_bus-PNP0C14:01: [Firmware Info]: 8232DE3D-663D-4327-A8F4-E293ADB9BF05 has zero instances
[    0.352634] wmi_bus wmi_bus-PNP0C14:01: [Firmware Info]: 8F1F6436-9F42-42C8-BADC-0E9424F20C9A has zero instances
[    0.352634] wmi_bus wmi_bus-PNP0C14:01: [Firmware Info]: 8F1F6435-9F42-42C8-BADC-0E9424F20C9A has zero instances
[    2.573231] input: HP WMI hotkeys as /devices/virtual/input/input14
Quoted 1 line

(Btw that "info" key does get illuminated when I touch/press it, even though no codes are seen.)

These warnings in dmesg are harmless, they are informing you that some WMI devices are unavailable.

I took a look at your ACPI tables and it seems that the WMI device used by hp-wmi is indeed unused. What is the model name of your HP notebook?

Armin Wolf

#9 lore raw

Am 23.01.24 um 09:58 schrieb Armin Wolf:

Quoted 98 lines

Am 23.01.24 um 05:40 schrieb Dennis Nezic:

Quoted 93 lines · Dennis Nezic
Quoted 70 lines · Armin Wolf
Quoted 40 lines

Am 22.01.24 um 08:05 schrieb Dennis Nezic:

Quoted 38 lines · Armin Wolf
Quoted 37 lines

Am 20.01.24 um 22:39 schrieb Dennis Nezic:

Quoted 23 lines · Armin Wolf
Quoted 22 lines

Am 20.01.24 um 19:58 schrieb Dennis Nezic:

Quoted 11 lines

Guys, the "info" illuminated touch-key (hotkey?) on my laptop "doesn't
work", showkey doesn't report any keycode or scancode. I don't see any
wmi related error messages from dmesg. All the other illuminated "hotkeys" work fine, although confusingly evtest and "libinput debug-events" report that they're coming through the event interface
associated with "AT Translated Set 2 keyboard" instead of "HP WMI hotkeys", but hey, as long as I receive them I'm okay :p.

Quoted 4 lines

hp-wmi.c does seem to reference it:
      { KE_KEY, 0x213b,  { KEY_INFO } },

How can I go about troubleshooting this? (I'm using kernel 6.6.8)

it can be possible that your machine does not use hp-wmi to deliver keycodes
to the operating system, but instead emulates a standard keyboard controller.

Quoted 9 lines
Quoted 3 lines

Can you check with "kacpimon" that events concerning a PNP0C14 device are being
received?

Very possible indeed. "kacpimon" doesn't show anything when I press that
touchkey, but it does when I press all the other touchkeys. (I do get
lots of accelerometer noise.)

Interesting, can you please share the output of:
- "kacpimon" while you where pressing the buttons
- "acpidump"

Quoted 7 lines
Quoted 5 lines

...
Input Layer:  Type: 1  Code: 325  Value: 1 Input Layer:  Type: 1  Code: 330  Value: 1 Input Layer:  Type: 1  Code: 330  Value: 0 Input Layer:  Type: 1  Code: 325  Value: 0

Those events are touchscreen events, maybe your mouse is responsible for them.

Right, of course, woops, these must have been the touchpad press events,
as I was moving the mouse around :P

Quoted 3 lines

Instead they look like this:

    netlink:  9DBB5994-A997- 000000d0 00000000

I'm definitely not seeing anything like that, just "^Input Layer:
Type"'s

Quoted 3 lines

Can you try to use kacpimon again but without root privileges? This way only netlink events show up.
You might also stop acpid while you are using kacpimon.

0 output from/with netlink, even though kacpimon said:

Netlink ACPI Family ID: 24
Netlink ACPI Multicast Group ID: 5
netlink opened successfully

Remember all my other fancy hotkeys "work", but they appear as regular keypress events from an "AT Translated Set 2 keyboard".

Quoted 8 lines
Quoted 3 lines

If you still cannot receive any netlink events, then i might need to take a look at your ACPI tables
via acpidump.

https://dennisn.mooo.com/stuff/dump.txt

Quoted 2 lines

Thanks,
Armin Wolf

Thank you again sir!

I'm not sure if this is helpful,  "dmesg | grep -i wmi" ...

[    0.352634] wmi_bus wmi_bus-PNP0C14:00: [Firmware Info]:
A1799AC3-9429-4529-927E-DFE13736EEBA has zero instances
[    0.352634] wmi_bus wmi_bus-PNP0C14:00: [Firmware Info]: A1799AC5-9429-4529-927E-DFE13736EEBA has zero instances [    0.352634] wmi_bus wmi_bus-PNP0C14:00: [Firmware Info]: A1799ACA-9429-4529-927E-DFE13736EEBA has zero instances [    0.352634] wmi_bus wmi_bus-PNP0C14:01: [Firmware Info]:
8232DE3D-663D-4327-A8F4-E293ADB9BF05 has zero instances
[    0.352634] wmi_bus wmi_bus-PNP0C14:01: [Firmware Info]:
8F1F6436-9F42-42C8-BADC-0E9424F20C9A has zero instances
[    0.352634] wmi_bus wmi_bus-PNP0C14:01: [Firmware Info]:
8F1F6435-9F42-42C8-BADC-0E9424F20C9A has zero instances
[    2.573231] input: HP WMI hotkeys as /devices/virtual/input/input14

Quoted 2 lines

(Btw that "info" key does get illuminated when I touch/press it, even though no codes are seen.)

Quoted 10 lines

These warnings in dmesg are harmless, they are informing you that some WMI devices are unavailable.

I took a look at your ACPI tables and it seems that the WMI device used by hp-wmi is indeed unused.
What is the model name of your HP notebook?

Armin Wolf

Also i just noted that you notebook might contain a PNP0C32 quickstart button device. Can you tell me the output of "cat /sys/bus/acpi/devices/PNP0C32\:00/status"?

Armin Wolf

#10 lore raw
Quoted 92 lines · Armin Wolf

Am 23.01.24 um 09:58 schrieb Armin Wolf:

Quoted 90 lines

Am 23.01.24 um 05:40 schrieb Dennis Nezic:

Quoted 74 lines · Dennis Nezic
Quoted 64 lines · Armin Wolf
Quoted 36 lines

Am 22.01.24 um 08:05 schrieb Dennis Nezic:

Quoted 34 lines · Armin Wolf
Quoted 33 lines

Am 20.01.24 um 22:39 schrieb Dennis Nezic:

Quoted 31 lines · Armin Wolf
Quoted 16 lines

Am 20.01.24 um 19:58 schrieb Dennis Nezic:

Quoted 11 lines

Guys, the "info" illuminated touch-key (hotkey?) on my laptop "doesn't
work", showkey doesn't report any keycode or scancode. I don't see any
wmi related error messages from dmesg. All the other illuminated "hotkeys" work fine, although confusingly evtest and "libinput debug-events" report that they're coming through the event interface
associated with "AT Translated Set 2 keyboard" instead of "HP WMI hotkeys", but hey, as long as I receive them I'm okay :p.

Quoted 3 lines

hp-wmi.c does seem to reference it:

How can I go about troubleshooting this? (I'm using kernel 6.6.8)

Quoted 8 lines

it can be possible that your machine does not use hp-wmi to deliver keycodes
to the operating system, but instead emulates a standard keyboard controller.

Can you check with "kacpimon" that events concerning a PNP0C14 device are being
received?

Very possible indeed. "kacpimon" doesn't show anything when I press that
touchkey, but it does when I press all the other touchkeys. (I do get
lots of accelerometer noise.)

Quoted 6 lines
Quoted 4 lines
Quoted 3 lines

Interesting, can you please share the output of:
- "kacpimon" while you where pressing the buttons
- "acpidump"

...

Those events are touchscreen events, maybe your mouse is responsible for them.

Right, of course, woops, these must have been the touchpad press events,
as I was moving the mouse around :P

Quoted 2 lines

Instead they look like this:

I'm definitely not seeing anything like that, just "^Input Layer:
Type"'s

Quoted 3 lines

Can you try to use kacpimon again but without root privileges? This way only netlink events show up.
You might also stop acpid while you are using kacpimon.

0 output from/with netlink, even though kacpimon said:

Netlink ACPI Family ID: 24
Netlink ACPI Multicast Group ID: 5
netlink opened successfully

Remember all my other fancy hotkeys "work", but they appear as regular keypress events from an "AT Translated Set 2 keyboard".

Quoted 8 lines
Quoted 3 lines

If you still cannot receive any netlink events, then i might need to take a look at your ACPI tables
via acpidump.

https://dennisn.mooo.com/stuff/dump.txt

Quoted 2 lines

Thanks,
Armin Wolf

Thank you again sir!

Quoted 7 lines

A1799AC3-9429-4529-927E-DFE13736EEBA has zero instances 8232DE3D-663D-4327-A8F4-E293ADB9BF05 has zero instances 8F1F6436-9F42-42C8-BADC-0E9424F20C9A has zero instances 8F1F6435-9F42-42C8-BADC-0E9424F20C9A has zero instances

(Btw that "info" key does get illuminated when I touch/press it, even though no codes are seen.)

These warnings in dmesg are harmless, they are informing you that some WMI devices are unavailable.

I took a look at your ACPI tables and it seems that the WMI device used by hp-wmi is indeed unused.
What is the model name of your HP notebook?

HP Compaq 8710p

Quoted 2 lines

Also i just noted that your notebook might contain a PNP0C32 quickstart button device. Can you tell me the output of "cat /sys/bus/acpi/devices/PNP0C32\:00/status"?

15

#11 lore raw

Hi,

Quoted 94 lines · Dennis Nezic
Quoted 92 lines · Armin Wolf

Am 23.01.24 um 09:58 schrieb Armin Wolf:

Quoted 90 lines

Am 23.01.24 um 05:40 schrieb Dennis Nezic:

Quoted 74 lines · Dennis Nezic
Quoted 64 lines · Armin Wolf
Quoted 36 lines

Am 22.01.24 um 08:05 schrieb Dennis Nezic:

Quoted 34 lines · Armin Wolf
Quoted 33 lines

Am 20.01.24 um 22:39 schrieb Dennis Nezic:

Quoted 31 lines · Armin Wolf
Quoted 16 lines

Am 20.01.24 um 19:58 schrieb Dennis Nezic:

Quoted 11 lines

Guys, the "info" illuminated touch-key (hotkey?) on my laptop "doesn't
work", showkey doesn't report any keycode or scancode. I don't see any
wmi related error messages from dmesg. All the other illuminated "hotkeys" work fine, although confusingly evtest and "libinput debug-events" report that they're coming through the event interface
associated with "AT Translated Set 2 keyboard" instead of "HP WMI hotkeys", but hey, as long as I receive them I'm okay :p.

Quoted 3 lines

hp-wmi.c does seem to reference it:

How can I go about troubleshooting this? (I'm using kernel 6.6.8)

Quoted 8 lines

it can be possible that your machine does not use hp-wmi to deliver keycodes
to the operating system, but instead emulates a standard keyboard controller.

Can you check with "kacpimon" that events concerning a PNP0C14 device are being
received?

Very possible indeed. "kacpimon" doesn't show anything when I press that
touchkey, but it does when I press all the other touchkeys. (I do get
lots of accelerometer noise.)

Quoted 6 lines
Quoted 4 lines
Quoted 3 lines

Interesting, can you please share the output of:
- "kacpimon" while you where pressing the buttons
- "acpidump"

...

Those events are touchscreen events, maybe your mouse is responsible for them.

Right, of course, woops, these must have been the touchpad press events,
as I was moving the mouse around :P

Quoted 2 lines

Instead they look like this:

I'm definitely not seeing anything like that, just "^Input Layer:
Type"'s

Quoted 3 lines

Can you try to use kacpimon again but without root privileges? This way only netlink events show up.
You might also stop acpid while you are using kacpimon.

0 output from/with netlink, even though kacpimon said:

Netlink ACPI Family ID: 24
Netlink ACPI Multicast Group ID: 5
netlink opened successfully

Remember all my other fancy hotkeys "work", but they appear as regular keypress events from an "AT Translated Set 2 keyboard".

Quoted 8 lines
Quoted 3 lines

If you still cannot receive any netlink events, then i might need to take a look at your ACPI tables
via acpidump.

https://dennisn.mooo.com/stuff/dump.txt

Quoted 2 lines

Thanks,
Armin Wolf

Thank you again sir!

Quoted 7 lines

A1799AC3-9429-4529-927E-DFE13736EEBA has zero instances 8232DE3D-663D-4327-A8F4-E293ADB9BF05 has zero instances 8F1F6436-9F42-42C8-BADC-0E9424F20C9A has zero instances 8F1F6435-9F42-42C8-BADC-0E9424F20C9A has zero instances

(Btw that "info" key does get illuminated when I touch/press it, even though no codes are seen.)

These warnings in dmesg are harmless, they are informing you that some WMI devices are unavailable.

I took a look at your ACPI tables and it seems that the WMI device used by hp-wmi is indeed unused.
What is the model name of your HP notebook?

Quoted 6 lines

HP Compaq 8710p

Quoted 2 lines

Also i just noted that your notebook might contain a PNP0C32 quickstart button device. Can you tell me the output of "cat /sys/bus/acpi/devices/PNP0C32\:00/status"?

15

Interesting.

There have been several attempts to add support for this in the past. The last one being:

https://lore.kernel.org/platform-driver-x86/[email protected]/

Note that in this case this also required some vender specific poking in toshiba_acpi to get things to work.

I see that the HP Compaq 8710p is about the same vintage as the Toshiba Z830 on which the last attempt to do something about the quick start buttons was done.

So this might very well explain the missing button issue.

Regards,

Hans

#12 lore raw

Am 23.01.24 um 16:34 schrieb Hans de Goede:

Quoted 113 lines

Hi,

Quoted 88 lines · Dennis Nezic
Quoted 87 lines · Armin Wolf

Am 23.01.24 um 09:58 schrieb Armin Wolf:

Quoted 85 lines

Am 23.01.24 um 05:40 schrieb Dennis Nezic:

Quoted 72 lines · Dennis Nezic
Quoted 71 lines · Armin Wolf
Quoted 36 lines

Am 22.01.24 um 08:05 schrieb Dennis Nezic:

Quoted 34 lines · Armin Wolf
Quoted 33 lines

Am 20.01.24 um 22:39 schrieb Dennis Nezic:

Quoted 31 lines · Armin Wolf
Quoted 16 lines

Am 20.01.24 um 19:58 schrieb Dennis Nezic:

Quoted 11 lines

Guys, the "info" illuminated touch-key (hotkey?) on my laptop "doesn't
work", showkey doesn't report any keycode or scancode. I don't see any
wmi related error messages from dmesg. All the other illuminated "hotkeys" work fine, although confusingly evtest and "libinput debug-events" report that they're coming through the event interface
associated with "AT Translated Set 2 keyboard" instead of "HP WMI hotkeys", but hey, as long as I receive them I'm okay :p.

Quoted 3 lines

hp-wmi.c does seem to reference it:

How can I go about troubleshooting this? (I'm using kernel 6.6.8)

Quoted 8 lines

it can be possible that your machine does not use hp-wmi to deliver keycodes
to the operating system, but instead emulates a standard keyboard controller.

Can you check with "kacpimon" that events concerning a PNP0C14 device are being
received?

Very possible indeed. "kacpimon" doesn't show anything when I press that
touchkey, but it does when I press all the other touchkeys. (I do get
lots of accelerometer noise.)

Quoted 6 lines
Quoted 4 lines
Quoted 3 lines

Interesting, can you please share the output of:
- "kacpimon" while you where pressing the buttons
- "acpidump"

...

Those events are touchscreen events, maybe your mouse is responsible for them.

Right, of course, woops, these must have been the touchpad press events,
as I was moving the mouse around :P

Quoted 2 lines

Instead they look like this:

I'm definitely not seeing anything like that, just "^Input Layer:
Type"'s

Quoted 3 lines

Can you try to use kacpimon again but without root privileges? This way only netlink events show up.
You might also stop acpid while you are using kacpimon.

0 output from/with netlink, even though kacpimon said:

Netlink ACPI Family ID: 24
Netlink ACPI Multicast Group ID: 5
netlink opened successfully

Remember all my other fancy hotkeys "work", but they appear as regular keypress events from an "AT Translated Set 2 keyboard".

Quoted 3 lines

If you still cannot receive any netlink events, then i might need to take a look at your ACPI tables
via acpidump.

https://dennisn.mooo.com/stuff/dump.txt

Quoted 2 lines

Thanks,
Armin Wolf

Quoted 8 lines
Quoted 1 line

Thank you again sir!

A1799AC3-9429-4529-927E-DFE13736EEBA has zero instances 8232DE3D-663D-4327-A8F4-E293ADB9BF05 has zero instances 8F1F6436-9F42-42C8-BADC-0E9424F20C9A has zero instances 8F1F6435-9F42-42C8-BADC-0E9424F20C9A has zero instances

(Btw that "info" key does get illuminated when I touch/press it, even though no codes are seen.)

These warnings in dmesg are harmless, they are informing you that some WMI devices are unavailable.

Quoted 8 lines
Quoted 3 lines
Quoted 3 lines

I took a look at your ACPI tables and it seems that the WMI device used by hp-wmi is indeed unused.
What is the model name of your HP notebook?

HP Compaq 8710p

Quoted 2 lines

Also i just noted that your notebook might contain a PNP0C32 quickstart button device. Can you tell me the output of "cat /sys/bus/acpi/devices/PNP0C32\:00/status"?

15

Interesting.

There have been several attempts to add support for this in the past. The last one being:

https://lore.kernel.org/platform-driver-x86/[email protected]/

Note that in this case this also required some vender specific poking in toshiba_acpi to get things to work.

I see that the HP Compaq 8710p is about the same vintage as the Toshiba Z830 on which the last attempt to do something about the quick start buttons was done.

Quoted 6 lines

So this might very well explain the missing button issue.

Regards,

Hans

I can try to upstream the necessary changes. But i cannot test the changes concerning the toshiba_acpi driver. Would it be ok if i omit those changes?

Dennis, can you check that your device runs the latest BIOS? And if this is not the case, could you do a BIOS update and send me an updated acpidump?

The reason for this is that currently, the button device receives only system wake events, but no button press events during runtime. Maybe this is a BIOS bug, although this could also be intentional (fancy power button).

Armin Wolf

#13 lore raw

Am 23.01.24 um 20:58 schrieb Armin Wolf:

Quoted 141 lines

Am 23.01.24 um 16:34 schrieb Hans de Goede:

Quoted 125 lines

Hi,

Quoted 100 lines · Dennis Nezic
Quoted 99 lines · Armin Wolf

Am 23.01.24 um 09:58 schrieb Armin Wolf:

Quoted 97 lines

Am 23.01.24 um 05:40 schrieb Dennis Nezic:

Quoted 80 lines · Dennis Nezic
Quoted 71 lines · Armin Wolf
Quoted 41 lines

Am 22.01.24 um 08:05 schrieb Dennis Nezic:

Quoted 39 lines · Armin Wolf
Quoted 38 lines

Am 20.01.24 um 22:39 schrieb Dennis Nezic:

Quoted 36 lines · Armin Wolf
Quoted 21 lines

Am 20.01.24 um 19:58 schrieb Dennis Nezic:

Quoted 19 lines

Guys, the "info" illuminated touch-key (hotkey?) on my laptop
"doesn't
work", showkey doesn't report any keycode or scancode. I
don't
see any
wmi related error messages from dmesg. All the other
illuminated
"hotkeys" work fine, although confusingly evtest and
"libinput
debug-events" report that they're coming through the event
interface
associated with "AT Translated Set 2 keyboard" instead of
"HP WMI
hotkeys", but hey, as long as I receive them I'm okay :p.

hp-wmi.c does seem to reference it:

How can I go about troubleshooting this? (I'm using kernel
6.6.8)

Quoted 8 lines

it can be possible that your machine does not use hp-wmi to deliver keycodes
to the operating system, but instead emulates a standard keyboard controller.

Can you check with "kacpimon" that events concerning a PNP0C14 device are being
received?

Very possible indeed. "kacpimon" doesn't show anything when I press that
touchkey, but it does when I press all the other touchkeys. (I do get
lots of accelerometer noise.)

Quoted 6 lines
Quoted 4 lines
Quoted 3 lines

Interesting, can you please share the output of:
- "kacpimon" while you where pressing the buttons
- "acpidump"

...

Those events are touchscreen events, maybe your mouse is responsible for them.

Right, of course, woops, these must have been the touchpad press events,
as I was moving the mouse around :P

Quoted 2 lines

Instead they look like this:

I'm definitely not seeing anything like that, just "^Input Layer:
Type"'s

Quoted 4 lines

Can you try to use kacpimon again but without root privileges? This
way only netlink events show up.
You might also stop acpid while you are using kacpimon.

0 output from/with netlink, even though kacpimon said:

Netlink ACPI Family ID: 24
Netlink ACPI Multicast Group ID: 5
netlink opened successfully

Remember all my other fancy hotkeys "work", but they appear as regular
keypress events from an "AT Translated Set 2 keyboard".

Quoted 8 lines
Quoted 3 lines

If you still cannot receive any netlink events, then i might need to take a look at your ACPI tables
via acpidump.

https://dennisn.mooo.com/stuff/dump.txt

Quoted 2 lines

Thanks,
Armin Wolf

Thank you again sir!

Quoted 8 lines

A1799AC3-9429-4529-927E-DFE13736EEBA has zero instances 8232DE3D-663D-4327-A8F4-E293ADB9BF05 has zero instances 8F1F6436-9F42-42C8-BADC-0E9424F20C9A has zero instances 8F1F6435-9F42-42C8-BADC-0E9424F20C9A has zero instances

(Btw that "info" key does get illuminated when I touch/press it, even
though no codes are seen.)

These warnings in dmesg are harmless, they are informing you that some
WMI devices are unavailable.

I took a look at your ACPI tables and it seems that the WMI device used by hp-wmi is indeed unused.
What is the model name of your HP notebook?

Quoted 7 lines

HP Compaq 8710p

Quoted 4 lines

Also i just noted that your notebook might contain a PNP0C32 quickstart button device.
Can you tell me the output of "cat /sys/bus/acpi/devices/PNP0C32\:00/status"?

15

Interesting.

There have been several attempts to add support for this in the past. The last one being:

https://lore.kernel.org/platform-driver-x86/[email protected]/

Note that in this case this also required some vender specific poking in toshiba_acpi to get things to work.

I see that the HP Compaq 8710p is about the same vintage as the Toshiba Z830 on which the last attempt to do something about the quick start buttons was done.

Quoted 6 lines

So this might very well explain the missing button issue.

Regards,

Hans

I can try to upstream the necessary changes. But i cannot test the changes concerning the toshiba_acpi driver.
Would it be ok if i omit those changes?

Dennis, can you check that your device runs the latest BIOS? And if this is not the case, could you do a BIOS
update and send me an updated acpidump?

Quoted 7 lines

The reason for this is that currently, the button device receives only system wake events, but no button press
events during runtime. Maybe this is a BIOS bug, although this could also be intentional (fancy power button).

Armin Wolf

Hi,

while modifying the quickstart button driver to use the standard pm wake infrastructure, i have run into a little problem: how to properly hook up the platform device with the ACPI device wakeup infrastructure?

Is this possible when using a platform driver, or do i need to use a ACPI driver?

Thanks,
Armin Wolf

#14 lore raw

Hi,

Quoted 148 lines · Armin Wolf

Am 23.01.24 um 20:58 schrieb Armin Wolf:

Quoted 146 lines

Am 23.01.24 um 16:34 schrieb Hans de Goede:

Quoted 125 lines

Hi,

Quoted 100 lines · Dennis Nezic
Quoted 99 lines · Armin Wolf

Am 23.01.24 um 09:58 schrieb Armin Wolf:

Quoted 97 lines

Am 23.01.24 um 05:40 schrieb Dennis Nezic:

Quoted 80 lines · Dennis Nezic
Quoted 71 lines · Armin Wolf
Quoted 41 lines

Am 22.01.24 um 08:05 schrieb Dennis Nezic:

Quoted 39 lines · Armin Wolf
Quoted 38 lines

Am 20.01.24 um 22:39 schrieb Dennis Nezic:

Quoted 36 lines · Armin Wolf
Quoted 29 lines

Am 20.01.24 um 19:58 schrieb Dennis Nezic:

Guys, the "info" illuminated touch-key (hotkey?) on my laptop
"doesn't
work", showkey doesn't report any keycode or scancode. I
don't
see any
wmi related error messages from dmesg. All the other
illuminated
"hotkeys" work fine, although confusingly evtest and
"libinput
debug-events" report that they're coming through the event
interface
associated with "AT Translated Set 2 keyboard" instead of
"HP WMI
hotkeys", but hey, as long as I receive them I'm okay :p.

hp-wmi.c does seem to reference it:

How can I go about troubleshooting this? (I'm using kernel
6.6.8)
it can be possible that your machine does not use hp-wmi to
deliver keycodes
to the operating system, but instead emulates a standard
keyboard controller.

Can you check with "kacpimon" that events concerning a PNP0C14
device are being
received?

Very possible indeed. "kacpimon" doesn't show anything when I press that
touchkey, but it does when I press all the other touchkeys. (I do get
lots of accelerometer noise.)

Quoted 6 lines
Quoted 4 lines
Quoted 3 lines

Interesting, can you please share the output of:
- "kacpimon" while you where pressing the buttons
- "acpidump"

...

Those events are touchscreen events, maybe your mouse is responsible for them.

Right, of course, woops, these must have been the touchpad press events,
as I was moving the mouse around :P

Quoted 2 lines

Instead they look like this:

I'm definitely not seeing anything like that, just "^Input Layer:
Type"'s

Quoted 4 lines

Can you try to use kacpimon again but without root privileges? This
way only netlink events show up.
You might also stop acpid while you are using kacpimon.

0 output from/with netlink, even though kacpimon said:

Netlink ACPI Family ID: 24
Netlink ACPI Multicast Group ID: 5
netlink opened successfully

Remember all my other fancy hotkeys "work", but they appear as regular
keypress events from an "AT Translated Set 2 keyboard".

Quoted 8 lines
Quoted 3 lines

If you still cannot receive any netlink events, then i might need to take a look at your ACPI tables
via acpidump.

https://dennisn.mooo.com/stuff/dump.txt

Quoted 2 lines

Thanks,
Armin Wolf

Thank you again sir!

Quoted 8 lines

A1799AC3-9429-4529-927E-DFE13736EEBA has zero instances 8232DE3D-663D-4327-A8F4-E293ADB9BF05 has zero instances 8F1F6436-9F42-42C8-BADC-0E9424F20C9A has zero instances 8F1F6435-9F42-42C8-BADC-0E9424F20C9A has zero instances

(Btw that "info" key does get illuminated when I touch/press it, even
though no codes are seen.)

These warnings in dmesg are harmless, they are informing you that some
WMI devices are unavailable.

I took a look at your ACPI tables and it seems that the WMI device used by hp-wmi is indeed unused.
What is the model name of your HP notebook?

Quoted 7 lines

HP Compaq 8710p

Quoted 4 lines

Also i just noted that your notebook might contain a PNP0C32 quickstart button device.
Can you tell me the output of "cat /sys/bus/acpi/devices/PNP0C32\:00/status"?

15

Interesting.

There have been several attempts to add support for this in the past. The last one being:

https://lore.kernel.org/platform-driver-x86/[email protected]/

Note that in this case this also required some vender specific poking in toshiba_acpi to get things to work.

I see that the HP Compaq 8710p is about the same vintage as the Toshiba Z830 on which the last attempt to do something about the quick start buttons was done.

Quoted 6 lines

So this might very well explain the missing button issue.

Regards,

Hans

I can try to upstream the necessary changes. But i cannot test the changes concerning the toshiba_acpi driver.
Would it be ok if i omit those changes?

Dennis, can you check that your device runs the latest BIOS? And if this is not the case, could you do a BIOS
update and send me an updated acpidump?

The reason for this is that currently, the button device receives only system wake events, but no button press
events during runtime. Maybe this is a BIOS bug, although this could also be intentional (fancy power button).

Quoted 8 lines
Quoted 2 lines

Armin Wolf

Hi,

while modifying the quickstart button driver to use the standard pm wake infrastructure, i have run into a little problem: how to properly hook up the platform device with the ACPI device wakeup infrastructure?

Is this possible when using a platform driver, or do i need to use a ACPI driver?

I'm not sure what exactly you are looking for but I think the powerbutton handling in: drivers/platform/x86/intel/hid.c (search for wakeup) may help ?

If that does not help can you point me to the lines of code in the old version of the code which you are trying to adjust ?

Regards,

Hans

Quoted 4 lines

Thanks,
Armin Wolf

#15 lore raw
In reply to Armin Wolf

Hi Armin,

Quoted 115 lines · Armin Wolf

Am 23.01.24 um 16:34 schrieb Hans de Goede:

Quoted 113 lines

Hi,

Quoted 88 lines · Dennis Nezic
Quoted 87 lines · Armin Wolf

Am 23.01.24 um 09:58 schrieb Armin Wolf:

Quoted 85 lines

Am 23.01.24 um 05:40 schrieb Dennis Nezic:

Quoted 72 lines · Dennis Nezic
Quoted 71 lines · Armin Wolf
Quoted 36 lines

Am 22.01.24 um 08:05 schrieb Dennis Nezic:

Quoted 34 lines · Armin Wolf
Quoted 33 lines

Am 20.01.24 um 22:39 schrieb Dennis Nezic:

Quoted 31 lines · Armin Wolf
Quoted 16 lines

Am 20.01.24 um 19:58 schrieb Dennis Nezic:

Quoted 14 lines

Guys, the "info" illuminated touch-key (hotkey?) on my laptop
"doesn't
work", showkey doesn't report any keycode or scancode. I don't
see any
wmi related error messages from dmesg. All the other illuminated
"hotkeys" work fine, although confusingly evtest and "libinput
debug-events" report that they're coming through the event
interface
associated with "AT Translated Set 2 keyboard" instead of "HP WMI
hotkeys", but hey, as long as I receive them I'm okay :p.

hp-wmi.c does seem to reference it:

How can I go about troubleshooting this? (I'm using kernel 6.6.8)

Quoted 8 lines

it can be possible that your machine does not use hp-wmi to deliver keycodes
to the operating system, but instead emulates a standard keyboard controller.

Can you check with "kacpimon" that events concerning a PNP0C14 device are being
received?

Very possible indeed. "kacpimon" doesn't show anything when I press that
touchkey, but it does when I press all the other touchkeys. (I do get
lots of accelerometer noise.)

Quoted 6 lines
Quoted 4 lines
Quoted 3 lines

Interesting, can you please share the output of:
- "kacpimon" while you where pressing the buttons
- "acpidump"

...

Those events are touchscreen events, maybe your mouse is responsible for them.

Right, of course, woops, these must have been the touchpad press events,
as I was moving the mouse around :P

Quoted 2 lines

Instead they look like this:

I'm definitely not seeing anything like that, just "^Input Layer:
Type"'s

Quoted 3 lines

Can you try to use kacpimon again but without root privileges? This way only netlink events show up.
You might also stop acpid while you are using kacpimon.

0 output from/with netlink, even though kacpimon said:

Netlink ACPI Family ID: 24
Netlink ACPI Multicast Group ID: 5
netlink opened successfully

Remember all my other fancy hotkeys "work", but they appear as regular keypress events from an "AT Translated Set 2 keyboard".

Quoted 3 lines

If you still cannot receive any netlink events, then i might need to take a look at your ACPI tables
via acpidump.

https://dennisn.mooo.com/stuff/dump.txt

Quoted 2 lines

Thanks,
Armin Wolf

Quoted 8 lines
Quoted 1 line

Thank you again sir!

A1799AC3-9429-4529-927E-DFE13736EEBA has zero instances 8232DE3D-663D-4327-A8F4-E293ADB9BF05 has zero instances 8F1F6436-9F42-42C8-BADC-0E9424F20C9A has zero instances 8F1F6435-9F42-42C8-BADC-0E9424F20C9A has zero instances

(Btw that "info" key does get illuminated when I touch/press it, even though no codes are seen.)

These warnings in dmesg are harmless, they are informing you that some WMI devices are unavailable.

Quoted 8 lines
Quoted 3 lines
Quoted 3 lines

I took a look at your ACPI tables and it seems that the WMI device used by hp-wmi is indeed unused.
What is the model name of your HP notebook?

HP Compaq 8710p

Quoted 2 lines

Also i just noted that your notebook might contain a PNP0C32 quickstart button device. Can you tell me the output of "cat /sys/bus/acpi/devices/PNP0C32\:00/status"?

15

Interesting.

There have been several attempts to add support for this in the past. The last one being:

https://lore.kernel.org/platform-driver-x86/[email protected]/

Note that in this case this also required some vender specific poking in toshiba_acpi to get things to work.

I see that the HP Compaq 8710p is about the same vintage as the Toshiba Z830 on which the last attempt to do something about the quick start buttons was done.

Quoted 7 lines
Quoted 6 lines

So this might very well explain the missing button issue.

Regards,

Hans

I can try to upstream the necessary changes.

If you can work on this that would be great.

Quoted 1 line

But i cannot test the changes concerning the toshiba_acpi driver.

I think that just compile testing them is fine.

Quoted 1 line

Would it be ok if i omit those changes?

I have a slight preference for keeping the Toshiba changes.

As discussed below these "quick start" buttons normally are only intended to wake up the laptop and then immediately on wakeup start a specific app tied to the button (IIRC). But at least on the Toshiba the toshiba_acpi driver's special "poke" of the firmware makes the button also send events normally, so that it can actually be used as a normal button.

IMHO the Toshiba code is helpful in documenting the need for such a special code (maybe extend it with a comment?).

With all that said if you don't want to submit the Toshiba part compile-tested only, then I understand and you can omit it.

Quoted 5 lines

Dennis, can you check that your device runs the latest BIOS? And if this is not the case, could you do a BIOS update and send me an updated acpidump?

The reason for this is that currently, the button device receives only system wake events, but no button press events during runtime. Maybe this is a BIOS bug, although this could also be intentional (fancy power button).

See above IIRC what was discussed last time this is an intentional (mis)feature of these buttons. Chances are there might be some workaround for this for HP too, but that will likely be tricky to find.

Regards,

Hans

#16 lore raw
Quoted 35 lines
Quoted 29 lines
Quoted 8 lines
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines

Remember all my other fancy hotkeys "work", but they appear as regular keypress events from an "AT Translated Set 2 keyboard".

Quoted 3 lines

If you still cannot receive any netlink events, then i might need to take a look at your ACPI tables
via acpidump.

https://dennisn.mooo.com/stuff/dump.txt

Quoted 8 lines
Quoted 3 lines
Quoted 3 lines

I took a look at your ACPI tables and it seems that the WMI device used by hp-wmi is indeed unused.
What is the model name of your HP notebook?

HP Compaq 8710p

Quoted 2 lines

Also i just noted that your notebook might contain a PNP0C32 quickstart button device. Can you tell me the output of "cat /sys/bus/acpi/devices/PNP0C32\:00/status"?

15

Interesting.

There have been several attempts to add support for this in the past. The last one being:
https://lore.kernel.org/platform-driver-x86/[email protected]/

Note that in this case this also required some vender specific poking in toshiba_acpi to get things to work.

I see that the HP Compaq 8710p is about the same vintage as the Toshiba Z830 on which the last attempt to do something about the quick start buttons was done.

Quoted 5 lines

So this might very well explain the missing button issue.

Regards,

Hans

Quoted 7 lines

As discussed below these "quick start" buttons normally are only intended to wake up the laptop and then immediately on wakeup start a specific app tied to the button (IIRC). But at least on the Toshiba the toshiba_acpi driver's special "poke" of the firmware makes the button also send events normally, so that it can actually be used as a normal button.

Can someone roughly explain what's going on? :p On my HP Compaq laptop all those "buttons" work, except that one "info" one. How are those keys being emulated(?) as my regular keyboard? Why would only one not work?

Quoted 14 lines
Quoted 6 lines

Dennis, can you check that your device runs the latest BIOS? And if this is not the case, could you do a BIOS update and send me an updated acpidump? The reason for this is that currently, the button device receives only system wake events, but no button press events during runtime. Maybe this is a BIOS bug, although this could also be intentional (fancy power button).

See above IIRC what was discussed last time this is an intentional (mis)feature of these buttons. Chances are there might be some workaround for this for HP too, but that will likely be tricky to find.

Regards,

Hans

#17 lore raw
In reply to Armin Wolf
Quoted 121 lines · Armin Wolf

Am 23.01.24 um 16:34 schrieb Hans de Goede:

Quoted 113 lines

Hi,

Quoted 88 lines · Dennis Nezic
Quoted 87 lines · Armin Wolf

Am 23.01.24 um 09:58 schrieb Armin Wolf:

Quoted 85 lines

Am 23.01.24 um 05:40 schrieb Dennis Nezic:

Quoted 72 lines · Dennis Nezic
Quoted 71 lines · Armin Wolf
Quoted 36 lines

Am 22.01.24 um 08:05 schrieb Dennis Nezic:

Quoted 34 lines · Armin Wolf
Quoted 33 lines

Am 20.01.24 um 22:39 schrieb Dennis Nezic:

Quoted 31 lines · Armin Wolf
Quoted 16 lines

Am 20.01.24 um 19:58 schrieb Dennis Nezic:

Quoted 14 lines

Guys, the "info" illuminated touch-key (hotkey?) on my laptop
"doesn't
work", showkey doesn't report any keycode or scancode. I don't
see any
wmi related error messages from dmesg. All the other illuminated
"hotkeys" work fine, although confusingly evtest and "libinput
debug-events" report that they're coming through the event
interface
associated with "AT Translated Set 2 keyboard" instead of "HP WMI
hotkeys", but hey, as long as I receive them I'm okay :p.

hp-wmi.c does seem to reference it:

How can I go about troubleshooting this? (I'm using kernel 6.6.8)

Quoted 8 lines

it can be possible that your machine does not use hp-wmi to deliver keycodes
to the operating system, but instead emulates a standard keyboard controller.

Can you check with "kacpimon" that events concerning a PNP0C14 device are being
received?

Very possible indeed. "kacpimon" doesn't show anything when I press that
touchkey, but it does when I press all the other touchkeys. (I do get
lots of accelerometer noise.)

Quoted 6 lines
Quoted 4 lines
Quoted 3 lines

Interesting, can you please share the output of:
- "kacpimon" while you where pressing the buttons
- "acpidump"

...

Those events are touchscreen events, maybe your mouse is responsible for them.

Right, of course, woops, these must have been the touchpad press events,
as I was moving the mouse around :P

Quoted 2 lines

Instead they look like this:

I'm definitely not seeing anything like that, just "^Input Layer:
Type"'s

Quoted 3 lines

Can you try to use kacpimon again but without root privileges? This way only netlink events show up.
You might also stop acpid while you are using kacpimon.

0 output from/with netlink, even though kacpimon said:

Netlink ACPI Family ID: 24
Netlink ACPI Multicast Group ID: 5
netlink opened successfully

Remember all my other fancy hotkeys "work", but they appear as regular keypress events from an "AT Translated Set 2 keyboard".

Quoted 3 lines

If you still cannot receive any netlink events, then i might need to take a look at your ACPI tables
via acpidump.

https://dennisn.mooo.com/stuff/dump.txt

Quoted 2 lines

Thanks,
Armin Wolf

Quoted 8 lines
Quoted 1 line

Thank you again sir!

A1799AC3-9429-4529-927E-DFE13736EEBA has zero instances 8232DE3D-663D-4327-A8F4-E293ADB9BF05 has zero instances 8F1F6436-9F42-42C8-BADC-0E9424F20C9A has zero instances 8F1F6435-9F42-42C8-BADC-0E9424F20C9A has zero instances

(Btw that "info" key does get illuminated when I touch/press it, even though no codes are seen.)

These warnings in dmesg are harmless, they are informing you that some WMI devices are unavailable.

Quoted 8 lines
Quoted 3 lines
Quoted 3 lines

I took a look at your ACPI tables and it seems that the WMI device used by hp-wmi is indeed unused.
What is the model name of your HP notebook?

HP Compaq 8710p

Quoted 2 lines

Also i just noted that your notebook might contain a PNP0C32 quickstart button device. Can you tell me the output of "cat /sys/bus/acpi/devices/PNP0C32\:00/status"?

15

Interesting.

There have been several attempts to add support for this in the past. The last one being:

https://lore.kernel.org/platform-driver-x86/[email protected]/

Note that in this case this also required some vender specific poking in toshiba_acpi to get things to work.

I see that the HP Compaq 8710p is about the same vintage as the Toshiba Z830 on which the last attempt to do something about the quick start buttons was done.

Quoted 6 lines

So this might very well explain the missing button issue.

Regards,

Hans

Quoted 8 lines

I can try to upstream the necessary changes. But i cannot test the changes concerning the toshiba_acpi driver. Would it be ok if i omit those changes?

Dennis, can you check that your device runs the latest BIOS? And if this is not the case, could you do a BIOS update and send me an updated acpidump?

The reason for this is that currently, the button device receives only system wake events, but no button press events during runtime. Maybe this is a BIOS bug, although this could also be intentional (fancy power button).

I was /finally/ able to update my BIOS slightly, only with the latest freedos image available, one version up ... there seems to be another newer (2011) windows-only one that I'm not able to use.

No change.

Why do all the other "quick start" buttons work - I see their key press events, albeit not through hp-wmi?

#18 lore raw
Quoted 9 lines
Quoted 8 lines

Dennis, can you check that your device runs the latest BIOS? And if this is not the case, could you do a BIOS update and send me an updated acpidump?

The reason for this is that currently, the button device receives only system wake events, but no button press events during runtime. Maybe this is a BIOS bug, although this could also be intentional (fancy power button).

Quoted 5 lines

I was /finally/ able to update my BIOS slightly, only with the latest freedos image available, one version up ... there seems to be another newer (2011) windows-only one that I'm not able to use.

No change.

(I "hacked" the "latest" 2011 bios rom in, and although it reports being a newer version and newer release date, acpidump is exactly the same. dmidecode says it's the newer one though. No difference.)

#19 lore raw
In reply to Armin Wolf
Quoted 121 lines · Armin Wolf

Am 23.01.24 um 16:34 schrieb Hans de Goede:

Quoted 113 lines

Hi,

Quoted 88 lines · Dennis Nezic
Quoted 87 lines · Armin Wolf

Am 23.01.24 um 09:58 schrieb Armin Wolf:

Quoted 85 lines

Am 23.01.24 um 05:40 schrieb Dennis Nezic:

Quoted 72 lines · Dennis Nezic
Quoted 71 lines · Armin Wolf
Quoted 36 lines

Am 22.01.24 um 08:05 schrieb Dennis Nezic:

Quoted 34 lines · Armin Wolf
Quoted 33 lines

Am 20.01.24 um 22:39 schrieb Dennis Nezic:

Quoted 31 lines · Armin Wolf
Quoted 16 lines

Am 20.01.24 um 19:58 schrieb Dennis Nezic:

Quoted 14 lines

Guys, the "info" illuminated touch-key (hotkey?) on my laptop
"doesn't
work", showkey doesn't report any keycode or scancode. I don't
see any
wmi related error messages from dmesg. All the other illuminated
"hotkeys" work fine, although confusingly evtest and "libinput
debug-events" report that they're coming through the event
interface
associated with "AT Translated Set 2 keyboard" instead of "HP WMI
hotkeys", but hey, as long as I receive them I'm okay :p.

hp-wmi.c does seem to reference it:

How can I go about troubleshooting this? (I'm using kernel 6.6.8)

Quoted 8 lines

it can be possible that your machine does not use hp-wmi to deliver keycodes
to the operating system, but instead emulates a standard keyboard controller.

Can you check with "kacpimon" that events concerning a PNP0C14 device are being
received?

Very possible indeed. "kacpimon" doesn't show anything when I press that
touchkey, but it does when I press all the other touchkeys. (I do get
lots of accelerometer noise.)

Quoted 6 lines
Quoted 4 lines
Quoted 3 lines

Interesting, can you please share the output of:
- "kacpimon" while you where pressing the buttons
- "acpidump"

...

Those events are touchscreen events, maybe your mouse is responsible for them.

Right, of course, woops, these must have been the touchpad press events,
as I was moving the mouse around :P

Quoted 2 lines

Instead they look like this:

I'm definitely not seeing anything like that, just "^Input Layer:
Type"'s

Quoted 3 lines

Can you try to use kacpimon again but without root privileges? This way only netlink events show up.
You might also stop acpid while you are using kacpimon.

0 output from/with netlink, even though kacpimon said:

Netlink ACPI Family ID: 24
Netlink ACPI Multicast Group ID: 5
netlink opened successfully

Remember all my other fancy hotkeys "work", but they appear as regular keypress events from an "AT Translated Set 2 keyboard".

Quoted 3 lines

If you still cannot receive any netlink events, then i might need to take a look at your ACPI tables
via acpidump.

https://dennisn.mooo.com/stuff/dump.txt

Quoted 2 lines

Thanks,
Armin Wolf

Quoted 8 lines
Quoted 1 line

Thank you again sir!

A1799AC3-9429-4529-927E-DFE13736EEBA has zero instances 8232DE3D-663D-4327-A8F4-E293ADB9BF05 has zero instances 8F1F6436-9F42-42C8-BADC-0E9424F20C9A has zero instances 8F1F6435-9F42-42C8-BADC-0E9424F20C9A has zero instances

(Btw that "info" key does get illuminated when I touch/press it, even though no codes are seen.)

These warnings in dmesg are harmless, they are informing you that some WMI devices are unavailable.

Quoted 8 lines
Quoted 3 lines
Quoted 3 lines

I took a look at your ACPI tables and it seems that the WMI device used by hp-wmi is indeed unused.
What is the model name of your HP notebook?

HP Compaq 8710p

Quoted 2 lines

Also i just noted that your notebook might contain a PNP0C32 quickstart button device. Can you tell me the output of "cat /sys/bus/acpi/devices/PNP0C32\:00/status"?

15

Interesting.

There have been several attempts to add support for this in the past. The last one being:

https://lore.kernel.org/platform-driver-x86/[email protected]/

Note that in this case this also required some vender specific poking in toshiba_acpi to get things to work.

I see that the HP Compaq 8710p is about the same vintage as the Toshiba Z830 on which the last attempt to do something about the quick start buttons was done.

Quoted 6 lines

So this might very well explain the missing button issue.

Regards,

Hans

Quoted 8 lines

I can try to upstream the necessary changes. But i cannot test the changes concerning the toshiba_acpi driver. Would it be ok if i omit those changes?

Dennis, can you check that your device runs the latest BIOS? And if this is not the case, could you do a BIOS update and send me an updated acpidump?

The reason for this is that currently, the button device receives only system wake events, but no button press events during runtime. Maybe this is a BIOS bug, although this could also be intentional (fancy power button).

Updated acpidump: https://dennisn.mooo.com/stuff/dump2.txt.gz