System doesn't come back from suspend

Hello everyone,

Earlier today, I found a post about a Nvidia system that doesn’t resume properly from suspend/hibernation. I commented on that post (since the recommendation is to check old posts first, right?). But for some reason I don’t understand, my reply was deleted, and I wasn’t even able to create a new post.

So, here’s my problem: when I suspend the system, the fans keep spinning and it doesn’t wake up.

I need help. I checked all recent posts with the same issue, but no luck.

I cannot offer much comment on this as your last post is shown as being five months ago.

However, it is more than possible that you found a topic that had been abandoned for some time. In those cases, a topic may be closed by Moderation staff without any warning.

Additionally, adding one’s own issue to that of another member’s Support topic is generally discouraged; as are so-called “me too” comments.

Members are expected to be aware of and adhere to Forum Rules as a condition of using the Manjaro Forum.

Some common examples:

Most are simply common sense to anyone who appreciates the difference between a Support forum and Facebook (and other online chat services).


And that, I’m afraid, doesn’t provide others much to work with.

Please provide (at a minimum) your system information as described (below); this is expected with each Support topic.

I’d further recommend removing the preamble/complaint/rant at the beginning of your first post as it detracts from the actual issue, and is likewise discouraged.

Focus on your issue. Add as much detail as you can find that might assist others wishing to help. Simply indicating a problem is seldom enough information to work with.

It’s good that you used the forum Search (many don’t bother at all, and demand help without investing any effort themselves).

In this case you say you didn’t discover anything that helped, but what did you try? If you don’t share detail like this, others will only repeat the same possible fixes that haven’t worked for you.

I’m sure someone will help when they are able.

Regards.


Welcome to the Manjaro community

As a new or infrequent forum user, please take some time to familiarise yourself with Forum requirements, and the many ways to use the forum to your benefit.

To that end, links are provided (below) - Please use them.


Be prepared to provide outputs from various commands when asked. It’s equally important to provide as much actionable information as possible in your first post, rather than simply indicating there is a problem.

Waiting for others to blindly ask questions can be counter-productive – typically, nobody has a :crystal_ball: at their disposal – Instead, please help others to make informed suggestions, based on information you provide.


Update Announcements

The Update Announcements contain important information and a Known Issues and Solutions section that should generally be checked before posting a request for support.

System Information

While information from *-fetch type apps might be fine for someone wishing to buy your computer, for Support purposes it’s better to ask your system directly; :eyes:

Output of the inxi command (with appropriate parameters, and formatted according to forum guidelines) will generate information useful for those wishing to help:

inxi --filter --verbosity=8

or the short form (preferred):

inxi -zv8
Highly Recommended
Technical Resources
Required Reading

My post is shown from five months ago because the post I made yesterday was deleted.

I have been a member since 2022, and I know a good part of the rules. I posted on an old post (March 30) because it was the same problem, and I took the same steps (with no success). I only mentioned this because it was very annoying: they just deleted a post from someone who is having a problem.

But, let’s move on.

System info:


System:
  Kernel: 6.12.48-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.12-x86_64
    quiet udev.log_priority=3
  Desktop: GNOME v: 48.5 tk: GTK v: 3.24.50 wm: gnome-shell
    tools: gsd-screensaver-proxy dm: GDM v: 48.0 Distro: Manjaro
    base: Arch Linux
Machine:
  Type: Desktop Mobo: ASUSTeK model: PRIME B450M-GAMING/BR v: Rev X.0x
    serial: <superuser required> part-nu: SKU uuid: <superuser required>
    UEFI-[Legacy]: American Megatrends v: 2202 date: 07/14/2020
Battery:
  Message: No system battery data found. Is one present?
Memory:
  System RAM: total: 16 GiB available: 15.55 GiB used: 4.48 GiB (28.8%)
  Message: For most reliable report, use superuser + dmidecode.
  Array-1: capacity: 128 GiB slots: 4 modules: 2 EC: None
    max-module-size: 32 GiB note: est.
  Device-1: DIMM_A1 type: no module installed
  Device-2: DIMM_A2 type: DDR4 detail: synchronous unbuffered (unregistered)
    size: 8 GiB speed: 2666 MT/s volts: note: check curr: 1 min: 1 max: 1
    width (bits): data: 64 total: 64 manufacturer: Kingston
    part-no: KHX2666C16/8G serial: <filter>
  Device-3: DIMM_B1 type: no module installed
  Device-4: DIMM_B2 type: DDR4 detail: synchronous unbuffered (unregistered)
    size: 8 GiB speed: 2666 MT/s volts: note: check curr: 1 min: 1 max: 1
    width (bits): data: 64 total: 64 manufacturer: Kingston
    part-no: KHX2666C16/8G serial: <filter>
