From: forkosh@panix.com
Jim Diamond wrote:
> I have a laptop running Slackware64 15.0, which, previous to upgrading
> to 5.15.27, required me to press a keyboard key after opening the lid
> to awaken it (after it was suspended to RAM).
>
> After upgrading to 5.15.27 (the dirty pipe saga of 2022), the laptop
> now awakens just by opening the lid. (I consider this to be A Good
> Thing.)
>
> However, it also awakens (with the lid still closed) if I unplug the
> AC power. (I consider this to be A Bad Thing.)
>
> I've hunted around a bit, but don't see any obvious reasons for this.
> (I define "diffing the code of 5.15.19 with 5.15.27" as "not obvious".)
> /proc/acpi/wakeup is the same in both 5.15.19 and .27.
>
> This happened with both Slackware64 15.0 and with Artix, so I'm
> leaning in the "something specific with kernel" direction, as opposed
> to "something peculiar of my distro".
>
> FWIW, it is an HP Envy x360 with a Ryzen 4700U.
>
> Has anyone here seen this on their hardware? I'd like it NOT to
> wakeup when the AC power is disconnected, and if anyone has some
> ideas, I'd be happy to hear it.
>
> Thanks. Jim
You might be able to add a file in /etc/acpi/events/ so that it
ignores that AC power connected/disconnected event. I'd tried but
failed to do a similar thing on a yoga-style laptop -- disable the
keyboard when folded to yoga-style, and re-enable it when folded back.
So, first modify the acpi/acpi_handler.sh to log every single event
it ever sees. Then plug/unplug the AC power and check the logs.
If you're actually trapping those events, then you should likely be
able to add some events/ scripts to handle them however you prefer.
(But, like I said, I failed to accomplish all that.)
--
John Forkosh ( mailto: j@f.com where j=john and f=forkosh )
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)
|
