Arch Linux

Kermir

Member

Registered: 2026-06-21

Posts: 18

Fresh install does not wake from suspend

I've recently installed Arch Linux with Hyprland on my Asus Tuf Gaming F16 (FX607VUR) Laptop and since the 340 BIOS version update i am unable to wake the system with keyboard/touchpad/power button and I have to turn off the entire laptop by holding the power button and then back on.

ewaller

Administrator

From: Pasadena, CA

Registered: 2009-07-13

Posts: 20,678

Re: Fresh install does not wake from suspend

Does the power come back on but to a black screen?  I ask because you say you cannot wake it up, but you have to force a power down.

After you force a reboot, look at the end of the journal related to your previous boot using the command journnalctl -b -1    There will be messages about going to sleep; any messages about waking up?

---

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way

Kermir

Member

Registered: 2026-06-21

Posts: 18

Re: Fresh install does not wake from suspend

The status leds are blinking as in to signify its in sleep, but it completely ignores any kind of input. It does not power on or does anything. Only the status lights are blinking. As for the logs it doesn't seem to get any wake up event.

Jun 21 20:26:59 diesel systemd-logind[659]: The system will sleep now!
Jun 21 20:26:59 diesel NetworkManager[657]: <info>  [1782066419.7880] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Jun 21 20:26:59 diesel NetworkManager[657]: <info>  [1782066419.7881] device (enp55s0): state change: unavailable -> unmanaged (reason 'unmanaged-nm-disabled', managed-type: 'full')
Jun 21 20:26:59 diesel NetworkManager[657]: <info>  [1782066419.7940] device (p2p-dev-wlp56s0): state change: disconnected -> unmanaged (reason 'unmanaged-nm-disabled', managed-type: 'full')
Jun 21 20:26:59 diesel NetworkManager[657]: <info>  [1782066419.7943] manager: NetworkManager state is now DISABLED (ASLEEP)
Jun 21 20:26:59 diesel NetworkManager[657]: <info>  [1782066419.7945] device (wlp56s0): state change: activated -> deactivating (reason 'sleeping', managed-type: 'full')
Jun 21 20:26:59 diesel systemd[1]: Starting Network Manager Script Dispatcher Service...
Jun 21 20:26:59 diesel systemd[1]: Started Network Manager Script Dispatcher Service.
Jun 21 20:26:59 diesel kernel: wlp56s0: deauthenticating from a2:b5:3c:cd:84:e5 by local choice (Reason: 3=DEAUTH_LEAVING)
Jun 21 20:26:59 diesel wpa_supplicant[714]: nl80211: send_event_marker failed: Source based routing not supported
Jun 21 20:26:59 diesel wpa_supplicant[714]: wlp56s0: CTRL-EVENT-DISCONNECTED bssid=a2:b5:3c:cd:84:e5 reason=3 locally_generated=1
Jun 21 20:26:59 diesel wpa_supplicant[714]: wlp56s0: CTRL-EVENT-DSCP-POLICY clear_all
Jun 21 20:26:59 diesel wpa_supplicant[714]: wlp56s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Jun 21 20:26:59 diesel NetworkManager[657]: <info>  [1782066419.9101] device (wlp56s0): supplicant interface state: completed -> disconnected
Jun 21 20:26:59 diesel NetworkManager[657]: <info>  [1782066419.9104] device (wlp56s0): state change: deactivating -> disconnected (reason 'sleeping', managed-type: 'full')
Jun 21 20:26:59 diesel NetworkManager[657]: <info>  [1782066419.9108] dhcp4 (wlp56s0): canceled DHCP transaction
Jun 21 20:26:59 diesel NetworkManager[657]: <info>  [1782066419.9108] dhcp4 (wlp56s0): activation: beginning transaction (timeout in 45 seconds)
Jun 21 20:26:59 diesel NetworkManager[657]: <info>  [1782066419.9108] dhcp4 (wlp56s0): state changed no lease
Jun 21 20:26:59 diesel NetworkManager[657]: <info>  [1782066419.9110] dhcp6 (wlp56s0): canceled DHCP transaction
Jun 21 20:26:59 diesel NetworkManager[657]: <info>  [1782066419.9110] dhcp6 (wlp56s0): activation: beginning transaction (timeout in 45 seconds)
Jun 21 20:26:59 diesel NetworkManager[657]: <info>  [1782066419.9110] dhcp6 (wlp56s0): state changed no lease
Jun 21 20:26:59 diesel NetworkManager[657]: <info>  [1782066419.9273] device (wlp56s0): set-hw-addr: set MAC address to 76:7C:2A:04:60:D5 (scanning)
Jun 21 20:27:00 diesel NetworkManager[657]: <info>  [1782066420.0778] device (wlp56s0): supplicant interface state: disconnected -> interface_disabled
Jun 21 20:27:00 diesel NetworkManager[657]: <info>  [1782066420.0779] device (wlp56s0): supplicant interface state: interface_disabled -> disconnected
Jun 21 20:27:00 diesel NetworkManager[657]: <info>  [1782066420.0785] device (wlp56s0): state change: disconnected -> unmanaged (reason 'unmanaged-nm-disabled', managed-type: 'full')
Jun 21 20:27:00 diesel NetworkManager[657]: <info>  [1782066420.2507] device (wlp56s0): set-hw-addr: reset MAC address to 9C:C7:D3:A2:E0:CA (unmanage)
Jun 21 20:27:00 diesel systemd[1]: Reached target Sleep.
Jun 21 20:27:00 diesel systemd[1]: Starting System Suspend then Hibernate...
Jun 21 20:27:00 diesel wpa_supplicant[714]: wlp56s0: CTRL-EVENT-DSCP-POLICY clear_all
Jun 21 20:27:00 diesel systemd-sleep[1656]: User sessions remain unfrozen on explicit request ($SYSTEMD_SLEEP_FREEZE_USER_SESSIONS=0).
Jun 21 20:27:00 diesel systemd-sleep[1656]: This is not recommended, and might result in unexpected behavior, particularly
Jun 21 20:27:00 diesel systemd-sleep[1656]: in suspend-then-hibernate operations or setups with encrypted home directories.
Jun 21 20:27:00 diesel wpa_supplicant[714]: wlp56s0: CTRL-EVENT-DSCP-POLICY clear_all
Jun 21 20:27:00 diesel wpa_supplicant[714]: nl80211: deinit ifname=wlp56s0 disabled_11b_rates=0
Jun 21 20:27:00 diesel systemd-sleep[1656]: Performing sleep operation 'suspend'...
[kermir@diesel ~]$ 

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 76,740

Re: Fresh install does not wake from suspend

Does https://wiki.archlinux.org/title/Keyboa … el_(SysRq) + REISUB work?
(Rebooting w/ holding the power button will lose the journal tail for sure)

The snippet there doesn't contain the mode,

cat /sys/power/mem_sleep

Does "deep" ./. s2idle make a difference?

Jun 21 20:27:00 diesel systemd-sleep[1656]: User sessions remain unfrozen on explicit request ($SYSTEMD_SLEEP_FREEZE_USER_SESSIONS=0).

