From: JimDiamond@ns.sympatico.ca
On 2022-04-05 at 05:36 ADT, Giovanni wrote:
> On 4/5/22 07:45, Henrik Carlqvist wrote:
>> If you are willing to do the work, it might be easier to diff only
>> between the two kernel versions where this change happened, for
>> example between 5.15.23 and 5.15.24.
>>
>> The quickest way to find where the change happened is to do a
>> binary search for that point. Now you know that 5.15.19 work as
>> before and 5.15.27 works at after. What about the version in the
>> middle in between? That would be 5.15.23. Once you have tested with
>> kernel 5.15.23 you will know if the next step is to search between
>> 5.15.19 and 5.15.23 or between 5.15.23 and 5.15.27.
>
> The handling of events by buttons is done on elogin daemon.
> The elogin daemon interacts with acpi daemon. I suggest to check the
> log to see which events are detected at boot time.
Giovanni,
I'm not sure which log you are referring to, but in /var/log the only
file I see with "elogind" is /var/log/message. At boot time there are
lines like this
Mar 9 18:09:15 x360 elogind-daemon[1300]: Watching system buttons on
/dev/input/event3 (Power Button)
Mar 9 18:09:15 x360 elogind-daemon[1300]: Watching system buttons on
/dev/input/event1 (Power Button)
Mar 9 18:09:15 x360 elogind-daemon[1300]: Watching system buttons on
/dev/input/event2 (Lid Switch)
Mar 9 18:09:15 x360 elogind-daemon[1300]: Watching system buttons on
/dev/input/event0 (AT Translated Set 2 keyboard)
Mar 9 18:09:15 x360 elogind-daemon[1300]: Watching system buttons on
/dev/input/event8 (HP WMI hotkeys)
but this is the same set of devices for both .19 and .27.
Were you thinking of some other log information?
Jim
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)
|
