So you’re not talking about a system suspend but about turning off your monitor?
Quite some different topic.
Please try adding
Option "HardDPMS" "false"
to the device section of your xorg.conf. If that doesn’t help, try setting it to “true”.
nvidia-bug-report.log.gz (895.3 KB)
Forget about the suspend command, it happens during a normal suspend. I see you suggested that in another thread: Screen does not "wake-up" after blanking from timeout in power settings from & incl v415-onwards and it didn’t work. I think I’ll wait until something more concrete before I try this or try that. I say this because some things if you try nvidia won’t come back from sleep and the ctrl-alt-f1, ctrl-alt-f7 trick won’t bring it back and I have to do a cold power down.
Maybe a different strategy is needed since we know NVIDIA-Linux-x86_64-410.78.run, NVIDIA-Linux-x86_64-415.23.run, and NVIDIA-Linux-x86_64-440.44.run work 100% every single time.
Changelog:
2019-10-17 version 440.26
Enabled HardDPMS by default
…
2020-02-03 version 440.59
* Disabled frame rate limiting for configurations without active
displays when HardDPMS is enabled.
* Fixed a bug that could cause the X server to crash while exiting
DPMS with HardDPMS enabled.
Unfortunately no go in this situation, but thanks for trying to help. I did look at the following page and my current default suspend mode is “s2idle”, so I am going to try to modify my grub.cfg to follow the suggestion below. I will update.
https://download.nvidia.com/XFree86/Linux-x86_64/460.67/README/powermanagement.html
On some systems, where the default suspend mode is "s2idle", the system may not resume properly due to a known timing issue in the kernel. The suspend mode can be verified by reading the contents of the file /sys/power/mem_sleep. The following upstream kernel changes have been proposed to fix the issue:
https://lore.kernel.org/linux-pci/20190927090202.1468-1-drake@endlessm.com/
https://lore.kernel.org/linux-pci/20190821124519.71594-1-mika.westerberg@linux.intel.com/
In the interim, the default suspend mode on the affected systems should be set to "deep" using the kernel command line parameter "mem_sleep_default" -
mem_sleep_default=deep
Nah, that didn’t work either:
menuentry "GNU/Linux, Linux current" {
linux /boot/current/bzImage root=/dev/sda4 ro nomodeset mem_sleep_default=deep
}
After it didn’t work I went to re-verify:
cat /sys/power/mem_sleep
s2idle [deep]
which is what it was before. Also I was using my original xorg.conf without any hardDPMS settings, but I can’t try all permutations.
Oh well, in some ways it’s no big deal at all, other times it is very frustrating. Hey! I know, they can create a special build just for me that includes all the new cool stuff, but uses the old wake-up system! lol
@amrits Hey, any developments on this? I provided the info, if you need anything else let me know. It seems like it should be fairly easy to figure out? We have the builds pinpointed where it starts happening and I can provide any logs or provide gathered data.
@nvisible_kid
thats fine
cat /sys/power/mem_sleep
s2idle [deep]
shows that the default is susbend to RAM since “deep” is highlighted by the brackets [deep]
Nevertheless, I assume you are not running Linux on a notebook with an internal monitor?
I am facing a similar issue on a notebook. The internal screen comes back from deep sleep, but the external monitor connected via a Thunderbolt does not come back. The external monitor is still not visible to the system. Only chance is to disconnect and reconnect the external monitor.
This issue happens with Fedora 34, 35 as well as other Distros like Ubuntu, Pop_OS
nvidia-bug-report.log.gz (285.8 KB)
Hi! No, running on desktop here. Hope you are able to find an answer. If I come across anything that might help I’ll post.
Since you do not have an internal monitor, that might explain it.
Imagine I would disable the internal screen.
May I ask, how do you have your monitor connected to your graphics card?
Right now via the HDMI port.
Haven’t done extensive testing, but NVIDIA-Linux-x86_64-510.54.run seems to have solved my issue. Monitor now wakes up correctly as it used to.