PCI Slots:
  Permissions: Unable to run dmidecode. Root privileges required.
CPU:
  Info: model: AMD Ryzen 5 1600 bits: 64 type: MT MCP arch: Zen+ gen: 1+
    level: v3 note: check built: 2018-21 process: GF 12nm family: 0x17 (23)
    model-id: 8 stepping: 2 microcode: 0x800820D
  Topology: cpus: 1x dies: 1 clusters: 1 cores: 6 threads: 12 tpc: 2
    smt: enabled cache: L1: 576 KiB desc: d-6x32 KiB; i-6x64 KiB L2: 3 MiB
    desc: 6x512 KiB L3: 16 MiB desc: 2x8 MiB
  Speed (MHz): avg: 1547 min/max: 1550/3200 boost: enabled scaling:
    driver: acpi-cpufreq governor: schedutil cores: 1: 1547 2: 1547 3: 1547
    4: 1547 5: 1547 6: 1547 7: 1547 8: 1547 9: 1547 10: 1547 11: 1547 12: 1547
    bogomips: 76671
  Flags: 3dnowprefetch abm adx aes aperfmperf apic arat avic avx avx2 bmi1
    bmi2 bpext clflush clflushopt clzero cmov cmp_legacy constant_tsc cpb
    cpuid cr8_legacy cx16 cx8 de decodeassists extapic extd_apicid f16c
    flushbyasid fma fpu fsgsbase fxsr fxsr_opt ht hw_pstate ibpb lahf_lm lbrv
    lm mca mce misalignsse mmx mmxext monitor movbe msr mtrr mwaitx
    nonstop_tsc nopl npt nrip_save nx osvw overflow_recov pae pat pausefilter
    pclmulqdq pdpe1gb perfctr_core perfctr_llc perfctr_nb pfthreshold pge pni
    popcnt pse pse36 rapl rdrand rdseed rdtscp rep_good sep sev sev_es sha_ni
    skinit smap smca smep ssbd sse sse2 sse4_1 sse4_2 sse4a ssse3 succor svm
    svm_lock syscall tce topoext tsc tsc_scale v_vmsave_vmload vgif
    vmcb_clean vme vmmcall wdt xgetbv1 xsave xsavec xsaveerptr xsaveopt
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: indirect_target_selection status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed mitigation: untrained return thunk; SMT vulnerable
  Type: spec_rstack_overflow mitigation: Safe RET
  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: Retpolines; IBPB: conditional; STIBP:
    disabled; RSB filling; PBRSB-eIBRS: Not affected; BHI: Not affected
  Type: srbds status: Not affected
  Type: tsa status: Not affected
  Type: tsx_async_abort status: Not affected
  Type: vmscape mitigation: IBPB before exit to userspace
Graphics:
  Device-1: NVIDIA GP107 [GeForce GTX 1050 Ti] vendor: ASUSTeK 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: Pascal code: GP10x
    process: TSMC 16nm built: 2016-2021 pcie: gen: 3 speed: 8 GT/s lanes: 16
    ports: active: HDMI-A-1 empty: DP-1,DVI-D-1 bus-ID: 08:00.0
    chip-ID: 10de:1c82 class-ID: 0300
  Display: wayland server: X.org v: 1.21.1.18 with: Xwayland v: 24.1.8
    compositor: gnome-shell driver: X: loaded: nvidia
    gpu: nvidia,nvidia-nvswitch display-ID: 0
  Monitor-1: HDMI-A-1 model: LG (GoldStar) ULTRAWIDE serial: <filter>
    built: 2016 res: 2560x1080 dpi: 81 gamma: 1.2 chroma: red: x: 0.651 y: 0.333
    green: x: 0.306 y: 0.631 blue: x: 0.149 y: 0.059 white: x: 0.314 y: 0.329
    size: 798x334mm (31.42x13.15") diag: 869mm (34.2") modes: 2560x1080,
    1920x1080, 1680x1050, 1600x900, 1280x1024, 1280x800, 1152x864, 1280x720,
    1024x768, 800x600, 720x576, 720x480, 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: 580.82.09
    glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2
    memory: 3.91 GiB display-ID: :0.0
  API: Vulkan v: 1.4.321 layers: 9 device: 0 type: discrete-gpu name: NVIDIA
    GeForce GTX 1050 Ti driver: nvidia v: 580.82.09 device-ID: 10de:1c82
    surfaces: N/A
  Info: Tools: api: eglinfo, glxinfo, vulkaninfo de: kscreen-doctor
    gpu: nvidia-settings,nvidia-smi x11: xprop,xrandr
