From: "Dennis Nezic" <dennisn@dennisn.mooo.com>
To: Armin Wolf <W_Armin@gmx.de>
Cc: Hans de Goede <hdegoede@redhat.com>, platform-driver-x86@vger.kernel.org
Subject: Re: hp-wmi: info hotkey has no keycode or scancode
Date: Tue, 30 Jan 2024 13:18:36 -0500 [thread overview]
Message-ID: <Zbk9fAMf_70EfLA3@panther> (raw)
In-Reply-To: <57df06ee-3aa1-4501-9dc6-a7bc57d770be@gmx.de>
On 23 Jan 20:58, Armin Wolf wrote:
> Am 23.01.24 um 16:34 schrieb Hans de Goede:
>
> > Hi,
> >
> > On 1/23/24 16:13, Dennis Nezic wrote:
> >> On 23 Jan 15:22, Armin Wolf wrote:
> >>> Am 23.01.24 um 09:58 schrieb Armin Wolf:
> >>>
> >>>> Am 23.01.24 um 05:40 schrieb Dennis Nezic:
> >>>>
> >>>>> On 22 Jan 22:23, Dennis Nezic wrote:
> >>>>>> On 22 Jan 11:44, Armin Wolf wrote:
> >>>>>>> Am 22.01.24 um 08:05 schrieb Dennis Nezic:
> >>>>>>>
> >>>>>>>> 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:
> >>>>>>>>>>>>
> >>>>>>>>>>>> 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"
> >>>>>>>> ...
> >>>>>>> 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
> >>>>>>
> >>>>>>> Instead they look like this:
> >>>>>>>
> >>>>>> I'm definitely not seeing anything like that, just "^Input Layer:
> >>>>>> Type"'s
> >>>>>>
> >>>>>>> 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".
> >>>>>>
> >>>>>>> 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
> >>>>>>
> >>>>>>> Thanks,
> >>>>>>> Armin Wolf
> >>>>>> 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.
> >>>>
> >>>> 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
> >>
> >>> 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/20220922182424.934340-1-lkml@vorpal.se/
> >
> > 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
> >
> 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?
next prev parent reply other threads:[~2024-01-30 18:18 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
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 [this message]
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=Zbk9fAMf_70EfLA3@panther \
--to=dennisn@dennisn.mooo.com \
--cc=W_Armin@gmx.de \
--cc=hdegoede@redhat.com \
--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.