You are not logged in.
So you're not running any (obvious, there could be some dynamic loading going on) 32 binaries…
https://archlinux.org/packages/multilib … dia-utils/ only puts a bunch of libraries onto your disk - the only way I see this could break stuff is if any of those gets used by https://wiki.archlinux.org/title/NVIDIA … er_suspendWhat happens if you disable that?
(The kernel commandline parameter is "nvidia.NVreg_PreserveVideoMemoryAllocations=0" and you'll have to disable all userspace services otherwise nvidia will complain when suspending)
At the first iteration installing "lib32-nvidia-utils" and adding "nvidia.NVreg_PreserveVideoMemoryAllocations=0" to the kernel parameters, then running
$ sudo mkinitcpio -P
$ systemctl disable nvidia-suspend.service nvidia-resume.service nvidia-hibernate.service
$ reboot ## login and
$ systemctl suspend ## wake up failsAlso the first iteration of reverting the settings above to how it previously was, also kept the wake up failing and I had to go through some tinkering in order to get it back to the previous suspend/resume working condition (but I do not know which of it made it). Other then reinstalling the nvidia drivers and rebooting many times:
I had a bad parameter "DHCP=yes" in "/etc/systemd/network/25-wireless.network" which used to work if "EnableNetworkConfiguration=false" is in "/etc/iwd/main.conf" but something probably changed with updates and I was getting a warning on the journalctl log.
I did also remove a testing parameter "FreezeUserspace=yes" in "/etc/systemd/sleep.conf"
Maybe one of it was conflicting with the suspend/resume as systemd seems to integrate many things.
After that, I did try your suggestion again and this time it seems (if not a fluke) to work well.
It has "nvidia.NVreg_PreserveVideoMemoryAllocations=0" on the kernel parameters and "lib32-nvidia-utils" is installed, but nvidia services has to be enabled (otherwise wake up fails). Nvidia seems to not complain when suspending and previous usb related errors when woke up didn't show up.
Is suspend/resume with the userspace services disabled ever supposed to work also considering that Nvidia is running as primary GPU?
Last edited by felipescotti (2025-12-29 01:27:38)
Offline
Is suspend/resume with the userspace services disabled ever supposed to work also considering that Nvidia is running as primary GPU?
Yesno. You're jeopardizing the VRAM, typically resulting in garbage textures in GL clients after the wakeup.
Gnome will refuse to start when you disable that but it's not strictly necessary.
I did also remove a testing parameter "FreezeUserspace=yes" in "/etc/systemd/sleep.conf"
Why was that enabled?
It has "nvidia.NVreg_PreserveVideoMemoryAllocations=0" on the kernel parameters and "lib32-nvidia-utils" is installed, but nvidia services has to be enabled (otherwise wake up fails). Nvidia seems to not complain when suspending
Does nvidia.NVreg_PreserveVideoMemoryAllocations=0 even apply?
systool -vm nvidiaOnline
Yesno. You're jeopardizing the VRAM, typically resulting in garbage textures in GL clients after the wakeup.
Gnome will refuse to start when you disable that but it's not strictly necessary.
I may try to disable it again but wake up was leaving the same previous blank screen, even without "lib32-nvidia-utils" installed.
I did also remove a testing parameter "FreezeUserspace=yes" in "/etc/systemd/sleep.conf"
Why was that enabled?
Chatgpt recommendation in my early attempts of solving the "wake up issue" and I forgot to remove afterwards.
Does nvidia.NVreg_PreserveVideoMemoryAllocations=0 even apply?
systool -vm nvidia
$ systool -vm nvidia
bash: systool: command not found
$ sudo sort /proc/driver/nvidia/params | grep "PreserveVideoMemoryAllocations"
PreserveVideoMemoryAllocations: 0Offline