Hibernate resumes to black screen (nvidia drivers)

AkkoBaka · n00b Joined: 12 Apr 2022 Posts: 6

I am trying to hibernate (i.e. suspend-to-disk) my computer, using the "suspend to disk with swap file" instructions on the wiki[0]. This works as long as X is not started, i.e. I am in a TTY. If X is started, even if I press ctrl-alt-f2 and go into a TTY, after hibernating and restarting the computer I am greeted with a black screen. I'm using recent nvidia proprietary drivers with a GTX 1070 GPU.
Note that the issue is specifically with hibernate, not suspend. The issue occurs both when running

alamahant · Advocate Joined: 23 Mar 2019 Posts: 3879

Plz create a wake up script like
https://wiki.gentoo.org/wiki/Elogind#Hook_scripts_to_be_run_when_suspending.2Fhibernating_and.2For_when_resuming.2Fthawing
and inside maybe reload nvidia drivers

Hu · Moderator Joined: 06 Mar 2007 Posts: 21602

Is this reproducible on an untainted kernel?

AkkoBaka · n00b Joined: 12 Apr 2022 Posts: 6

alamahant · Advocate Joined: 23 Mar 2019 Posts: 3879

In the post/*) section then just have
modprobe nvidia.

AkkoBaka · n00b Joined: 12 Apr 2022 Posts: 6

eccerr0r

AkkoBaka · n00b Joined: 12 Apr 2022 Posts: 6

Hu · Moderator Joined: 06 Mar 2007 Posts: 21602

The nVidia drivers have a long history of being involved with weird problems, and the inability to meaningfully debug them just exacerbates the situation. If your problem goes away when using Nouveau, that would strongly suggest a bug in the nVidia drivers. If it persists while using Nouveau, that says your problem is either hardware or a more general kernel problem. Removing the nVidia drivers before hibernating, while not as good as hibernating from an untainted kernel, would partly test whether the nVidia drivers are responsible for your problem.

Running Windows in the interim is probably fine. Mounting a Linux filesystem that was also mounted at hibernation time is strongly discouraged, which is what eccerr0r was warning against.

AkkoBaka · n00b Joined: 12 Apr 2022 Posts: 6

Alright, I'm back to report that the issue does not show up with nouveau. Also, my mouse cursor is comically large.

Hu · Moderator Joined: 06 Mar 2007 Posts: 21602

That is good news. It suggests the problem is in nVidia drivers, and that it can be fixed there. It is also bad news, since only nVidia has the source to the drivers and therefore only they can reasonably debug or fix this.

AkkoBaka · n00b Joined: 12 Apr 2022 Posts: 6

Hu · Moderator Joined: 06 Mar 2007 Posts: 21602

Now that you know nVidia drivers are the problem, you could experiment with newer or older versions of the drivers, in hopes that either this is a recent regression you can avoid in an older version, or that it is already fixed in a newer version. You could try to enable/disable functionality in the drivers to see if some optional part, hopefully one you don't care about, is guilty. You could try raising an issue with nVidia.

Ionen · Developer Joined: 06 Dec 2018 Posts: 2716

I don't use hibernation myself but there's been a lot reports for regressions with hibernation since 460 branch and recall it got even worse in 465 (kinda go far back), which were never really fully resolved afaik (and these older version aren't supported by nvidia anymore and plagued with security issues, and 390 is generally unsuitable so I wouldn't bother with it -- Edit: not in-tree anymore due to security but 450.119.03 would probably be the one to try if really wanted to.. albeit it it'll need IgnoreABI with newer Xorg to load the module, and a older LTS kernel branch.. think 5.10 was okay?).

If was systemd, there's nvidia-{hibernate,resume,suspend}.services to enable for the intended nvidia way. Could also want to try to switch NVreg_PreserveVideoMemoryAllocations=0 to =1 if these services were enabled in /etc/modprobe.d/nvidia.conf (default to 0 because it tend to work better with missing services or with openrc/elogind according to reports). Although some people had issue even with systemd since 460.

If find solutions/workarounds that could be integrated in the nvidia ebuild feel free to file a bug/PR, but otherwise nothing I can do about this

smartding · Tux's lil' helper Joined: 22 Jan 2021 Posts: 129

I had a similar but different issue: black screen after wake up from suspend to ram.

Many people were kind enough to offer help: https://forums.gentoo.org/viewtopic-t-1133268-highlight-.html.

Maybe their solutions will help you too.

Viorel · Developer Joined: 13 Feb 2012 Posts: 16

Nvidia is very hit and miss. I noticed resume from hibernate works if I use lightdm instead of gdm, but I lose the screensaver: the screen is always on, it's not blanking after a while by itself. I use GNOME. It seems gnome power works only if I use gdm (but then resume from hibernate leaves me in a black screen).

Anyway, given the choice I choose hibernate. I can hibernate and go to Fedora and back without losing anything (I configured Fedora to use a different swap partition).

On resume, everything that uses GL turns to garbage, I have to click on every Firefox window to force it to redraw, also if I leave a game running in Steam I have to exit it and restart it, it doesn't repair by itself. It's clear nvidia doesn't actually save its vram when I hibernate. So there are a few flaws in this process, but it kind of works.