Hello, each time I put the computer in sleep mode, I can’t wake it up. The computer starts, but the screen wont turn on. This started happening after an update, but I don’t remember when it was.
I’m using KDE Plasma and Wayland
Here are the logs from the last time I tried to wake it up: https://dpaste.com/9SL8USD47
I have hidden all ips just in case
Another detail, while the screen is completely black, I can still access the machine through ssh.
This occasionally happens to me. I press Esc and the screens wake up. It may be that simple or it may not.
manuel
March 12, 2026, 11:50am
3
For the record, please show the output of command
inxi -Gza
Sadly, it’s not my case, but thank you for the suggestion
I forgot to mention I’m using Nvidia, here is the result of the command:
Graphics:
Device-1: NVIDIA GA102 [GeForce RTX 3080] vendor: ASUSTeK driver: nvidia
v: 590.48.01 alternate: nouveau,nvidia_drm non-free: 550-580.xx+
status: current (as of 2025-11; EOL~2026-12-xx) arch: Ampere code: GAxxx
process: TSMC n7 (7nm) built: 2020-2023 pcie: gen: 3 speed: 8 GT/s
lanes: 4 link-max: gen: 4 speed: 16 GT/s lanes: 16 ports:
active: DP-2,HDMI-A-2 empty: DP-1,DP-3,HDMI-A-1 bus-ID: 01:00.0
chip-ID: 10de:2206 class-ID: 0300
Display: wayland server: X.org v: 1.21.1.21 with: Xwayland v: 24.1.9
compositor: kwin_wayland driver: X: loaded: nvidia unloaded: modesetting
alternate: fbdev,nouveau,nv,vesa gpu: nv_platform,nvidia,nvidia-nvswitch
d-rect: 4480x2520 display-ID: 0
Monitor-1: DP-2 pos: primary,top-left model: Gigabyte G27QC
serial: <filter> built: 2020 res: mode: 2560x1440 hz: 165 scale: 100% (1)
dpi: 109 gamma: 1.2 size: 597x336mm (23.5x13.23") diag: 685mm (27")
ratio: 16:9 modes: max: 2560x1440 min: 640x480
Monitor-2: HDMI-A-2 pos: bottom-r model: Philips PHL 223V5
serial: <filter> built: 2016 res: mode: 1920x1080 hz: 60 scale: 100% (1)
dpi: 102 gamma: 1.2 size: 477x268mm (18.78x10.55") diag: 547mm (21.5")
ratio: 16:9 modes: max: 1920x1080 min: 640x480
API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2
drv: swrast gbm: drv: nvidia surfaceless: drv: nvidia wayland: drv: nvidia
x11: drv: nvidia inactive: device-1
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 26.0.1-arch1.1
glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 3080/PCIe/SSE2
memory: 9.77 GiB display-ID: :0.0
API: Vulkan v: 1.4.341 layers: 6 device: 0 type: discrete-gpu
name: NVIDIA GeForce RTX 3080 driver: nvidia v: 590.48.01
device-ID: 10de:2206 surfaces: N/A
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor gpu: nvidia-smi wl: wayland-info
x11: xdpyinfo, xprop, xrandr
manuel
March 12, 2026, 3:54pm
6
There have been some threads about a similar problem here.
Also, if you haven’t looked at this: https://wiki.archlinux.org/title/NVIDIA
I’d suggest browsing it because it contains lots of useful information.
Yeah, I found some of those threads, but the issue slightly different (or at least those which I was able to find)
The arch linux guide was useful to fix other issues I had, but I could not fix this one.
manuel
March 12, 2026, 8:51pm
8
Please show the output of
pacman -Q | grep nvidia
lib32-nvidia-utils 590.48.01-1
linux-firmware-nvidia 20260221-1
nvidia-hook 1.5.3-1
nvidia-inst 26.1.1-1
nvidia-open 590.48.01-13
nvidia-utils 590.48.01-4
manuel
March 13, 2026, 10:03am
10
Hard to say what the exact reason is. And I don’t have that particular GPU to test.
I guess some GPU model dependent setting or settings described in the Arch wiki might help. Nvidia’s support pages might also help.
Another idea is to try nvidia-580xx-dkms (AUR) instead of nvidia-open.
If none of the above helps, then I’d try using nvidia-open-dkms instead of nvidia-open.
Thanks for the suggestion. I have tried nvidia-580xx-dkms and nvidia-open-dkms, but neither of them seems to fix the issue.
What I have discovered is that sometimes, the screen actually turns on, but doesn’t show anything. When this happens I can access the terminal with Ctrl+Alt+F3, but still no desktop.
manuel
March 17, 2026, 3:50pm
12
Your log shows a problem with snapper. I guess you are using btrfs, so maybe the problem is related to btfrs and/or snapper?