Black screen with cursor on resume from suspend-then-hibernate

rmeno12 · 2025-09-13 14:51:26

On resuming from suspend-then-hibernate, instead of the GNOME lock screen, I see a black screen with a flashing cursor until I switch to tty2 (ctrl-alt-f2). As far as I can tell, this only happens on resume from suspend-then-hibernate. On resuming from just suspend or just hibernate, the flashing cursor shows for a second or two then goes to the GNOME lock screen, and a clean boot works without issues.

A relevant fragment of a journal where this happened is here: https://pastebin.com/JFpUTYwB. In this, I let the system suspend, waited for a few seconds, then resumed with the power button. I let the flashing cursor screen appear for about 10 seconds before manually switching the tty and logging in. I don't see any obvious errors in the journal, but I may be missing something.

System info:
This machine is a laptop with both an integrated Intel GPU (using the i915 driver) and a dedicated Nvidia GPU (using the proprietary nvidia driver).

System:
  Kernel: 6.12.47-1-lts arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
    clocksource: tsc avail: acpi_pm
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-lts
    root=UUID=4d43bcaa-c0f1-4d4e-8378-a83a850dcedc rw rootflags=subvol=@
    loglevel=3 resume=UUID=ba0d0be8-0b83-47f1-9f3e-f62bf149055e
    mem_sleep_default=deep i915.enable_psr=0
  Desktop: GNOME v: 48.4 tk: GTK v: 3.24.50 wm: gnome-shell
    tools: gsd-screensaver-proxy dm: GDM v: 48.0 Distro: Arch Linux
Machine:
  Type: Laptop System: Dell product: XPS 15 7590 v: N/A
    serial: <superuser required> Chassis: type: 10 serial: <superuser required>
  Mobo: Dell model: 0VYV0G v: A00 serial: <superuser required> part-nu: 0905
    uuid: <superuser required> UEFI: Dell v: 1.17.0 date: 04/19/2022
Battery:
  ID-1: BAT0 charge: 79.5 Wh (100%) condition: 79.5/97 Wh (81.9%) volts: 13.22
    min: 11.4 model: SMP DELL GPM0365 type: Li-ion serial: <filter> charging:
    status: full control: start: 50% end: 90% type: custom
    avail: adaptive,custom,fast,standard,trickle cycles: N/A
CPU:
  Info: model: Intel Core i7-9750H bits: 64 type: MT MCP arch: Coffee Lake
    gen: core 9 level: v3 note: check built: 2018 process: Intel 14nm family: 6
    model-id: 0x9E (158) stepping: 0xA (10) microcode: 0xFA
  Topology: cpus: 1x dies: 1 clusters: 6 cores: 6 threads: 12 tpc: 2
    smt: enabled cache: L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 1.5 MiB
    desc: 6x256 KiB L3: 12 MiB desc: 1x12 MiB
  Speed (MHz): avg: 800 min/max: 800/4500 scaling: driver: intel_pstate
    governor: powersave cores: 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800
    8: 800 9: 800 10: 800 11: 800 12: 800 bogomips: 62431
  Flags-basic: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: gather_data_sampling mitigation: Microcode
  Type: indirect_target_selection status: Not affected
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT
    vulnerable
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed mitigation: IBRS
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: IBRS; IBPB: conditional; STIBP: conditional;
    RSB filling; PBRSB-eIBRS: Not affected; BHI: Not affected
  Type: srbds mitigation: Microcode
  Type: tsa status: Not affected
  Type: tsx_async_abort status: Not affected
  Type: vmscape mitigation: IBPB before exit to userspace
