You are not logged in.
Since a day or two, if I execute
systemctl suspend
the system freezes completely, or at least that's how I describe what I observe:
not even the mouse cursor moves,
I can't even switch to another VT via cltr+alt+F2,3,4...
My OS is an up-to-date ArchLinux, and I use XMonad as WM, but I've reproduced the issue from i3 as well.
I haven't tried yet executing the above command from a virtual console, i.e. without X running. Would such experiment be useful?
Here is the output of
journalctl -b -1
if that's useful to understand what's going on.
Last edited by Enrico1989 (2024-06-21 17:39:33)
Offline
I bet it started when you updated to systemd v256. That update breaks sleep on Nvidia laptops like yours (and mine)!
"The behavior of systemd-sleep and systemd-homed has been updated to freeze user sessions when entering the various sleep modes or when locking a homed-managed home area. This is known to cause issues with the proprietary NVIDIA drivers. Packagers of the NVIDIA proprietary drivers may want to add drop-in configuration files that set SYSTEMD_SLEEP_FREEZE_USER_SESSIONS=false for systemd-suspend.service and related services, and SYSTEMD_HOME_LOCK_FREEZE_SESSION=false for systemd-homed.service."
See this Debian mail thread for how to fix it. You'll have to create five nvidia.conf files in /usr/lib/systemd/system.
Offline
A fix is also pending in the current nvidia-utils package from testing, might want to install that instead, or wait a bit for it to go to stable.
Online
Ok, I've got the update and suspend works fine. Not even needed to reboot.
Offline
Hi. It also breaks nvidia desktops, at least those that derive their modules and libs from aur/nvidia-390xx-utils, like mine.
Offline
Follow the instructions in the linked thread or apply the same fix. https://gitlab.archlinux.org/archlinux/ … 4b45a60708
Online
Sorry - I had to grep for the environment variable name and combine with a different hack for it to work:
~]$ more $(find /etc/systemd -name nvidia.conf)
::::::::::::::
/etc/systemd/system/systemd-suspend.service.d/nvidia.conf
::::::::::::::
[Service]
Environment="SYSTEMD_SLEEP_FREEZE_USER_SESSIONS=false"
::::::::::::::
/etc/systemd/system/systemd-homed.service.d/nvidia.conf
::::::::::::::
[Service]
Environment="SYSTEMD_HOME_LOCK_FREEZE_SESSION=false"
AND ALSO
~]$ cat /proc/cmdline
... nvidia-drm.modeset=1 nvidia-drm.fbdev=1 ...
Offline
The number of people hit by this issue may be a lot bigger than Nvidia laptops, I use HP Probook with Radeon integrated card, non-UEFI legacy BIOS machine, no Nvidia components. The above workaround with drop-in user unit for systemd-suspend.service worked. It may be useful to have it a part of distro or indicated in Power_management/Suspend_and_hibernate.
Offline