I have done some searching on this and cannot find a solution. I have tried disabling bluetooth, disabling the default power controls and using tlp (from here), suspending without power plugged in, sudo dnf update,
What happens is when I suspend, screen goes black, power button slowly blinks then, nothing. Power button, keyboard, mouse nothing will bring the system out of suspend. I have to hold the power button down for ~10 seconds to shut the machine off, then boot.
Any suggestions?
journalctl | grep -i suspend output:
Jan 03 10:07:55 fedora kernel: nvme 0000:c1:00.0: platform quirk: setting simple suspend
Jan 03 10:17:23 fedora kernel: Low-power S0 idle used by default for system suspend
Jan 03 10:17:24 fedora kernel: nvme 0000:c1:00.0: platform quirk: setting simple suspend
Jan 03 10:19:35 fedora dracut[22017]: -rw-r--r-- 1 root root 704 Nov 26 19:00 usr/lib/udev/rules.d/60-autosuspend.rules
Jan 03 10:19:55 fedora kernel: Low-power S0 idle used by default for system suspend
Jan 03 10:19:56 fedora kernel: nvme 0000:c1:00.0: platform quirk: setting simple suspend
Jan 03 11:22:06 fedora kernel: Low-power S0 idle used by default for system suspend
Jan 03 11:22:07 fedora kernel: nvme 0000:c1:00.0: platform quirk: setting simple suspend
Jan 03 11:53:52 fedora systemd-logind[1269]: The system will suspend now!
Jan 03 11:53:52 fedora ModemManager[1361]: [sleep-monitor-systemd] system is about to suspend
Jan 03 11:53:53 fedora systemd[1]: Starting systemd-suspend.service - System Suspend...
Jan 03 11:53:53 fedora systemd-sleep[7265]: in suspend-then-hibernate operations or setups with encrypted home directories.
Jan 03 11:53:53 fedora systemd-sleep[7265]: Performing sleep operation 'suspend'...
Jan 03 11:53:53 fedora kernel: PM: suspend entry (s2idle)
Jan 03 12:57:35 fedora kernel: Low-power S0 idle used by default for system suspend
Jan 03 12:57:36 fedora kernel: nvme 0000:c1:00.0: platform quirk: setting simple suspend
Jan 03 14:02:35 fedora systemd-logind[1266]: The system will suspend now!
Jan 03 14:02:35 fedora ModemManager[1354]: [sleep-monitor-systemd] system is about to suspend
Jan 03 14:02:35 fedora systemd[1]: Starting systemd-suspend.service - System Suspend...
Jan 03 14:02:35 fedora systemd-sleep[21938]: in suspend-then-hibernate operations or setups with encrypted home directories.
Jan 03 14:02:35 fedora systemd-sleep[21938]: Performing sleep operation 'suspend'...
Jan 03 14:02:35 fedora kernel: PM: suspend entry (s2idle)
Jan 03 14:03:43 fedora kernel: Low-power S0 idle used by default for system suspend
Jan 03 14:03:44 fedora kernel: nvme 0000:c1:00.0: platform quirk: setting simple suspend
output of dmesg | grep error
[ 3.363269] amdgpu 0000:c3:00.0: Direct firmware load for amdgpu/isp_4_1_0.bin failed with error -2
output of dmesg -a
Linux fedora 6.12.7-200.fc41.x86_64 #1 SMP PREEMPT_DYNAMIC Fri Dec 27 17:05:33 UTC 2024 x86_64 GNU/Linux
What do you have in the output from cat /sys/power/state?
I’d also have a look in your UEFI/BIOS setting for configuring different types of power-states fort suspend. Are you wanting to suspend to RAM or suspend to disk?
I’ll also assume that you’ve already ensured that you are using the latest firmware in this laptop and fwupdmgr doesn’t find any new firmware for your equipment.
fwupdmgr needs one of the following commands to tell it what is desired or it gives no useful info.
I would use it as sudo fwupdmgr get-updates
Use fwupdmgr --help to show the options and commands
Ok - execute the following to encourage the use of the S3 state for sleep: echo mem > /sys/power/state (prepend sudo if required)
Then try hibernating the system and see if it wakes up as expected. That value written into that entry is not permanent and will need to be scripted up in your profile script if it works for you.
WARNING: UEFI capsule updates not available or enabled in firmware setup
See PluginFlag:capsules unsupported · fwupd/fwupd Wiki · GitHub for more information.
Devices with no available firmware updates:
• ELAN0676:00 04F3:3195
• Integrated Camera
Devices with the latest available firmware version:
• KXG8AZNV1T02 LA KIOXIA
Yep - I wanted to force the system into a state of memory suspend by actually writing a value into that sys location, as per:
`state`
This file contains a list of strings representing sleep states supported by the kernel. Writing one of these strings into it causes the kernel to start a transition of the system into the sleep state represented by that string.
In particular, the “disk”, “freeze” and “standby” strings represent the hibernation, suspend-to-idle and standby sleep states, respectively. The “mem” string is interpreted in accordance with the contents of the `mem_sleep` file described below.
If the kernel does not support any system sleep states, this file is not present.
Have a read of that linked page, as it documents each way a system can be put into low-power sleep states. You could try experimenting with the various levels of power saving states, hopefully one of which works for your system and also allows it to recover fully when woken back up. That fact that your laptop has issues resuming from whatever the default is, is indicative of a driver or a piece of hardware which is not playing ball so finding an alternative that works for your specific configuration is going to take some experimentation, possibly with switching on debugging with the /sys/power/pm_trace file and seeing what is logged when you try to hibernate and resume.
I’m facing the same issue on my Lenovo LOQ Gen 9. Hard rebooting each time was really annoying. I’m using KDE so i ended up changing the lid close behaviour to turn off screen instead of sleep in the power management section in the system settings. you can also tweak the settings there to make it lock the screen after some time of inactivity as well.