Fresh install does not allow Suspend and Hibernate

On a new device (LENOVO X13, Gen. 6) I installed MANJARO and found, that Suspend and Hibernate are not working: The user gets logged out, the screen gets black for a short time and returns then to Log-In - Screen again. I tried the standard install (use complete drive) once with Partition for SWAP / Resume and once with SWAP-file, both having the same issue.
I checked grep ^HOOKS /etc/mkinitcpio.conf: resume had been added for the partition, not for the file. I added it into the file without success.

$ inxi -zv8
System:
  Kernel: 6.12.39-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 15.1.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.12-x86_64
    root=UUID=bfb4a781-981b-4158-84ba-e66d2d28c671 rw quiet splash
    udev.log_priority=3
  Desktop: KDE Plasma v: 6.3.6 tk: Qt v: N/A info: frameworks v: 6.16.0
    wm: kwin_x11 vt: 2 dm: SDDM Distro: Manjaro base: Arch Linux
Machine:
  Type: Laptop System: LENOVO product: 21RM002KGE v: ThinkPad X13 Gen 6
    serial: <superuser required> Chassis: type: 10 serial: <superuser required>
  Mobo: LENOVO model: 21RM002KGE v: SDK0T76576 WIN
    serial: <superuser required> part-nu: LENOVO_MT_21RM_BU_Think_FM_ThinkPad
    X13 Gen 6 uuid: <superuser required> UEFI: LENOVO v: R32ET20W (1.03 )
    date: 04/21/2025
Battery:
  ID-1: BAT0 charge: 54.4 Wh (100.0%) condition: 54.4/54.7 Wh (99.5%)
    volts: 17.9 min: 15.6 model: Sunwoda 5B11M90122 type: Li-poly
    serial: <filter> status: full cycles: 3
Memory:
  System RAM: total: 32 GiB available: 30.49 GiB used: 2.11 GiB (6.9%)
  Message: For most reliable report, use superuser + dmidecode.
  Array-1: capacity: 64 GiB slots: 4 modules: 4 EC: None
    max-module-size: 16 GiB note: est.
  Device-1: Channel-A DIMM 0 type: LPDDR5 detail: synchronous unbuffered
    (unregistered) size: 8 GiB speed: 8000 MT/s volts: curr: 0.5 min: 0.5
    max: 0.5 width (bits): data: 32 total: 32 manufacturer: Hynix
    part-no: H58G66CK8BX147N serial: N/A
  Device-2: Channel-B DIMM 0 type: LPDDR5 detail: synchronous unbuffered
    (unregistered) size: 8 GiB speed: 8000 MT/s volts: curr: 0.5 min: 0.5
    max: 0.5 width (bits): data: 32 total: 32 manufacturer: Hynix
    part-no: H58G66CK8BX147N serial: N/A
  Device-3: Channel-C DIMM 0 type: LPDDR5 detail: synchronous unbuffered
    (unregistered) size: 8 GiB speed: 8000 MT/s volts: curr: 0.5 min: 0.5
    max: 0.5 width (bits): data: 32 total: 32 manufacturer: Hynix
    part-no: H58G66CK8BX147N serial: N/A
  Device-4: Channel-D DIMM 0 type: LPDDR5 detail: synchronous unbuffered
    (unregistered) size: 8 GiB speed: 8000 MT/s volts: curr: 0.5 min: 0.5
    max: 0.5 width (bits): data: 32 total: 32 manufacturer: Hynix
    part-no: H58G66CK8BX147N serial: N/A
PCI Slots:
  Permissions: Unable to run dmidecode. Root privileges required.
