You are not logged in.
Hello, im using Xorg with Gnome and everytime i wake up my system from suspend the screen stays black with my cursor (i can move the cursor) then i have to wait a while to the image come back and prompt my password, im using nvidia-open drivers and i properly installed them, updated the microcode and even checked the nvidia troubleshooting fix "Black screen returning from suspend": enable the services nvidia-suspend.service, nvidia-hibernate.service, and nvidia-resume.service also adding the kernel module parameter via editing /etc/default/grub and didnt fix it. What can i do? Thanks here are my specs:
System:
Kernel: 6.12.4-arch1-1 arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
Desktop: GNOME v: 47.2 Distro: Arch Linux
Machine:
Type: Desktop Mobo: ASRock model: B550 Steel Legend
serial: <superuser required> UEFI: American Megatrends LLC. v: P3.40
date: 01/18/2024
Graphics:
Device-1: NVIDIA TU116 [GeForce GTX 1650 SUPER] vendor: ASUSTeK
driver: nvidia v: 565.77 arch: Turing bus-ID: 05:00.0
Display: x11 server: X.Org v: 21.1.15 with: Xwayland v: 24.1.4 driver: X:
loaded: nvidia gpu: nvidia,nvidia-nvswitch resolution: 2560x1080~60Hz
API: OpenGL Message: Unable to show GL data. glxinfo is missing.
CPU:
Info: 6-core model: AMD Ryzen 5 3600X bits: 64 type: MT MCP arch: Zen 2
rev: 0 cache: L1: 384 KiB L2: 3 MiB L3: 32 MiB
Speed (MHz): avg: 550 min/max: 550/4409 boost: enabled cores: 1: 550
2: 550 3: 550 4: 550 5: 550 6: 550 7: 550 8: 550 9: 550 10: 550 11: 550
12: 550 bogomips: 91070
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svmLast edited by HenryStickman420 (2024-12-23 21:47:16)
Offline
and didnt work. What can i do?
Please don't paraphrase, https://bbs.archlinux.org/viewtopic.php?id=57855
Please post your complete system journal for a boot covering such wakeup delay:
sudo journalctl -b | curl -F 'file=@-' 0x0.stOn a limb
using nvidia-open drivers
Same w/ the binary blob nvidia kernel modules?
Also test the behavior of the LTS kernel, there's at least https://bbs.archlinux.org/viewtopic.php?id=301901
Finally please use [code][/code] tags. Edit your post in this regard.
Offline
Finally please use tags. Edit your post in this regard.
done, sorry about that its been a while without posting.
Please post your complete system journal for a boot covering such wakeup delay:
Here's the link that outputs the command
http://0x0.st/XCGc.txt
test the behavior of the LTS kernel
to do that, do i have to reinstall the system? and lastly, do you recommend me to stay on LTS? i checked the link you sent me, and im starting to think that maybe is better stay a little bit delayed than the linux kernel to avoid a lot of issues. Thanks for the reply
Offline
to do that, do i have to reinstall the system?
No, you can just install linux-lts and nvidia-lts and add the lts kernel to your bootloader, then boot it.
I think I also explained in that link that 6.12 will become the next LTS kernel pretty soon. Not a longterm strategy, but still allows us to check whether the issue is the nvidia driver update, the 6.12 kernel or a combination of them.
But before that:
Same w/ the binary blob nvidia kernel modules?
Also how long approximately do you "have to wait a while to the image come back"?
(5 seconds, 10 seconds, 25 seconds, 90 seconds, 2 minutes, 5 minutes, 10 minutes…)
Offline
Same w/ the binary blob nvidia kernel modules?
sorry for the dumb question but what do you mean with binary blob? the drivers offered in the nvidia official page?
you can just install linux-lts and nvidia-lts
alright i'm gonna try that
Also how long approximately do you "have to wait a while to the image come back"?
takes around 20 seconds
Offline
Ok now im using the linux-lts kernel version:
6.6.65-1-ltsand using the nvidia-lts aswell, then i tried to suspend and the issue still persists, the black image lasts around 20 seconds until get image back again.
here's the journal output: http://0x0.st/XCDj.txt
Last edited by HenryStickman420 (2024-12-21 00:43:31)
Offline
Dec 20 18:39:58 DeveloperBox systemd[1]: Stopped target Sleep.
Dec 20 18:40:25 DeveloperBox gsd-power[1342]: Error setting property 'PowerSaveMode' on interface org.gnome.Mutter.DisplayConfig: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Remote peer disconnected (g-dbus-error-quark, 4)Seems gnome at work:
https://gitlab.gnome.org/GNOME/mutter/-/issues/2467
Do you get the same behavior w/ not-gnome ?
Offline
Do you get the same behavior w/ not-gnome ?
Haven't tried yet, gonna install cinnamon and check it out. If the problem doesn't exists in cinnamon I'll be thinking in switching to cinnamon or use the caffeine extension to never suspend the PC.
EDIT: Installed cinnamon and the problem still exists
Last edited by HenryStickman420 (2024-12-22 01:31:21)
Offline
Cinnabun being a gnome derivate is maybe not the best alternative for comparism, try openbox or icewm.
The point isn't to switch your DE but to figure whether it's the X11 server or nvidia driver or some session process.
Can you switch the VT during the black-out (ctrl+alt+F3)?
Another player here might simply be GDM, same w/ startx or lightdm or at least https://wiki.archlinux.org/title/GDM#Use_Xorg_backend ?
Offline
Another player here might simply be GDM
haven't thought in that. gonna try lightdm
try openbox or icewm.
got it. gonna try it.
Can you switch the VT during the black-out (ctrl+alt+F3)?
well i can move the mouse in this state, i guess is the same with the keyboard. i'll check it out.
EDIT: Yes i can switch the VT. Also icewm doesnt have problems with suspend. i tried with lightdm-gtk-greeter and the issue still persists. now i realize something. cinnamon doesnt ask for the password (like normally would) but directly jumps to the desktop when i wake the computer up from suspend.
Last edited by HenryStickman420 (2024-12-22 16:41:38)
Offline
After testing with another disk drive I can say that this is a gnome issue, not the Nvidia driver itself, I installed xfce4 and the suspend service works fine. Using lightdm doesn't fix the problem.
Offline
EDIT: Installed cinnamon and the problem still exists
cinnamon doesnt ask for the password (like normally would) but directly jumps to the desktop when i wake the computer up from suspend.
?
Is this after switching from GDM to lightdm?
Did you try to run GDM on the xorg backend (it actually serves as screenlocker for gnome and I could imagine cinnabun as well…)
Offline
Is this after switching from GDM to lightdm?
Yes
Did you try to run GDM on the xorg backend (it actually serves as screenlocker for gnome and I could imagine cinnabun as well…)
yes i did and nothing.
also i tried debian on another disk and the problem still exists. i give up, my pc is just bad for linux. i have a thinkpad wich runs arch without any issues. How can i close this thread? do i have to mark it down as closed or something?
Offline
my pc is just bad for linux.
I can say that this is a gnome issue
Seems gnome at work:
https://gitlab.gnome.org/GNOME/mutter/-/issues/2467
You can mark it a "[gave up]" or so, but first, try to globally export "GSK_RENDERER=gl", https://wiki.archlinux.org/title/Environment_variables
Offline
try to globally export "GSK_RENDERER=gl"
didnt work either, so i guess its over... Thanks a lot for all your help buddy. my pc is surely the problem, tbh its not the first time that my pc faces this kind of problems (even with windows has sometime issues). hopefully i'll build a pc with an intel processor.
Offline
my pc is surely the problem
Seems gnome at work:
https://gitlab.gnome.org/GNOME/mutter/-/issues/2467
Offline
Hi, I know it has been quite some time but what solved this for me (not ideal but a good direction for an actual patch, for me it's good enough) was editing /usr/bin/nvidia-sleep.sh such that the first line is "exit 0" - making the script do nothing.
I found that on suspend and resume (/lib/systemd/system/nvidia-suspend.service and /lib/systemd/system/nvidia-resume.service respectively) this script is run and it seems that without it everything works fine.
Behind the scenes the script interacts with /proc/driver/nvidia/suspend (just cat it to see what you can echo to it) and calling "echo 'suspend' > /proc/driver/nvidia/suspend" of course causes graphical problems (for me the terminal froze) so going to a different TTY and calling "echo 'resume' > /proc/driver/nvidia/suspend" fixed it.
Some problems remain:
1. Suspending without locking first will not prompt password when resuming. (only happens sometimes)
2. There might be side effects on the behavior of the graphics card, didn't go into it.
Good luck ![]()
Last edited by elyshaffir (2025-07-17 22:12:32)
Offline
I have similar symptoms: the GNOME desktop shows a black screen after resume. In this situation I can switch VTs back and forth to get my session working again. The trigger for me is non-default refresh rate, i.e. for my hardware 240Hz is the default and anything under causes trouble.
The aforementioned script hack will not work because Arch now ships /usr/lib/modprobe.d/nvidia-sleep.conf, and it enables the new experimental sleep mode by default. Suspension without interaction of the procfs interface will fail immediately.
Offline
https://wiki.archlinux.org/title/NVIDIA … er_suspend
nvidia.NVreg_PreserveVideoMemoryAllocations=0
Though the TTY juggle sounds like some recent threads (do you also have an AMD GPU?)
Offline