From: "Dennis Nezic" <dennisn@dennisn.mooo.com>
To: Armin Wolf <W_Armin@gmx.de>
Cc: platform-driver-x86@vger.kernel.org
Subject: Re: hp-wmi: info hotkey has no keycode or scancode
Date: Mon, 22 Jan 2024 02:05:53 -0500 [thread overview]
Message-ID: <Za4T0RwClHOoCPCy@panther> (raw)
In-Reply-To: <e97ae805-d006-4f0c-96c0-976385772bb7@gmx.de>
On 21 Jan 16:16, Armin Wolf wrote:
> Am 20.01.24 um 22:39 schrieb Dennis Nezic:
>
> > On 20 Jan 21:52, Armin Wolf wrote:
> >> 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:
> >>> { 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?
> > 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?)
next prev parent reply other threads:[~2024-01-22 7:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-20 18:58 hp-wmi: info hotkey has no keycode or scancode Dennis Nezic
2024-01-20 20:52 ` Armin Wolf
2024-01-20 21:39 ` Dennis Nezic
2024-01-21 15:16 ` Armin Wolf
2024-01-22 7:05 ` Dennis Nezic [this message]
2024-01-22 10:44 ` Armin Wolf
[not found] ` <Za8xL39m1X22f2Bb@panther>
[not found] ` <Za9DQdLg2d_CnrZG@panther>
2024-01-23 8:58 ` Armin Wolf
2024-01-23 14:22 ` Armin Wolf
2024-01-23 15:13 ` Dennis Nezic
2024-01-23 15:34 ` Hans de Goede
2024-01-23 19:58 ` Armin Wolf
2024-01-25 20:53 ` Armin Wolf
2024-01-29 13:00 ` Hans de Goede
2024-01-29 12:57 ` Hans de Goede
2024-03-26 16:47 ` Dennis Nezic
2024-01-30 18:18 ` Dennis Nezic
2024-01-31 4:06 ` Dennis Nezic
2024-01-30 20:20 ` Dennis Nezic
-- strict thread matches above, loose matches on Subject: below --
2024-01-31 4:01 Dennis Nezic
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Za4T0RwClHOoCPCy@panther \
--to=dennisn@dennisn.mooo.com \
--cc=W_Armin@gmx.de \
--cc=platform-driver-x86@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.