Graphics:
  Device-1: Intel CoffeeLake-H GT2 [UHD Graphics 630] vendor: Dell driver: i915
    v: kernel arch: Gen-9.5 process: Intel 14nm built: 2016-20 ports:
    active: eDP-1 empty: DP-1,DP-2,DP-3 bus-ID: 00:02.0 chip-ID: 8086:3e9b
    class-ID: 0300
  Device-2: NVIDIA TU117M [GeForce GTX 1650 Mobile / Max-Q] vendor: Dell
    driver: nvidia v: 580.82.09 alternate: nouveau,nvidia_drm
    non-free: 550-580.xx+ status: current (as of 2025-08; EOL~2026-12-xx)
    arch: Turing code: TUxxx process: TSMC 12nm FF built: 2018-2022 pcie:
    gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 01:00.0 chip-ID: 10de:1f91
    class-ID: 0302
  Device-3: Microdia Integrated_Webcam_HD driver: uvcvideo type: USB rev: 2.0
    speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-12:4 chip-ID: 0c45:6d13
    class-ID: 0e02
  Display: wayland server: X.org v: 1.21.1.18 with: Xwayland v: 24.1.8
    compositor: gnome-shell driver: X: loaded: modesetting,nvidia
    alternate: fbdev,intel,nouveau,nv,vesa dri: iris gpu: i915 display-ID: 0
  Monitor-1: eDP-1 model: Samsung 0xa029 built: 2019 res: 3840x2160 dpi: 284
    gamma: 1.2 size: 344x194mm (13.54x7.64") diag: 395mm (15.5") ratio: 16:9
    modes: 3840x2160
  API: EGL v: 1.5 hw: drv: intel iris drv: nvidia platforms: device: 0
    drv: nvidia device: 2 drv: iris device: 3 drv: swrast gbm: drv: nvidia
    surfaceless: drv: nvidia wayland: drv: iris x11: drv: iris
    inactive: device-1
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: intel mesa v: 25.2.2-arch1.2
    glx-v: 1.4 direct-render: yes renderer: Mesa Intel UHD Graphics 630 (CFL GT2)
    device-ID: 8086:3e9b memory: 14.9 GiB unified: yes display-ID: :0.0
  Info: Tools: api: eglinfo,glxinfo gpu: gputop, intel_gpu_top, lsgpu,
    nvidia-smi x11: xprop,xrandr
Audio:
  Device-1: Intel Cannon Lake PCH cAVS vendor: Dell driver: snd_hda_intel
    v: kernel alternate: snd_soc_avs,snd_sof_pci_intel_cnl bus-ID: 00:1f.3
    chip-ID: 8086:a348 class-ID: 0403
  API: ALSA v: k6.12.47-1-lts status: kernel-api
    tools: alsactl,alsamixer,amixer
  Server-1: PipeWire v: 1.4.8 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel Wi-Fi 6 AX200 vendor: Rivet Networks Killer driver: iwlwifi
    v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1 bus-ID: 3b:00.0
    chip-ID: 8086:2723 class-ID: 0280
  IF: wlp59s0 state: up mac: <filter>
  IF-ID-1: tailscale0 state: unknown speed: -1 duplex: full mac: N/A
  Info: services: NetworkManager, systemd-networkd, systemd-timesyncd,
    wpa_supplicant
Bluetooth:
  Device-1: Intel AX200 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
    speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-4:7 chip-ID: 8087:0029
    class-ID: e001
  Report: btmgmt ID: hci0 rfk-id: 4 state: up address: N/A
