You are not logged in.
I used to be able to wake my laptop from systemctl suspend by pressing any key on the keyboard. However, for some unknown reason, this no longer works. Now I have to manually close and reopen the lid to wake the laptop.
I noticed that if I suspend the system via terminal and press keys on the keyboard, nothing seems to happen — the screen stays off. But after waking it up by closing/opening the lid, I can see in the terminal that the keystrokes I typed while it was apparently suspended have been registered. This suggests that the laptop already woke up, but the screen doesn't turn on.
I checked journalctl but didn’t notice anything that looked out of the ordinary. I disabled TLP to test, but the issue remained.
My laptop have hybrid graphics (intel UHD graphics + Nvidia gtx 1650) and I use nouveau drives for my Nvidia GPU.
Last edited by PauLuke (2025-04-09 17:32:34)
Offline
I ended up solving the issue by completely removing TLP. Basically, I just reversed the installation steps to uninstall it:
$ systemctl disable tlp.service$ systemctl disable NetworkManager-dispatcher.service$ systemctl unmask systemd-rfkill.service systemd-rfkill.socket$ yay -Rns tlp tlp-rdwI can't explain exactly what was going on. I've been using TLP for a while and never had any issues — until now. I also don't know why the problem only went away after removing TLP entirely, and not just by stopping its service.
Offline
cat /proc/acpi/wakeupfor the wakeup triggers, TLP might deactivate some of them?
Online