Re: [hp_wmi] Recieving same keycode from two keys

Re: [hp_wmi] Recieving same keycode from two keys

[Rhys Perry]

On Fri, 3 Jul 2020 at 23:22, <rhysperry111@gmail.com> wrote:
>
> Hi,
>
> I would just like to preface this by saying that I am no too familiar
> with mailing list etiquette so I am sorry if I break any rules.
>
> I have a laptop with dedicated brighness keys (HP Pavilion
> 15-cx0598na). I believe these keys are handled by hp_wmi.
>
> Whenever I press (and release) one of the brightness keys, this message
> appears in the journal:
> ```
> [50761.461630] atkbd serio0: Unknown key pressed (translated set 2,
> code 0xab on isa0060/serio0).
> [50761.461637] atkbd serio0: Use 'setkeycodes e02b <keycode>' to make
> it known.
> [50761.492161] atkbd serio0: Unknown key released (translated set 2,
> code 0xab on isa0060/serio0).
> [50761.492168] atkbd serio0: Use 'setkeycodes e02b <keycode>' to make
> it known.
> ```
> Now, this is not that interesting at first, I obviously just need to
> map a keycode. The confusing part is that for both the brightness up
> AND the brightness down key I get the same code (e02b). I am not to
> sure how to debug this behavior but I would appreciate if someone
> helped investigate this issue.
>
> I am not sure if this is relevant, but my RFKILL key does not work
> either (but does not show anything in journal).
>
> Here is a link to acpidump:
> https://www.dropbox.com/s/ulyltq0gz35s79l/acpidump?dl=0
>
> ::: Rhys Perry :::

Sorry if this is breaking kernel mailing list etiquette, but I am
posting this question again as I did not get a response last time.

Re: [hp_wmi] Recieving same keycode from two keys

[Barnabás Pőcze]

Hi

> [...]
> > I have a laptop with dedicated brighness keys (HP Pavilion
> > 15-cx0598na). I believe these keys are handled by hp_wmi.
> >
> > Whenever I press (and release) one of the brightness keys, this message
> > appears in the journal:
> > ```
> > [50761.461630] atkbd serio0: Unknown key pressed (translated set 2,
> > code 0xab on isa0060/serio0).
> > [50761.461637] atkbd serio0: Use 'setkeycodes e02b <keycode>' to make
> > it known.
> > [50761.492161] atkbd serio0: Unknown key released (translated set 2,
> > code 0xab on isa0060/serio0).
> > [50761.492168] atkbd serio0: Use 'setkeycodes e02b <keycode>' to make
> > it known.
> > ```

Can you see any messages generated by the hp-wmi driver when these key presses occur?


> > Now, this is not that interesting at first, I obviously just need to
> > map a keycode. The confusing part is that for both the brightness up
> > AND the brightness down key I get the same code (e02b). I am not to
> > sure how to debug this behavior but I would appreciate if someone
> > helped investigate this issue.
> >
> > I am not sure if this is relevant, but my RFKILL key does not work
> > either (but does not show anything in journal).
> >

Could you please run `evtest` and see if you have a "HP WMI hotkeys" input device?
If so, please select it, and then press the function keys and see if any events appear.

Furthermore, you could install `acpid`, start it (something along the lines of
`sudo systemctl start acpid`), then run `acpi_listen` and see if you get anything
when you press the keys.


> > Here is a link to acpidump:
> > https://www.dropbox.com/s/ulyltq0gz35s79l/acpidump?dl=0
> >
> > ::: Rhys Perry :::
>
> Sorry if this is breaking kernel mailing list etiquette, but I am
> posting this question again as I did not get a response last time.
>


Regards,
Barnabás Pőcze

Re: [hp_wmi] Recieving same keycode from two keys

[Barnabás Pőcze]

(please use reply-all so that the mailing list gets the emails as well)


> > [...]
> > > > Can you see any messages generated by the hp-wmi driver when these key presses occur?
> > >
> > > Not that I know of, unless there is some sort of debug mode that can be enabled
> > >
> > > > > > Now, this is not that interesting at first, I obviously just need to
> > > > > > map a keycode. The confusing part is that for both the brightness up
> > > > > > AND the brightness down key I get the same code (e02b). I am not to
> > > > > > sure how to debug this behavior but I would appreciate if someone
> > > > > > helped investigate this issue.
> > > > > > I am not sure if this is relevant, but my RFKILL key does not work
> > > > > > either (but does not show anything in journal).
> > > >
> > > > Could you please run `evtest` and see if you have a "HP WMI hotkeys" input device?
> > > > If so, please select it, and then press the function keys and see if any events appear.
> > >
> > > After running`evtest` there is a device called "HP WMI hotkeys" (on
> > > /dev/input/event16). However, after selecting it and pressing the
> > > brightness keys no events appear.
> > >
> > > > Furthermore, you could install `acpid`, start it (something along the lines of
> > > > `sudo systemctl start acpid`), then run `acpi_listen` and see if you get anything
> > > > when you press the keys.
> > >
> > > After starting the service and running`acpi_listen`, no events appear
> > > when pressing the brightness keys
> > >
> > > > > > Here is a link to acpidump:
> > > > > > https://www.dropbox.com/s/ulyltq0gz35s79l/acpidump?dl=0
> > > > > > ::: Rhys Perry :::
> > > [...]
> >
> > Could you test other function keys like volume up/down, etc.?
> >
> After running some tests with evtest I have found out:
> - Brightness keys: "AT Translated Set 2 keyboard" (although same keycode)
> - Volume keys: "AT Translated Set 2 keyboard"
> - Media keys: "AT Translated Set 2 keyboard"
> - RFKILL key: (none, although there is a device called "HP Wireless hotkeys")

Please install the `evemu` program suite, and run `evemu-record /dev/input/event...`
for the AT keyboard, HP WMI hotkeys, and HP Wireless hotkeys; in each run press the
brightness up/down, volume up/down keys in any fixed order you like, and then send
the output of each run (including the part that is initially printed before
receiving any events). Could you also run `acpi_listen` at the same time and
see if any key presses are registered there? If yes, what was the output?

