The same problem happened to me when having 470 drivers installed I installed 460 drivers without first purging all the nvidia related packages manually.
After a lot of experimenting and inspection I found a fix for this issue, if youāre affected you can follow my procedure as described HERE until NVIDIA patches this in future drivers.
I tried duplicating issue on another test system but no luck so far.
ASUSTeK COMPUTER INC P9X79 + Intel(R) Coreā¢ i7-3820 CPU @ 3.60GHz + Ubuntu 20.04.1 LTS + 5.11.0-27-generic + Driver 470.57.02 + NVIDIA GeForce GTX 980
Performed suspend resume 5 times and display turned on each time successfully.
Shall try again on another system and keep updated on it.
Hi there. Are you testing installing driver from .run file or installing driver from distro packages?
Could you try following the steps that most users do installing drivers from distro packages?
Also perhaps it would be good to test by first installing 460 drivers from distro packages, and then upgrading to 470 drivers also from distro packages.
If nvidia team cannot reproduce the problem, could you at least try to find out what has changed between versions 460 and 470 in terms of suspend/resume things? Many of us in this thread only have the problem with 470 drivers.
Just in case CUDA toolkit may have something to do with the problem, I have installed nvidia driver from distro repositories, but CUDA toolkit 11.1.105 from .run file.
Hi! I just did a clean install of Ubuntu 20.04 and whatever updates that come with it. Coming out of suspend, the screen stays blank every single time.
I realized two problems. Rebooting after install, I didnāt understand how to Enroll MOK. And then, while installing an earlier driver version, I realized update-initramfs would say itāll resume from the wrong partition.
A clean Ubuntu 20.04 reinstall, with secure boot properly MOKāed, and making a new initramfs after setting RESUME env var to the proper partition, now suspend works. At least for now.
I uninstalled .run installer file, installed 460 drivers from distro packages and later upgraded to 470.63.01 from ubuntu PPA but could not duplicate issue after performing suspend/resume operation for 10 times.
Shall try on few other test systems and also look for any significant changes done between 460 and 470 drivers which might led to issue.
Okay, suspend/resume worked for me for one day, but now resume doesnāt work anymore. Doesnāt seem to depend on the initramfs. I am unaware of any changes to the system.
What type of connection to the monitor are you using? at some point recently, drivers had issue with DisplayPort (black screen at startup) if i recall correctly - which is what iām using
Hi there, Iām currently running Kubuntu 18.04 LTS
Iām able to reproduce the problem.
EDIT: Trying to do a fresh reproduction failed, uncertain if information below can actually trigger the problem or if something changed meanwhile
EDIT2/3: I was able to reproduce it again, but it requires the PC to be suspended for a longer period of time (I think it was about 1 hour).
Can provide Stack Trace upon request. If necessary can also perform additional steps to obtain further information (for example use kgdb etc.)
I prefer not to share the logs with public downloads as they might or might not include login tokens for running programs.
I will try to upgrade the Linux kernel and see if the problem persists.
EDIT 4: I noticed an interesting thing. Version 465.27 is still present in the kernel log, so maybe this is a mere kernel/driver mismatch nvidia-crash.txt (16.9 KB)
Yep, same issue here, suspending from the TTY session (no DE) resumes without screen turning on. Nvidia drivers seem to works fine: CUDA works, nvidia-smi shows correct info and stats. Monitors can be queried with ddcutil interrogate
In fact, if I remember correctly, it existed on my PC from the very beginning (several years ago when I built my computer and installed Arch). I donāt remember when I last used suspension or hybernation.