Recent nVidia Linux drivers no longer wake up after suspend

Linux Slackware current, running kernel 6.1.63 and nVidia X11 driver 545.29.06.

Scenario:

  1. put machine to sleep from keyboard, with Fn-ESC
  2. wake it up after a while.

The machine wakes up but the screen doesn’t. If I press Ctrl-Alt-F1 to get to a text console the screen does wake up, I can login in the console, run commands, etc. From there I can see the X server and the apps started from it running, but if I press Ctrl-F7 to get to X the screen goes back to sleep. Killing the X server and starting it again gives me a working X again, but that also kills the apps in the old server, which defeats the purpose of putting the machine to sleep rather than shutting it down.

I’m attaching the output of nvidia-bug-report.sh before putting the machine to sleep, and after waking it up.

before_nvidia-bug-report.log.gz (278.0 KB)
after_nvidia-bug-report.log.gz (310.6 KB)

Help please?

1 Like

After resume, the monitor is off and the nvidia driver disables output:

[   237.582] (--) NVIDIA(0): No enabled display devices found; starting anyway because
[   237.582] (--) NVIDIA(0):     AllowEmptyInitialConfiguration is enabled
[   237.586] (II) NVIDIA(0): Setting mode "NULL"

but when the monitor is redetected, it doesn’t set any mode.

[   237.807] (--) NVIDIA(GPU-0): Asustek Computer Inc PA329C (DFP-5): connected

For a workaround, please try removing xorg.conf and check the power saving setting of your monitor. If it’s set to “deep”, try setting it to “normal”.

1 Like

Thank you for the quick reply.

Removing xorg.conf doesn’t seem to change anything (not anything obvious anyway). But the monitor’s power saving mode was indeed “deep”, and setting it to “normal” does make the problem go away.

For what it’s worth all this started happening a few weeks ago, presumably after I upgraded the drivers. Sadly I was travelling a lot at that time and I haven’t noticed the problem immediately, so I don’t know the last working version.

Anyway, the workaround solves the problem as far as I’m concerned. So I’m fine with either closing the issue, or with investigating further if you think it’s useful. Please let me know if you need additional information.

1 Like

The (mis-)behaviour should be quite clear from the logs you already provided. Might only be interesting which driver version was the last known working.
In general, im not very fond of the DP deep-sleep feature, from my experience it’s not reliably working, also on Windows with non-nvidia gpus. Most times needing to cut the power to the monitor to get it working again.

Same problem here with 545.29.06 on Archlinux + i3wm, everything up to date, kernel 6.6.8-arch1-1.

When trying to wake up the laptop via pressing a key the led of my lenovo laptop goes from blinking to a fix state (expected behavior) but neither the laptop integrated monitor nor my external one start off, sometimes the fans don’t start either and I can’t access a TTY.

Quite strange since I didn’t remember having this problem with those drivers, it just started happening few days ago.

Here are the bug reports after going to sleep (systemctl suspend) + starting X from a TTY :

nvidia-bug-report.log.gz (1.1 MB)

Possibly related to ivan.bogush’s issue?

What card does your laptop have? Desktop users, many with with 970s which admittedly you probably don’t have, have been reporting issues with 545/6.6.* on the Arch fora too.

I know it’s a stupid question, but can you tell me how to check my monitor power saving mode and change it? Thank you.