Just to summarize (please correct me if I'm wrong):
- brightness up/down keys
  * send the same scan code via the keyboard; and
  * do not trigger any ACPI events
- volume up/down, and media keys send unique key codes via the keyboard and they work (?)
- the rfkill hotkey does not appear to generate any events whatsoever (?)
- the "HP WMI hotkeys" and "HP Wireless hotkeys" input devices don't register
  any events

By the way, I suppose that screen brightness control with hotkeys does not work,
correct?


> I wonder what the point of the HP WMI or Wireless devices are if they
> are not receiving any events.

I can only assume that they do work in some circumstances/with older models/etc.


> In the past I have done some
> experimenting with the ACPI_OSI kernel parameter and IIRC I did not
> get anything to change. This poses the question, how does Windows know
> the difference between brightness up/down?
> [...]


Regards,
Barnabás Pőcze

Re: [hp_wmi] Recieving same keycode from two keys

[Rhys Perry]

>
> (please use reply-all so that the mailing list gets the emails as well)
>

Oh, my mistake. I didn't actually know the difference between the two.
Sorry for any confusion this might cause in the future.

>
> > > [...]
> > > > > Can you see any messages generated by the hp-wmi driver when these key presses occur?
> > > >
> > > > Not that I know of, unless there is some sort of debug mode that can be enabled
> > > >
> > > > > > > Now, this is not that interesting at first, I obviously just need to
> > > > > > > map a keycode. The confusing part is that for both the brightness up
> > > > > > > AND the brightness down key I get the same code (e02b). I am not to
> > > > > > > sure how to debug this behavior but I would appreciate if someone
> > > > > > > helped investigate this issue.
> > > > > > > I am not sure if this is relevant, but my RFKILL key does not work
> > > > > > > either (but does not show anything in journal).
> > > > >
> > > > > Could you please run `evtest` and see if you have a "HP WMI hotkeys" input device?
> > > > > If so, please select it, and then press the function keys and see if any events appear.
> > > >
> > > > After running`evtest` there is a device called "HP WMI hotkeys" (on
> > > > /dev/input/event16). However, after selecting it and pressing the
> > > > brightness keys no events appear.
> > > >
> > > > > Furthermore, you could install `acpid`, start it (something along the lines of
> > > > > `sudo systemctl start acpid`), then run `acpi_listen` and see if you get anything
> > > > > when you press the keys.
> > > >
> > > > After starting the service and running`acpi_listen`, no events appear
> > > > when pressing the brightness keys
> > > >
> > > > > > > Here is a link to acpidump:
> > > > > > > https://www.dropbox.com/s/ulyltq0gz35s79l/acpidump?dl=0
> > > > > > > ::: Rhys Perry :::
> > > > [...]
> > >
> > > Could you test other function keys like volume up/down, etc.?
> > >
> > After running some tests with evtest I have found out:
> > - Brightness keys: "AT Translated Set 2 keyboard" (although same keycode)
> > - Volume keys: "AT Translated Set 2 keyboard"
> > - Media keys: "AT Translated Set 2 keyboard"
> > - RFKILL key: (none, although there is a device called "HP Wireless hotkeys")
>
> Please install the `evemu` program suite, and run `evemu-record /dev/input/event...`
> for the AT keyboard, HP WMI hotkeys, and HP Wireless hotkeys; in each run press the
> brightness up/down, volume up/down keys in any fixed order you like, and then send
> the output of each run (including the part that is initially printed before
> receiving any events). Could you also run `acpi_listen` at the same time and
> see if any key presses are registered there? If yes, what was the output?
>

Ok, here you go:
"AT Translated Set 2 Keyboard": https://0x0.st/idpK.txt
"HP Wireless hotkeys": https://0x0.st/idpP.txt
"HP WMI hotkeys": https://0x0.st/idpN.txt
`acpi_listen`: https://0x0.st/idpb.txt

> Just to summarize (please correct me if I'm wrong):
> - brightness up/down keys
>   * send the same scan code via the keyboard; and
>   * do not trigger any ACPI events

Yep, that is what I get

> - volume up/down, and media keys send unique key codes via the keyboard and they work (?)

Yes, they work as intended

> - the rfkill hotkey does not appear to generate any events whatsoever (?)
> - the "HP WMI hotkeys" and "HP Wireless hotkeys" input devices don't register
>   any events

Yes, that is the case

>
> By the way, I suppose that screen brightness control with hotkeys does not work,
> correct?
>

Yes

>
> > I wonder what the point of the HP WMI or Wireless devices are if they
> > are not receiving any events.
>
> I can only assume that they do work in some circumstances/with older models/etc.
>
>
> [...]

Thanks for all the help,
Rhys Perry

Re: [hp_wmi] Recieving same keycode from two keys

[Hans de Goede]

Hi,

On 11/3/20 2:35 PM, Rhys Perry wrote:
>>
>> (please use reply-all so that the mailing list gets the emails as well)
>>
> 
> Oh, my mistake. I didn't actually know the difference between the two.
> Sorry for any confusion this might cause in the future.
> 
>>
>>>> [...]
>>>>>> Can you see any messages generated by the hp-wmi driver when these key presses occur?
>>>>>
>>>>> Not that I know of, unless there is some sort of debug mode that can be enabled
>>>>>
>>>>>>>> Now, this is not that interesting at first, I obviously just need to
>>>>>>>> map a keycode. The confusing part is that for both the brightness up
>>>>>>>> AND the brightness down key I get the same code (e02b). I am not to
>>>>>>>> sure how to debug this behavior but I would appreciate if someone
>>>>>>>> helped investigate this issue.
>>>>>>>> I am not sure if this is relevant, but my RFKILL key does not work
>>>>>>>> either (but does not show anything in journal).
>>>>>>
>>>>>> Could you please run `evtest` and see if you have a "HP WMI hotkeys" input device?
>>>>>> If so, please select it, and then press the function keys and see if any events appear.
>>>>>
>>>>> After running`evtest` there is a device called "HP WMI hotkeys" (on
>>>>> /dev/input/event16). However, after selecting it and pressing the
>>>>> brightness keys no events appear.
>>>>>
>>>>>> Furthermore, you could install `acpid`, start it (something along the lines of
>>>>>> `sudo systemctl start acpid`), then run `acpi_listen` and see if you get anything
>>>>>> when you press the keys.
>>>>>
>>>>> After starting the service and running`acpi_listen`, no events appear
>>>>> when pressing the brightness keys
>>>>>
>>>>>>>> Here is a link to acpidump:
>>>>>>>> https://www.dropbox.com/s/ulyltq0gz35s79l/acpidump?dl=0
>>>>>>>> ::: Rhys Perry :::
>>>>> [...]
>>>>
>>>> Could you test other function keys like volume up/down, etc.?
>>>>
>>> After running some tests with evtest I have found out:
>>> - Brightness keys: "AT Translated Set 2 keyboard" (although same keycode)
>>> - Volume keys: "AT Translated Set 2 keyboard"
>>> - Media keys: "AT Translated Set 2 keyboard"
>>> - RFKILL key: (none, although there is a device called "HP Wireless hotkeys")
>>
>> Please install the `evemu` program suite, and run `evemu-record /dev/input/event...`
>> for the AT keyboard, HP WMI hotkeys, and HP Wireless hotkeys; in each run press the
>> brightness up/down, volume up/down keys in any fixed order you like, and then send
>> the output of each run (including the part that is initially printed before
>> receiving any events). Could you also run `acpi_listen` at the same time and
>> see if any key presses are registered there? If yes, what was the output?
>>
> 
> Ok, here you go:
> "AT Translated Set 2 Keyboard": https://0x0.st/idpK.txt
> "HP Wireless hotkeys": https://0x0.st/idpP.txt
> "HP WMI hotkeys": https://0x0.st/idpN.txt
> `acpi_listen`: https://0x0.st/idpb.txt

Can you also run evemu-record for the "Video Bus"
input device and check if you get events there for the
brightness up/down key presses?  On modern laptops events
for the brightness keys are typically delivered there.

Also are you perhaps using the nvidia binary driver for
your GPU ?

Regards,

Hans

Re: [hp_wmi] Recieving same keycode from two keys

[Rhys Perry]

On Tue, 3 Nov 2020 at 14:16, Hans de Goede <hdegoede@redhat.com> wrote:
>
> Hi,
>
> On 11/3/20 2:35 PM, Rhys Perry wrote:
> >>
> >> (please use reply-all so that the mailing list gets the emails as well)
> >>
> >
> > Oh, my mistake. I didn't actually know the difference between the two.
> > Sorry for any confusion this might cause in the future.
> >
> >>
> >>>> [...]
> >>>>>> Can you see any messages generated by the hp-wmi driver when these key presses occur?
> >>>>>
> >>>>> Not that I know of, unless there is some sort of debug mode that can be enabled
> >>>>>
> >>>>>>>> Now, this is not that interesting at first, I obviously just need to
> >>>>>>>> map a keycode. The confusing part is that for both the brightness up
> >>>>>>>> AND the brightness down key I get the same code (e02b). I am not to
> >>>>>>>> sure how to debug this behavior but I would appreciate if someone
> >>>>>>>> helped investigate this issue.
> >>>>>>>> I am not sure if this is relevant, but my RFKILL key does not work
> >>>>>>>> either (but does not show anything in journal).
> >>>>>>
> >>>>>> Could you please run `evtest` and see if you have a "HP WMI hotkeys" input device?
> >>>>>> If so, please select it, and then press the function keys and see if any events appear.
> >>>>>
> >>>>> After running`evtest` there is a device called "HP WMI hotkeys" (on
> >>>>> /dev/input/event16). However, after selecting it and pressing the
> >>>>> brightness keys no events appear.
> >>>>>
> >>>>>> Furthermore, you could install `acpid`, start it (something along the lines of
> >>>>>> `sudo systemctl start acpid`), then run `acpi_listen` and see if you get anything
> >>>>>> when you press the keys.
> >>>>>
> >>>>> After starting the service and running`acpi_listen`, no events appear
> >>>>> when pressing the brightness keys
> >>>>>
> >>>>>>>> Here is a link to acpidump:
> >>>>>>>> https://www.dropbox.com/s/ulyltq0gz35s79l/acpidump?dl=0
> >>>>>>>> ::: Rhys Perry :::
> >>>>> [...]
> >>>>
> >>>> Could you test other function keys like volume up/down, etc.?
> >>>>
> >>> After running some tests with evtest I have found out:
> >>> - Brightness keys: "AT Translated Set 2 keyboard" (although same keycode)
> >>> - Volume keys: "AT Translated Set 2 keyboard"
> >>> - Media keys: "AT Translated Set 2 keyboard"
> >>> - RFKILL key: (none, although there is a device called "HP Wireless hotkeys")
> >>
> >> Please install the `evemu` program suite, and run `evemu-record /dev/input/event...`
> >> for the AT keyboard, HP WMI hotkeys, and HP Wireless hotkeys; in each run press the
> >> brightness up/down, volume up/down keys in any fixed order you like, and then send
> >> the output of each run (including the part that is initially printed before
> >> receiving any events). Could you also run `acpi_listen` at the same time and
> >> see if any key presses are registered there? If yes, what was the output?
> >>
> >
> > Ok, here you go:
> > "AT Translated Set 2 Keyboard": https://0x0.st/idpK.txt
> > "HP Wireless hotkeys": https://0x0.st/idpP.txt
> > "HP WMI hotkeys": https://0x0.st/idpN.txt
> > `acpi_listen`: https://0x0.st/idpb.txt
>
> Can you also run evemu-record for the "Video Bus"
> input device and check if you get events there for the
> brightness up/down key presses?  On modern laptops events
> for the brightness keys are typically delivered there.
>

I ran evemu-record for my "Video Bus" devices (of which I had two) and
there was nothing on those either. I quickly ran over every single
input device and I can confirm that "AT Translated Set 2 Keyboard" is
the only one that responds to brightness keys.


> Also are you perhaps using the nvidia binary driver for
> your GPU ?
>

No, I am running with nouveau. Most of the performance isn't there, as
they haven't worked out reclocking on the 1050Ti yet, but it's enough
for what I do

> Regards,
>
> Hans
>

Yours thankfully,
Rhys Perry

Re: [hp_wmi] Recieving same keycode from two keys

[Hans de Goede]

Hi,

Note I restored the Cc list again, please use Reply-to-all.

On 11/3/20 3:25 PM, Rhys Perry wrote:
>>
>> Hi,
>>
>> On 11/3/20 2:35 PM, Rhys Perry wrote:
>>>>>>>> (please use reply-all so that the mailing list gets the emails as well)
>>>>
>>>
>>> Oh, my mistake. I didn't actually know the difference between the two.
>>> Sorry for any confusion this might cause in the future.
>>>
>>>>
>>>>>> [...]
>>>>>>>> Can you see any messages generated by the hp-wmi driver when these key presses occur?
>>>>>>>
>>>>>>> Not that I know of, unless there is some sort of debug mode that can be enabled
>>>>>>>
>>>>>>>>>> Now, this is not that interesting at first, I obviously just need to
>>>>>>>>>> map a keycode. The confusing part is that for both the brightness up
>>>>>>>>>> AND the brightness down key I get the same code (e02b). I am not to
>>>>>>>>>> sure how to debug this behavior but I would appreciate if someone
>>>>>>>>>> helped investigate this issue.
>>>>>>>>>> I am not sure if this is relevant, but my RFKILL key does not work
>>>>>>>>>> either (but does not show anything in journal).
>>>>>>>>
>>>>>>>> Could you please run `evtest` and see if you have a "HP WMI hotkeys" input device?
>>>>>>>> If so, please select it, and then press the function keys and see if any events appear.
>>>>>>>
>>>>>>> After running`evtest` there is a device called "HP WMI hotkeys" (on
>>>>>>> /dev/input/event16). However, after selecting it and pressing the
>>>>>>> brightness keys no events appear.
>>>>>>>
>>>>>>>> Furthermore, you could install `acpid`, start it (something along the lines of
>>>>>>>> `sudo systemctl start acpid`), then run `acpi_listen` and see if you get anything
>>>>>>>> when you press the keys.
>>>>>>>
>>>>>>> After starting the service and running`acpi_listen`, no events appear
>>>>>>> when pressing the brightness keys
>>>>>>>
>>>>>>>>>> Here is a link to acpidump:
>>>>>>>>>> https://www.dropbox.com/s/ulyltq0gz35s79l/acpidump?dl=0
>>>>>>>>>> ::: Rhys Perry :::
>>>>>>> [...]
>>>>>>
>>>>>> Could you test other function keys like volume up/down, etc.?
>>>>>>
>>>>> After running some tests with evtest I have found out:
>>>>> - Brightness keys: "AT Translated Set 2 keyboard" (although same keycode)
>>>>> - Volume keys: "AT Translated Set 2 keyboard"
>>>>> - Media keys: "AT Translated Set 2 keyboard"
>>>>> - RFKILL key: (none, although there is a device called "HP Wireless hotkeys")
>>>>
>>>> Please install the `evemu` program suite, and run `evemu-record /dev/input/event...`
>>>> for the AT keyboard, HP WMI hotkeys, and HP Wireless hotkeys; in each run press the
>>>> brightness up/down, volume up/down keys in any fixed order you like, and then send
>>>> the output of each run (including the part that is initially printed before
>>>> receiving any events). Could you also run `acpi_listen` at the same time and
>>>> see if any key presses are registered there? If yes, what was the output?
>>>>
>>>
>>> Ok, here you go:
>>> "AT Translated Set 2 Keyboard": https://0x0.st/idpK.txt
>>> "HP Wireless hotkeys": https://0x0.st/idpP.txt
>>> "HP WMI hotkeys": https://0x0.st/idpN.txt
>>> `acpi_listen`: https://0x0.st/idpb.txt
>>
>> Can you also run evemu-record for the "Video Bus"
>> input device and check if you get events there for the
>> brightness up/down key presses?  On modern laptops events
>> for the brightness keys are typically delivered there.
>>
> 
> I ran evemu-record for my "Video Bus" devices (of which I had two) and
> there was nothing on those either. I quickly ran over every single
> input device and I can confirm that "AT Translated Set 2 Keyboard" is
> the only one that responds to brightness keys.

Hmm, ok, weird.

Usually at least something is generating events for this. Often
we have the problem that we get the brightness keys reported
by multiple input devices, this is a new problem.

Can you try adding:

wmi.debug_event=1

To your kernel commandline and then after rebooting do:

cat /proc/cmdline

To check that it really is there and then do:

dmesg -w

To monitor kernel messages and then press the brightness
up/down hotkeys and see if you get any new messages ?

>> Also are you perhaps using the nvidia binary driver for
>> your GPU ?
>>
> 
> No, I am running with nouveau. Most of the performance isn't there, as
> they haven't worked out reclocking on the 1050Ti yet, but it's enough
> for what I do.

Ok, good, then at least the nvidia binary driver is not
getting in the way.

Regards,

Hans

Re: [hp_wmi] Recieving same keycode from two keys

[Rhys Perry]

On Tue, 3 Nov 2020 at 14:43, Hans de Goede <hdegoede@redhat.com> wrote:
>
> Hi,
>
> Note I restored the Cc list again, please use Reply-to-all.
>

Yeah, sorry about that again. I have a hotkey set for reply and am
using it out of habit.

> On 11/3/20 3:25 PM, Rhys Perry wrote:
> >>
> >> Hi,
> >>
> >> On 11/3/20 2:35 PM, Rhys Perry wrote:
> >>>>>>>> (please use reply-all so that the mailing list gets the emails as well)
> >>>>
> >>>
> >>> Oh, my mistake. I didn't actually know the difference between the two.
> >>> Sorry for any confusion this might cause in the future.
> >>>
> >>>>
> >>>>>> [...]
> >>>>>>>> Can you see any messages generated by the hp-wmi driver when these key presses occur?
> >>>>>>>
> >>>>>>> Not that I know of, unless there is some sort of debug mode that can be enabled
> >>>>>>>
> >>>>>>>>>> Now, this is not that interesting at first, I obviously just need to
> >>>>>>>>>> map a keycode. The confusing part is that for both the brightness up
> >>>>>>>>>> AND the brightness down key I get the same code (e02b). I am not to
> >>>>>>>>>> sure how to debug this behavior but I would appreciate if someone
> >>>>>>>>>> helped investigate this issue.
> >>>>>>>>>> I am not sure if this is relevant, but my RFKILL key does not work
> >>>>>>>>>> either (but does not show anything in journal).
> >>>>>>>>
> >>>>>>>> Could you please run `evtest` and see if you have a "HP WMI hotkeys" input device?
> >>>>>>>> If so, please select it, and then press the function keys and see if any events appear.
> >>>>>>>
> >>>>>>> After running`evtest` there is a device called "HP WMI hotkeys" (on
> >>>>>>> /dev/input/event16). However, after selecting it and pressing the
> >>>>>>> brightness keys no events appear.
> >>>>>>>
> >>>>>>>> Furthermore, you could install `acpid`, start it (something along the lines of
> >>>>>>>> `sudo systemctl start acpid`), then run `acpi_listen` and see if you get anything
> >>>>>>>> when you press the keys.
> >>>>>>>
> >>>>>>> After starting the service and running`acpi_listen`, no events appear
> >>>>>>> when pressing the brightness keys
> >>>>>>>
> >>>>>>>>>> Here is a link to acpidump:
> >>>>>>>>>> https://www.dropbox.com/s/ulyltq0gz35s79l/acpidump?dl=0
> >>>>>>>>>> ::: Rhys Perry :::
> >>>>>>> [...]
> >>>>>>
> >>>>>> Could you test other function keys like volume up/down, etc.?
> >>>>>>
> >>>>> After running some tests with evtest I have found out:
> >>>>> - Brightness keys: "AT Translated Set 2 keyboard" (although same keycode)
> >>>>> - Volume keys: "AT Translated Set 2 keyboard"
> >>>>> - Media keys: "AT Translated Set 2 keyboard"
> >>>>> - RFKILL key: (none, although there is a device called "HP Wireless hotkeys")
> >>>>
> >>>> Please install the `evemu` program suite, and run `evemu-record /dev/input/event...`
> >>>> for the AT keyboard, HP WMI hotkeys, and HP Wireless hotkeys; in each run press the
> >>>> brightness up/down, volume up/down keys in any fixed order you like, and then send
> >>>> the output of each run (including the part that is initially printed before
> >>>> receiving any events). Could you also run `acpi_listen` at the same time and
> >>>> see if any key presses are registered there? If yes, what was the output?
> >>>>
> >>>
> >>> Ok, here you go:
> >>> "AT Translated Set 2 Keyboard": https://0x0.st/idpK.txt
> >>> "HP Wireless hotkeys": https://0x0.st/idpP.txt
> >>> "HP WMI hotkeys": https://0x0.st/idpN.txt
> >>> `acpi_listen`: https://0x0.st/idpb.txt
> >>
> >> Can you also run evemu-record for the "Video Bus"
> >> input device and check if you get events there for the
> >> brightness up/down key presses?  On modern laptops events
> >> for the brightness keys are typically delivered there.
> >>
> >
> > I ran evemu-record for my "Video Bus" devices (of which I had two) and
> > there was nothing on those either. I quickly ran over every single
> > input device and I can confirm that "AT Translated Set 2 Keyboard" is
> > the only one that responds to brightness keys.
>
> Hmm, ok, weird.
>
> Usually at least something is generating events for this. Often
> we have the problem that we get the brightness keys reported
> by multiple input devices, this is a new problem.
>
> Can you try adding:
>
> wmi.debug_event=1
>
> To your kernel commandline and then after rebooting do:
>
> cat /proc/cmdline
>
> To check that it really is there and then do:
>
> dmesg -w
>
> To monitor kernel messages and then press the brightness
> up/down hotkeys and see if you get any new messages ?
>

Nope, exactly the same as before:
```
[   42.501517] atkbd serio0: Unknown key pressed (translated set 2,
code 0xab on isa0060/serio0).
[   42.501524] atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[   42.512377] atkbd serio0: Unknown key released (translated set 2,
code 0xab on isa0060/serio0).
[   42.512383] atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[   43.160730] atkbd serio0: Unknown key pressed (translated set 2,
code 0xab on isa0060/serio0).
[   43.160738] atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
[   43.171970] atkbd serio0: Unknown key released (translated set 2,
code 0xab on isa0060/serio0).
[   43.171978] atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
```

> >> Also are you perhaps using the nvidia binary driver for
> >> your GPU ?
> >>
> >
> > No, I am running with nouveau. Most of the performance isn't there, as
> > they haven't worked out reclocking on the 1050Ti yet, but it's enough
> > for what I do.
>
> Ok, good, then at least the nvidia binary driver is not
> getting in the way.
>
> Regards,
>
> Hans
>

Thanks,
Rhys

Re: [hp_wmi] Recieving same keycode from two keys

[Hans de Goede]

Hi,

On 11/3/20 3:51 PM, Rhys Perry wrote:
> On Tue, 3 Nov 2020 at 14:43, Hans de Goede <hdegoede@redhat.com> wrote:
>>
>> Hi,
>>
>> Note I restored the Cc list again, please use Reply-to-all.
>>
> 
> Yeah, sorry about that again. I have a hotkey set for reply and am
> using it out of habit.
> 
>> On 11/3/20 3:25 PM, Rhys Perry wrote:
>>>>
>>>> Hi,
>>>>
>>>> On 11/3/20 2:35 PM, Rhys Perry wrote:
>>>>>>>>>> (please use reply-all so that the mailing list gets the emails as well)
>>>>>>
>>>>>
>>>>> Oh, my mistake. I didn't actually know the difference between the two.
>>>>> Sorry for any confusion this might cause in the future.
>>>>>
>>>>>>
>>>>>>>> [...]
>>>>>>>>>> Can you see any messages generated by the hp-wmi driver when these key presses occur?
>>>>>>>>>
>>>>>>>>> Not that I know of, unless there is some sort of debug mode that can be enabled
>>>>>>>>>
>>>>>>>>>>>> Now, this is not that interesting at first, I obviously just need to
>>>>>>>>>>>> map a keycode. The confusing part is that for both the brightness up
>>>>>>>>>>>> AND the brightness down key I get the same code (e02b). I am not to
>>>>>>>>>>>> sure how to debug this behavior but I would appreciate if someone
>>>>>>>>>>>> helped investigate this issue.
>>>>>>>>>>>> I am not sure if this is relevant, but my RFKILL key does not work
>>>>>>>>>>>> either (but does not show anything in journal).
>>>>>>>>>>
>>>>>>>>>> Could you please run `evtest` and see if you have a "HP WMI hotkeys" input device?
>>>>>>>>>> If so, please select it, and then press the function keys and see if any events appear.
>>>>>>>>>
>>>>>>>>> After running`evtest` there is a device called "HP WMI hotkeys" (on
>>>>>>>>> /dev/input/event16). However, after selecting it and pressing the
>>>>>>>>> brightness keys no events appear.
>>>>>>>>>
>>>>>>>>>> Furthermore, you could install `acpid`, start it (something along the lines of
>>>>>>>>>> `sudo systemctl start acpid`), then run `acpi_listen` and see if you get anything
>>>>>>>>>> when you press the keys.
>>>>>>>>>
>>>>>>>>> After starting the service and running`acpi_listen`, no events appear
>>>>>>>>> when pressing the brightness keys
>>>>>>>>>
>>>>>>>>>>>> Here is a link to acpidump:
>>>>>>>>>>>> https://www.dropbox.com/s/ulyltq0gz35s79l/acpidump?dl=0
>>>>>>>>>>>> ::: Rhys Perry :::
>>>>>>>>> [...]
>>>>>>>>
>>>>>>>> Could you test other function keys like volume up/down, etc.?
>>>>>>>>
>>>>>>> After running some tests with evtest I have found out:
>>>>>>> - Brightness keys: "AT Translated Set 2 keyboard" (although same keycode)
>>>>>>> - Volume keys: "AT Translated Set 2 keyboard"
>>>>>>> - Media keys: "AT Translated Set 2 keyboard"
>>>>>>> - RFKILL key: (none, although there is a device called "HP Wireless hotkeys")
>>>>>>
>>>>>> Please install the `evemu` program suite, and run `evemu-record /dev/input/event...`
>>>>>> for the AT keyboard, HP WMI hotkeys, and HP Wireless hotkeys; in each run press the
>>>>>> brightness up/down, volume up/down keys in any fixed order you like, and then send
>>>>>> the output of each run (including the part that is initially printed before
>>>>>> receiving any events). Could you also run `acpi_listen` at the same time and
>>>>>> see if any key presses are registered there? If yes, what was the output?
>>>>>>
>>>>>
>>>>> Ok, here you go:
>>>>> "AT Translated Set 2 Keyboard": https://0x0.st/idpK.txt
>>>>> "HP Wireless hotkeys": https://0x0.st/idpP.txt
>>>>> "HP WMI hotkeys": https://0x0.st/idpN.txt
>>>>> `acpi_listen`: https://0x0.st/idpb.txt
>>>>
>>>> Can you also run evemu-record for the "Video Bus"
>>>> input device and check if you get events there for the
>>>> brightness up/down key presses?  On modern laptops events
>>>> for the brightness keys are typically delivered there.
>>>>
>>>
>>> I ran evemu-record for my "Video Bus" devices (of which I had two) and
>>> there was nothing on those either. I quickly ran over every single
>>> input device and I can confirm that "AT Translated Set 2 Keyboard" is
>>> the only one that responds to brightness keys.
>>
>> Hmm, ok, weird.
>>
>> Usually at least something is generating events for this. Often
>> we have the problem that we get the brightness keys reported
>> by multiple input devices, this is a new problem.
>>
>> Can you try adding:
>>
>> wmi.debug_event=1
>>
>> To your kernel commandline and then after rebooting do:
>>
>> cat /proc/cmdline
>>
>> To check that it really is there and then do:
>>
>> dmesg -w
>>
>> To monitor kernel messages and then press the brightness
>> up/down hotkeys and see if you get any new messages ?
>>
> 
> Nope, exactly the same as before:
> ```
> [   42.501517] atkbd serio0: Unknown key pressed (translated set 2,
> code 0xab on isa0060/serio0).
> [   42.501524] atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
> [   42.512377] atkbd serio0: Unknown key released (translated set 2,
> code 0xab on isa0060/serio0).
> [   42.512383] atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
> [   43.160730] atkbd serio0: Unknown key pressed (translated set 2,
> code 0xab on isa0060/serio0).
> [   43.160738] atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
> [   43.171970] atkbd serio0: Unknown key released (translated set 2,
> code 0xab on isa0060/serio0).
> [   43.171978] atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
> ```

Ok bummer, so it looks like only get the one event and need to catch
that (we can use i8042_install_filter() from some driver for that) and
then when we catch it probably make some ACPI call to figure out what
is going on. I took a quick peek at the acpidump you provided, but it is
huge.  One thing which did stand out is that ssdt14.dsl (after disassembling)
has:

            Method (GHKS, 0, NotSerialized)
            {
                Debug = "GetHotkeyState-----"


            Method (SHKS, 1, Serialized)
            {
                Debug = "SetHotkeyState-----"

Which may or may not be related ... But I'm afraid I do not have
the time to investigate that avenue further.

One last thing to try (I guess) is adding the following to your kernel
commandline and see if that changes things:

acpi_backlight=video

Possible other values to try are "vendor" "native" and "none"

Regards,

Hans

p.s.

I think you mentioned this before, but what was the exact model of your laptop again? 

Re: [hp_wmi] Recieving same keycode from two keys

[Rhys Perry]

>
> Hi,
>
> On 11/3/20 3:51 PM, Rhys Perry wrote:
> > On Tue, 3 Nov 2020 at 14:43, Hans de Goede <hdegoede@redhat.com> wrote:
> >>
> >> Hi,
> >>
> >> Note I restored the Cc list again, please use Reply-to-all.
> >>
> >
> > Yeah, sorry about that again. I have a hotkey set for reply and am
> > using it out of habit.
> >
> >> On 11/3/20 3:25 PM, Rhys Perry wrote:
> >>>>
> >>>> Hi,
> >>>>
> >>>> On 11/3/20 2:35 PM, Rhys Perry wrote:
> >>>>>>>>>> (please use reply-all so that the mailing list gets the emails as well)
> >>>>>>
> >>>>>
> >>>>> Oh, my mistake. I didn't actually know the difference between the two.
> >>>>> Sorry for any confusion this might cause in the future.
> >>>>>
> >>>>>>
> >>>>>>>> [...]
> >>>>>>>>>> Can you see any messages generated by the hp-wmi driver when these key presses occur?
> >>>>>>>>>
> >>>>>>>>> Not that I know of, unless there is some sort of debug mode that can be enabled
> >>>>>>>>>
> >>>>>>>>>>>> Now, this is not that interesting at first, I obviously just need to
> >>>>>>>>>>>> map a keycode. The confusing part is that for both the brightness up
> >>>>>>>>>>>> AND the brightness down key I get the same code (e02b). I am not to
> >>>>>>>>>>>> sure how to debug this behavior but I would appreciate if someone
> >>>>>>>>>>>> helped investigate this issue.
> >>>>>>>>>>>> I am not sure if this is relevant, but my RFKILL key does not work
> >>>>>>>>>>>> either (but does not show anything in journal).
> >>>>>>>>>>
> >>>>>>>>>> Could you please run `evtest` and see if you have a "HP WMI hotkeys" input device?
> >>>>>>>>>> If so, please select it, and then press the function keys and see if any events appear.
> >>>>>>>>>
> >>>>>>>>> After running`evtest` there is a device called "HP WMI hotkeys" (on
> >>>>>>>>> /dev/input/event16). However, after selecting it and pressing the
> >>>>>>>>> brightness keys no events appear.
> >>>>>>>>>
> >>>>>>>>>> Furthermore, you could install `acpid`, start it (something along the lines of
> >>>>>>>>>> `sudo systemctl start acpid`), then run `acpi_listen` and see if you get anything
> >>>>>>>>>> when you press the keys.
> >>>>>>>>>
> >>>>>>>>> After starting the service and running`acpi_listen`, no events appear
> >>>>>>>>> when pressing the brightness keys
> >>>>>>>>>
> >>>>>>>>>>>> Here is a link to acpidump:
> >>>>>>>>>>>> https://www.dropbox.com/s/ulyltq0gz35s79l/acpidump?dl=0
> >>>>>>>>>>>> ::: Rhys Perry :::
> >>>>>>>>> [...]
> >>>>>>>>
> >>>>>>>> Could you test other function keys like volume up/down, etc.?
> >>>>>>>>
> >>>>>>> After running some tests with evtest I have found out:
> >>>>>>> - Brightness keys: "AT Translated Set 2 keyboard" (although same keycode)
> >>>>>>> - Volume keys: "AT Translated Set 2 keyboard"
> >>>>>>> - Media keys: "AT Translated Set 2 keyboard"
> >>>>>>> - RFKILL key: (none, although there is a device called "HP Wireless hotkeys")
> >>>>>>
> >>>>>> Please install the `evemu` program suite, and run `evemu-record /dev/input/event...`
> >>>>>> for the AT keyboard, HP WMI hotkeys, and HP Wireless hotkeys; in each run press the
> >>>>>> brightness up/down, volume up/down keys in any fixed order you like, and then send
> >>>>>> the output of each run (including the part that is initially printed before
> >>>>>> receiving any events). Could you also run `acpi_listen` at the same time and
> >>>>>> see if any key presses are registered there? If yes, what was the output?
> >>>>>>
> >>>>>
> >>>>> Ok, here you go:
> >>>>> "AT Translated Set 2 Keyboard": https://0x0.st/idpK.txt
> >>>>> "HP Wireless hotkeys": https://0x0.st/idpP.txt
> >>>>> "HP WMI hotkeys": https://0x0.st/idpN.txt
> >>>>> `acpi_listen`: https://0x0.st/idpb.txt
> >>>>
> >>>> Can you also run evemu-record for the "Video Bus"
> >>>> input device and check if you get events there for the
> >>>> brightness up/down key presses?  On modern laptops events
> >>>> for the brightness keys are typically delivered there.
> >>>>
> >>>
> >>> I ran evemu-record for my "Video Bus" devices (of which I had two) and
> >>> there was nothing on those either. I quickly ran over every single
> >>> input device and I can confirm that "AT Translated Set 2 Keyboard" is
> >>> the only one that responds to brightness keys.
> >>
> >> Hmm, ok, weird.
> >>
> >> Usually at least something is generating events for this. Often
> >> we have the problem that we get the brightness keys reported
> >> by multiple input devices, this is a new problem.
> >>
> >> Can you try adding:
> >>
> >> wmi.debug_event=1
> >>
> >> To your kernel commandline and then after rebooting do:
> >>
> >> cat /proc/cmdline
> >>
> >> To check that it really is there and then do:
> >>
> >> dmesg -w
> >>
> >> To monitor kernel messages and then press the brightness
> >> up/down hotkeys and see if you get any new messages ?
> >>
> >
> > Nope, exactly the same as before:
> > ```
> > [   42.501517] atkbd serio0: Unknown key pressed (translated set 2,
> > code 0xab on isa0060/serio0).
> > [   42.501524] atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
> > [   42.512377] atkbd serio0: Unknown key released (translated set 2,
> > code 0xab on isa0060/serio0).
> > [   42.512383] atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
> > [   43.160730] atkbd serio0: Unknown key pressed (translated set 2,
> > code 0xab on isa0060/serio0).
> > [   43.160738] atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
> > [   43.171970] atkbd serio0: Unknown key released (translated set 2,
> > code 0xab on isa0060/serio0).
> > [   43.171978] atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
> > ```
>
> Ok bummer, so it looks like only get the one event and need to catch
> that (we can use i8042_install_filter() from some driver for that) and
> then when we catch it probably make some ACPI call to figure out what
> is going on. I took a quick peek at the acpidump you provided, but it is
> huge.  One thing which did stand out is that ssdt14.dsl (after disassembling)
> has:
>
>             Method (GHKS, 0, NotSerialized)
>             {
>                 Debug = "GetHotkeyState-----"
>
>
>             Method (SHKS, 1, Serialized)
>             {
>                 Debug = "SetHotkeyState-----"
>
> Which may or may not be related ... But I'm afraid I do not have
> the time to investigate that avenue further.
>

That looks promising (I think). I don't have any experience working
with this sort of stuff, so is there a place you recommend I start?

> One last thing to try (I guess) is adding the following to your kernel
> commandline and see if that changes things:
>
> acpi_backlight=video
>
> Possible other values to try are "vendor" "native" and "none"
>

Just tried all of those, sadly it's still not working.

> Regards,
>
> Hans
>

Yours Thankfully,
Rhys Perry

> p.s.
>
> I think you mentioned this before, but what was the exact model of your laptop again?
>

HP Pavilion cx-0598na. It has an i5-8300H and a 1050Ti

Re: [hp_wmi] Recieving same keycode from two keys

[Hans de Goede]

Hi,

On 11/3/20 4:43 PM, Rhys Perry wrote:
>>
>> Hi,
>>
>> On 11/3/20 3:51 PM, Rhys Perry wrote:
>>> On Tue, 3 Nov 2020 at 14:43, Hans de Goede <hdegoede@redhat.com> wrote:
>>>>
>>>> Hi,
>>>>
>>>> Note I restored the Cc list again, please use Reply-to-all.
>>>>
>>>
>>> Yeah, sorry about that again. I have a hotkey set for reply and am
>>> using it out of habit.
>>>
>>>> On 11/3/20 3:25 PM, Rhys Perry wrote:
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> On 11/3/20 2:35 PM, Rhys Perry wrote:
>>>>>>>>>>>> (please use reply-all so that the mailing list gets the emails as well)
>>>>>>>>
>>>>>>>
>>>>>>> Oh, my mistake. I didn't actually know the difference between the two.
>>>>>>> Sorry for any confusion this might cause in the future.
>>>>>>>
>>>>>>>>
>>>>>>>>>> [...]
>>>>>>>>>>>> Can you see any messages generated by the hp-wmi driver when these key presses occur?
>>>>>>>>>>>
>>>>>>>>>>> Not that I know of, unless there is some sort of debug mode that can be enabled
>>>>>>>>>>>
>>>>>>>>>>>>>> Now, this is not that interesting at first, I obviously just need to
>>>>>>>>>>>>>> map a keycode. The confusing part is that for both the brightness up
>>>>>>>>>>>>>> AND the brightness down key I get the same code (e02b). I am not to
>>>>>>>>>>>>>> sure how to debug this behavior but I would appreciate if someone
>>>>>>>>>>>>>> helped investigate this issue.
>>>>>>>>>>>>>> I am not sure if this is relevant, but my RFKILL key does not work
>>>>>>>>>>>>>> either (but does not show anything in journal).
>>>>>>>>>>>>
>>>>>>>>>>>> Could you please run `evtest` and see if you have a "HP WMI hotkeys" input device?
>>>>>>>>>>>> If so, please select it, and then press the function keys and see if any events appear.
>>>>>>>>>>>
>>>>>>>>>>> After running`evtest` there is a device called "HP WMI hotkeys" (on
>>>>>>>>>>> /dev/input/event16). However, after selecting it and pressing the
>>>>>>>>>>> brightness keys no events appear.
>>>>>>>>>>>
>>>>>>>>>>>> Furthermore, you could install `acpid`, start it (something along the lines of
>>>>>>>>>>>> `sudo systemctl start acpid`), then run `acpi_listen` and see if you get anything
>>>>>>>>>>>> when you press the keys.
>>>>>>>>>>>
>>>>>>>>>>> After starting the service and running`acpi_listen`, no events appear
>>>>>>>>>>> when pressing the brightness keys
>>>>>>>>>>>
>>>>>>>>>>>>>> Here is a link to acpidump:
>>>>>>>>>>>>>> https://www.dropbox.com/s/ulyltq0gz35s79l/acpidump?dl=0
>>>>>>>>>>>>>> ::: Rhys Perry :::
>>>>>>>>>>> [...]
>>>>>>>>>>
>>>>>>>>>> Could you test other function keys like volume up/down, etc.?
>>>>>>>>>>
>>>>>>>>> After running some tests with evtest I have found out:
>>>>>>>>> - Brightness keys: "AT Translated Set 2 keyboard" (although same keycode)
>>>>>>>>> - Volume keys: "AT Translated Set 2 keyboard"
>>>>>>>>> - Media keys: "AT Translated Set 2 keyboard"
>>>>>>>>> - RFKILL key: (none, although there is a device called "HP Wireless hotkeys")
>>>>>>>>
>>>>>>>> Please install the `evemu` program suite, and run `evemu-record /dev/input/event...`
>>>>>>>> for the AT keyboard, HP WMI hotkeys, and HP Wireless hotkeys; in each run press the
>>>>>>>> brightness up/down, volume up/down keys in any fixed order you like, and then send
>>>>>>>> the output of each run (including the part that is initially printed before
>>>>>>>> receiving any events). Could you also run `acpi_listen` at the same time and
>>>>>>>> see if any key presses are registered there? If yes, what was the output?
>>>>>>>>
>>>>>>>
>>>>>>> Ok, here you go:
>>>>>>> "AT Translated Set 2 Keyboard": https://0x0.st/idpK.txt
>>>>>>> "HP Wireless hotkeys": https://0x0.st/idpP.txt
>>>>>>> "HP WMI hotkeys": https://0x0.st/idpN.txt
>>>>>>> `acpi_listen`: https://0x0.st/idpb.txt
>>>>>>
>>>>>> Can you also run evemu-record for the "Video Bus"
>>>>>> input device and check if you get events there for the
>>>>>> brightness up/down key presses?  On modern laptops events
>>>>>> for the brightness keys are typically delivered there.
>>>>>>
>>>>>
>>>>> I ran evemu-record for my "Video Bus" devices (of which I had two) and
>>>>> there was nothing on those either. I quickly ran over every single
>>>>> input device and I can confirm that "AT Translated Set 2 Keyboard" is
>>>>> the only one that responds to brightness keys.
>>>>
>>>> Hmm, ok, weird.
>>>>
>>>> Usually at least something is generating events for this. Often
>>>> we have the problem that we get the brightness keys reported
>>>> by multiple input devices, this is a new problem.
>>>>
>>>> Can you try adding:
>>>>
>>>> wmi.debug_event=1
>>>>
>>>> To your kernel commandline and then after rebooting do:
>>>>
>>>> cat /proc/cmdline
>>>>
>>>> To check that it really is there and then do:
>>>>
>>>> dmesg -w
>>>>
>>>> To monitor kernel messages and then press the brightness
>>>> up/down hotkeys and see if you get any new messages ?
>>>>
>>>
>>> Nope, exactly the same as before:
>>> ```
>>> [   42.501517] atkbd serio0: Unknown key pressed (translated set 2,
>>> code 0xab on isa0060/serio0).
>>> [   42.501524] atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
>>> [   42.512377] atkbd serio0: Unknown key released (translated set 2,
>>> code 0xab on isa0060/serio0).
>>> [   42.512383] atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
>>> [   43.160730] atkbd serio0: Unknown key pressed (translated set 2,
>>> code 0xab on isa0060/serio0).
>>> [   43.160738] atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
>>> [   43.171970] atkbd serio0: Unknown key released (translated set 2,
>>> code 0xab on isa0060/serio0).
>>> [   43.171978] atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.
>>> ```
>>
>> Ok bummer, so it looks like only get the one event and need to catch
>> that (we can use i8042_install_filter() from some driver for that) and
>> then when we catch it probably make some ACPI call to figure out what
>> is going on. I took a quick peek at the acpidump you provided, but it is
>> huge.  One thing which did stand out is that ssdt14.dsl (after disassembling)
>> has:
>>
>>             Method (GHKS, 0, NotSerialized)
>>             {
>>                 Debug = "GetHotkeyState-----"
>>
>>
>>             Method (SHKS, 1, Serialized)
>>             {
>>                 Debug = "SetHotkeyState-----"
>>
>> Which may or may not be related ... But I'm afraid I do not have
>> the time to investigate that avenue further.
>>
> 
> That looks promising (I think). I don't have any experience working
> with this sort of stuff, so is there a place you recommend I start?

Ubuntu has a writeup on WMI here:
https://wiki.ubuntu.com/Kernel/Reference/WMI

And this looks interesting:
https://adamtheautomator.com/query-wmi-linux-python/

That seems to be just about querying and not about calling WMI
methods though.

Good luck with this. My own WMI experience is limited and I also
really don't have time to coach you on this. But perhaps someone
else on the list can help you further ?

Regards,

Hans

Re: [hp_wmi] Recieving same keycode from two keys

[Hans de Goede]

Hi Rhys,

I just heard from another HP user that updating his BIOS fixed this for him,
are you at the latest BIOS for your machine?

Regards,

Hans

Re: [hp_wmi] Recieving same keycode from two keys

[Rhys Perry]

>
> Hi Rhys,
>
> I just heard from another HP user that updating his BIOS fixed this for him,
> are you at the latest BIOS for your machine?
>

Thanks for notifing me, I just checked the HP website and there *is* a
bios update available for my laptop (released on Jul 7th). However, as
HP does not provide BIOS updates for my model through the LVFS
(desptite being a member), I am going to have to reinstall Windows -
which, as I am sure you can appreciate, is not an enjoyable task.
Especially trying to stop it messing with my pure Linux install.

>
> Regards,
>
> Hans
>

Regards,
Rhys Perry

Re: [hp_wmi] Recieving same keycode from two keys

[Hans de Goede]

Hi,

On 11/24/20 2:28 PM, Rhys Perry wrote:
>>
>> Hi Rhys,
>>
>> I just heard from another HP user that updating his BIOS fixed this for him,
>> are you at the latest BIOS for your machine?
>>
> 
> Thanks for notifing me, I just checked the HP website and there *is* a
> bios update available for my laptop (released on Jul 7th). However, as
> HP does not provide BIOS updates for my model through the LVFS
> (desptite being a member), I am going to have to reinstall Windows -
> which, as I am sure you can appreciate, is not an enjoyable task.

Yeah I've been there myself and I did not like it much either.
Tip if you have not installed Windows 10 for a while, do not
give Windows network access during installation! Otherwise it will
force you to create a Microsoft online account.

> Especially trying to stop it messing with my pure Linux install.

This webpages lists some other options which you can try:
https://wiki.archlinux.org/index.php/Flashing_BIOS_from_Linux

Note the results with this might vary, you might be better of just
biting the bullet and re-installing Windows...

Regards,

Hans