nvidia GPU?
Are you using the nvidia-open drivers or 580xx proprietary module (latter isn't an option w/ blackwell but with them you can disable the https://wiki.archlinux.org/title/NVIDIA … P_firmware )

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Kermir

Member

Registered: 2026-06-21

Posts: 18

Re: Fresh install does not wake from suspend

Does https://wiki.archlinux.org/title/Keyboa … el_(SysRq) + REISUB work?
(Rebooting w/ holding the power button will lose the journal tail for sure)

Doesn't work when laptop is put to sleep, otherwise while running normaly it works as intended. The laptop doesn't seem to react to any keypresses, touchpad or power button during sleep.

The snippet there doesn't contain the mode
Does "deep" ./. s2idle make a difference?

Sorry forgot to add that additionally. here

[kermir@diesel ~]$ cat /sys/power/mem_sleep 
[s2idle] deep
[kermir@diesel ~]$ 

tried switching temporarily with

echo deep | sudo tee /sys/power/mem_sleep

but didn't make any difference when initiating sleep

nvidia GPU?

Yes a dGPU, this PC has hybrid graphics. I have an RTX 4050 Max-Q Mobile.
I am using the version 610.43.02 of nvidia-open.

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 76,740

Re: Fresh install does not wake from suspend

That's an ADA chip, right?
Can you disable the GPU in the UEFI settings?
If that helps I'd try the 580xx drivers and to disable the GSP

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Kermir

Member

Registered: 2026-06-21

Posts: 18

Re: Fresh install does not wake from suspend

I cannot disable the GPU unfortunately, i can either set it to dGPU only or Adaptive

I downgraded my drivers and disabled GSP.

[kermir@diesel ~]$ cat /proc/driver/nvidia/params | grep EnableGpuFirmware
EnableGpuFirmware: 0
EnableGpuFirmwareLogs: 2
[kermir@diesel ~]$ 

But now the laptop doesn't go to sleep when using "systemctl suspend" unless the lid is closed, and the same issue persists of not being come out off sleep.

Error code when attempting to put the pc in sleep

Jun 21 23:25:52 diesel systemd-logind[633]: The system will sleep now!
Jun 21 23:25:52 diesel NetworkManager[631]: <info>  [1782077152.0953] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Jun 21 23:25:52 diesel NetworkManager[631]: <info>  [1782077152.0954] device (enp55s0): state change: unavailable -> unmanaged (reason 'unmanaged-nm-disabled', managed-type: 'full')
Jun 21 23:25:52 diesel NetworkManager[631]: <info>  [1782077152.1018] device (p2p-dev-wlp56s0): state change: disconnected -> unmanaged (reason 'unmanaged-nm-disabled', managed-type: 'full')
Jun 21 23:25:52 diesel NetworkManager[631]: <info>  [1782077152.1020] manager: NetworkManager state is now DISABLED (ASLEEP)
Jun 21 23:25:52 diesel NetworkManager[631]: <info>  [1782077152.1023] device (wlp56s0): state change: activated -> deactivating (reason 'sleeping', managed-type: 'full')
Jun 21 23:25:52 diesel systemd[1]: Starting Network Manager Script Dispatcher Service...
Jun 21 23:25:52 diesel systemd[1]: Started Network Manager Script Dispatcher Service.
Jun 21 23:25:52 diesel kernel: wlp56s0: deauthenticating from a2:b5:3c:cd:84:e5 by local choice (Reason: 3=DEAUTH_LEAVING)
Jun 21 23:25:52 diesel wpa_supplicant[701]: nl80211: send_event_marker failed: Source based routing not supported
Jun 21 23:25:52 diesel wpa_supplicant[701]: wlp56s0: CTRL-EVENT-DISCONNECTED bssid=a2:b5:3c:cd:84:e5 reason=3 locally_generated=1
Jun 21 23:25:52 diesel wpa_supplicant[701]: wlp56s0: CTRL-EVENT-DSCP-POLICY clear_all
Jun 21 23:25:52 diesel wpa_supplicant[701]: wlp56s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Jun 21 23:25:52 diesel NetworkManager[631]: <info>  [1782077152.2301] device (wlp56s0): supplicant interface state: completed -> disconnected
Jun 21 23:25:52 diesel NetworkManager[631]: <info>  [1782077152.2304] device (wlp56s0): state change: deactivating -> disconnected (reason 'sleeping', managed-type: 'full')
Jun 21 23:25:52 diesel NetworkManager[631]: <info>  [1782077152.2324] dhcp4 (wlp56s0): canceled DHCP transaction
Jun 21 23:25:52 diesel NetworkManager[631]: <info>  [1782077152.2324] dhcp4 (wlp56s0): activation: beginning transaction (timeout in 45 seconds)
Jun 21 23:25:52 diesel NetworkManager[631]: <info>  [1782077152.2324] dhcp4 (wlp56s0): state changed no lease
Jun 21 23:25:52 diesel NetworkManager[631]: <info>  [1782077152.2326] dhcp6 (wlp56s0): canceled DHCP transaction
Jun 21 23:25:52 diesel NetworkManager[631]: <info>  [1782077152.2326] dhcp6 (wlp56s0): activation: beginning transaction (timeout in 45 seconds)
Jun 21 23:25:52 diesel NetworkManager[631]: <info>  [1782077152.2326] dhcp6 (wlp56s0): state changed no lease
Jun 21 23:25:52 diesel NetworkManager[631]: <info>  [1782077152.2507] device (wlp56s0): set-hw-addr: set MAC address to 6A:60:47:49:49:DA (scanning)
Jun 21 23:25:52 diesel NetworkManager[631]: <info>  [1782077152.4073] device (wlp56s0): supplicant interface state: disconnected -> interface_disabled
Jun 21 23:25:52 diesel NetworkManager[631]: <info>  [1782077152.4074] device (wlp56s0): supplicant interface state: interface_disabled -> disconnected
Jun 21 23:25:52 diesel NetworkManager[631]: <info>  [1782077152.4080] device (wlp56s0): state change: disconnected -> unmanaged (reason 'unmanaged-nm-disabled', managed-type: 'full')
Jun 21 23:25:52 diesel NetworkManager[631]: <info>  [1782077152.5673] device (wlp56s0): set-hw-addr: reset MAC address to 9C:C7:D3:A2:E0:CA (unmanage)
Jun 21 23:25:52 diesel systemd[1]: Reached target Sleep.
Jun 21 23:25:52 diesel systemd[1]: Starting System Suspend then Hibernate...
Jun 21 23:25:52 diesel wpa_supplicant[701]: wlp56s0: CTRL-EVENT-DSCP-POLICY clear_all
Jun 21 23:25:52 diesel systemd-sleep[1446]: User sessions remain unfrozen on explicit request ($SYSTEMD_SLEEP_FREEZE_USER_SESSIONS=0).
Jun 21 23:25:52 diesel systemd-sleep[1446]: This is not recommended, and might result in unexpected behavior, particularly
Jun 21 23:25:52 diesel systemd-sleep[1446]: in suspend-then-hibernate operations or setups with encrypted home directories.
Jun 21 23:25:52 diesel wpa_supplicant[701]: wlp56s0: CTRL-EVENT-DSCP-POLICY clear_all
Jun 21 23:25:52 diesel wpa_supplicant[701]: nl80211: deinit ifname=wlp56s0 disabled_11b_rates=0
Jun 21 23:25:52 diesel systemd-sleep[1446]: Performing sleep operation 'suspend'...
Jun 21 23:25:52 diesel kernel: PM: suspend entry (s2idle)
Jun 21 23:25:52 diesel kernel: Filesystems sync: 0.001 seconds
Jun 21 23:25:54 diesel kernel: Freezing user space processes
Jun 21 23:25:54 diesel kernel: Freezing user space processes completed (elapsed 0.001 seconds)
Jun 21 23:25:54 diesel kernel: OOM killer disabled.
Jun 21 23:25:54 diesel kernel: Freezing remaining freezable tasks
Jun 21 23:25:54 diesel kernel: Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
Jun 21 23:25:54 diesel kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Jun 21 23:25:54 diesel kernel: NVRM: GPU 0000:01:00.0: PreserveVideoMemoryAllocations module parameter is set. System Power Management attempted without driver procfs suspe
nd interface. Please refer to the 'Configuring Power Management Support' section in the driver README.
Jun 21 23:25:54 diesel kernel: nvidia 0000:01:00.0: PM: pci_pm_suspend(): nv_pmops_suspend [nvidia] returns -5
Jun 21 23:25:54 diesel kernel: nvidia 0000:01:00.0: PM: dpm_run_callback(): pci_pm_suspend returns -5
Jun 21 23:25:54 diesel bluetoothd[632]: Battery Provider Manager destroyed
Jun 21 23:25:54 diesel kernel: nvidia 0000:01:00.0: PM: failed to suspend async: error -5
Jun 21 23:25:54 diesel kernel: PM: Some devices failed to suspend, or early wake event detected
Jun 21 23:25:54 diesel kernel: spd5118 16-0050: Failed to write b = 0: -6
Jun 21 23:25:54 diesel kernel: spd5118 16-0050: PM: dpm_run_callback(): spd5118_resume [spd5118] returns -6
Jun 21 23:25:54 diesel systemd[1]: Starting Load/Save RF Kill Switch Status...
Jun 21 23:25:54 diesel kernel: spd5118 16-0050: PM: failed to resume async: error -6
Jun 21 23:25:54 diesel kernel: i915 0000:00:02.0: [drm] GT0: GuC firmware i915/adlp_guc_70.bin version 70.49.4
Jun 21 23:25:54 diesel kernel: i915 0000:00:02.0: [drm] GT0: HuC firmware i915/tgl_huc.bin version 7.9.3
Jun 21 23:25:54 diesel kernel: i915 0000:00:02.0: [drm] GT0: HuC: authenticated for all workloads
Jun 21 23:25:54 diesel kernel: i915 0000:00:02.0: [drm] GT0: GUC: submission enabled
Jun 21 23:25:54 diesel kernel: i915 0000:00:02.0: [drm] GT0: GUC: SLPC enabled
Jun 21 23:25:54 diesel kernel: i915 0000:00:02.0: [drm] GT0: GUC: RC enabled
Jun 21 23:25:54 diesel kernel: usb 3-10: reset full-speed USB device number 3 using xhci_hcd
Jun 21 23:25:54 diesel kernel: mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_ops [i915])
Jun 21 23:25:54 diesel kernel: OOM killer enabled.
Jun 21 23:25:54 diesel kernel: Restarting tasks: Starting
Jun 21 23:25:54 diesel kernel: mei_pxp 0000:00:16.0-fbf6fcf1-96cf-4e2e-a6a6-1bab8cbe36b1: bound 0000:00:02.0 (ops i915_pxp_tee_component_ops [i915])
Jun 21 23:25:54 diesel kernel: Restarting tasks: Done
Jun 21 23:25:54 diesel kernel: efivarfs: resyncing variable state
Jun 21 23:25:54 diesel kernel: Bluetooth: hci0: RTL: examining hci_ver=0b hci_rev=000b lmp_ver=0b lmp_subver=8852
Jun 21 23:25:54 diesel kernel: Bluetooth: hci0: RTL: rom_version status=0 version=1
Jun 21 23:25:54 diesel kernel: Bluetooth: hci0: RTL: btrtl_initialize: key id 0
Jun 21 23:25:54 diesel kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8852bu_fw.bin
Jun 21 23:25:54 diesel kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8852bu_config.bin
Jun 21 23:25:54 diesel kernel: Bluetooth: hci0: RTL: cfg_sz 6, total sz 62539
Jun 21 23:25:54 diesel kernel: efivarfs: finished resyncing variable state
Jun 21 23:25:54 diesel kernel: random: crng reseeded on system resumption
Jun 21 23:25:54 diesel kernel: PM: suspend exit
Jun 21 23:25:54 diesel kernel: PM: suspend entry (s2idle)
Jun 21 23:25:54 diesel systemd[777]: Reached target Sound Card.
Jun 21 23:25:54 diesel kernel: Filesystems sync: 0.003 seconds
Jun 21 23:25:54 diesel systemd[1]: Stopped target Bluetooth Support.
Jun 21 23:25:54 diesel systemd[1]: Started Load/Save RF Kill Switch Status.
Jun 21 23:25:54 diesel systemd[1]: Reached target Bluetooth Support.
Jun 21 23:25:54 diesel systemd[748]: Reached target Bluetooth.
Jun 21 23:25:54 diesel systemd[777]: Reached target Bluetooth.
Jun 21 23:25:54 diesel kernel: Freezing user space processes
Jun 21 23:26:01 diesel kernel: Freezing user space processes completed (elapsed 0.001 seconds)
Jun 21 23:26:01 diesel kernel: OOM killer disabled.
Jun 21 23:26:01 diesel kernel: Freezing remaining freezable tasks
Jun 21 23:26:01 diesel kernel: Freezing remaining freezable tasks completed (elapsed 0.000 seconds)
Jun 21 23:26:01 diesel kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Jun 21 23:26:01 diesel kernel: NVRM: GPU 0000:01:00.0: PreserveVideoMemoryAllocations module parameter is set. System Power Management attempted without driver procfs suspe
nd interface. Please refer to the 'Configuring Power Management Support' section in the driver README.
Jun 21 23:26:01 diesel kernel: nvidia 0000:01:00.0: PM: pci_pm_suspend(): nv_pmops_suspend [nvidia] returns -5
Jun 21 23:26:01 diesel kernel: nvidia 0000:01:00.0: PM: dpm_run_callback(): pci_pm_suspend returns -5
Jun 21 23:26:01 diesel kernel: nvidia 0000:01:00.0: PM: failed to suspend async: error -5
Jun 21 23:26:01 diesel kernel: PM: Some devices failed to suspend, or early wake event detected
Jun 21 23:26:01 diesel kernel: spd5118 16-0050: PM: dpm_run_callback(): spd5118_resume [spd5118] returns -6
Jun 21 23:26:01 diesel kernel: spd5118 16-0050: PM: failed to resume async: error -6
Jun 21 23:26:01 diesel kernel: usb 3-10: reset full-speed USB device number 3 using xhci_hcd
Jun 21 23:26:01 diesel kernel: Bluetooth: hci0: command 0xfc20 tx timeout
Jun 21 23:26:01 diesel kernel: Bluetooth: hci0: RTL: Failed to generate devcoredump
Jun 21 23:26:01 diesel kernel: Bluetooth: hci0: Resetting usb device.
Jun 21 23:26:01 diesel kernel: Bluetooth: hci0: RTL: download fw command failed (-110)
Jun 21 23:26:01 diesel kernel: Bluetooth: hci0: Failed to read MSFT supported features (-110)
Jun 21 23:26:01 diesel kernel: Bluetooth: hci0: AOSP get vendor capabilities (-110)
Jun 21 23:26:01 diesel kernel: Bluetooth: hci0: unexpected event for opcode 0xfc20
Jun 21 23:26:01 diesel kernel: OOM killer enabled.
Jun 21 23:26:01 diesel kernel: Restarting tasks: Starting
Jun 21 23:26:01 diesel kernel: Bluetooth: hci0: RTL: examining hci_ver=0b hci_rev=000b lmp_ver=0b lmp_subver=8852
Jun 21 23:26:01 diesel kernel: Restarting tasks: Done
Jun 21 23:26:01 diesel kernel: efivarfs: resyncing variable state
Jun 21 23:26:01 diesel kernel: Bluetooth: hci0: RTL: rom_version status=0 version=1
Jun 21 23:26:01 diesel kernel: Bluetooth: hci0: RTL: btrtl_initialize: key id 0
Jun 21 23:26:01 diesel kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8852bu_fw.bin
Jun 21 23:26:01 diesel kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8852bu_config.bin
Jun 21 23:26:01 diesel kernel: Bluetooth: hci0: RTL: cfg_sz 6, total sz 62539
Jun 21 23:26:01 diesel systemd[748]: Stopped target Bluetooth.
Jun 21 23:26:01 diesel systemd[777]: Stopped target Bluetooth.
Jun 21 23:26:01 diesel systemd[1]: Stopped target Bluetooth Support.
Jun 21 23:26:01 diesel kernel: efivarfs: finished resyncing variable state
Jun 21 23:26:01 diesel kernel: random: crng reseeded on system resumption
Jun 21 23:26:01 diesel systemd-sleep[1446]: Failed to put system to sleep. System resumed again: Input/output error
Jun 21 23:26:01 diesel kernel: PM: suspend exit
Jun 21 23:26:01 diesel systemd[748]: Reached target Bluetooth.
Jun 21 23:26:01 diesel systemd[777]: Reached target Bluetooth.
Jun 21 23:26:01 diesel systemd[1]: Reached target Bluetooth Support.
Jun 21 23:26:01 diesel systemd[1]: systemd-suspend-then-hibernate.service: Main process exited, code=exited, status=1/FAILURE
Jun 21 23:26:01 diesel systemd[1]: systemd-suspend-then-hibernate.service: Failed with result 'exit-code'.
Jun 21 23:26:01 diesel systemd[1]: Failed to start System Suspend then Hibernate.
Jun 21 23:26:01 diesel systemd[1]: Dependency failed for Suspend; Hibernate if not used for a period of time.
Jun 21 23:26:01 diesel systemd[1]: suspend-then-hibernate.target: Job suspend-then-hibernate.target/start failed with result 'dependency'.
Jun 21 23:26:01 diesel systemd-logind[633]: Operation 'suspend-then-hibernate' finished.
Jun 21 23:26:01 diesel systemd[1]: Stopped target Sleep.
Jun 21 23:26:01 diesel NetworkManager[631]: <info>  [1782077161.1119] manager: sleep: wake requested (sleeping: yes  enabled: yes)
Jun 21 23:26:01 diesel NetworkManager[631]: <info>  [1782077161.1120] device (enp55s0): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')
Jun 21 23:26:01 diesel systemd[1]: Starting NVIDIA system resume actions...
Jun 21 23:26:01 diesel kernel: Generic FE-GE Realtek PHY r8169-0-3700:00: attached PHY driver (mii_bus:phy_addr=r8169-0-3700:00, irq=MAC)
Jun 21 23:26:01 diesel suspend[1563]: nvidia-resume.service
Jun 21 23:26:01 diesel logger[1563]: <13>Jun 21 23:26:01 suspend: nvidia-resume.service
Jun 21 23:26:01 diesel systemd[1]: nvidia-resume.service: Deactivated successfully.
Jun 21 23:26:01 diesel systemd[1]: Finished NVIDIA system resume actions.
Jun 21 23:26:01 diesel kernel: r8169 0000:37:00.0 enp55s0: Link is Down
Jun 21 23:26:01 diesel NetworkManager[631]: <info>  [1782077161.2955] device (wlp56s0): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')
Jun 21 23:26:01 diesel NetworkManager[631]: <info>  [1782077161.2968] device (p2p-dev-wlp56s0): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')
Jun 21 23:26:01 diesel NetworkManager[631]: <warn>  [1782077161.2969] device (p2p-dev-wlp56s0): error setting IPv4 forwarding to '0': Resource temporarily unavailable
Jun 21 23:26:01 diesel NetworkManager[631]: <info>  [1782077161.2972] manager: NetworkManager state is now DISCONNECTED
Jun 21 23:26:01 diesel NetworkManager[631]: <info>  [1782077161.3105] device (wlp56s0): supplicant interface state: internal-starting -> disconnected
Jun 21 23:26:01 diesel NetworkManager[631]: <info>  [1782077161.3105] device (p2p-dev-wlp56s0): state change: unavailable -> unmanaged (reason 'unmanaged-link-not-init', managed-type: 'removed')
Jun 21 23:26:01 diesel NetworkManager[631]: <info>  [1782077161.3110] Wi-Fi P2P device controlled by interface wlp56s0 created
Jun 21 23:26:01 diesel NetworkManager[631]: <info>  [1782077161.3112] manager: (p2p-dev-wlp56s0): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/5)
Jun 21 23:26:01 diesel NetworkManager[631]: <info>  [1782077161.3114] device (p2p-dev-wlp56s0): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')
Jun 21 23:26:01 diesel NetworkManager[631]: <warn>  [1782077161.3115] device (p2p-dev-wlp56s0): error setting IPv4 forwarding to '0': Resource temporarily unavailable
Jun 21 23:26:01 diesel NetworkManager[631]: <info>  [1782077161.3119] device (wlp56s0): state change: unavailable -> disconnected (reason 'supplicant-available', managed-type: 'full')
Jun 21 23:26:01 diesel NetworkManager[631]: <info>  [1782077161.3123] device (p2p-dev-wlp56s0): state change: unavailable -> disconnected (reason 'none', managed-type: 'full')
Jun 21 23:26:01 diesel kernel: Bluetooth: hci0: RTL: fw version 0x127cfd78
Jun 21 23:26:01 diesel kernel: Bluetooth: hci0: AOSP extensions version v1.00
Jun 21 23:26:01 diesel kernel: Bluetooth: MGMT ver 1.23
Jun 21 23:26:01 diesel bluetoothd[632]: Battery Provider Manager created
Jun 21 23:26:01 diesel bluetoothd[632]: Failed to set default system config for hci0
Jun 21 23:26:05 diesel NetworkManager[631]: <info>  [1782077165.0482] policy: auto-activating connection 'Kamu' (fb012141-56f4-4754-b662-5486e4e1fee3)
Jun 21 23:26:05 diesel NetworkManager[631]: <info>  [1782077165.0488] device (wlp56s0): Activation: starting connection 'Kamu' (fb012141-56f4-4754-b662-5486e4e1fee3)
Jun 21 23:26:05 diesel NetworkManager[631]: <info>  [1782077165.0489] device (wlp56s0): state change: disconnected -> prepare (reason 'none', managed-type: 'full')
Jun 21 23:26:05 diesel NetworkManager[631]: <info>  [1782077165.0492] manager: NetworkManager state is now CONNECTING
Jun 21 23:26:05 diesel NetworkManager[631]: <info>  [1782077165.0495] device (wlp56s0): state change: prepare -> config (reason 'none', managed-type: 'full')
Jun 21 23:26:05 diesel NetworkManager[631]: <info>  [1782077165.0497] device (wlp56s0): Activation: (wifi) access point 'Kamu' has security, but secrets are required.
Jun 21 23:26:05 diesel NetworkManager[631]: <info>  [1782077165.0497] device (wlp56s0): state change: config -> need-auth (reason 'none', managed-type: 'full')
Jun 21 23:26:05 diesel NetworkManager[631]: <info>  [1782077165.0498] sup-iface[c5d755d2db644553,1,wlp56s0]: wps: type pbc start...
Jun 21 23:26:05 diesel NetworkManager[631]: <info>  [1782077165.0511] device (wlp56s0): state change: need-auth -> prepare (reason 'none', managed-type: 'full')
Jun 21 23:26:05 diesel NetworkManager[631]: <info>  [1782077165.0514] device (wlp56s0): state change: prepare -> config (reason 'none', managed-type: 'full')
Jun 21 23:26:05 diesel wpa_supplicant[701]: wlp56s0: WPS-PBC-ACTIVE
Jun 21 23:26:05 diesel wpa_supplicant[701]: wlp56s0: WPS-CANCEL
Jun 21 23:26:05 diesel NetworkManager[631]: <info>  [1782077165.0516] device (wlp56s0): Activation: (wifi) connection 'Kamu' has security, and secrets exist.  No new secrets needed.
Jun 21 23:26:05 diesel NetworkManager[631]: <info>  [1782077165.0516] Config: added 'ssid' value 'Kamu'
Jun 21 23:26:05 diesel NetworkManager[631]: <info>  [1782077165.0516] Config: added 'scan_ssid' value '1'
Jun 21 23:26:05 diesel NetworkManager[631]: <info>  [1782077165.0516] Config: added 'bgscan' value 'simple:30:-65:300'
Jun 21 23:26:05 diesel NetworkManager[631]: <info>  [1782077165.0517] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK SAE FT-SAE'
Jun 21 23:26:05 diesel NetworkManager[631]: <info>  [1782077165.0517] Config: added 'auth_alg' value 'OPEN'
Jun 21 23:26:05 diesel NetworkManager[631]: <info>  [1782077165.0517] Config: added 'psk' value '<hidden>'
Jun 21 23:26:05 diesel NetworkManager[631]: <info>  [1782077165.0524] device (wlp56s0): supplicant interface state: disconnected -> scanning
Jun 21 23:26:05 diesel NetworkManager[631]: <info>  [1782077165.0524] device (p2p-dev-wlp56s0): supplicant management interface state: disconnected -> scanning
Jun 21 23:26:05 diesel wpa_supplicant[701]: wlp56s0: SME: Trying to authenticate with a2:b5:3c:cd:84:e5 (SSID='Kamu' freq=2432 MHz)
Jun 21 23:26:05 diesel NetworkManager[631]: <info>  [1782077165.3817] device (wlp56s0): supplicant interface state: scanning -> authenticating
Jun 21 23:26:05 diesel NetworkManager[631]: <info>  [1782077165.3818] device (p2p-dev-wlp56s0): supplicant management interface state: scanning -> authenticating
Jun 21 23:26:05 diesel kernel: wlp56s0: authenticate with a2:b5:3c:cd:84:e5 (local address=9c:c7:d3:a2:e0:ca)
Jun 21 23:26:05 diesel kernel: wlp56s0: send auth to a2:b5:3c:cd:84:e5 (try 1/3)
Jun 21 23:26:05 diesel kernel: wlp56s0: authenticated
Jun 21 23:26:05 diesel wpa_supplicant[701]: wlp56s0: Trying to associate with a2:b5:3c:cd:84:e5 (SSID='Kamu' freq=2432 MHz)
Jun 21 23:26:05 diesel NetworkManager[631]: <info>  [1782077165.3864] device (wlp56s0): supplicant interface state: authenticating -> associating
Jun 21 23:26:05 diesel NetworkManager[631]: <info>  [1782077165.3864] device (p2p-dev-wlp56s0): supplicant management interface state: authenticating -> associating
Jun 21 23:26:05 diesel kernel: wlp56s0: associate with a2:b5:3c:cd:84:e5 (try 1/3)
Jun 21 23:26:05 diesel kernel: wlp56s0: RX AssocResp from a2:b5:3c:cd:84:e5 (capab=0x1411 status=0 aid=13)
Jun 21 23:26:05 diesel kernel: wlp56s0: associated
Jun 21 23:26:05 diesel kernel: wlp56s0: Limiting TX power to 20 (20 - 0) dBm as advertised by a2:b5:3c:cd:84:e5
Jun 21 23:26:05 diesel wpa_supplicant[701]: wlp56s0: Associated with a2:b5:3c:cd:84:e5
Jun 21 23:26:05 diesel wpa_supplicant[701]: wlp56s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Jun 21 23:26:05 diesel NetworkManager[631]: <info>  [1782077165.5099] device (wlp56s0): supplicant interface state: associating -> 4way_handshake
Jun 21 23:26:05 diesel NetworkManager[631]: <info>  [1782077165.5100] device (p2p-dev-wlp56s0): supplicant management interface state: associating -> 4way_handshake
Jun 21 23:26:05 diesel wpa_supplicant[701]: wlp56s0: WPA: Key negotiation completed with a2:b5:3c:cd:84:e5 [PTK=CCMP GTK=CCMP]
Jun 21 23:26:05 diesel wpa_supplicant[701]: wlp56s0: CTRL-EVENT-CONNECTED - Connection to a2:b5:3c:cd:84:e5 completed [id=0 id_str=]
Jun 21 23:26:05 diesel NetworkManager[631]: <info>  [1782077165.5304] device (wlp56s0): supplicant interface state: 4way_handshake -> completed
Jun 21 23:26:05 diesel NetworkManager[631]: <info>  [1782077165.5305] device (wlp56s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "Kamu"
Jun 21 23:26:05 diesel NetworkManager[631]: <info>  [1782077165.5305] device (p2p-dev-wlp56s0): supplicant management interface state: 4way_handshake -> completed
Jun 21 23:26:05 diesel NetworkManager[631]: <info>  [1782077165.5308] device (wlp56s0): state change: config -> ip-config (reason 'none', managed-type: 'full')
Jun 21 23:26:05 diesel NetworkManager[631]: <info>  [1782077165.5314] dhcp4 (wlp56s0): activation: beginning transaction (timeout in 45 seconds)
Jun 21 23:26:05 diesel NetworkManager[631]: <info>  [1782077165.5359] dhcp4 (wlp56s0): state changed new lease, address=192.168.1.81, acd pending
Jun 21 23:26:05 diesel NetworkManager[631]: <info>  [1782077165.6746] dhcp4 (wlp56s0): state changed new lease, address=192.168.1.81
Jun 21 23:26:05 diesel NetworkManager[631]: <info>  [1782077165.6769] policy: set 'Kamu' (wlp56s0) as default for IPv4 routing and DNS
Jun 21 23:26:05 diesel NetworkManager[631]: <info>  [1782077165.6948] device (wlp56s0): state change: ip-config -> ip-check (reason 'none', managed-type: 'full')
Jun 21 23:26:05 diesel NetworkManager[631]: <info>  [1782077165.6971] device (wlp56s0): state change: ip-check -> secondaries (reason 'none', managed-type: 'full')
Jun 21 23:26:05 diesel NetworkManager[631]: <info>  [1782077165.6974] device (wlp56s0): state change: secondaries -> activated (reason 'none', managed-type: 'full')
Jun 21 23:26:05 diesel NetworkManager[631]: <info>  [1782077165.6978] manager: NetworkManager state is now CONNECTED_SITE
Jun 21 23:26:05 diesel systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Jun 21 23:26:05 diesel NetworkManager[631]: <info>  [1782077165.6983] device (wlp56s0): Activation: successful, device activated.
Jun 21 23:26:05 diesel systemd[1]: Starting Network Manager Script Dispatcher Service...
Jun 21 23:26:05 diesel systemd[1]: Started Network Manager Script Dispatcher Service.
Jun 21 23:26:05 diesel NetworkManager[631]: <info>  [1782077165.9013] manager: NetworkManager state is now CONNECTED_GLOBAL
Jun 21 23:26:06 diesel systemd[1]: systemd-rfkill.service: Deactivated successfully.
Jun 21 23:26:06 diesel NetworkManager[631]: <info>  [1782077166.9306] dhcp6 (wlp56s0): activation: beginning transaction (timeout in 45 seconds)
Jun 21 23:26:06 diesel NetworkManager[631]: <info>  [1782077166.9328] policy: set 'Kamu' (wlp56s0) as default for IPv6 routing and DNS
Jun 21 23:26:06 diesel NetworkManager[631]: <info>  [1782077166.9366] dhcp6 (wlp56s0): state changed new lease
Jun 21 23:26:15 diesel systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Jun 21 23:26:15 diesel systemd[777]: Current graphical user session is inactive.
Jun 21 23:26:15 diesel systemd[777]: Dependency failed for Portal service.
Jun 21 23:26:15 diesel systemd[777]: xdg-desktop-portal.service: Job xdg-desktop-portal.service/start failed with result 'dependency'.
Jun 21 23:26:15 diesel systemd[1]: Starting Time & Date Service...
Jun 21 23:26:15 diesel systemd[1]: Started Time & Date Service.

It feels like the situation only got worse

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 76,740

Re: Fresh install does not wake from suspend

Jun 21 23:26:01 diesel kernel: NVRM: GPU 0000:01:00.0: PreserveVideoMemoryAllocations module parameter is set. System Power Management attempted without driver procfs suspe
nd interface. Please refer to the 'Configuring Power Management Support' section in the driver README.
Jun 21 23:26:01 diesel kernel: nvidia 0000:01:00.0: PM: pci_pm_suspend(): nv_pmops_suspend [nvidia] returns -5
Jun 21 23:26:01 diesel kernel: nvidia 0000:01:00.0: PM: dpm_run_callback(): pci_pm_suspend returns -5
Jun 21 23:26:01 diesel kernel: nvidia 0000:01:00.0: PM: failed to suspend async: error -5
Jun 21 23:26:01 diesel kernel: PM: Some devices failed to suspend, or early wake event detected

https://wiki.archlinux.org/title/NVIDIA … er_suspend

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Kermir

Member

Registered: 2026-06-21

Posts: 18

Re: Fresh install does not wake from suspend

Nvidia hibernate, suspend and resume services are enabled and running

[kermir@diesel ~]$ sort /proc/driver/nvidia/params
CoherentGPUMemoryMode: ""
CreateImexChannel0: 0
DeviceFileGID: 0
DeviceFileMode: 438
DeviceFileUID: 0
DmaRemapPeerMmio: 1
DynamicPowerManagement: 2
DynamicPowerManagementVideoMemoryThreshold: 200
EnableDbgBreakpoint: 0
EnableGpuFirmware: 0
EnableGpuFirmwareLogs: 2
EnableMSI: 1
EnablePCIeGen3: 0
EnablePCIERelaxedOrderingMode: 0
EnableResizableBar: 0
EnableS0ixPowerManagement: 1
EnableStreamMemOPs: 0
EnableUserNUMAManagement: 1
ExcludedGpus: ""
GpuBlacklist: ""
GrdmaPciTopoCheckOverride: 0
IgnoreMMIOCheck: 0
ImexChannelCount: 2048
InitializeSystemMemoryAllocations: 1
KMallocHeapMaxSize: 0
MemoryPoolSize: 0
ModifyDeviceFiles: 1
NvLinkDisable: 0
OpenRmEnableUnsupportedGpus: 1
PreserveVideoMemoryAllocations: 1
RegisterPCIDriver: 1
RegistryDwords: ""
RegistryDwordsPerDevice: ""
ResmanDebugLevel: 4294967295
RmLogonRC: 1
RmMsg: ""
RmNvlinkBandwidthLinkCount: 0
RmProfilingAdminOnly: 1
S0ixPowerManagementVideoMemoryThreshold: 256
TemporaryFilePath: "/var/tmp"
UsePageAttributeTable: 4294967295
VMallocHeapMaxSize: 0
[kermir@diesel ~]$ 

I do have PreserveVideoMemoryAllocations enabled

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 76,740

Re: Fresh install does not wake from suspend

Please post your complete system journal for the boot:

sudo journalctl -b | curl -s -H "Accept: application/json, */*" --upload-file - 'https://paste.c-net.org/'

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Kermir

Member

Registered: 2026-06-21

Posts: 18

Re: Fresh install does not wake from suspend

Here you go

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 76,740

Re: Fresh install does not wake from suspend

systemctl status nvidia-suspend.service

There's no trace of that

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Kermir

Member

Registered: 2026-06-21

Posts: 18

Re: Fresh install does not wake from suspend

It may have been because since then i rebooted a couple of times

[kermir@diesel ~]$ systemctl status nvidia-hibernate.service
○ nvidia-hibernate.service - NVIDIA system hibernate actions
     Loaded: loaded (/usr/lib/systemd
/system/nvidia-hibernate.service; enabled; preset: disabled)
     Active: inactive (dead)
[kermir@diesel ~]$ systemctl status nvidia-suspend.service
○ nvidia-suspend.service - NVIDIA system suspend actions
     Loaded: loaded (/usr/lib/systemd/s
ystem/nvidia-suspend.service; enabled; preset: disabled)
     Active: inactive (dead)
[kermir@diesel ~]$ systemctl status nvidia-resume.service
○ nvidia-resume.service - NVIDIA system resume actions
     Loaded: loaded (/usr/lib/systemd/sy
stem/nvidia-resume.service; enabled; preset: disabled)
     Active: inactive (dead) since Sun 2026-06-21 23:45:23 CEST; 13min ago
 Invocation: f87f5e049a204ca6a829696871dbf63b
    Process: 1747 ExecStart=/usr/bin/logger -t suspend -s nvidia-resume.service (code=exited, status=0/
SUCCESS)
    Process: 1749 ExecStart=/usr/bin/nvidia-sleep.sh resume (code=exited, status=0/SUCCESS)
   Main PID: 1749 (code=exited, status=0/SUCCESS)
   Mem peak: 2.4M
        CPU: 16ms

Jun 21 23:45:23 diesel systemd[1]: Starting NVIDIA system resume actions...
Jun 21 23:45:23 diesel suspend[1747]: nvidia-resume.service
Jun 21 23:45:23 diesel logger[1747]: <13>Jun 21 23:45:23 suspend: nvidia-resume.service
Jun 21 23:45:23 diesel systemd[1]: nvidia-resume.service: Deactivated successfully.
Jun 21 23:45:23 diesel systemd[1]: Finished NVIDIA system resume actions.
[kermir@diesel ~]$ 

But I did not fiddle with these since enabling them way before I shared the logs

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 76,740

Re: Fresh install does not wake from suspend

For this test you can just completely deactivate the VRAM preservation, it might leave any GUI session w/ black or garbled textures but resuming from the multi-user.target should™ work and we only want to figure whether the resume currently fails over the nvidia-open drivers.

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Kermir

Member

Registered: 2026-06-21

Posts: 18

Re: Fresh install does not wake from suspend

I disabled VRAM preservation and couldn't enter sleep and just threw me back
https://paste.c-net.org/WaivedLoverboy

However when swtiching back to nvidia-open-dkms I am able to enter sleep but then again I can't wake it up.
BUT! I've used rtcwake to put the system to suspend and then wake itself up. It was able to come back (still no reaction to keyboard, touchpad or powerbutton, it was simply a 20s timer on rtcwake) however the network card wasn't responding so i had to move the journalctl -b into a file and then upload that to the site, but it should have everythinig after it comes back from sleep by itself.
https://paste.c-net.org/BottlesSweetie

Kermir

Member

Registered: 2026-06-21

Posts: 18

Re: Fresh install does not wake from suspend

I did it again just to make sure I share the right logs:
https://paste.c-net.org/HotheadSwimmer

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 76,740

Re: Fresh install does not wake from suspend

https://paste.c-net.org/WaivedLoverboy

Jun 22 14:03:54 diesel 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.
Jun 22 14:03:54 diesel kernel: nvidia 0000:01:00.0: PM: pci_pm_suspend(): nv_pmops_suspend [nvidia] returns -5
Jun 22 14:03:54 diesel kernel: nvidia 0000:01:00.0: PM: dpm_run_callback(): pci_pm_suspend returns -5

PreserveVideoMemoryAllocations is still set, add "nvidia.PreserveVideoMemoryAllocations=0" to the https://wiki.archlinux.org/title/Kernel_parameters

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Kermir

Member

Registered: 2026-06-21

Posts: 18

Re: Fresh install does not wake from suspend

Okay i made a mistake but now i fixed that. Now the laptop goes to sleep on the older nvidia-580xx-dkms drivers too. However i still can't wake it up by keyboard, touchpad or power button. It only wakes itself up if use

rtxwake -m mem -s 20

and the timer wakes it up. And from that rtcwake attempt here's the journal:
https://paste.c-net.org/DoorkChorus
And here is confirmation that preserve memory is disabled:

[kermir@diesel ~]$ sort /proc/driver/nvidia/params 
CoherentGPUMemoryMode: ""
CreateImexChannel0: 0
DeviceFileGID: 0
DeviceFileMode: 438
DeviceFileUID: 0
DmaRemapPeerMmio: 1
DynamicPowerManagement: 2
DynamicPowerManagementVideoMemoryThreshold: 200
EnableDbgBreakpoint: 0
EnableGpuFirmware: 0
EnableGpuFirmwareLogs: 2
EnableMSI: 1
EnablePCIeGen3: 0
EnablePCIERelaxedOrderingMode: 0
EnableResizableBar: 0
EnableS0ixPowerManagement: 1
EnableStreamMemOPs: 0
EnableUserNUMAManagement: 1
ExcludedGpus: ""
GpuBlacklist: ""
GrdmaPciTopoCheckOverride: 0
IgnoreMMIOCheck: 0
ImexChannelCount: 2048
InitializeSystemMemoryAllocations: 1
KMallocHeapMaxSize: 0
MemoryPoolSize: 0
ModifyDeviceFiles: 1
NvLinkDisable: 0
OpenRmEnableUnsupportedGpus: 1
PreserveVideoMemoryAllocations: 0
RegisterPCIDriver: 1
RegistryDwords: ""
RegistryDwordsPerDevice: ""
ResmanDebugLevel: 4294967295
RmLogonRC: 1
RmMsg: ""
RmNvlinkBandwidthLinkCount: 0
RmProfilingAdminOnly: 1
S0ixPowerManagementVideoMemoryThreshold: 256
TemporaryFilePath: ""
UsePageAttributeTable: 4294967295
VMallocHeapMaxSize: 0
[kermir@diesel ~]$ 

I would give a log of using systemctl sleep/suspend or the keycode on my keyboard for sleep but because of not being able to wake up the laptop the log gets cut when it enters sleep fully.

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 76,740

Re: Fresh install does not wake from suspend

However i still can't wake it up by keyboard, touchpad or power button.

cat /proc/acpi/wakeup

There's some noise from rtw89_8852be but does the system otherwise reasonably work after the rtc wake?

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Kermir

Member

Registered: 2026-06-21

Posts: 18

Re: Fresh install does not wake from suspend

besides the network card not functioning (different issue) everything else works after resume.
As for the acpis

[kermir@diesel ~]$ cat /proc/acpi/wakeup
Device	S-state	 Status   Sysfs node
PEG1	 S4	*enabled   pci:0000:00:01.0
PEGP	 S4	*disabled  pci:0000:01:00.0
		*disabled  auxiliary:acpi.video_bus.0
PEG2	 S4	*disabled
PEGP	 S4	*disabled
PEG0	 S4	*disabled  pci:0000:00:06.0
PEGP	 S4	*disabled
RP09	 S4	*disabled
PXSX	 S4	*disabled
RP10	 S4	*disabled
PXSX	 S4	*disabled
RP11	 S4	*disabled
PXSX	 S4	*disabled
RP12	 S4	*disabled
PXSX	 S4	*disabled
RP13	 S4	*disabled
PXSX	 S4	*disabled
RP14	 S4	*disabled
PXSX	 S4	*disabled
RP15	 S4	*disabled
PXSX	 S4	*disabled
RP16	 S4	*disabled
PXSX	 S4	*disabled
RP01	 S4	*disabled
PXSX	 S4	*disabled
RP02	 S4	*disabled
PXSX	 S4	*disabled
RP03	 S4	*disabled
PXSX	 S4	*disabled
RP04	 S4	*disabled
PXSX	 S4	*disabled
RP05	 S4	*disabled
PXSX	 S4	*disabled
RP06	 S4	*disabled
PXSX	 S4	*disabled
RP07	 S4	*enabled   pci:0000:00:1c.0
PXSX	 S4	*disabled  pci:0000:37:00.0
RP08	 S3	*enabled   pci:0000:00:1c.7
PXSX	 S4	*disabled  pci:0000:38:00.0
RP17	 S4	*disabled
PXSX	 S4	*disabled
RP18	 S4	*disabled
PXSX	 S4	*disabled
RP19	 S4	*disabled
PXSX	 S4	*disabled
RP20	 S4	*disabled
PXSX	 S4	*disabled
RP21	 S4	*disabled
PXSX	 S4	*disabled
RP22	 S4	*disabled
PXSX	 S4	*disabled
RP23	 S4	*disabled
PXSX	 S4	*disabled
RP24	 S4	*disabled
PXSX	 S4	*disabled
XHCI	 S3	*enabled   pci:0000:00:14.0
XDCI	 S4	*disabled
HDAS	 S4	*disabled  pci:0000:00:1f.3
CNVW	 S4	*disabled
TXHC	 S3	*enabled   pci:0000:00:0d.0
TDM0	 S4	*enabled   pci:0000:00:0d.2
TDM1	 S4	*disabled
TRP0	 S4	*enabled   pci:0000:00:07.0
PXSX	 S4	*disabled
TRP1	 S4	*disabled
PXSX	 S4	*disabled
TRP2	 S4	*disabled
PXSX	 S4	*disabled
TRP3	 S4	*disabled
PXSX	 S4	*disabled
AWAC	 S4	*enabled   platform:ACPI000E:00
[kermir@diesel ~]$ 

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 76,740

Re: Fresh install does not wake from suspend

There's no LID and nothing that looks like PWR, XHCI is enabled, can you wake the system w/ a USB device?
(nb. that for notebooks that typically only works when the system is and stays on AC for the entire duration of the sleep)

Is

		*disabled  auxiliary:acpi.video_bus.0

a copy/paste error or verbatim in that file?

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Kermir

Member

Registered: 2026-06-21

Posts: 18

Re: Fresh install does not wake from suspend

a copy/paste error or verbatim in that file?

Not a copy paste error! That is literally there with no device. Its probably because of having an optimus system.

As for whetever it works with an USB device (In this case I used a keyboard): Yes!!.
It can resume it seems that for whatever reason its not detecting the built in keyboard when going to sleep. But it does detect it with an USB device, or in this case an USB keyboard.
Here is the journalctl
https://paste.c-net.org/RoycePointy

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 76,740

Re: Fresh install does not wake from suspend

Writing the 4l code into the file will flip the setting eg.

echo PXSX | sudo tee /proc/acpi/wakeup

should™ invert (all) PXSX devices.
Happy testing

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Kermir

Member

Registered: 2026-06-21

Posts: 18

Re: Fresh install does not wake from suspend

The keyboard itself doesn't seem to come up under /proc/acpi/wakeup and PXSX devices stay the same even after using the command.

with cat /proc/bus/input/devices i am able to find the keyboard and lid switch, but none of these seem to come up as a pci device.

I: Bus=0019 Vendor=0000 Product=0005 Version=0000
N: Name="Lid Switch"
P: Phys=PNP0C0D/button/input0
S: Sysfs=/devices/pci0000:00/0000:00:1f.0/PNP0C0D:01/input/input0
U: Uniq=
H: Handlers=event0 
B: PROP=0
B: EV=21
B: SW=1

I: Bus=0019 Vendor=0000 Product=0003 Version=0000
N: Name="Sleep Button"
P: Phys=PNP0C0E/button/input0
S: Sysfs=/devices/platform/PNP0C0E:00/input/input1
U: Uniq=
H: Handlers=kbd event1 
B: PROP=0
B: EV=3
B: KEY=4000 0 0

I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button"
P: Phys=PNP0C0C/button/input0
S: Sysfs=/devices/platform/PNP0C0C:00/input/input2
U: Uniq=
H: Handlers=kbd event2 
B: PROP=0
B: EV=3
B: KEY=8000 10000000000000 0

I: Bus=0011 Vendor=0001 Product=0001 Version=ab83
N: Name="AT Translated Set 2 keyboard"
P: Phys=isa0060/serio0/input0
S: Sysfs=/devices/platform/i8042/serio0/input/input3
U: Uniq=
H: Handlers=sysrq kbd leds event3 
B: PROP=0
B: EV=120013
B: KEY=402000007 ff803078f800d001 feffffdfffcfffff fffffffffffffffe
B: MSC=10
B: LED=7

I: Bus=0019 Vendor=0000 Product=0006 Version=0000
N: Name="Video Bus"
P: Phys=LNXVIDEO/video/input0
S: Sysfs=/devices/pci0000:00/0000:00:01.0/acpi.video_bus.0/input/input6
U: Uniq=
H: Handlers=kbd event6 
B: PROP=0
B: EV=3
B: KEY=3e000b00000000 0 0 0

I: Bus=0019 Vendor=0000 Product=0006 Version=0000
N: Name="Video Bus"
P: Phys=LNXVIDEO/video/input0
S: Sysfs=/devices/pci0000:00/acpi.video_bus.1/input/input7
U: Uniq=
H: Handlers=kbd event7 
B: PROP=0
B: EV=3
B: KEY=3e000b00000000 0 0 0

I: Bus=0018 Vendor=0b05 Product=19b6 Version=0100
N: Name="ITE5570:00 0B05:19B6"
P: Phys=i2c-ITE5570:00
S: Sysfs=/devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1/i2c-ITE5570:00/0018:0B05:19B6.0006/input/input10
U: Uniq=
H: Handlers=kbd event10 rfkill 
B: PROP=0
B: EV=13
B: KEY=80000000000000 0 0 0
B: MSC=10

I: Bus=0010 Vendor=001f Product=0001 Version=0100
N: Name="PC Speaker"
P: Phys=isa0061/input0
S: Sysfs=/devices/platform/pcspkr/input/input11
U: Uniq=
H: Handlers=kbd event11 
B: PROP=0
B: EV=40001
B: SND=6

I: Bus=0018 Vendor=093a Product=2008 Version=0100
N: Name="ASUP1205:00 093A:2008 Mouse"
P: Phys=i2c-ASUP1205:00
S: Sysfs=/devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-0/i2c-ASUP1205:00/0018:093A:2008.0005/input/input12
U: Uniq=
H: Handlers=event8 mouse1 
B: PROP=0
B: EV=17
B: KEY=30000 0 0 0 0
B: REL=903
B: MSC=10

I: Bus=0018 Vendor=093a Product=2008 Version=0100
N: Name="ASUP1205:00 093A:2008 Touchpad"
P: Phys=i2c-ASUP1205:00
S: Sysfs=/devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-0/i2c-ASUP1205:00/0018:093A:2008.0005/input/input13
U: Uniq=
H: Handlers=event9 mouse2 
B: PROP=5
B: EV=1b
B: KEY=e520 10000 0 0 0 0
B: ABS=2e0800000000003
B: MSC=20

I: Bus=0019 Vendor=0000 Product=0000 Version=0000
N: Name="Asus WMI hotkeys"
P: Phys=asus-nb-wmi/input0
S: Sysfs=/devices/platform/asus-nb-wmi/input/input14
U: Uniq=
H: Handlers=kbd event12 rfkill 
B: PROP=0
B: EV=100013
B: KEY=400000000000000 10000000c0000 400400000 800000000000 0 0 181606f00900c00 380027801701000 e000000000000 0
B: MSC=10

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA NVidia HDMI/DP,pcm=3"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input15
U: Uniq=
H: Handlers=event13 
B: PROP=0
B: EV=21
B: SW=140

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA NVidia HDMI/DP,pcm=7"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input16
U: Uniq=
H: Handlers=event14 
B: PROP=0
B: EV=21
B: SW=140

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA NVidia HDMI/DP,pcm=8"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input17
U: Uniq=
H: Handlers=event15 
B: PROP=0
B: EV=21
B: SW=140

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA NVidia HDMI/DP,pcm=9"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input18
U: Uniq=
H: Handlers=event16 
B: PROP=0
B: EV=21
B: SW=140

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA Intel PCH Headphone"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:1f.3/sound/card0/input19
U: Uniq=
H: Handlers=event17 
B: PROP=0
B: EV=21
B: SW=4

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 76,740

Re: Fresh install does not wake from suspend

PXSX devices stay the same even after using the command.

Can you flip the XDCI device?

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc