Broken Suspend & Resume

Issues & Assistance Hyprland
1

Hey Guys,

i don’t know what to try anymore… i am on NVidia and installed Garuda Hyprland last month.

Everything is working beautifully but i can’t suspend & resume my system. First it would just be full of graphical bugs with xwayland windows. But when i restarted them it worked. No big deal…

One update later my hyprland would completely crash on resum and would throw me back into sddm…

Now with the latest update i can’t resume at all anymore! I just get black screens… my displays will turn on, tell me there is no signal and turn back off. They would do that 2-3 times until they will just stay on but completely black. Even another tty doesn’t work anymore. All i can do is restart…

I tried everything from this post: Garuda Hyprland doesn't lock the screen and doesn't go sleep in idle - #21

and also the power management steps on arch wiki NVIDIA/Tips and tricks - ArchWiki (i did try it WITH nvidia-resume.service and WITHOUT).

No luck for me… so maybe someone can point me in another helpful direction?

Thanks!

System:
  Kernel: 6.7.3-zen1-2-zen arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
    clocksource: tsc available: hpet,acpi_pm
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
    root=UUID=70298202-3941-4097-b3f6-9e9ab18d10bf rw rootflags=subvol=@
    "GRUB_CMDLINE_LINUX_DEFAULT=quiet
    resume=UUID=2a710883-dad9-4c61-a48e-9712c540943e loglevel=3"
    nvidia_drm.modeset=1 ibt=off
  Desktop: Hyprland info: waybar vt: 1 dm: SDDM Distro: Garuda Linux
    base: Arch Linux
Machine:
  Type: Desktop Mobo: ASUSTeK model: ROG STRIX X570-I GAMING v: Rev X.0x
    serial: <superuser required> UEFI: American Megatrends v: 4601
    date: 02/02/2023
CPU:
  Info: model: AMD Ryzen 7 5800X3D bits: 64 type: MT MCP arch: Zen 3+ gen: 4
    level: v3 note: check built: 2022 process: TSMC n6 (7nm) family: 0x19 (25)
    model-id: 0x21 (33) stepping: 2 microcode: 0xA20120A
  Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache:
    L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB desc: 8x512 KiB
    L3: 96 MiB desc: 1x96 MiB
  Speed (MHz): avg: 3556 high: 3840 min/max: 2200/4549 boost: enabled
    scaling: driver: acpi-cpufreq governor: performance cores: 1: 3584 2: 3598
    3: 3600 4: 3589 5: 3540 6: 3594 7: 3573 8: 3400 9: 3400 10: 3519 11: 3840
    12: 3549 13: 3582 14: 3537 15: 3400 16: 3597 bogomips: 108804
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities: <filter>
Graphics:
  Device-1: NVIDIA GA104 [GeForce RTX 3070] vendor: ASUSTeK driver: nvidia
    v: 545.29.06 alternate: nouveau,nvidia_drm non-free: 545.xx+ status: current
    (as of 2023-10; EOL~2026-12-xx) arch: Ampere code: GAxxx
    process: TSMC n7 (7nm) built: 2020-2023 pcie: gen: 3 speed: 8 GT/s
    lanes: 16 link-max: gen: 4 speed: 16 GT/s ports: active: none
    off: DP-1,DP-2 empty: DP-3,HDMI-A-1,HDMI-A-2 bus-ID: 0a:00.0
    chip-ID: 10de:2484 class-ID: 0300
  Display: wayland server: X.org v: 1.21.1.11 with: Xwayland v: 23.2.4
    compositor: Hyprland driver: X: loaded: nvidia unloaded: modesetting,nouveau
    alternate: fbdev,nv,vesa gpu: nvidia,nvidia-nvswitch display-ID: 1
  Monitor-1: DP-1 model: AOC U34G2G4R3 serial: <filter> built: 2020
    res: 3440x1440 hz: 144 dpi: 110 gamma: 1.2 scale: 1
    size: 797x334mm (31.38x13.15") diag: 864mm (34") modes: max: 3440x1440
    min: 640x480
  Monitor-2: DP-2 model: AOC 2460G5 serial: <filter> built: 2018
    res: 1920x1080 hz: 60 dpi: 92 gamma: 1.2 scale: 1
    size: 531x299mm (20.91x11.77") diag: 609mm (24") 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: zink inactive: device-1
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 545.29.06
    glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 3070/PCIe/SSE2
    memory: 7.81 GiB
  API: Vulkan v: 1.3.276 layers: 11 device: 0 type: discrete-gpu
    name: NVIDIA GeForce RTX 3070 driver: nvidia v: 545.29.06
    device-ID: 10de:2484 surfaces: xcb,xlib,wayland device: 1 type: cpu
    name: llvmpipe (LLVM 16.0.6 256 bits) driver: mesa llvmpipe
    v: 23.3.5-arch1.1 (LLVM 16.0.6) device-ID: 10005:0000
    surfaces: xcb,xlib,wayland
