Skip to main content ↑ ↓
Topic: Black screen after suspending/hibernating (Read 993 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Black screen after suspending/hibernating

I have nvidia-dkms installed since I have a nvidia card:
Device-1: NVIDIA GP106 [GeForce GTX 1060 3GB].
I have only that one GPU.

I know that the closed source nvidia driver can cause this kind of problems.

I was able to suspend/hibernate fine.

Kernel: 6.6.9-artix1-1.

Should I post other info?

I get a black screen and I cannot change tty, when resuming.

Re: Black screen after suspending/hibernating

Reply #1 –
Take a look here

Re: Black screen after suspending/hibernating

Reply #2 –
Is "echo mem > /sys/power/state" (or "echo disk..." to hibernate) the same as that C app?

That (echo...) works better I was using that before.

Previously I added "nvidia.NVreg_PreserveVideoMemoryAllocations=1" to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub but I was not able to suspend/hibernate with that.

When I resume I have a black screen but I can see the pointer and change tty.
Not sure how often, I have to try some.
So I pkill the GUI to fix it.

That's why I tried that thing in /etc/default/grub.

Re: Black screen after suspending/hibernating

Reply #3 –
Quote from: kiblaster – on
Is "echo mem > /sys/power/state" (or "echo disk..." to hibernate) the same as that C app?
Yes
I adapted the C from a tutorial so that I could set KDE keyboard shortcuts to two separate programs. One to suspend(Ctrl-Alt-Shift-S), one to hibernate(Ctrl-Alt-Shift-H).

I've had the black screen on resume for as long as I had this motherboard on all distros and inits when I do do it the 'normal' way
echo mem > /sys/power/state always works though.
No clue why.

Re: Black screen after suspending/hibernating

Reply #4 –
I have been hibernating/suspending fine, thanks.

Re: Black screen after suspending/hibernating

Reply #5 –
But your not now unless you echo mem > /sys/power/state
Is that correct?

Re: Black screen after suspending/hibernating

Reply #6 –
Yes I have to use "echo mem > /sys/power/state ", otherwise I have completely black screen without ttys.

But I got again the black screen with pointer and ttys again once meanwhile.

If I knew I wouldn't bought a GPU of that brand, while others have at lest open-source drivers (but non-free firmware).

Re: Black screen after suspending/hibernating

Reply #7 –
Quote from: kiblaster – on
I wouldn't bought a GPU of that brand, while others have at lest open-source drivers (but non-free firmware).
While it does seem more common with Nvidia GPU's AMD can be affected as well.

I spent a lot of time investigating and trying to fix the issue on my system a few years ago and got nowhere other than talking to to the kernel directly. It doesn't make a lot of sense.

If it's only just started for you maybe a future kernel will bring it back to fully working.?

Re: Black screen after suspending/hibernating

Reply #8 –
Running the closed source driver it is not safe, if you ask me.
And if you want to use wayland it is a problem.

Also

Quote
AMD FreeSync™ technology has two key advantages over G-Sync: no licensing fees to display OEMs for adoption and no expensive or proprietary hardware modules.

AMD aims to make the benefits of FreeSync™ technology more accessible to everyone through an open ecosystem, free of licensing fees and expensive hardware modules, which encourages broad adoption and low end-user costs.

Quote
If it's only just started for you maybe a future kernel will bring it back to fully working.?

I hope so.
At the moment It is not working too bad I suspended/hibernated many times and only once it didn't work well.

Re: Black screen after suspending/hibernating

Reply #9 –
Well I know I'm on my own here (or at least my view differs from many in the Linux ecosphere) but most of us are running closed source CPU's which load closed source microcode. Both CPU types contain their own mini 'operating systems'.  Intel Management Engine and AMD Platform Security Processor doing god knows what.
We plug these CPU's into motherboards with closed source UEFI / BIOS which may or may not contain closed source firmware for hardware on the motherboard. Or this firmware may be loaded by the operating along with other closed source firmware later on by the OS.

So not using Nvidia because it's 'closed source' is a bit like closing the gate after the horse has bolted imho.
Then add the fact that the last I checked AMD GPU's load closed source firmware themselves.

I don't like wayland so that's a non issue for me. But if you wish to use it then Nvidia was probably not the best choice.
In other areas the Nvidia cards seem better to me so I've stuck with them. Been using them for almost 30 years except one ATI card which was a complete dog and tainted me forever.

TLDR
None of it's safe.

Re: Black screen after suspending/hibernating

Reply #10 –
I would use libreboot (UEFI / BIOS), no Intel ME/ AMD PSP, no microcode  etc. too but it's hard.
Using Intel or AMD GPUs is very easy so next time I'll do what I can, better than nothing.

Nvidia driver has inconveniences you need DKMS and build an external module etc.

Linus on Nvidia
Quote from: Linus
Nvidia has been one of the worst trouble spot we've had with hardware manufactures...

Re: Black screen after suspending/hibernating

Reply #11 –
Quote
Linus on Nvidia
I'm well aware of this.

I am curious now though
Why do you have an Nvidia GPU ?
 

Re: Black screen after suspending/hibernating

Reply #12 –
When I bought the computer I didn't know about open source, GNU, Linux etc.