@Sebastian adding both the kernel parameter and the two lines in the nvidia module conf file works for "systemctl suspend" - the machine can now resume OK when on wayland.
Curiously though, when I try systemctl suspend-then-hibernate (my default way of suspending), I get the following in dmesg:
NVRM: GPU 0000:02:00.0: PreserveVideoMemoryAllocations module parameter is set. System Power Management attempted without driver procfs suspend interface. Please refer to the 'Configuring Power Management Support' section in the driver README.
and the machine does not suspend (I get a login prompt after 30 seconds or so). After this issue is triggered once, "systemctl suspend" also seems to break until the next reboot.
Note that "systemctl hibernate" works fine on wayland and Xorg. Also, on xorg, systemctl suspend-then-hibernate also works fine.
Could this be a bug on systemd?
@Sebastian adding both the kernel parameter and the two lines in the nvidia module conf file works for "systemctl suspend" - the machine can now resume OK when on wayland.
Curiously though, when I try systemctl suspend- then-hibernate (my default way of suspending), I get the following in dmesg:
NVRM: GPU 0000:02:00.0: PreserveVideoMe moryAllocations module parameter is set. System Power Management attempted without driver procfs suspend interface. Please refer to the 'Configuring Power Management Support' section in the driver README.
and the machine does not suspend (I get a login prompt after 30 seconds or so). After this issue is triggered once, "systemctl suspend" also seems to break until the next reboot.
Note that "systemctl hibernate" works fine on wayland and Xorg. Also, on xorg, systemctl suspend- then-hibernate also works fine.
Could this be a bug on systemd?