Audio:
  Device-1: NVIDIA GA104 High Definition Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
    link-max: gen: 4 speed: 16 GT/s bus-ID: 0a:00.1 chip-ID: 10de:228b
    class-ID: 0403
  Device-2: AMD Starship/Matisse HD Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
    bus-ID: 0c:00.4 chip-ID: 1022:1487 class-ID: 0403
  Device-3: SteelSeries ApS GameDAC driver: hid-generic,snd-usb-audio,usbhid
    type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-1.4.2:7
    chip-ID: 1038:1283 class-ID: 0300 serial: <filter>
  API: ALSA v: k6.7.3-zen1-2-zen status: kernel-api with: aoss
    type: oss-emulator tools: N/A
  Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
  Server-2: PipeWire v: 1.0.3 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 driver: iwlwifi v: kernel pcie: gen: 2
    speed: 5 GT/s lanes: 1 bus-ID: 05:00.0 chip-ID: 8086:2723 class-ID: 0280
  IF: wlp5s0 state: down mac: <filter>
  Device-2: Intel I211 Gigabit Network vendor: ASUSTeK driver: igb v: kernel
    pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: f000 bus-ID: 06:00.0
    chip-ID: 8086:1539 class-ID: 0200
  IF: enp6s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Bluetooth:
  Device-1: ASUSTek Broadcom BCM20702A0 Bluetooth driver: btusb v: 0.8
    type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-1.1.1:5
    chip-ID: 0b05:17cb class-ID: fe01 serial: <filter>
  Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 4.0
    lmp-v: 6 status: discoverable: yes pairing: yes class-ID: 6c0104
  Device-2: SINO WEALTH RK Bluetooth Keyboar driver: hid-generic,usbhid
    type: USB rev: 1.1 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 5-3.4:3
    chip-ID: 258a:0059 class-ID: 0300