Drives:
  Local Storage: total: 931.51 GiB used: 192.83 GiB (20.7%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 980 1TB
    size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: 1B4QFXO7 temp: 36.9 C
    scheme: GPT
Partition:
  ID-1: / raw-size: 438 GiB size: 438 GiB (100.00%) used: 192.78 GiB (44.0%)
    fs: btrfs dev: /dev/nvme0n1p7 maj-min: 259:7
  ID-2: /boot/efi raw-size: 389 MiB size: 388.2 MiB (99.80%)
    used: 48.7 MiB (12.5%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
  ID-3: /home raw-size: 438 GiB size: 438 GiB (100.00%)
    used: 192.78 GiB (44.0%) fs: btrfs dev: /dev/nvme0n1p7 maj-min: 259:7
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: yes
    compressor: zstd max-pool: 20%
  ID-1: swap-1 type: partition size: 16.57 GiB used: 0 KiB (0.0%)
    priority: -2 dev: /dev/nvme0n1p8 maj-min: 259:8
Sensors:
  System Temperatures: cpu: 51.0 C pch: 45.0 C mobo: 42.0 C
  Fan Speeds (rpm): cpu: 0 fan-2: 0
Info:
  Memory: total: 16 GiB note: est. available: 15.26 GiB used: 4.11 GiB (26.9%)
  Processes: 360 Power: uptime: 30m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 2 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 6.09 GiB services: gsd-power,upowerd
    Init: systemd v: 257 default: graphical tool: systemctl
  Packages: pm: pacman pkgs: 2014 libs: 418 tools: gnome-software,yay
    pm: flatpak pkgs: 0 Compilers: clang: 20.1.8 gcc: 15.2.1 Shell: Bash v: 5.3.3
    running-in: ghostty inxi: 3.3.39

Relevant package versions:

linux-lts 6.12.47-1
nvidia-lts 1:580.82.09-2
gdm 48.0-2
gnome-shell 1:48.4-1

Configuration
I've configured my initramfs to early load the intel_agp and i915 modules, but not the nvidia- ones. Adding those caused resuming from hibernation to fail.

MODULES=(intel_agp i915)
HOOKS=(base udev autodetect microcode modconf block btrfs filesystems keyboard resume fsck)

I don't think they're the cause of this, but my kernel parameters are set to:

loglevel=3 resume=UUID=ba0d0be8-0b83-47f1-9f3e-f62bf149055e mem_sleep_default=deep i915.enable_psr=0

Thanks in advance for any help.

seth · 2025-09-13 15:23:31

Is this gnome/GDM specific?
https://bbs.archlinux.org/viewtopic.php … 2#p2261132

this only happens on resume from suspend-then-hibernate

Do you have the nvidia modules in the initramfs?

rmeno12 · 2025-09-13 15:37:38

Is this gnome/GDM specific?

I'm not sure. I'll try installing KDE and seeing if the same issue exists unless there's a better way to test. Will update once I try that.
UPDATE: I installed `plasma-desktop` and still see the same issues. However, KDE is still launched from GDM, so that's not eliminated yet.

Do you have the nvidia modules in the initramfs?

No, I don't have them. I tried that as a solution earlier, but it causes resuming from hibernation to fail:

Sep 13 08:28:21 rahul-xps kernel: NVRM: GPU 0000:01:00.0: PreserveVideoMemoryAllocations module parameter is set. System Power Management attempted without driver procfs suspend interface. Please refer to the 'Configuring Power Management Support' section in the driver README.
Sep 13 08:28:21 rahul-xps kernel: nvidia 0000:01:00.0: PM: pci_pm_freeze(): nv_pmops_freeze [nvidia] returns -5
Sep 13 08:28:21 rahul-xps kernel: nvidia 0000:01:00.0: PM: dpm_run_callback(): pci_pm_freeze returns -5
Sep 13 08:28:21 rahul-xps kernel: nvidia 0000:01:00.0: PM: failed to quiesce async: error -5
Sep 13 08:28:21 rahul-xps kernel: nvme nvme0: D3 entry latency set to 8 seconds
Sep 13 08:28:21 rahul-xps kernel: nvme nvme0: 12/0/0 default/read/poll queues
Sep 13 08:28:21 rahul-xps kernel: ata3: SATA link down (SStatus 4 SControl 300)
Sep 13 08:28:21 rahul-xps kernel: PM: hibernation: Failed to load image, recovering.

However, I do have the relevant nvidia power management systemd units enabled and working:

$ sudo systemctl status nvidia-resume.service nvidia-suspend.service nvidia-suspend-then-hibernate.service nvidia-hibernate.service
○ nvidia-resume.service - NVIDIA system resume actions
     Loaded: loaded (/usr/lib/systemd/system/nvidia-resume.service; enabled; preset: disabled)
     Active: inactive (dead)

Sep 13 09:12:48 rahul-xps systemd[1]: Starting NVIDIA system resume actions...
Sep 13 09:12:48 rahul-xps suspend[2592]: nvidia-resume.service
Sep 13 09:12:48 rahul-xps logger[2592]: <13>Sep 13 09:12:48 suspend: nvidia-resume.service
Sep 13 09:12:48 rahul-xps systemd[1]: nvidia-resume.service: Deactivated successfully.
Sep 13 09:12:48 rahul-xps systemd[1]: Finished NVIDIA system resume actions.

○ nvidia-suspend.service - NVIDIA system suspend actions
     Loaded: loaded (/usr/lib/systemd/system/nvidia-suspend.service; enabled; preset: disabled)
     Active: inactive (dead)

○ nvidia-suspend-then-hibernate.service - NVIDIA actions for suspend-then-hibernate
     Loaded: loaded (/usr/lib/systemd/system/nvidia-suspend-then-hibernate.service; enabled; preset: disabled)
     Active: inactive (dead)

Sep 13 09:13:01 rahul-xps systemd[1]: Starting NVIDIA actions for suspend-then-hibernate...
Sep 13 09:13:01 rahul-xps suspend[2763]: nvidia-suspend-then-hibernate.service
Sep 13 09:13:01 rahul-xps logger[2763]: <13>Sep 13 09:13:01 suspend: nvidia-suspend-then-hibernate.service
Sep 13 09:13:02 rahul-xps systemd[1]: nvidia-suspend-then-hibernate.service: Deactivated successfully.
Sep 13 09:13:02 rahul-xps systemd[1]: Finished NVIDIA actions for suspend-then-hibernate.
Sep 13 09:29:07 rahul-xps systemd[1]: Starting NVIDIA actions for suspend-then-hibernate...
Sep 13 09:29:07 rahul-xps suspend[5651]: nvidia-suspend-then-hibernate.service
Sep 13 09:29:07 rahul-xps logger[5651]: <13>Sep 13 09:29:07 suspend: nvidia-suspend-then-hibernate.service
Sep 13 09:29:09 rahul-xps systemd[1]: nvidia-suspend-then-hibernate.service: Deactivated successfully.
Sep 13 09:29:09 rahul-xps systemd[1]: Finished NVIDIA actions for suspend-then-hibernate.

○ nvidia-hibernate.service - NVIDIA system hibernate actions
     Loaded: loaded (/usr/lib/systemd/system/nvidia-hibernate.service; enabled; preset: disabled)
     Active: inactive (dead)

Sep 13 09:11:53 rahul-xps systemd[1]: Starting NVIDIA system hibernate actions...
Sep 13 09:11:53 rahul-xps hibernate[2404]: nvidia-hibernate.service
Sep 13 09:11:53 rahul-xps logger[2404]: <13>Sep 13 09:11:53 hibernate: nvidia-hibernate.service
Sep 13 09:11:54 rahul-xps systemd[1]: nvidia-hibernate.service: Deactivated successfully.
Sep 13 09:11:54 rahul-xps systemd[1]: Finished NVIDIA system hibernate actions.

Last edited by rmeno12 (2025-09-13 15:46:16)

seth · 2025-09-13 16:15:50

nb that if you're using GDM that sorta implies gnome-shell and idk whether the other user moved away from that as well.
In doubt just boot the multi-user.target (2nd link below) and manually start plasma from there.

but it causes resuming from hibernation to fail

Hence the question

rmeno12 · 2025-09-13 16:49:14

I actually just tested from only multi-user.target without starting any graphical session at all and the same issue persists. I see a black screen with a blinking cursor until I manually switch into a tty (in this case tty1 with ctrl-alt-f1). The log for this is at https://pastebin.com/2HqjcEeC. In this, I first suspended, then hibernated, then did suspend-then-hibernate, so all of those should be visible in that log.

Hence the question

I'm not sure what you mean. I do not have the nvidia modules in the initramfs.

seth · 2025-09-13 18:59:33

I asked because that would become a problem w/ hibernation specifically - all good.

The other thread suggested that *only* running KDE (possibly some specific display server) would fix this while for the multi-user.target facing the symptoms of your OP (and w/ gnome actually not getting the framebuffer back at all but for a reboot)

rmeno12 · 2025-09-13 19:30:32

So since the issue still happens without starting a graphical session, I'm thinking it's something deeper, but I don't know where to look on that since there are no errors in the log.
For now, I can test two more things: testing using just the console under the mainline kernel instead of lts; and using KDE from multi-user.target instead of GDM. Anything else?

seth · 2025-09-13 20:35:06

Mostly "using KDE from multi-user.target instead of GDM" to see whether you're in the same boat as the other thread.
Can you disable the nvidia GPU?

rmeno12 · 2025-09-14 13:47:34

Here's the log of just launching KDE from the console: https://pastebin.com/HkLzTnxZ. The same issue is present.

Can you disable the nvidia GPU?

As a debug measure, sure, if you can point me to some instructions. I've seen these instructions on the wiki and have also heard of envycontrol/bumblebee type management tools.
In general, though, I'd like to keep using the nvidia GPU (which I do currently through prime-run for things like games).

seth · 2025-09-14 13:53:55

Ideally in the UEFI (use internal GPU only or sth. like that) and yes, it's meant for debugging.

rmeno12 · 2025-09-14 14:31:37

My laptop doesn't have UEFI options to do that. Is the udev rule method the next best thing?

UPDATE: Disabling the nvidia gpu with the udev rules does fix the issue.

Last edited by rmeno12 (2025-09-14 14:45:19)

seth · 2025-09-15 19:45:21

Sorry for the delay

UPDATE: Disabling the nvidia gpu with the udev rules does fix the issue.

do yo still have the journal for that attempt?

As far as I can tell, this only happens on resume from suspend-then-hibernate. On resuming from just suspend or just hibernate, the flashing cursor shows for a second or two then goes to the GNOME lock screen, and a clean boot works without issues.

I kinda wonder how much

Sep 13 09:29:09 rahul-xps systemd-sleep[5693]: User sessions remain unfrozen on explicit request ($SYSTEMD_SLEEP_FREEZE_USER_SESSIONS=0).
Sep 13 09:29:09 rahul-xps systemd-sleep[5693]: This is not recommended, and might result in unexpected behavior, particularly
Sep 13 09:29:09 rahul-xps systemd-sleep[5693]: in suspend-then-hibernate operations or setups with encrypted home directories.

relates to this, you might test nouveau or simply allowing the freeze
https://gitlab.archlinux.org/archlinux/ … type=heads

usr/lib/systemd/system/systemd-hibernate.service.d/10-nvidia-no-freeze-session.conf
usr/lib/systemd/system/systemd-homed.service.d/10-nvidia-no-freeze-session.conf
usr/lib/systemd/system/systemd-hybrid-sleep.service.d/10-nvidia-no-freeze-session.conf
usr/lib/systemd/system/systemd-suspend-then-hibernate.service.d/10-nvidia-no-freeze-session.conf
usr/lib/systemd/system/systemd-suspend.service.d/10-nvidia-no-freeze-session.conf

rmeno12 · 2025-09-15 23:49:29

Journal from when the nvidia card was disabled: https://pastebin.com/n9XT3eRR

I'll try allowing the freeze and report back when I can.

seth · 2025-09-16 06:40:14

If that alone doesn't help, next to that and disabling the nvidia GPU also disable

Sep 14 09:42:24 rahul-xps suspend[2802]: nvidia-suspend.service
Sep 14 09:42:24 rahul-xps logger[2802]: <13>Sep 14 09:42:24 suspend: nvidia-suspend.service
Sep 14 09:42:24 rahul-xps systemd[1]: nvidia-suspend.service: Deactivated successfully.
Sep 14 09:42:38 rahul-xps suspend[2917]: nvidia-resume.service
Sep 14 09:42:38 rahul-xps logger[2917]: <13>Sep 14 09:42:38 suspend: nvidia-resume.service
Sep 14 09:42:38 rahul-xps systemd[1]: nvidia-resume.service: Deactivated successfully.
Sep 14 09:42:53 rahul-xps suspend[3060]: nvidia-suspend-then-hibernate.service
Sep 14 09:42:53 rahul-xps logger[3060]: <13>Sep 14 09:42:53 suspend: nvidia-suspend-then-hibernate.service
Sep 14 09:42:54 rahul-xps systemd[1]: nvidia-suspend-then-hibernate.service: Deactivated successfully.
Sep 14 09:43:22 rahul-xps hibernate[3250]: nvidia-hibernate.service
Sep 14 09:43:22 rahul-xps logger[3250]: <13>Sep 14 09:43:22 hibernate: nvidia-hibernate.service
Sep 14 09:43:22 rahul-xps systemd[1]: nvidia-hibernate.service: Deactivated successfully.
Sep 14 09:44:21 rahul-xps suspend[3332]: nvidia-resume.service
Sep 14 09:44:21 rahul-xps logger[3332]: <13>Sep 14 09:44:21 suspend: nvidia-resume.service
Sep 14 09:44:21 rahul-xps systemd[1]: nvidia-resume.service: Deactivated successfully.

resp. just remove the nvidia packages when disabling the GPU.

rmeno12 · 2025-09-17 12:52:21

Disabling the freeze didn't help, unfortunately. Journal: https://pastebin.com/TyHu9CMw.

What does disabling the nvidia services or removing the nvidia package do when the nvidia gpu is disabled? Disabling the nvidia gpu already solves the issue.

seth · 2025-09-17 13:21:16

Disabling the nvidia gpu with the udev rules does fix the issue.

My brain read a "not" into that…

In this case try to disable the services and flip the parameter so we can see whether that's where this is coming from.
https://wiki.archlinux.org/title/NVIDIA … er_suspend
"nvidia.NVreg_PreserveVideoMemoryAllocations=0", https://wiki.archlinux.org/title/Kernel_parameters

systemctl disable --now nvidia-suspend.service
systemctl disable --now  nvidia-hibernate.service
systemctl disable --now  nvidia-resume.service

nb. the GDM related caveat in the wiki, you might have to https://wiki.archlinux.org/title/GDM#Wa … DIA_driver

rmeno12 · 2025-09-23 23:46:24

Sorry for the long delay; I've been quite busy recently.

I haven't had the chance to test the service/parameter suggestion above, but in the interim I did a full system update.
Now, instead of just the black screen with the flashing cursor, I see this error message repeated twice:

ACPI: PM: Hardware changed while hibernated, success doubtful!

These are followed by the flashing cursor. As before, switching to tty2 manually brings me to the gnome lock screen with no obvious errors.

seth · 2025-09-24 18:54:39

ACPI: PM: Hardware changed while hibernated, success doubtful!

How? Do you un/dock the system or add/remove devices? You're not booting another OS while linux is hibernated, do you?

If none of the above and because of the special condition: it seems you're loosing some hardware (at least temporarily) when waking from the suspend? Do you unload modules or are there related errors/warning when just suspending the system (no hibernation)?

Arch Linux

#1 2025-09-13 14:51:26

Black screen with cursor on resume from suspend-then-hibernate

#2 2025-09-13 15:23:31

Re: Black screen with cursor on resume from suspend-then-hibernate

#3 2025-09-13 15:37:38

Re: Black screen with cursor on resume from suspend-then-hibernate

#4 2025-09-13 16:15:50

Re: Black screen with cursor on resume from suspend-then-hibernate

#5 2025-09-13 16:49:14

Re: Black screen with cursor on resume from suspend-then-hibernate

#6 2025-09-13 18:59:33

Re: Black screen with cursor on resume from suspend-then-hibernate

#7 2025-09-13 19:30:32

Re: Black screen with cursor on resume from suspend-then-hibernate

#8 2025-09-13 20:35:06

Re: Black screen with cursor on resume from suspend-then-hibernate

#9 2025-09-14 13:47:34

Re: Black screen with cursor on resume from suspend-then-hibernate

#10 2025-09-14 13:53:55

Re: Black screen with cursor on resume from suspend-then-hibernate

#11 2025-09-14 14:31:37

Re: Black screen with cursor on resume from suspend-then-hibernate

#12 2025-09-15 19:45:21

Re: Black screen with cursor on resume from suspend-then-hibernate

#13 2025-09-15 23:49:29

Re: Black screen with cursor on resume from suspend-then-hibernate

#14 2025-09-16 06:40:14

Re: Black screen with cursor on resume from suspend-then-hibernate

#15 2025-09-17 12:52:21

Re: Black screen with cursor on resume from suspend-then-hibernate

#16 2025-09-17 13:21:16

Re: Black screen with cursor on resume from suspend-then-hibernate

#17 2025-09-23 23:46:24

Re: Black screen with cursor on resume from suspend-then-hibernate

#18 2025-09-24 18:54:39

Re: Black screen with cursor on resume from suspend-then-hibernate

Board footer