CPU:
  Info: model: AMD Ryzen AI 7 PRO 350 w/ Radeon 860M bits: 64 type: MT MCP
    arch: N/A level: v4 note: check family: 0x1A (26) model-id: 0x60 (96)
    stepping: 0 microcode: 0xB60000E
  Topology: cpus: 1x dies: 1 clusters: 1 cores: 8 threads: 16 tpc: 2
    smt: enabled cache: L1: 640 KiB desc: d-8x48 KiB; i-8x32 KiB L2: 8 MiB
    desc: 8x1024 KiB L3: 16 MiB desc: 1x16 MiB
  Speed (MHz): avg: 623 min/max: 599/4310 boost: enabled scaling:
    driver: amd-pstate-epp governor: powersave cores: 1: 623 2: 623 3: 623
    4: 623 5: 623 6: 623 7: 623 8: 623 9: 623 10: 623 11: 623 12: 623 13: 623
    14: 623 15: 623 16: 623 bogomips: 63916
  Flags: 3dnowprefetch abm adx aes amd_lbr_pmc_freeze amd_lbr_v2 aperfmperf
    apic arat avic avx avx2 avx512_bf16 avx512_bitalg avx512_vbmi2
    avx512_vnni avx512_vp2intersect avx512_vpopcntdq avx512bw avx512cd
    avx512dq avx512f avx512ifma avx512vbmi avx512vl avx_vnni bmi1 bmi2 bpext
    bus_lock_detect cat_l3 cdp_l3 clflush clflushopt clwb clzero cmov
    cmp_legacy constant_tsc cpb cppc cpuid cqm cqm_llc cqm_mbm_local
    cqm_mbm_total cqm_occup_llc cr8_legacy cx16 cx8 de decodeassists erms
    extapic extd_apicid f16c flush_l1d flushbyasid fma fpu fsgsbase fsrm fxsr
    fxsr_opt gfni ht hw_pstate ibpb ibrs ibrs_enhanced ibs invpcid irperf
    lahf_lm lbrv lm mba mca mce misalignsse mmx mmxext monitor movbe
    movdir64b movdiri msr mtrr mwaitx nonstop_tsc nopl npt nrip_save nx ospke
    osvw overflow_recov pae pat pausefilter pclmulqdq pdpe1gb perfctr_core
    perfctr_llc perfctr_nb perfmon_v2 pfthreshold pge pku pni popcnt pse
    pse36 rapl rdpid rdpru rdrand rdseed rdt_a rdtscp rep_good sep sha_ni
    skinit smap smca smep ssbd sse sse2 sse4_1 sse4_2 sse4a ssse3 stibp
    succor svm svm_lock syscall tce topoext tsc tsc_adjust tsc_scale umip
    user_shstk v_spec_ctrl v_vmsave_vmload vaes vgif vmcb_clean vme vmmcall
    vnmi vpclmulqdq wbnoinvd wdt x2avic xgetbv1 xsave xsavec xsaveerptr
    xsaveopt xsaves xtopology
  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 status: Not affected
  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: Enhanced / Automatic IBRS; IBPB:
    conditional; STIBP: always-on; PBRSB-eIBRS: Not affected; BHI: Not
    affected
  Type: srbds status: Not affected
  Type: tsa status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Advanced Micro Devices [AMD/ATI] Krackan [Radeon 840M / 860M
    Graphics] vendor: Lenovo driver: amdgpu v: kernel pcie: gen: 4
    speed: 16 GT/s lanes: 16 ports: active: eDP-1 empty: DP-1, DP-2, DP-3,
    DP-4, DP-5, DP-6, DP-7, HDMI-A-1, Writeback-1 bus-ID: c4:00.0
    chip-ID: 1002:1114 class-ID: 0380 temp: 39.0 C
  Device-2: Luxvisions Innotech Integrated Camera
    driver: hid-sensor-hub,usbhid,uvcvideo type: USB rev: 2.0 speed: 480 Mb/s
    lanes: 1 mode: 2.0 bus-ID: 1-1:2 chip-ID: 30c9:00f3 class-ID: fe01
    serial: <filter>
  Display: x11 server: X.Org v: 21.1.18 with: Xwayland v: 24.1.8
    compositor: kwin_x11 driver: X: loaded: amdgpu unloaded: modesetting
    alternate: fbdev,vesa dri: radeonsi gpu: amdgpu display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1920x1200 s-dpi: 96 s-size: 508x317mm (20.00x12.48")
    s-diag: 599mm (23.57") monitors: <missing: xrandr>
  Monitor-1: eDP-1 model: TL133VDMP01 built: 2024 res: 1920x1200 dpi: 171
    gamma: 1.2 chroma: red: x: 0.647 y: 0.325 green: x: 0.294 y: 0.616 blue:
    x: 0.141 y: 0.051 white: x: 0.314 y: 0.329 size: 286x179mm (11.26x7.05")
    diag: 337mm (13.3") ratio: 16:10 modes: 1920x1200, 1920x1080, 1600x1200,
    1680x1050, 1280x1024, 1440x900, 1280x800, 1280x720, 1024x768, 800x600,
    640x480
  EDID-Warnings: 1: parse_edid: unknown tag 112
  API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
    device: 1 drv: swrast gbm: drv: kms_swrast surfaceless: drv: radeonsi x11:
    drv: radeonsi inactive: wayland
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 25.1.6-arch1.1
    glx-v: 1.4 direct-render: yes renderer: AMD Radeon 860M Graphics (radeonsi
    gfx1152 LLVM 20.1.8 DRM 3.61 6.12.39-1-MANJARO) device-ID: 1002:1114
    memory: 500 MiB unified: no
  API: Vulkan v: 1.4.321 layers: N/A device: 0 type: integrated-gpu name: AMD
    Radeon 860M Graphics (RADV GFX1152) driver: mesa radv v: 25.1.6-arch1.1
    device-ID: 1002:1114 surfaces: N/A
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor wl: wayland-info x11: xdpyinfo,xprop
Audio:
  Device-1: Advanced Micro Devices [AMD/ATI] Radeon High Definition Audio
    [Rembrandt/Strix] vendor: Lenovo driver: snd_hda_intel v: kernel pcie:
    gen: 4 speed: 16 GT/s lanes: 16 bus-ID: c4:00.1 chip-ID: 1002:1640
    class-ID: 0403
  Device-2: Advanced Micro Devices [AMD] Audio Coprocessor vendor: Lenovo
    driver: snd_acp_pci v: kernel alternate: snd_pci_acp3x, snd_rn_pci_acp3x,
    snd_pci_acp5x, snd_pci_acp6x, snd_rpl_pci_acp6x, snd_pci_ps,
    snd_sof_amd_renoir, snd_sof_amd_rembrandt, snd_sof_amd_vangogh,
    snd_sof_amd_acp63, snd_sof_amd_acp70 pcie: gen: 4 speed: 16 GT/s lanes: 16
    bus-ID: c4:00.5 chip-ID: 1022:15e2 class-ID: 0480
  Device-3: Advanced Micro Devices [AMD] Family 17h/19h/1ah HD Audio
    vendor: Lenovo driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s
    lanes: 16 bus-ID: c4:00.6 chip-ID: 1022:15e3 class-ID: 0403
  API: ALSA v: k6.12.39-1-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: JACK v: 1.9.22 status: off tools: N/A
  Server-2: PipeWire v: 1.4.6 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: MEDIATEK vendor: Lenovo driver: mt7925e v: kernel pcie: gen: 2
    speed: 5 GT/s lanes: 1 port: N/A bus-ID: c2:00.0 chip-ID: 14c3:7925
    class-ID: 0280
  IF: wlp194s0 state: down mac: <filter>
  Device-2: Realtek RTL8153 Gigabit Ethernet Adapter driver: r8152 type: USB
    rev: 3.0 speed: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 bus-ID: 6-1:2
    chip-ID: 0bda:8153 class-ID: 0000 serial: <filter>
  IF: enp198s0f3u1 state: up speed: 100 Mbps duplex: full mac: <filter>
  IP v4: <filter> type: dynamic noprefixroute scope: global
    broadcast: <filter>
  IP v6: <filter> type: dynamic noprefixroute scope: global
  IP v6: <filter> type: noprefixroute scope: link
  IF-ID-1: wwan0 state: down mac: N/A
  Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
  WAN IP: <filter>
Bluetooth:
  Device-1: MediaTek Wireless_Device driver: btusb v: 0.8 type: USB rev: 2.1
    speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-5:4 chip-ID: 0e8d:e025
    class-ID: e001 serial: <filter>
  Report: rfkill ID: hci0 rfk-id: 3 state: up address: see --recommends
Logical:
  Message: No logical block device data found.
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 3.87 TiB used: 9.03 GiB (0.2%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 990 PRO 4TB
    size: 3.64 TiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: 4B2QJXD7 temp: 44.9 C
    scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 vendor: SanDisk model: USB 3.2Gen1
    size: 232.88 GiB block-size: physical: 512 B logical: 512 B type: USB
    rev: 3.2 spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 tech: N/A serial: <filter>
    fw-rev: 1.00 scheme: MBR
  Message: No optical or floppy data found.
Partition:
  ID-1: / raw-size: 3.64 TiB size: 3.58 TiB (98.40%) used: 9.03 GiB (0.2%)
    fs: ext4 dev: /dev/nvme0n1p2 maj-min: 259:2 label: N/A
    uuid: bfb4a781-981b-4158-84ba-e66d2d28c671
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 320 KiB (0.1%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1 label: N/A
    uuid: 803A-E49D
  ID-3: /run/media/myname/TESTDATEN raw-size: 4 GiB size: 3.99 GiB (99.80%)
    used: 448 KiB (0.0%) fs: vfat dev: /dev/sda3 maj-min: 8:3 label: TESTDATEN
    uuid: 6F40-2A69
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: file size: 512 MiB used: 0 KiB (0.0%) priority: -2
    file: /swapfile
Unmounted:
  ID-1: /dev/sda1 maj-min: 8:1 size: 228.84 GiB fs: ext4 label: VentoyISO
    uuid: 3313b505-1402-49c4-9833-e32f0241ac12
  ID-2: /dev/sda2 maj-min: 8:2 size: 32 MiB fs: vfat label: VTOYEFI
    uuid: 626B-4255
USB:
  Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 1 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: 1-1:2 info: Luxvisions Innotech Integrated Camera
    type: video,HID driver: hid-sensor-hub,usbhid,uvcvideo interfaces: 6
    rev: 2.0 speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 500mA
    chip-ID: 30c9:00f3 class-ID: fe01 serial: <filter>
  Hub-2: 2-0:1 info: super-speed hub ports: 1 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: 5 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: Generic EMV Smartcard Reader type: smart card
    driver: N/A interfaces: 1 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s) lanes: 1
    mode: 1.1 power: 50mA chip-ID: 2ce3:9563 class-ID: 0b00
  Device-2: 3-4:3 info: Synaptics type: <vendor specific> driver: N/A
    interfaces: 1 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1
    power: 100mA chip-ID: 06cb:00f9 class-ID: ff00 serial: <filter>
  Device-3: 3-5:4 info: MediaTek Wireless_Device type: bluetooth
    driver: btusb interfaces: 3 rev: 2.1 speed: 480 Mb/s (57.2 MiB/s) lanes: 1
    mode: 2.0 power: 100mA chip-ID: 0e8d:e025 class-ID: e001 serial: <filter>
  Hub-4: 4-0:1 info: super-speed hub ports: 2 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
  Device-1: 4-2:2 info: SanDisk Ultra type: mass storage driver: usb-storage
    interfaces: 1 rev: 3.2 speed: 5 Gb/s (596.0 MiB/s) lanes: 1
    mode: 3.2 gen-1x1 power: 896mA chip-ID: 0781:5581 class-ID: 0806
    serial: <filter>
  Hub-5: 5-0:1 info: hi-speed hub with single TT ports: 1 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-6: 6-0:1 info: super-speed hub ports: 1 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
  Device-1: 6-1:2 info: Realtek RTL8153 Gigabit Ethernet Adapter
    type: Network driver: r8152 interfaces: 1 rev: 3.0
    speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 power: 288mA
    chip-ID: 0bda:8153 class-ID: 0000 serial: <filter>
  Hub-7: 7-0:1 info: hi-speed hub with single TT ports: 1 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-8: 8-0:1 info: super-speed hub ports: 1 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
Sensors:
  System Temperatures: cpu: 41.0 C mobo: N/A gpu: amdgpu temp: 39.0 C
  Fan Speeds (rpm): fan-1: 1903 fan-2: 1903
Repos:
  Packages: pm: pacman pkgs: 1246 libs: 344 tools: pamac pm: flatpak pkgs: 0
  Active pacman repo servers in: /etc/pacman.d/mirrorlist
    1: https://mirror.easyname.at/manjaro/stable/$repo/$arch
    2: https://forksystems.mm.fcix.net/manjaro/stable/$repo/$arch
    3: https://manjaro.c3sl.ufpr.br/stable/$repo/$arch
Processes:
  CPU top: 5 of 378
  1: cpu: 0.9% command: Xorg pid: 854 mem: 137.7 MiB (0.4%)
  2: cpu: 0.5% command: kwin_x11 pid: 1079 mem: 204.7 MiB (0.6%)
  3: cpu: 0.5% command: plasmashell pid: 1122 mem: 433.9 MiB (1.3%)
  4: cpu: 0.4% command: konsole pid: 2203 mem: 243.0 MiB (0.7%)
  5: cpu: 0.3% command: zsh pid: 2222 mem: 10.8 MiB (0.0%)
  Memory top: 5 of 378
  1: mem: 433.9 MiB (1.3%) command: plasmashell pid: 1122 cpu: 0.5%
  2: mem: 243.0 MiB (0.7%) command: konsole pid: 2203 cpu: 0.4%
  3: mem: 204.7 MiB (0.6%) command: kwin_x11 pid: 1079 cpu: 0.5%
  4: mem: 199.1 MiB (0.6%) command: thumbnail.so started-by: kioworker
    pid: 2707 cpu: 0.3%
  5: mem: 137.7 MiB (0.4%) command: Xorg pid: 854 cpu: 0.9%
Info:
  Processes: 378 Power: uptime: 11m states: freeze,mem,disk suspend: s2idle
    wakeups: 0 fails: 2 hibernate: platform avail: shutdown, reboot, suspend,
    test_resume image: 12.17 GiB services: org_kde_powerdevil,
    power-profiles-daemon, upowerd Init: systemd v: 257 default: graphical
    tool: systemctl
  Compilers: N/A Shell: Zsh v: 5.9 running-in: konsole inxi: 3.3.38

See here - section 4.2

Power management/Suspend and hibernate - ArchWiki

The keyword needs to be at a specific location - not just at the end.

And then you need to rebuild the initrd and update boot loaders configuration file:

sudo mkinitcpio -P
sudo update-grub

Start reading at the top of section 4:

In order to use hibernation, you must create a swap partition or file, configure the initramfs so that the resume process will be initiated in early userspace, and specify the location of the swap space in a way that is available to the initramfs, e.g. HibernateLocation EFI variable defined by systemd or resume= kernel parameter. These three steps are described in detail below.

… the kernel command line in /etc/default/grub also needs to be adapted for resume to work …




… I can’t make sense of this statement :man_shrugging:

the output of:
grep ^HOOKS /etc/mkinitcpio.conf
shows where it is now - but you know, since you did edit the file yourself

posting in german is also o.k. - but you limit the number of people being willing and able to read your query - obviously :wink:

Thank you!

As described earlier, I tried two installs, one with SWAP-Partition (installer added resume into the HOOKS) one with SWAP-file (installer did not add resume into the HOOKS, so I did).

Now I inststalled again with SWAP-Partition. HOOKS-line was:

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

I modified the file so actually it is:

# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run.  Advanced users may wish to specify all system modules
# in this array.  For instance:
#     MODULES=(usbhid xhci_hcd)
MODULES=()

# BINARIES
# This setting includes any additional binaries a given user may
# wish into the CPIO image.  This is run last, so it may be used to
# override the actual binaries included by a given hook
# BINARIES are dependency parsed, so you may safely ignore libraries
BINARIES=()

# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in any way.  This is useful for config files.
FILES=()

# HOOKS
# This is the most important setting in this file.  The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added.  Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
##   This setup specifies all modules in the MODULES setting above.
##   No RAID, lvm2, or encrypted root is needed.
#    HOOKS=(base)
#
##   This setup will autodetect all modules for your system and should
##   work as a sane default
#    HOOKS=(base udev autodetect modconf block filesystems fsck)
#
##   This setup will generate a 'full' image which supports most systems.
##   No autodetection is done.
#    HOOKS=(base udev modconf block filesystems fsck)
#
##   This setup assembles a mdadm array with an encrypted root file system.
##   Note: See 'mkinitcpio -H mdadm_udev' for more information on RAID devices.
#    HOOKS=(base udev modconf keyboard keymap consolefont block mdadm_udev encrypt filesystems fsck)
#
##   This setup loads an lvm2 volume group.
#    HOOKS=(base udev modconf block lvm2 filesystems fsck)
#
##   This will create a systemd based initramfs which loads an encrypted root filesystem.
#    HOOKS=(base systemd autodetect modconf kms keyboard sd-vconsole sd-encrypt block filesystems fsck)
#
##   NOTE: If you have /usr on a separate partition, you MUST include the
#    usr and fsck hooks.
HOOKS=(base udev autodetect microcode kms modconf block keyboard keymap consolefont plymouth filesystems resume fsck)

# COMPRESSION
# Use this to compress the initramfs image. By default, zstd compression
# is used for Linux β‰₯ 5.9 and gzip compression is used for Linux < 5.9.
# Use 'cat' to create an uncompressed image.
#COMPRESSION="zstd"
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"
#COMPRESSION="lz4"

# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=()

# MODULES_DECOMPRESS
# Decompress loadable kernel modules and their firmware during initramfs
# creation. Switch (yes/no).
# Enable to allow further decreasing image size when using high compression
# (e.g. xz -9e or zstd --long --ultra -22) at the expense of increased RAM usage
# at early boot.
# Note that any compressed files will be placed in the uncompressed early CPIO
# to avoid double compression.
#MODULES_DECOMPRESS="no"

The actual grub-file is this:

# GRUB boot loader configuration

GRUB_DEFAULT=saved
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR='Manjaro'
GRUB_CMDLINE_LINUX_DEFAULT='quiet splash resume=UUID=0aa21fbb-9e35-488e-ab03-e1bc5adfe01e udev.log_priority=3'
GRUB_CMDLINE_LINUX=""

# Preload both GPT and MBR modules so that they are not missed
GRUB_PRELOAD_MODULES="part_gpt part_msdos"

# Uncomment to enable booting from LUKS encrypted devices
#GRUB_ENABLE_CRYPTODISK=y

# Set to 'countdown' or 'menu' to change timeout behavior,
# press ESC key to display menu.
GRUB_TIMEOUT_STYLE=hidden

# Uncomment to use basic console
GRUB_TERMINAL_INPUT=console

# Uncomment to disable graphical terminal
#GRUB_TERMINAL_OUTPUT=console

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command 'videoinfo'
GRUB_GFXMODE=auto

# Uncomment to allow the kernel use the same resolution used by grub
GRUB_GFXPAYLOAD_LINUX=keep

# Uncomment if you want GRUB to pass to the Linux kernel the old parameter
# format "root=/dev/xxx" instead of "root=/dev/disk/by-uuid/xxx"
#GRUB_DISABLE_LINUX_UUID=true

# Uncomment to disable generation of recovery mode menu entries
GRUB_DISABLE_RECOVERY=true

# Uncomment and set to the desired menu colors.  Used by normal and wallpaper
# modes only.  Entries specified as foreground/background.
GRUB_COLOR_NORMAL="light-gray/black"
GRUB_COLOR_HIGHLIGHT="green/black"

# Uncomment one of them for the gfx desired, a image background or a gfxtheme
#GRUB_BACKGROUND="/usr/share/grub/background.png"
GRUB_THEME="/usr/share/grub/themes/manjaro/theme.txt"

# Uncomment to get a beep at GRUB start
#GRUB_INIT_TUNE="480 440 1"

# Uncomment to make GRUB remember the last selection. This requires
# setting 'GRUB_DEFAULT=saved' above.
GRUB_SAVEDEFAULT=true

# Uncomment to disable submenus in boot menu
#GRUB_DISABLE_SUBMENU=y

# Uncomment this option to enable os-prober execution in the grub-mkconfig command
GRUB_DISABLE_OS_PROBER=false

# Uncomment to ensure that the root filesystem is mounted read-only so that
# systemd-fsck can run the check automatically. We use 'fsck' by default, which
# needs 'rw' as boot parameter, to avoid delay in boot-time. 'fsck' needs to be
# removed from 'mkinitcpio.conf' to make 'systemd-fsck' work.
# See also Arch-Wiki: https://wiki.archlinux.org/index.php/Fsck#Boot_time_checking
#GRUB_ROOT_FS_RO=true

You should be fine as long as that
resume=UUID=0aa21fbb-9e35-488e-ab03-e1bc5adfe01e
corresponds to your swap partition

But:

your inxi output above
doesn’t show a swap partition! - it shows a swap file

and it doesn’t show it to be present in the kernel command line:

resume cannot work this way

A swap file will work as well as a swap partition.

The way the grub command line is set up is different between the two, though.
For a swap file, you have to give the resume_offset= parameter as well as the partition where the swap file is.

see here:
https://wiki.archlinux.org/title/Power_management/Suspend_and_hibernate#Acquire_swap_file_offset

Power management/Suspend and hibernate - ArchWiki

and, obviously,
in the case of a swap file, it has to be large enough to hold the contents of your RAM.
The swap file created by the automatic installer isn’t big enough.
(I think it is only 512 MB or so …)

Yes, this UUID is the swap-partition. The SWAP-Partition is 33,54 GB and my RAM is 32 GB. But same issue as in my first post.

Please don’t be confused: As I installed more than once (SWAP-Partition / SWAP-File) the inxi I showed above, was from the SWAP-File - version … Let’s forget the SWAP-file.

Using gParted, I increased the SWAP-partition to 64 GB: Same issue as in my first post. What can I do?

It looks like your machine is pretty new.
Bios/UEFI is from April this year.

It might just be … too new.

The suspend and hibernate issues might not be caused by misconfigured swap.

Perhaps a newer kernel will help.
There are quite a few threads here with issues due to pretty new hardware.

You can just search and read - I cannot help.
Sorry!

(my laptop is 13 years old and I bought it used about 10 years ago …)

Thank you. Today at 10:04 a.m. I triggered StandBy. These are the LOG-entries for that:

$ journalctl --catalog --no-pager
Aug 13 10:04:10 XYZ-X136 systemd-logind[727]: The system will suspend now!
Aug 13 10:04:10 XYZ-X136 NetworkManager[723]: <info>  [1755072250.6888] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Aug 13 10:04:10 XYZ-X136 ModemManager[759]: <msg> [sleep-monitor-systemd] system is about to suspend
Aug 13 10:04:10 XYZ-X136 NetworkManager[723]: <info>  [1755072250.6891] device (enp198s0f3u1): state change: unavailable -> unmanaged (reason 'unmanaged-sleeping', managed-type: 'full')
Aug 13 10:04:10 XYZ-X136 ModemManager[759]: <msg> [sleep-monitor-systemd] ready to sleep; dropping inhibitor
Aug 13 10:04:10 XYZ-X136 NetworkManager[723]: <info>  [1755072250.7041] device (wlp194s0): state change: disconnected -> unmanaged (reason 'unmanaged-sleeping', managed-type: 'full')
Aug 13 10:04:10 XYZ-X136 NetworkManager[723]: <info>  [1755072250.7890] device (wlp194s0): set-hw-addr: reset MAC address to AC:F2:3C:D2:9C:59 (unmanage)
Aug 13 10:04:11 XYZ-X136 NetworkManager[723]: <info>  [1755072251.3974] device (p2p-dev-wlp194s0): state change: disconnected -> unmanaged (reason 'unmanaged-sleeping', managed-type: 'full')
Aug 13 10:04:11 XYZ-X136 NetworkManager[723]: <info>  [1755072251.3975] device (wwan0mbim0): state change: unavailable -> unmanaged (reason 'unmanaged-sleeping', managed-type: 'full')
Aug 13 10:04:11 XYZ-X136 wpa_supplicant[817]: wlp194s0: CTRL-EVENT-DSCP-POLICY clear_all
Aug 13 10:04:11 XYZ-X136 NetworkManager[723]: <info>  [1755072251.3976] manager: NetworkManager state is now ASLEEP
Aug 13 10:04:11 XYZ-X136 systemd[1]: Reached target Sleep.
β–‘β–‘ Subject: A start job for unit sleep.target has finished successfully
β–‘β–‘ Defined-By: systemd
β–‘β–‘ Support: https://forum.manjaro.org/c/support
β–‘β–‘
β–‘β–‘ A start job for unit sleep.target has finished successfully.
β–‘β–‘
β–‘β–‘ The job identifier is 5238.
Aug 13 10:04:11 XYZ-X136 systemd[1]: Starting System Suspend...
β–‘β–‘ Subject: A start job for unit systemd-suspend.service has begun execution
β–‘β–‘ Defined-By: systemd
β–‘β–‘ Support: https://forum.manjaro.org/c/support
β–‘β–‘
β–‘β–‘ A start job for unit systemd-suspend.service has begun execution.
β–‘β–‘
β–‘β–‘ The job identifier is 5235.
Aug 13 10:04:11 XYZ-X136 systemd[1]: session-2.scope: Unit now frozen-by-parent.
Aug 13 10:04:11 XYZ-X136 systemd[1]: user@1000.service: Unit now frozen-by-parent.
Aug 13 10:04:11 XYZ-X136 systemd[1]: user.slice: Unit now frozen.
Aug 13 10:04:11 XYZ-X136 systemd[1]: user-1000.slice: Unit now frozen-by-parent.
Aug 13 10:04:11 XYZ-X136 systemd-sleep[2720]: Successfully froze unit 'user.slice'.
Aug 13 10:04:11 XYZ-X136 systemd-sleep[2720]: Performing sleep operation 'suspend'...
β–‘β–‘ Subject: System sleep state suspend entered
β–‘β–‘ Defined-By: systemd
β–‘β–‘ Support: https://forum.manjaro.org/c/support
β–‘β–‘
β–‘β–‘ The system has now entered the suspend sleep state.
Aug 13 10:04:11 XYZ-X136 kernel: PM: suspend entry (s2idle)
Aug 13 10:04:11 XYZ-X136 kernel: Filesystems sync: 0.006 seconds
Aug 13 10:04:16 XYZ-X136 kernel: Freezing user space processes
Aug 13 10:04:16 XYZ-X136 kernel: Freezing user space processes completed (elapsed 0.013 seconds)
Aug 13 10:04:16 XYZ-X136 kernel: OOM killer disabled.
Aug 13 10:04:16 XYZ-X136 kernel: Freezing remaining freezable tasks
Aug 13 10:04:16 XYZ-X136 kernel: Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
Aug 13 10:04:16 XYZ-X136 kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Aug 13 10:04:16 XYZ-X136 kernel: queueing ieee80211 work while going to suspend
Aug 13 10:04:16 XYZ-X136 kernel: mt7925e 0000:c2:00.0: Message 00020007 (seq 1) timeout
Aug 13 10:04:16 XYZ-X136 kernel: mt7925e 0000:c2:00.0: PM: pci_pm_suspend(): mt7925_pci_suspend [mt7925e] returns -110
Aug 13 10:04:16 XYZ-X136 kernel: mt7925e 0000:c2:00.0: PM: dpm_run_callback(): pci_pm_suspend returns -110
Aug 13 10:04:16 XYZ-X136 kernel: mt7925e 0000:c2:00.0: PM: failed to suspend async: error -110
Aug 13 10:04:16 XYZ-X136 kernel: PM: Some devices failed to suspend, or early wake event detected
Aug 13 10:04:16 XYZ-X136 kernel: [drm] PCIE GART of 512M enabled (table at 0x0000008000900000).
Aug 13 10:04:16 XYZ-X136 kernel: amdgpu 0000:c4:00.0: amdgpu: SMU is resuming...
Aug 13 10:04:16 XYZ-X136 kernel: amdgpu 0000:c4:00.0: amdgpu: SMU is resumed successfully!
Aug 13 10:04:16 XYZ-X136 kernel: nvme nvme0: D3 entry latency set to 10 seconds
Aug 13 10:04:16 XYZ-X136 kernel: nvme nvme0: 16/0/0 default/read/poll queues
Aug 13 10:04:16 XYZ-X136 kernel: mt7925e 0000:c2:00.0: HW/SW Version: 0x8a108a10, Build Time: 20250721232852a
Aug 13 10:04:16 XYZ-X136 kernel: amdgpu 0000:c4:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
Aug 13 10:04:16 XYZ-X136 kernel: amdgpu 0000:c4:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
Aug 13 10:04:16 XYZ-X136 kernel: amdgpu 0000:c4:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
Aug 13 10:04:16 XYZ-X136 kernel: amdgpu 0000:c4:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 6 on hub 0
Aug 13 10:04:16 XYZ-X136 kernel: amdgpu 0000:c4:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 7 on hub 0
Aug 13 10:04:16 XYZ-X136 kernel: amdgpu 0000:c4:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 8 on hub 0
Aug 13 10:04:16 XYZ-X136 kernel: amdgpu 0000:c4:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 9 on hub 0
Aug 13 10:04:16 XYZ-X136 kernel: amdgpu 0000:c4:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 10 on hub 0
Aug 13 10:04:16 XYZ-X136 kernel: amdgpu 0000:c4:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 11 on hub 0
Aug 13 10:04:16 XYZ-X136 kernel: amdgpu 0000:c4:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0
Aug 13 10:04:16 XYZ-X136 kernel: amdgpu 0000:c4:00.0: amdgpu: ring vcn_unified_0 uses VM inv eng 0 on hub 8
Aug 13 10:04:16 XYZ-X136 kernel: amdgpu 0000:c4:00.0: amdgpu: ring jpeg_dec_0 uses VM inv eng 1 on hub 8
Aug 13 10:04:16 XYZ-X136 kernel: amdgpu 0000:c4:00.0: amdgpu: ring mes_kiq_3.1.0 uses VM inv eng 13 on hub 0
Aug 13 10:04:16 XYZ-X136 kernel: amdgpu 0000:c4:00.0: amdgpu: ring vpe uses VM inv eng 4 on hub 8
Aug 13 10:04:16 XYZ-X136 kernel: [drm] ring gfx_32788.1.1 was added
Aug 13 10:04:16 XYZ-X136 kernel: [drm] ring compute_32788.2.2 was added
Aug 13 10:04:16 XYZ-X136 kernel: [drm] ring sdma_32788.3.3 was added
Aug 13 10:04:16 XYZ-X136 kernel: [drm] ring gfx_32788.1.1 ib test pass
Aug 13 10:04:16 XYZ-X136 kernel: [drm] ring compute_32788.2.2 ib test pass
Aug 13 10:04:16 XYZ-X136 kernel: [drm] ring sdma_32788.3.3 ib test pass
Aug 13 10:04:16 XYZ-X136 kernel: mt7925e 0000:c2:00.0: WM Firmware Version: ____000000, Build Time: 20250721232943
Aug 13 10:04:16 XYZ-X136 kernel: wlp194s0: Driver requested disconnection from AP 00:00:00:00:00:00
Aug 13 10:04:16 XYZ-X136 kernel: OOM killer enabled.
Aug 13 10:04:16 XYZ-X136 kernel: Restarting tasks ... done.
Aug 13 10:04:16 XYZ-X136 kernel: random: crng reseeded on system resumption
Aug 13 10:04:16 XYZ-X136 rtkit-daemon[1018]: The canary thread is apparently starving. Taking action.
Aug 13 10:04:16 XYZ-X136 rtkit-daemon[1018]: Demoting known real-time threads.
Aug 13 10:04:16 XYZ-X136 rtkit-daemon[1018]: Successfully demoted thread 1279 of process 1273.
Aug 13 10:04:16 XYZ-X136 rtkit-daemon[1018]: Successfully demoted thread 1273 of process 1273.
Aug 13 10:04:16 XYZ-X136 rtkit-daemon[1018]: Successfully demoted thread 1068 of process 1055.
Aug 13 10:04:16 XYZ-X136 rtkit-daemon[1018]: Successfully demoted thread 1055 of process 1055.
Aug 13 10:04:16 XYZ-X136 rtkit-daemon[1018]: Successfully demoted thread 1059 of process 1054.
Aug 13 10:04:16 XYZ-X136 rtkit-daemon[1018]: Successfully demoted thread 1054 of process 1054.
Aug 13 10:04:16 XYZ-X136 rtkit-daemon[1018]: Demoted 6 threads.
Aug 13 10:04:16 XYZ-X136 wpa_supplicant[817]: wlp194s0: CTRL-EVENT-DSCP-POLICY clear_all
Aug 13 10:04:16 XYZ-X136 wpa_supplicant[817]: nl80211: deinit ifname=wlp194s0 disabled_11b_rates=0
Aug 13 10:04:16 XYZ-X136 bluetoothd[725]: Controller resume with wake event 0x0
Aug 13 10:04:16 XYZ-X136 kernel: PM: suspend exit
Aug 13 10:04:16 XYZ-X136 kernel: PM: suspend entry (s2idle)
Aug 13 10:04:20 XYZ-X136 kernel: Filesystems sync: 0.006 seconds
Aug 13 10:04:20 XYZ-X136 kernel: Freezing user space processes
Aug 13 10:04:20 XYZ-X136 kernel: Freezing user space processes completed (elapsed 0.001 seconds)
Aug 13 10:04:20 XYZ-X136 kernel: OOM killer disabled.
Aug 13 10:04:20 XYZ-X136 kernel: Freezing remaining freezable tasks
Aug 13 10:04:20 XYZ-X136 kernel: Freezing remaining freezable tasks completed (elapsed 0.018 seconds)
Aug 13 10:04:20 XYZ-X136 kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Aug 13 10:04:20 XYZ-X136 kernel: mt7925e 0000:c2:00.0: Message 00020007 (seq 2) timeout
Aug 13 10:04:20 XYZ-X136 kernel: mt7925e 0000:c2:00.0: PM: pci_pm_suspend(): mt7925_pci_suspend [mt7925e] returns -110
Aug 13 10:04:20 XYZ-X136 kernel: mt7925e 0000:c2:00.0: PM: dpm_run_callback(): pci_pm_suspend returns -110
Aug 13 10:04:20 XYZ-X136 kernel: mt7925e 0000:c2:00.0: PM: failed to suspend async: error -110
Aug 13 10:04:20 XYZ-X136 kernel: PM: Some devices failed to suspend, or early wake event detected
Aug 13 10:04:20 XYZ-X136 kernel: [drm] PCIE GART of 512M enabled (table at 0x0000008000900000).
Aug 13 10:04:20 XYZ-X136 kernel: amdgpu 0000:c4:00.0: amdgpu: SMU is resuming...
Aug 13 10:04:20 XYZ-X136 kernel: nvme nvme0: D3 entry latency set to 10 seconds
Aug 13 10:04:20 XYZ-X136 kernel: nvme nvme0: 16/0/0 default/read/poll queues
Aug 13 10:04:20 XYZ-X136 kernel: amdgpu 0000:c4:00.0: amdgpu: SMU is resumed successfully!
Aug 13 10:04:20 XYZ-X136 kernel: mt7925e 0000:c2:00.0: HW/SW Version: 0x8a108a10, Build Time: 20250721232852a
Aug 13 10:04:20 XYZ-X136 kernel: amdgpu 0000:c4:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
Aug 13 10:04:20 XYZ-X136 kernel: amdgpu 0000:c4:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
Aug 13 10:04:20 XYZ-X136 kernel: amdgpu 0000:c4:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
Aug 13 10:04:20 XYZ-X136 kernel: amdgpu 0000:c4:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 6 on hub 0
Aug 13 10:04:20 XYZ-X136 kernel: amdgpu 0000:c4:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 7 on hub 0
Aug 13 10:04:20 XYZ-X136 kernel: amdgpu 0000:c4:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 8 on hub 0
Aug 13 10:04:20 XYZ-X136 kernel: amdgpu 0000:c4:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 9 on hub 0
Aug 13 10:04:20 XYZ-X136 kernel: amdgpu 0000:c4:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 10 on hub 0
Aug 13 10:04:20 XYZ-X136 kernel: amdgpu 0000:c4:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 11 on hub 0
Aug 13 10:04:20 XYZ-X136 kernel: amdgpu 0000:c4:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0
Aug 13 10:04:20 XYZ-X136 kernel: amdgpu 0000:c4:00.0: amdgpu: ring vcn_unified_0 uses VM inv eng 0 on hub 8
Aug 13 10:04:20 XYZ-X136 kernel: amdgpu 0000:c4:00.0: amdgpu: ring jpeg_dec_0 uses VM inv eng 1 on hub 8
Aug 13 10:04:20 XYZ-X136 kernel: amdgpu 0000:c4:00.0: amdgpu: ring mes_kiq_3.1.0 uses VM inv eng 13 on hub 0
Aug 13 10:04:20 XYZ-X136 kernel: amdgpu 0000:c4:00.0: amdgpu: ring vpe uses VM inv eng 4 on hub 8
Aug 13 10:04:20 XYZ-X136 kernel: [drm] ring gfx_32788.1.1 was added
Aug 13 10:04:20 XYZ-X136 kernel: [drm] ring compute_32788.2.2 was added
Aug 13 10:04:20 XYZ-X136 kernel: [drm] ring sdma_32788.3.3 was added
Aug 13 10:04:20 XYZ-X136 kernel: [drm] ring gfx_32788.1.1 ib test pass
Aug 13 10:04:20 XYZ-X136 kernel: [drm] ring compute_32788.2.2 ib test pass
Aug 13 10:04:20 XYZ-X136 kernel: [drm] ring sdma_32788.3.3 ib test pass
Aug 13 10:04:20 XYZ-X136 kernel: mt7925e 0000:c2:00.0: WM Firmware Version: ____000000, Build Time: 20250721232943
Aug 13 10:04:20 XYZ-X136 kernel: wlp194s0: Driver requested disconnection from AP 00:00:00:00:00:00
Aug 13 10:04:20 XYZ-X136 kernel: OOM killer enabled.
Aug 13 10:04:20 XYZ-X136 kernel: Restarting tasks ... done.
Aug 13 10:04:20 XYZ-X136 kernel: random: crng reseeded on system resumption
Aug 13 10:04:20 XYZ-X136 systemd-sleep[2720]: Failed to put system to sleep. System resumed again: Connection timed out
β–‘β–‘ Subject: System sleep state suspend left
β–‘β–‘ Defined-By: systemd
β–‘β–‘ Support: https://forum.manjaro.org/c/support
β–‘β–‘
β–‘β–‘ The system has now left the suspend sleep state.
Aug 13 10:04:20 XYZ-X136 bluetoothd[725]: Controller resume with wake event 0x0
Aug 13 10:04:20 XYZ-X136 systemd[1]: user.slice: Unit now thawed.
Aug 13 10:04:20 XYZ-X136 systemd[1]: user-1000.slice: Unit now thawed.
Aug 13 10:04:20 XYZ-X136 systemd-sleep[2720]: Successfully thawed unit 'user.slice'.
Aug 13 10:04:20 XYZ-X136 systemd[1]: user@1000.service: Unit now thawed.
Aug 13 10:04:20 XYZ-X136 systemd[1]: session-2.scope: Unit now thawed.
Aug 13 10:04:20 XYZ-X136 systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE
β–‘β–‘ Subject: Unit process exited
β–‘β–‘ Defined-By: systemd
β–‘β–‘ Support: https://forum.manjaro.org/c/support
β–‘β–‘
β–‘β–‘ An ExecStart= process belonging to unit systemd-suspend.service has exited.
β–‘β–‘
β–‘β–‘ The process' exit code is 'exited' and its exit status is 1.
Aug 13 10:04:20 XYZ-X136 systemd[1]: systemd-suspend.service: Failed with result 'exit-code'.
β–‘β–‘ Subject: Unit failed
β–‘β–‘ Defined-By: systemd
β–‘β–‘ Support: https://forum.manjaro.org/c/support
β–‘β–‘
β–‘β–‘ The unit systemd-suspend.service has entered the 'failed' state with result 'exit-code'.
Aug 13 10:04:20 XYZ-X136 kernel: PM: suspend exit
Aug 13 10:04:20 XYZ-X136 systemd[1]: Failed to start System Suspend.
β–‘β–‘ Subject: A start job for unit systemd-suspend.service has failed
β–‘β–‘ Defined-By: systemd
β–‘β–‘ Support: https://forum.manjaro.org/c/support
β–‘β–‘
β–‘β–‘ A start job for unit systemd-suspend.service has finished with a failure.
β–‘β–‘
β–‘β–‘ The job identifier is 5235 and the job result is failed.
Aug 13 10:04:20 XYZ-X136 systemd[1]: Dependency failed for Suspend.
β–‘β–‘ Subject: A start job for unit suspend.target has failed
β–‘β–‘ Defined-By: systemd
β–‘β–‘ Support: https://forum.manjaro.org/c/support
β–‘β–‘
β–‘β–‘ A start job for unit suspend.target has finished with a failure.
β–‘β–‘
β–‘β–‘ The job identifier is 5234 and the job result is dependency.
Aug 13 10:04:20 XYZ-X136 systemd[1]: suspend.target: Job suspend.target/start failed with result 'dependency'.
Aug 13 10:04:20 XYZ-X136 systemd-logind[727]: Operation 'suspend' finished.
Aug 13 10:04:20 XYZ-X136 ModemManager[759]: <msg> [sleep-monitor-systemd] system is resuming
Aug 13 10:04:20 XYZ-X136 NetworkManager[723]: <info>  [1755072260.5800] manager: sleep: wake requested (sleeping: yes  enabled: yes)
Aug 13 10:04:20 XYZ-X136 NetworkManager[723]: <info>  [1755072260.5805] device (enp198s0f3u1): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')
Aug 13 10:04:20 XYZ-X136 systemd[1]: Stopped target Sleep.
β–‘β–‘ Subject: A stop job for unit sleep.target has finished
β–‘β–‘ Defined-By: systemd
β–‘β–‘ Support: https://forum.manjaro.org/c/support
β–‘β–‘
β–‘β–‘ A stop job for unit sleep.target has finished.
β–‘β–‘

Perhaps do you or someone else can find the source of the issue.

Your machine, it’s hardware:

Try another, more recent kernel.
linux616 is available.
Install it and boot using it by selecting it from the grub menu.

Even linux617-rc1 is available.

That is the only thing I can suggest.

Looks like a Bluetooth device resumes the laptop immediately after it is suspended.

You could do something like what is described here:

2 Likes

Thank you very much for your support! I’ve got it working fine by now, this is the solution:

  • It works with Kernel 6.15 but with Kernel 6.12 or earlier.
  • BIOS-settings:
    • Security > SecureBoot: OFF
    • Security > Security Chip > MICROSOFT PlutonProcessor Control: ON
    • It is imperative to have this ON! And:
      • Security > Security Chip > Security Chip Type: Discrete TPM 2.0
    • If it is OFF system reaches suspend, but can not wake-up! And:
      • Security > Security Chip > Security Chip Type: Not accessible.

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