[arch-general] Resume from sleep doesn't work any more

Andy Pieters arch-general at andypieters.me.uk
Mon Mar 8 15:00:05 UTC 2021


Hi all

As per the subject, Arch goes nicely to sleep, but waking up goes wrong.

I see the entries in the dmesg logs:

[32990.466213] nvidia-modeset: ERROR: GPU:0: Failed detecting connected
display devices
[32990.466250] nvidia-modeset: ERROR: GPU:0: Failed detecting connected
display devices
[32990.466256] nvidia-modeset: ERROR: GPU:0: Failure reading maximum pixel
clock value for display device DVI-I-1.
[32990.466785] nvidia-modeset: ERROR: GPU:0: Failed detecting connected
display devices
[32990.466791] nvidia-modeset: ERROR: GPU:0: Failure reading maximum pixel
clock value for display device HDMI-0.
[32990.467214] nvidia-modeset: ERROR: GPU:0: Failed detecting connected
display devices
[32990.467219] nvidia-modeset: ERROR: GPU:0: Failure reading maximum pixel
clock value for display device HDMI-1.
[32990.467678] nvidia-modeset: ERROR: GPU:0: Failed detecting connected
display devices

Which are mentioned in the Arch Linux NVIDIA troubleshooting:
https://wiki.archlinux.org/index.php/NVIDIA/Troubleshooting#System_does_not_return_from_suspend

I have applied the fix:

sudo strings /sys/firmware/acpi/tables/DSDT | grep -i 'windows ' | sort |
tail -1
Windows 2015

cat /boot/loader/entries/arch.conf
title          Arch Linux
linux          /vmlinuz-linux
initrd         /intel-ucode.img
initrd         /initramfs-linux.img
options        root=UUID=0d9c3207-a30f-4273-95fa-80e0cf5624ba rw
nvidia-drm.modeset=1 resume=PARTUUID=82a0cf4c-5d39-7647-94e3-be1a46741847
acpi_osi=! \"acpi_osi=Windows 2015\"

Which is how I boot:
 cat /proc/cmdline
initrd=\intel-ucode.img initrd=\initramfs-linux.img
root=UUID=0d9c3207-a30f-4273-95fa-80e0cf5624ba rw nvidia-drm.modeset=1
resume=PARTUUID=82a0cf4c-5d39-7647-94e3-be1a46741847 acpi_osi=!
\"acpi_osi=Windows 2015\"

I've tried any combination of with and without quotes

But resuming from spend still doesn't work.

I don't recall exactly when this started happening but things used to work
for years...

This system has got a built-in Intel GPU and I can switch between setting
the intel as IGD in the cmos. but using this setting has no bearing...


More information about the arch-general mailing list