SOLVED System Won't Resume from Sleep/Suspend (Black Screen)

[deepakdeshp]

Kudos SMG for analyzing the issue well.

[qed]

My apologies, but my issue still persists! When I leave the system idle for longer than 30 min, I can't boot back into the linux desktop. The last time it happened, I couldn't get back into a terminal command prompt when I hit alt + ctrl + f1. I checked my power settings and I have it set so that the screen turns off after 30 minutes. I can't imagine that this is the issue however, because the screen SHOULD turn on after I wake up the computer, correct? The computer is set to NEVER suspect when inactive (although I'd like it to).

This is the second distro I've been through and this issue is still a problem. Honestly I love LM, but I think I'm just cursed Can anyone help?

[SMG]

My apologies, but my issue still persists! When I leave the system idle for longer than 30 min, I can't boot back into the linux desktop.

What do you mean by idle? Like when you just go away from the computer for more than 30 minutes and just let the default settings work? Or do you mean after the computer has been asleep for more than 30 minutes.

The last time it happened, I couldn't get back into a terminal command prompt when I hit alt + ctrl + f1. I checked my power settings and I have it set so that the screen turns off after 30 minutes. I can't imagine that this is the issue however, because the screen SHOULD turn on after I wake up the computer, correct? The computer is set to NEVER suspect when inactive (although I'd like it to).

I do not know anything about your monitor, so I do not know what is "should" do. Not all monitors are designed the same way.

[FooYoungHi]

I think I'm having the same issues. On windows everything works fine, and on Mint it suddenly stopped working a few weeks ago.
Even if I just turn off my display, it won't come back on. It will just go back to standby after showing a 'no signal' message. It is hooked up by HDMI.
I've been messing around with different kernels (found out today you can change them at boot), and I found that up to 5.4.0-66 everything works fine, but after that one, the screen won't turn back on when waking up from sleep or standby. I tried the latest 5.8 kernel, but the issue remains.
The system doesn't crash or anything, it's just the monitor that doesn't turn back on. I can press the power button on my PC (set to ask what to do), press Enter and it will shut down.
Whatever it is (handshake issue?), it seemingly happened in 5.4.0-67.

[SMG]

I think I'm having the same issues.

Do you have the exact same hardware? If not, please create your own thread for your issue. There are a number of things which can cause this type of issue.
Example: There is an issue with computers with AMD graphics not resuming from sleep which started with kernel 5.4.0-66. Kernel 5.4.0-66 - monitor doesn't wake from sleep which is a known bug and does not apply to the OP of this thread. The fact you are seeing your issue consistently while the OP of this thread is not makes it likely your issue is different.

[qed]

Hello, sorry for the late reply! I nearly gave up on this VERY frustrating issue.

What do you mean by idle?

When I leave the computer idol for more than 30 min and let the default settings work, the screen goes black. If I try to wake it up, the screen stays black, and my monitor displays a message that says "no input signal received".

Sometimes I can get into a tty by pressing CTRL + ALT + F1. CTRL + ALT + Backspace does not do anything.

I'm just totally clueless about what to do about this.

[SMG]

Some people found their laptops were having issues with the Nvidia-460 and suspend. When they used the Nvidia-450 everything worked properly. I do not know if that might apply in your case or even if you are still using the same driver version you were earlier in the thread. It's possible an updated graphics driver (if available) might help.

Please supply the current inxi -SMCGx.

[qed]

OK, here is the result of my

Code: Select all

inxi -SMCGx

:

Code: Select all

System:
  Host: nick-Z390-AORUS-PRO-WIFI Kernel: 5.8.0-53-generic x86_64 bits: 64 
  compiler: N/A Desktop: Cinnamon 4.8.6 Distro: Linux Mint 20.1 Ulyssa 
  base: Ubuntu 20.04 focal 
Machine:
  Type: Desktop System: Gigabyte product: Z390 AORUS PRO WIFI v: N/A 
  serial: <superuser/root required> 
  Mobo: Gigabyte model: Z390 AORUS PRO WIFI-CF v: x.x 
  serial: <superuser/root required> UEFI: American Megatrends v: F12k 
  date: 01/19/2021 
CPU:
  Topology: 6-Core model: Intel Core i5-9600K bits: 64 type: MCP 
  arch: Kaby Lake rev: D L2 cache: 9216 KiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
  bogomips: 44398 
  Speed: 800 MHz min/max: 800/4600 MHz Core speeds (MHz): 1: 800 2: 800 
  3: 800 4: 800 5: 801 6: 800 
Graphics:
  Device-1: NVIDIA TU104 [GeForce RTX 2080 SUPER] vendor: eVga.com. 
  driver: nvidia v: 460.73.01 bus ID: 02:00.0 
  Display: x11 server: X.Org 1.20.9 driver: nvidia 
  unloaded: fbdev,modesetting,nouveau,vesa resolution: 2560x1440~100Hz 
  OpenGL: renderer: GeForce RTX 2080 SUPER/PCIe/SSE2 
  v: 4.6.0 NVIDIA 460.73.01 direct render: Yes 

I just updated to the latest Nvidia driver (460.73.01). I was using an earlier version of the 460 driver before.

Oddly enough, I have the power settings set so that the machine never goes into stand-by mode. I just want the display to turn off after 30 min, that's it!

Thanks for your continued support

[qed]

I tried following the advice given here: https://askubuntu.com/questions/477138/ ... tor-off-on

I created an xorg.conf file in my /etc/X11 directory using nvidia-xconf. I modified the xorg.conf file, adding Option "UseHotplugEvents" "false" but the issue persists. This is only an issue when I have the monitor set to turn off after a specified time. When I press CTRL + ALT + F7, I'm able to get back into the desktop. VERY strange issue.

[SMG]

I tried following the advice given here: https://askubuntu.com/questions/477138/ ... tor-off-on

I created an xorg.conf file in my /etc/X11 directory using nvidia-xconf. I modified the xorg.conf file, adding Option "UseHotplugEvents" "false" but the issue persists. This is only an issue when I have the monitor set to turn off after a specified time. When I press CTRL + ALT + F7, I'm able to get back into the desktop. VERY strange issue.

Your system is based on Ubuntu 20.04 which means the advice you followed in that thread is very, very old. There have been a lot of changes to the underlying code since then. We generally do not recommend following advice that old.

Also, the setting in Power Management is to blank the screen and not turn off the monitor. If you have the monitor set to turn off, then that seems like it would be a setting on the monitor.

I just updated to the latest Nvidia driver (460.73.01). I was using an earlier version of the 460 driver before.

So you have not yet tried the Nvidia-450?

Oddly enough, I have the power settings set so that the machine never goes into stand-by mode. I just want the display to turn off after 30 min, that's it!

There are settings in both the Screensaver app and the Power Management app. You will want to make sure neither is suspending the computer.

[qed]

I can't believe it, but downgrading from the nvidia 460 to the 450 fixed the issue. Not sure what the difference is between the two versions other than the number, but it works!

Thanks again!

[Larry78723]

If you have found the solution to your initial post, please open your original post, click on the pencil, and add (Solved) to the Subject.

[GaryD]

I can't believe it, but downgrading from the nvidia 460 to the 450 fixed the issue. Not sure what the difference is between the two versions other than the number, but it works!

Thanks again!

Same problem here. I have a B550 Aorus Pro AC with Nvidia 460 driver.
Clicking on suspend button on my Linuxmint 20.2, takes me to locked screen.

[SMG]

I can't believe it, but downgrading from the nvidia 460 to the 450 fixed the issue. Not sure what the difference is between the two versions other than the number, but it works!

Thanks again!

Same problem here. I have a B550 Aorus Pro AC with Nvidia 460 driver.
Clicking on suspend button on my Linuxmint 20.2, takes me to locked screen.

Are you saying you went to the Nvidia-450 to resolve the issue? If not and you are having issues, please create your own thread because this one is already marked SOLVED by the original poster.

[392781]

So to everyone in this thread, I was looking for solutions to this exact same problem (Trying to wake from suspend and getting a black screen... while using an Nvidia GPU).

viewtopic.php?f=49&t=361973&p=2099605&h ... d#p2099605

According to the link above it's an issue with

Code: Select all

/usr/bin/nvidia-sleep.sh

. Once I added "exit 0" at the top of the file, I was able to wake from suspend for the first time in months of dealing with this issue.

It is a little bit of a hacky way of going about it. I am not sure why this causes the problem and I don't think that Kernel updates will fix this. To me it seems that it's something on Nvidia's end. I say this because previously, I was using a rather outdated driver (v3XX or something... can't remember the specific number) on an old Linux Mint install that worked fine. I ended up needing to do a fresh install which resulted in Nvidia driver v470 installed which has been causing issues. No amount of reading system logs seemed to be the fix though.

At least until now.

[seven]

I can confirm that this hack works for my setup. Editing:

Code: Select all

/usr/bin/nvidia-sleep.sh

Addding "exit 0" at the top solved the problem.

Code: Select all

#!/bin/bash

exit 0

if [ ! -f /proc/driver/nvidia/suspend ]; then
    exit 0
fi

RUN_DIR="/var/run/nvidia-sleep"
XORG_VT_FILE="${RUN_DIR}"/Xorg.vt_number

PATH="/bin:/usr/bin"

case "$1" in
    suspend|hibernate)
    ...

System: LENOVO ThinkStation P500
Kernel: 5.4.0-91-generic x86_64
Desktop: Xfce 4.16.0
Distro: Linux Mint 20.2 Uma
Graphics: NVIDIA GM204GL [Quadro M4000]
Driver: nvidia v: 470.86