Drives:
  Local Storage: total: 4.12 TiB used: 2.31 TiB (56.2%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/nvme0n1 maj-min: 259:2 vendor: Samsung
    model: SSD 970 EVO Plus 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: 2B2QEXM7 temp: 45.9 C scheme: GPT
  ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: SK Hynix
    model: HFM256GDHTNG-8310A size: 238.47 GiB block-size: physical: 512 B
    logical: 512 B speed: 15.8 Gb/s lanes: 2 tech: SSD serial: <filter>
    fw-rev: 80070C00 temp: 49.9 C scheme: MBR
  ID-3: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 870 EVO 2TB
    size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 2B6Q scheme: GPT
  ID-4: /dev/sdb maj-min: 8:16 vendor: Crucial model: CT1000MX500SSD1
    size: 931.51 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 033 scheme: GPT
  ID-5: /dev/sdc maj-min: 8:32 model: iSCSI Disk size: 250 GiB block-size:
    physical: 16384 B logical: 512 B tech: N/A serial: N/A fw-rev: 0123
    scheme: GPT
Partition:
  ID-1: / raw-size: 862.24 GiB size: 862.24 GiB (100.00%)
    used: 134.9 GiB (15.6%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:4
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 584 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:3
  ID-3: /home raw-size: 862.24 GiB size: 862.24 GiB (100.00%)
    used: 134.9 GiB (15.6%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:4
  ID-4: /var/log raw-size: 862.24 GiB size: 862.24 GiB (100.00%)
    used: 134.9 GiB (15.6%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:4
  ID-5: /var/tmp raw-size: 862.24 GiB size: 862.24 GiB (100.00%)
    used: 134.9 GiB (15.6%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:4
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: zram size: 62.7 GiB used: 0 KiB (0.0%) priority: 100
    comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 16 dev: /dev/zram0
  ID-2: swap-2 type: partition size: 68.97 GiB used: 0 KiB (0.0%)
    priority: -2 dev: /dev/nvme0n1p3 maj-min: 259:5
Sensors:
  System Temperatures: cpu: 49.5 C mobo: 46.0 C
  Fan Speeds (rpm): fan-1: 857 fan-2: 1593 fan-5: 820 fan-7: 0
Info:
  Processes: 431 Uptime: 31m wakeups: 0 Memory: total: 64 GiB note: est.
  available: 62.7 GiB used: 9.27 GiB (14.8%) Init: systemd v: 255
  default: graphical tool: systemctl Compilers: gcc: 13.2.1 alt: 12
  clang: 16.0.6 Packages: 2001 pm: pacman pkgs: 1979 libs: 543 tools: paru
  pm: flatpak pkgs: 22 Shell: fish v: 3.7.0 running-in: alacritty inxi: 3.3.31
Garuda (2.6.23-1):
  System install date:     2024-01-18
  Last full system update: 2024-02-05
  Is partially upgraded:   No
  Relevant software:       snapper NetworkManager dracut nvidia-dkms
  Windows dual boot:       No/Undetected
  Failed units:
2

Hi @RandomLegend , try running sudo systemctl enable nvidia-suspend
and please share journalctl -xe | grep -i suspend , oh and trying another kernel can help (LTS, etc …)

3

i assume you meant sudo systemctl enable nvidia-suspend.service ? if not, i just did both.

My journalctl before suspending now looks like this then:

journalctl -xe | grep -i suspend
Feb 06 13:22:44 frank-garuda sudo[1761528]: frank-garuda : TTY=pts/0 ; PWD=/home/frank-garuda ; USER=root ; COMMAND=/usr/bin/systemctl enable nvidia-suspend
Feb 06 13:23:51 frank-garuda sudo[1763553]: frank-garuda : TTY=pts/0 ; PWD=/home/frank-garuda ; USER=root ; COMMAND=/usr/bin/systemctl enable nvidia-suspend.service

i will try to suspend now and post the journalctl here right after.

Feb 06 13:29:48 frank-garuda systemd[1]: /etc/systemd/system/suspending.service:6: Invalid user/group name or numeric ID:
Feb 06 13:29:48 frank-garuda systemd[1]: suspending.service: Unit configuration has fatal error, unit will not be started.
Feb 06 13:29:48 frank-garuda systemd[1]: /etc/systemd/system/suspending.service:6: Invalid user/group name or numeric ID:
Feb 06 13:29:48 frank-garuda systemd[1]: suspending.service: Unit configuration has fatal error, unit will not be started.
Feb 06 13:29:48 frank-garuda systemd[1]: /etc/systemd/system/suspending.service:6: Invalid user/group name or numeric ID:
Feb 06 13:29:48 frank-garuda systemd[1]: suspending.service: Unit configuration has fatal error, unit will not be started.
4

So the errors in that last journalctl were based on the service entry i made according to Garuda Hyprland doesn't lock the screen and doesn't go sleep in idle - #21 but apparently i fudged something up. I disabled that service and suspended again… it still doesn’t work but now the system takes a few seconds longer to turn off all the fans but the result is the same. After waking it up, the displays “turn on” but stay black, turn off again, turn on again and then just stay black.

The journalctl -xe | grep -i suspend doesn’t show me anything after i restart after such failed suspend / wake up process…

5

As i was testing around i just went ahead to do a garuda-update and saw there is a kernel upgrade open.

Did that and now it works… soooo i guess weird issues with that particular kernel and my sys config.

1 Like
6

You are using nvidia proprietary drivers and proprietary drivers don’t work well with wayland at all. If you have ever looked at your journal logs after a crash like this it would have been filled with nvidia errors.

I don’t know if nouveau supports RTX 3070 yet you can check that out on your own if it does switch to open source drivers and save yourself the headache because this problem will definitely come back.

If they don’t and you absolutely need the proprietary drivers go with Xorg. Either use something like KDE or gnome and switch to X11 instead of the default wayland there (pretty simple to do just select your choice when logging in. There is going to be a drop down right below password box for this.)

If you absolutely need a tiling window manager go with i3wm which works on Xorg.

2 Likes
7

i know there are compatibility issues with NVidia and i am taking the risks of my system breaking.

I need the proprietary drivers for CUDA support as i do a lot of stuff with Stable Diffusion and LLMs - so Nouveau isn’t usable for me sadly.

I’ve been on KDE for the last years and tbh i just want something new and fresh. Gnome i’ve started with and i just dislike it so that’s out of the way.

I know that Hyprland is extremely unstable and experimental on NVidia but i want to use it. I really really like it and besides issues like these, the system works perfectly fine so in my books it’s worth the hassle.

I really really like that you offer a hyprland garuda WITH Nvidia drivers and i absolutely love garuda. I am using it since the last couple years and i don’t want to switch to anything else. I have donated to you guys because i love your work.

But i dislike how you guys keep telling me to use KDE / Gnome or something else, the second i face an issue on my Hyprland NVidia Setup.

That’s why i phrased my post “Maybe someone can point me in another helpful direction” - I am specifically NOT asking “you guys to fix this and that” but rather for helpful conversation and tips. And sorry to say it like this, but telling someone to completely leave the current setup and install something else is not helpful.

If we ever want to have a “working out of the box” Nvidia + Hyprland setup we simply cannot tell everyone to NOT even try to fix it. If everyone will leave this setup the second they face an issue, problems will never get fixed and it will stay unusable.

To conclude, i am so grateful for everything you guys do and this forum is the nicest and most helpful place i’ve seen in all the linux communities. But please stop telling people to just uninstall and use something else.

8

I am not sure if I have done this, it is possible to use Nvidia, but not with the ISOs I create.

Maybe Hyprland changed something, I didn’t check the Nvidia | Hyprland Wiki site every day, but today I don’t see any difference.

On my first install attempts on an Nvidia PC I had to change the following, which I posted in the Hyprland thread.

So I’m out of here now to give more hints.

9

But from the ISO you guys provide i installed Garuda Hyprland with proprietary NVidia drivers and it works awesome.

This particular issue here is resolved. The link you posted was very helpful and i consulted this prior to installing; This was all very helpful to get my system up and running.

11

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.