Audio:
  Device-1: NVIDIA GP107GL High Definition Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
    bus-ID: 08:00.1 chip-ID: 10de:0fb9 class-ID: 0403
  Device-2: Advanced Micro Devices [AMD] Family 17h HD Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
    bus-ID: 0a:00.3 chip-ID: 1022:1457 class-ID: 0403
  Device-3: Generalplus Usb Audio Device
    driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 1.1 speed: 12 Mb/s
    lanes: 1 mode: 1.1 bus-ID: 3-2:3 chip-ID: 1b3f:2008 class-ID: 0300
    serial: <filter>
  API: ALSA v: k6.12.48-1-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: PipeWire v: 1.4.8 status: active with: 1: pipewire-pulse
    status: active 2: pipewire-media-session status: active 3: pipewire-alsa
    type: plugin 4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli
Network:
  Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    vendor: ASUSTeK RTL8111H driver: r8169 v: kernel pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 port: f000 bus-ID: 07:00.0 chip-ID: 10ec:8168
    class-ID: 0200
  IF: enp7s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
    broadcast: <filter>
  Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
Bluetooth:
  Message: No bluetooth data found.
Logical:
  Message: No logical block device data found.
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 1.58 TiB used: 929.13 GiB (57.3%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Western Digital
    model: WD10EZEX-08WN4A0 size: 931.51 GiB block-size: physical: 4096 B
    logical: 512 B speed: 6.0 Gb/s tech: HDD rpm: 7200 serial: <filter>
    fw-rev: 1A02 scheme: GPT
  ID-2: /dev/sdb maj-min: 8:16 vendor: Western Digital
    model: WDS500G2B0A-00SM50 size: 465.76 GiB block-size: physical: 512 B
    logical: 512 B speed: 6.0 Gb/s tech: SSD serial: <filter> fw-rev: 20WD
    scheme: MBR
  ID-3: /dev/sdc maj-min: 8:32 vendor: Seagate model: WDC WDS240G2G0B-00EPW0
    size: 223.57 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 0400 scheme: GPT
  Message: No optical or floppy data found.
Partition:
  ID-1: / raw-size: 456.96 GiB size: 448.72 GiB (98.20%)
    used: 225.99 GiB (50.4%) fs: ext4 dev: /dev/sdb1 maj-min: 8:17 label: N/A
    uuid: d6ecda09-ff35-416a-9f44-94f281802154
  ID-2: /mnt/0730390f-64f7-4722-8644-0b147af0a682 raw-size: 931.51 GiB
    size: 915.82 GiB (98.31%) used: 703.14 GiB (76.8%) fs: ext4 dev: /dev/sda1
    maj-min: 8:1 label: HD uuid: 0730390f-64f7-4722-8644-0b147af0a682
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: partition size: 8.8 GiB used: 7 MiB (0.1%) priority: -2
    dev: /dev/sdb2 maj-min: 8:18 label: swap
    uuid: b1b7c693-1d50-44de-b647-e3f032335bfa
Unmounted:
  ID-1: /dev/sdc1 maj-min: 8:33 size: 223.57 GiB fs: ext4 label: SSD-VMS
    uuid: 0a8dbb6f-1615-4fe7-869d-f847134b304d
USB:
  Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 10 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-2: 2-0:1 info: super-speed hub ports: 4 rev: 3.1
    speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
    class-ID: 0900
  Hub-3: 3-0:1 info: hi-speed hub with single TT ports: 4 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Device-1: 3-1:2 info: Holtek Gaming Mouse [Redragon M711]
    type: mouse,keyboard,HID driver: hid-generic,usbhid interfaces: 3 rev: 2.0
    speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 100mA
    chip-ID: 04d9:fc30 class-ID: 0300
  Device-2: 3-2:3 info: Generalplus Usb Audio Device type: audio,HID
    driver: hid-generic,snd-usb-audio,usbhid interfaces: 3 rev: 1.1
    speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 100mA
    chip-ID: 1b3f:2008 class-ID: 0300 serial: <filter>
  Device-3: 3-4:4 info: Logitech G213 Prodigy Gaming Keyboard
    type: keyboard,HID driver: hid-generic,usbhid interfaces: 2 rev: 2.0
    speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 500mA
    chip-ID: 046d:c336 class-ID: 0300 serial: <filter>
  Hub-4: 4-0:1 info: super-speed hub ports: 4 rev: 3.0
    speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 chip-ID: 1d6b:0003
    class-ID: 0900
Sensors:
  System Temperatures: cpu: 42.4 C mobo: N/A
  Fan Speeds (rpm): N/A
Repos:
  Packages: 2221 pm: dpkg pkgs: 0 pm: pacman pkgs: 2153 libs: 569
    tools: gnome-software,pamac,yay pm: flatpak pkgs: 62 pm: snap pkgs: 6
  Active pacman repo servers in: /etc/pacman.d/mirrorlist
    1: https://manjaro.c3sl.ufpr.br/stable/$repo/$arch
Processes:
  CPU top: 5 of 374
  1: cpu: 25.3% command: firefox pid: 3879 mem: 1046.5 MiB (6.5%)
  2: cpu: 24.4% command: firefox pid: 4056 mem: 71.8 MiB (0.4%)
  3: cpu: 12.3% command: gnome-shell pid: 1696 mem: 504.5 MiB (3.1%)
  4: cpu: 8.4% command: zsh pid: 26358 mem: 10.8 MiB (0.0%)
  5: cpu: 3.2% command: firefox pid: 24151 mem: 374.4 MiB (2.3%)
  Memory top: 5 of 374
  1: mem: 1046.5 MiB (6.5%) command: firefox pid: 3879 cpu: 25.3%
  2: mem: 513.6 MiB (3.2%) command: firefox pid: 4225 cpu: 0.6%
  3: mem: 504.5 MiB (3.1%) command: gnome-shell pid: 1696 cpu: 12.3%
  4: mem: 499.0 MiB (3.1%) command: steamwebhelper pid: 2826 cpu: 0.2%
  5: mem: 398.1 MiB (2.5%) command: firefox pid: 4110 cpu: 0.9%
Info:
  Processes: 374 Power: uptime: 2h 7m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 6.21 GiB services: gsd-power,
    power-profiles-daemon, upowerd Init: systemd v: 257 default: graphical
    tool: systemctl
  Compilers: clang: 20.1.8 gcc: 15.2.1 alt: 14 Shell: Zsh v: 5.9
    running-in: gnome-terminal inxi: 3.3.39

What I’ve done so far:

I edited /etc/mkinitcpio.conf, and in the HOOKS line, I added “resume”:

HOOKS=(base udev autodetect microcode modconf keyboard keymap consolefont block filesystems fsck resume)

What I haven’t done yet:

In another post (the same one where my reply was deleted), they mentioned something about the UUID from swap in the /etc/default/grub file. If I remember correctly, the line with GRUB_CMDLINE_LINUX_DEFAULT needs to have this UUID.

My file is as follows:

GRUB_DEFAULT=saved
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR="Manjaro"
GRUB_CMDLINE_LINUX_DEFAULT="nvidia_drm.modeset=1 quiet udev.log_priority=3"
GRUB_CMDLINE_LINUX=""

I modified GRUB_CMDLINE_LINUX_DEFAULT in the past for a test.

So, I need help fixing this. I don’t know if the issue of my system not resuming from suspend is related to this grub file configuration, but I want to give it a try.

When I press “suspend,” my screen goes black, and the fans keep spinning. When I press any key on the keyboard or the power button, nothing happens.

Then my presumption was correct. The forum rules are quite clear when it comes to attempting to revive an abandoned topic – I do acknowledge some may miss the date of the last post, however, Moderation staff (as already noted) may close such a topic without warning.

For reference, the correct procedure would be to create your own topic, and refer to the other topic via a link – this holds true even if that topic has been closed or abandoned.

To use your example, in your first topic post you could include something like the following after explaining your problem;

“I found a similar issue in [link to another topic] and tried the steps they suggested (with no success). Any help will be appreciated. Thank you.”


Thank you for the additional detail.

Hopefully someone with some insight will offer assistance when they are able.

Regards.

Can you link to the post so we have an idea of what was suggested and why?

Generally yes, and if you created a swap partition when you installed Manjaro it usually adds this for you. You can obtain the UUID of the swap partition with the blkid command. Then add resume=UUID=xxxxxxxxxxxxxxx replacing xxxxxxxx’s with your UUID from the blkid command.

Once you have edited /etc/default/grub you’ll need to update-grub to write that information to your root folder. Reboot then try suspending and resuming. Whatever the result, you’ll then want to check your system log for info regarding the suspend and resume. Something like journalctl -b | grep suspend.

1 Like

I was the one who did that, because you’ve been a member here long enough to have read the rules and to know that necro-bumping and hijacking somebody else’s thread are against the rules.

The proper course of action would have been to start a new thread.

1 Like

I was just tryind to be more objective. No intentional. Yes, I readed the rules, but my access to the forum are being just in cause of updates or problems (which I almost don’t have).

Not going to repeat anyway.

Thank you and to the team all the suport. Manjaro it is my main system since 2022, no big issues until today.

I will try insert the UUID of the swap partition and provide feedback, when I test on my desktop.

Hello.

In my first attempt, adding:

GRUB_CMDLINE_LINUX_DEFAULT="nvidia_drm.modeset=1 quiet udev.log_priority=3 resume=UUID=b1b7c693-1d50-44de-b647-e3f032335bfa"

in the “/etc/default/grub“ file seems to worked, but now it’s the same. When I press “Suspend”, video turns off, but the fans, keyboard light and everything elses keep working. The worst thing is: even pressing any key or even the power button, the system don’t come back.

Still need help.

Are you trying to suspend (suspend to ram) or hibernate (suspend to disk)? You need that resume config for hibernating not suspending.

If you’re hibernating then it may be copying stuff from RAM to the disk, especially if the fans ramp up.

How long have you left it running for?
If you leave it, does it eventually shutdown?


Sometimes you may need to enable or disable some services. If they’re already enabled then try disabling them, and vice versa.

systemctl status nvidia-suspend.service nvidia-hibernate.service nvidia-resume.service

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

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

Just suspend

Sometimes even 10 minutes, and nothing happens. Even if I just started the system.

So I can just remove “resume“?

The output status from service is:

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

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

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

I disabled before trying enabling again.
When enabling, the screen turned off. On first time, it came back but the system was very slow. On second attempt, just turned black and don’t came back

EDIT:

On the link from ArchWiki, I checked the output from “cat /sys/power/mem_sleep“

$ cat /sys/power/mem_sleep
s2idle [deep]

Don’t know if it can bring any idea, but it is here anyway

Does your system actually support S3 (STR)?

Many recent laptops either do not, or it’s blocked in BIOS to appease Microsoft.

If you want.

I assume we’re on the same page, but just to be clear I’m talking about the changes in /etc/default/grub and /etc/mkinitcpio.conf.

Did you try suspending with them disabled?

I’ve seen one or two posts that said disabling them worked. If that doesn’t work then you could try preserving video memory as stated in the nvidia tips and tricks link I posted.

You could also try different kernels to see if that makes a difference.

If that doesn’t work then you could test with s2idle. :man_shrugging:

inxi says it’s a desktop, but there could still be an issue with S3.

Yep, this files

Not yet. For me it will only work enable: dind’t know that can work disabled. I will try and give feedback.

Yes, it is a desktop

Yes. The screen turn black, the keyboard blinks and screen turn on on lockscreen. I think this Nvidia process is essential to Suspend mode.

Yep, but it don’t make sense. After inserting “resume” in /etc/default/grub, Suspend worked in first test, but after that stays the same. If the problem was in “deep” mode, it will never work.

Made a test here, and same thing, system looks like keep running. The disk led keeps blinking, even with no video and no reaction pressing the keyboard.

So, I copy the log from journalctl -r

out 21 22:39:03 dwightspc kernel: Linux version 6.12.48-1-MANJARO (linux612@manjaro) (gcc (GCC) 15.2.1 20250813, GNU ld (GNU Binutils) 2.45.0) #1 SMP PREEMPT_DYNAMIC Fri, 19 Sep 2025 16:11:04 +0000
-- Boot ce08cd1249604c0c0000000000000000 --
-- Boot ce08cd1249604c0ca10212c0e379db6c -- ### MOMENT WHEN SYSTEM REBOOT, MANUALLY BY ME
out 21 22:38:28 dwightspc kernel: [UFW BLOCK] IN=enp7s0 OUT= SRC=2a04:4e42:0000:0000:0000:0000:0000:0347 DST=2804:58d8:0e03:4842:839d:221d:5a18:435e LEN=96 TC=0 HOPLIMIT=53 >
out 21 22:38:28 dwightspc kernel: [UFW BLOCK] IN=enp7s0 OUT= SRC=2a04:4e42:0000:0000:0000:0000:0000:0347 DST=2804:58d8:0e03:4842:839d:221d:5a18:435e LEN=123 TC=0 HOPLIMIT=53>
out 21 22:38:23 dwightspc kernel: [UFW BLOCK] IN=enp7s0 OUT=  SRC=34.120.208.123 DST=10.0.0.199 LEN=125 TOS=0x00 PREC=0x00 TTL=119 ID=60812 PROTO=TCP SPT=443 DPT=51648 WINDOW>
out 21 22:38:22 dwightspc systemd[1]: Starting Network Manager Script Dispatcher Service...
out 21 22:38:22 dwightspc NetworkManager[768]: <info>  [] device (enp7s0): state change: ip-config -> ip-check (reason 'none', managed-type: 'full')
out 21 22:38:22 dwightspc NetworkManager[768]: <info>  [] policy: set '' (enp7s0) as default for IPv4 routing and DNS
out 21 22:38:22 dwightspc NetworkManager[768]: <info>  [] dhcp4 (enp7s0): state changed new lease, address=
out 21 22:38:22 dwightspc NetworkManager[768]: <info>  [1] dhcp4 (enp7s0): state changed new lease, address=, acd pending
out 21 22:38:21 dwightspc NetworkManager[768]: <info>  [] policy: set 'Soli Deo Gloria' (enp7s0) as default for IPv6 routing and DNS
out 21 22:38:21 dwightspc NetworkManager[768]: <info>  [] dhcp6 (enp7s0): activation: beginning transaction (timeout in 45 seconds)
out 21 22:38:20 dwightspc ModemManager[831]: <msg> [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:01.3/0000:01:00.2/0000:02:07.0/0000:07:00.0': not supported by any plugin
out 21 22:38:20 dwightspc NetworkManager[768]: <info>  [] dhcp4 (enp7s0): activation: beginning transaction (timeout in 45 seconds)
out 21 22:38:20 dwightspc NetworkManager[768]: <info>  [] device (enp7s0): state change: config -> ip-config (reason 'none', managed-type: 'full')
out 21 22:38:20 dwightspc NetworkManager[768]: <info>  [1761097100.1771] device (enp7s0): state change: prepare -> config (reason 'none', managed-type: 'full')
out 21 22:38:20 dwightspc NetworkManager[768]: <info>  [1761097100.1769] manager: NetworkManager state is now CONNECTING
out 21 22:38:20 dwightspc NetworkManager[768]: <info>  [1761097100.1765] device (enp7s0): state change: disconnected -> prepare (reason 'none', managed-type: 'full')
out 21 22:38:20 dwightspc NetworkManager[768]: <info>  [1761097100.1763] device (enp7s0): Activation: starting connection '' ()
out 21 22:38:20 dwightspc NetworkManager[768]: <info>  [1761097100.1756] policy: auto-activating connection '' ()
out 21 22:38:20 dwightspc NetworkManager[768]: <info>  [1761097100.1745] device (enp7s0): state change: unavailable -> disconnected (reason 'carrier-changed', managed-type: 'full')
out 21 22:38:20 dwightspc kernel: r8169 0000:07:00.0 enp7s0: Link is Up - 1Gbps/Full - flow control rx/tx
out 21 22:38:20 dwightspc NetworkManager[768]: <info>  [1761097100.1741] device (enp7s0): carrier: link connected
out 21 22:38:16 dwightspc kernel: r8169 0000:07:00.0 enp7s0: Link is Down
out 21 22:38:16 dwightspc NetworkManager[768]: <info>  [1761097096.8085] manager: NetworkManager state is now DISCONNECTED
out 21 22:38:16 dwightspc steam[1995]: [2025-10-21 22:38:16] Error: Failed to determine download location for universe 1
out 21 22:38:16 dwightspc kernel: Generic FE-GE Realtek PHY r8169-0-700:00: attached PHY driver (mii_bus:phy_addr=r8169-0-700:00, irq=MAC)
out 21 22:38:16 dwightspc systemd[1]: Starting NVIDIA system resume actions...
out 21 22:38:16 dwightspc NetworkManager[768]: <info>  [1761097096.6341] device (enp7s0): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')
out 21 22:38:16 dwightspc NetworkManager[768]: <info>  [1761097096.6340] manager: sleep: wake requested (sleeping: yes  enabled: yes)
out 21 22:38:16 dwightspc ModemManager[831]: <msg> [sleep-monitor-systemd] system is resuming
out 21 22:38:16 dwightspc systemd[1]: Stopped target Sleep.
out 21 22:38:16 dwightspc systemd-logind[772]: Operation 'suspend' finished.
out 21 22:38:16 dwightspc systemd[1]: systemd-suspend.service: Consumed 4min 13.299s CPU time, 2.6M memory peak.
out 21 22:38:16 dwightspc systemd[1]: suspend.target: Job suspend.target/start failed with result 'dependency'.
out 21 22:38:16 dwightspc systemd[1]: Dependency failed for Suspend.
out 21 22:38:16 dwightspc systemd[1]: Failed to start System Suspend.
out 21 22:38:16 dwightspc systemd[1]: systemd-suspend.service: Unit process 3759 (nvidia-sleep.sh) remains running after unit stopped.
out 21 22:38:16 dwightspc systemd[1]: systemd-suspend.service: Failed with result 'exit-code'.
out 21 22:38:16 dwightspc systemd[1]: systemd-suspend.service: Processes still around after final SIGKILL. Entering failed mode.
out 21 22:38:08 dwightspc steam[1995]: D3D12CreateDevice failed with error 0x80004005
out 21 22:38:08 dwightspc steam[1995]: Unable to read VR Path Registry from C:\users\steamuser\AppData\Local\openvr\openvrpaths.vrpath
out 21 22:38:08 dwightspc steam[1995]: Initializing D3D12.
out 21 22:38:02 dwightspc steam[1995]: reaping pid: 4580 -- srt-bwrap
out 21 22:37:55 dwightspc steam[1995]: wine: RLIMIT_NICE is <= 20, unable to use setpriority safely
out 21 22:37:55 dwightspc steam[1995]: fsync: up and running.
out 21 22:37:52 dwightspc systemd-coredump[4737]: Failed to initialize pidref from pid 4684: No such process
out 21 22:37:03 dwightspc kernel:  </TASK>
out 21 22:37:03 dwightspc kernel:  ret_from_fork_asm+0x1a/0x30
out 21 22:37:03 dwightspc kernel:  ? __pfx_kthread+0x10/0x10
out 21 22:37:03 dwightspc kernel:  ret_from_fork+0x34/0x50
out 21 22:37:03 dwightspc kernel:  ? __pfx_kthread+0x10/0x10
out 21 22:37:03 dwightspc kernel:  kthread+0xd2/0x100
out 21 22:37:03 dwightspc kernel:  ? __pfx_worker_thread+0x10/0x10
out 21 22:37:03 dwightspc kernel:  worker_thread+0x2d2/0x400
out 21 22:37:03 dwightspc kernel:  process_one_work+0x17f/0x340
out 21 22:37:03 dwightspc kernel:  drm_fb_helper_damage_work+0x8f/0x160
out 21 22:37:03 dwightspc kernel:  drm_fbdev_ttm_helper_fb_dirty+0xa3/0x320 [drm_ttm_helper c2caa0144069f1c2224e4071f2edf1d18b84e345]
out 21 22:37:03 dwightspc kernel:  ? psi_task_switch+0x113/0x2a0
out 21 22:37:03 dwightspc kernel:  __mutex_lock.constprop.0+0x31c/0x620
out 21 22:37:03 dwightspc kernel:  schedule_preempt_disabled+0x15/0x30
out 21 22:37:03 dwightspc kernel:  schedule+0x27/0xf0
out 21 22:37:03 dwightspc kernel:  __schedule+0x3cc/0x12f0
out 21 22:37:03 dwightspc kernel:  <TASK>
out 21 22:37:03 dwightspc kernel: Call Trace:
out 21 22:37:03 dwightspc kernel: Workqueue: events drm_fb_helper_damage_work
out 21 22:37:03 dwightspc kernel: task:kworker/3:2     state:D stack:0     pid:185   tgid:185   ppid:2      flags:0x00004000
out 21 22:37:03 dwightspc kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
out 21 22:37:03 dwightspc kernel:       Tainted: P           OE      6.12.48-1-MANJARO #1
out 21 22:37:03 dwightspc kernel: INFO: task kworker/3:2:185 blocked for more than 122 seconds.
out 21 22:37:00 dwightspc steam[1995]: reaping pid: 4424 -- srt-bwrap
out 21 22:36:56 dwightspc steam[1995]: wine: RLIMIT_NICE is <= 20, unable to use setpriority safely
out 21 22:36:56 dwightspc steam[1995]: fsync: up and running.
out 21 22:36:53 dwightspc steam[1995]: Proton: Prefix has an invalid version?! You may want to back up user files and delete this prefix.
out 21 22:36:53 dwightspc steam[1995]: Proton: Upgrading prefix from GE-Proton9-5 to GE-Proton8-4 (/home/dwightspenguin/.local/share/Steam/steamapps/compatdata/0/)
out 21 22:36:46 dwightspc systemd[1]: systemd-suspend.service: Killing process 3759 (nvidia-sleep.sh) with signal SIGKILL.
out 21 22:36:46 dwightspc systemd[1]: systemd-suspend.service: State 'final-sigterm' timed out. Killing.
out 21 22:36:04 dwightspc steam[1995]: wine: using kernel write watches, use_kernel_writewatch 1.
out 21 22:35:58 dwightspc steam[1995]: reaping pid: 4252 -- srt-bwrap
out 21 22:35:54 dwightspc steam[1995]: wine: using kernel write watches, use_kernel_writewatch 1.
out 21 22:35:53 dwightspc steam[1995]: wine: using kernel write watches, use_kernel_writewatch 1.
out 21 22:35:52 dwightspc steam[1995]: wine: using kernel write watches, use_kernel_writewatch 1.
out 21 22:35:52 dwightspc steam[1995]: wine: using kernel write watches, use_kernel_writewatch 1.
out 21 22:35:52 dwightspc steam[1995]: wine: using kernel write watches, use_kernel_writewatch 1.
out 21 22:35:52 dwightspc steam[1995]: wine: using kernel write watches, use_kernel_writewatch 1.
out 21 22:35:52 dwightspc steam[1995]: wine: using kernel write watches, use_kernel_writewatch 1.
out 21 22:35:52 dwightspc steam[1995]: fsync: up and running.
out 21 22:35:52 dwightspc steam[1995]: wine: using kernel write watches, use_kernel_writewatch 1.
out 21 22:35:16 dwightspc systemd[1]: systemd-suspend.service: Processes still around after SIGKILL. Ignoring.
out 21 22:35:12 dwightspc steam[1995]: wine: using kernel write watches, use_kernel_writewatch 1.
out 21 22:35:11 dwightspc steam[1995]: wine: configuration in L"/home/dwightspenguin/.local/share/Steam/steamapps/compatdata/0/pfx" has been updated.
out 21 22:35:11 dwightspc steam[1995]: wine: using kernel write watches, use_kernel_writewatch 1.
out 21 22:35:08 dwightspc steam[1995]: wine: using kernel write watches, use_kernel_writewatch 1.
out 21 22:35:08 dwightspc steam[1995]: wine: using kernel write watches, use_kernel_writewatch 1.
out 21 22:35:05 dwightspc steam[1995]: wine: using kernel write watches, use_kernel_writewatch 1.
out 21 22:34:56 dwightspc steam[1995]: reaping pid: 4084 -- srt-bwrap
out 21 22:34:55 dwightspc steam[1995]: wine: using kernel write watches, use_kernel_writewatch 1.
out 21 22:34:55 dwightspc steam[1995]: wine: using kernel write watches, use_kernel_writewatch 1.
out 21 22:34:54 dwightspc steam[1995]: wine: using kernel write watches, use_kernel_writewatch 1.
out 21 22:34:53 dwightspc steam[1995]: wine: using kernel write watches, use_kernel_writewatch 1.
out 21 22:34:53 dwightspc steam[1995]: wine: using kernel write watches, use_kernel_writewatch 1.
out 21 22:34:53 dwightspc steam[1995]: wine: using kernel write watches, use_kernel_writewatch 1.
out 21 22:34:53 dwightspc steam[1995]: wine: using kernel write watches, use_kernel_writewatch 1.
out 21 22:34:53 dwightspc steam[1995]: wine: using kernel write watches, use_kernel_writewatch 1.
out 21 22:34:53 dwightspc steam[1995]: fsync: up and running.
out 21 22:34:53 dwightspc steam[1995]: wine: using kernel write watches, use_kernel_writewatch 1.
out 21 22:34:50 dwightspc steam[1995]: Proton: Prefix has an invalid version?! You may want to back up user files and delete this prefix.
out 21 22:34:50 dwightspc steam[1995]: Proton: Upgrading prefix from GE-Proton10-3 to GE-Proton9-5 (/home/dwightspenguin/.local/share/Steam/steamapps/compatdata/0/)
out 21 22:34:46 dwightspc systemd[1]: systemd-timedated.service: Deactivated successfully.
out 21 22:34:34 dwightspc steam[1995]: reaping pid: 3778 -- srt-bwrap
out 21 22:34:24 dwightspc steam[1995]: reaping pid: 3932 -- srt-bwrap
out 21 22:34:17 dwightspc steam[1995]: [2025-10-21 22:34:17] Error: Failed to determine download location for universe 1
out 21 22:34:16 dwightspc systemd[1]: Started Time & Date Service.
out 21 22:34:16 dwightspc systemd[1]: Starting Time & Date Service...

Looks like a problem with some suspension service, but I don’t know which one.

Also, I kept the system running for some minutes after pressing “Suspend”, before I manually shutting down.
Still need some help anyway.

Did you remember to update the GRUB configuration after editing /etc/default/grub?

sudo update-grub

Yep, and this by itself don’t make effect.

Fresh news:

So, I tried to disable the hibernate service of Nvidia: systemctl disable --now nvidia-hibernate.service but it disabled Wayland on GDM. I checked /usr/lib/udev/rules.d/61-gdm.rules and when the hibernate services are disabled, Wayland got disabled too.

So, I enabled the hibernation service again to use Wayland again (it’s just better here). The problem is when Nvidia Hibernation Service are enabled.

Right now I have this options:

  1. Leave as it is, I don’t use suspension (not good)
  2. Comment the lines at /usr/lib/udev/rules.d/61-gdm.rules to ignore the rules and keep Wayland enabled with hibernation service from Nvidia disabled
  3. Investigate the problem related to Hibernation Service and try to fix it.

I am not understanding because am not using hibernation, just suspension. So, right now stills the same, but now I know what is causing problems.