4 ms·
As of a couple weeks ago a wakeup hack in the embedded controller that triggers wake with dummy keystrokes on lid events and AC connection was the suspect: http
by starkparker 3y ago
As of a couple weeks ago a wakeup hack in the embedded controller that triggers wake with dummy keystrokes on lid events and AC connection was the suspect: https://community.frame.work/t/tracking-framework-amd-ryzen-7040-series-lid-wakeup-behavior-feedback/39128/44 https://community.frame.work/t/tracking-framework-amd-ryzen-...
> When we go from S0i3 to S0ix, the EC will send some dummy key presses to the host so the keyboard will keep working. This may cause the host to wake up to screen on, and stay there.
Which is what spawned the udev workarounds of just disabling wake-on-keyboard altogether, which solves for both the lid and AC connection incorrectly waking from sleep.
Which is onerous because wake-on-keyboard is a pretty common thing to want enabled on a laptop! It's not the end of the world, just another "yeah, I'm using Linux" moment.