Bug#1038105: upgrade-reports: resume from suspend/hibernate broken by upgrade from bullseye to bookworm
I have more information.
As per the suggestion of mooff <moofff@proton.me>, I noticed
qobi@sapiencia>ls -l /etc/modprobe.d/nvidia-options.conf
lrwxrwxrwx 1 root root 45 Sep 7 2022 /etc/modprobe.d/nvidia-options.conf -> /etc/alternatives/nvidia--nvidia-options.conf
qobi@sapiencia>ls -l /etc/alternatives/nvidia--nvidia-options.conf
lrwxrwxrwx 1 root root 49 Sep 7 2022 /etc/alternatives/nvidia--nvidia-options.conf -> /etc/nvidia/nvidia-525.105.17/nvidia-options.conf
So I moved /etc/nvidia/nvidia-525.105.17/nvidia-options.conf to
/etc/nvidia/nvidia-525.105.17/nvidia-options.conf.orig and edited
/etc/nvidia/nvidia-525.105.17/nvidia-options.conf to add
options nvidia-current NVreg_PreserveVideoMemoryAllocations=1
This prevented the machine from properly suspending/hibernating in the first
place. I know this because the Lenovo P71 has a red LED on the lid that is on
when the machine is running and pulsates when it is in
suspend/hibernation. Before I made the change it would pulsate when the lid
was closed. But after I made the change, th LED would stay on. But when I
would open the lid the screen would show the pasword request, and the mouse
would work, but the keyboard would no longer work. I would need to power cycle.
Searching the web, I found
https://unix.stackexchange.com/questions/743506/pop-os-22-04-with-nvidia-driver-525-fails-to-suspend-on-a-hybrid-laptop
So I tried changing /etc/nvidia/nvidia-525.105.17/nvidia-options.conf to
instead add
options nvidia-current NVreg_PreserveVideoMemoryAllocations=1 NVreg_TemporaryFilePath=/var/tmp
I also did
sudo update-initramfs -u
But I observed the same behaviour where the LED would stay on when closing the
lid and the keyboard wouldn't work when opening the lid.
So I backed out the change and am back in a state where it appears to
suspend/hibernate (because the LED pulsates) but 30% of the time it properly
resumes and 70% of the time it does not (the disk light flashes a few times,
the screen is blank, and no response when using the keyboard or mouse.
I dont know if I should try putting it in
/etc/modprobe.d/nvidia-power-management.conf
instead. I haven't tried that yet.
Jeff (http: //engineering.purdue.edu/~qobi)
Reply to: