Thanks a lot for sharing your settings. I took over the settings in logind.conf and sleep.conf, rebooted … and it does not work yet. 
Am I missing something?
Kind regards, Andreas.
PS: I admit I would prefer if it could be even default to hibernate the laptop if the battery is on 2%.
@Andreas_Tille - a couple of things to look at and try: do the logs indicate that the machine is trying to go into hibernation after suspending? Does it work properly if you invoke it from a shell? If it works when manually invoked then something is preventing it from triggering when you close the lid or the idle timeout triggers. In my case, after proving that suspend-then-hibernate worked when invoked manually, I dug around and found that the idle triggers in gnome were taking precedence over the ones configured in the files above, so I set them to a longer time. The logs hopefully will show you if the system is trying to flip from suspend to hibernate.
I’m on a different OS, but here’s a snip of the output of journalctl showing the system going into suspend, then later to hibernate, and finally coming out of it. I would try setting the timeout to hibernate to only a couple of minutes, then manually invoking suspend-then-hibernate from the shell. If that works you should see something similar in your logs:
.
.
.
May 18 22:04:16 manjaro systemd-logind[724]: System idle. Will suspend and later hibernate now.
May 18 22:04:16 manjaro systemd-logind[724]: Suspending, then hibernating...
May 18 22:04:16 manjaro ModemManager[770]: <info> [sleep-monitor-systemd] system is about to suspend
May 18 22:04:16 manjaro NetworkManager[737]: <info> [1684461856.7008] manager: sleep: sleep requested (sleeping: no enabled: yes)
May 18 22:04:16 manjaro NetworkManager[737]: <info> [1684461856.7009] manager: NetworkManager state is now ASLEEP
May 18 22:04:16 manjaro NetworkManager[737]: <info> [1684461856.7013] device (wlp170s0): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed')
May 18 22:04:16 manjaro dbus-daemon[715]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.6' (uid=0 pid=737 comm="/usr/bin/NetworkManager --no-daemon")
May 18 22:04:16 manjaro systemd[1]: Starting Network Manager Script Dispatcher Service...
May 18 22:04:16 manjaro dbus-daemon[715]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
May 18 22:04:16 manjaro systemd[1]: Started Network Manager Script Dispatcher Service.
May 18 22:04:16 manjaro kernel: wlp170s0: deauthenticating from aa:bb:cc:dd:ee:ff by local choice (Reason: 3=DEAUTH_LEAVING)
May 18 22:04:16 manjaro wpa_supplicant[1004]: wlp170s0: CTRL-EVENT-DISCONNECTED bssid=aa:bb:cc:dd:ee:ff reason=3 locally_generated=1
May 18 22:04:16 manjaro wpa_supplicant[1004]: wlp170s0: CTRL-EVENT-DSCP-POLICY clear_all
May 18 22:04:16 manjaro NetworkManager[737]: <info> [1684461856.9837] device (wlp170s0): supplicant interface state: completed -> disconnected
May 18 22:04:16 manjaro NetworkManager[737]: <info> [1684461856.9840] device (wlp170s0): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed')
May 18 22:04:16 manjaro wpa_supplicant[1004]: wlp170s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
May 18 22:04:16 manjaro NetworkManager[737]: <info> [1684461856.9857] dhcp4 (wlp170s0): canceled DHCP transaction
May 18 22:04:16 manjaro NetworkManager[737]: <info> [1684461856.9857] dhcp4 (wlp170s0): activation: beginning transaction (timeout in 45 seconds)
May 18 22:04:16 manjaro NetworkManager[737]: <info> [1684461856.9857] dhcp4 (wlp170s0): state changed no lease
May 18 22:04:17 manjaro NetworkManager[737]: <info> [1684461857.0898] device (wlp170s0): set-hw-addr: set MAC address to 11:22:33:44:55:66 (scanning)
May 18 22:04:17 manjaro wpa_supplicant[1004]: wlp170s0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=US
May 18 22:04:17 manjaro NetworkManager[737]: <info> [1684461857.2016] device (wlp170s0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
May 18 22:04:17 manjaro NetworkManager[737]: <info> [1684461857.2592] device (wlp170s0): set-hw-addr: reset MAC address to 99:88:77:66:55:44 (unmanage)
May 18 22:04:17 manjaro systemd[1]: Reached target Sleep.
May 18 22:04:17 manjaro wpa_supplicant[1004]: wlp170s0: CTRL-EVENT-DSCP-POLICY clear_all
May 18 22:04:17 manjaro systemd[1]: Starting Suspend; Hibernate if not used for a period of time...
May 18 22:04:17 manjaro wpa_supplicant[1004]: wlp170s0: CTRL-EVENT-DSCP-POLICY clear_all
May 18 22:04:17 manjaro wpa_supplicant[1004]: nl80211: deinit ifname=wlp170s0 disabled_11b_rates=0
May 18 22:04:17 manjaro systemd-sleep[244888]: Entering sleep state 'suspend'...
May 18 22:04:17 manjaro kernel: PM: suspend entry (deep)
May 19 10:04:31 manjaro kernel: Filesystems sync: 0.016 seconds
May 19 10:04:31 manjaro kernel: Freezing user space processes
May 19 10:04:31 manjaro kernel: Freezing user space processes completed (elapsed 0.001 seconds)
May 19 10:04:31 manjaro kernel: OOM killer disabled.
May 19 10:04:31 manjaro kernel: Freezing remaining freezable tasks
May 19 10:04:31 manjaro kernel: Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
May 19 10:04:31 manjaro kernel: printk: Suspending console(s) (use no_console_suspend to debug)
May 19 10:04:31 manjaro kernel: queueing ieee80211 work while going to suspend
May 19 10:04:31 manjaro kernel: ACPI: EC: interrupt blocked
May 19 10:04:31 manjaro kernel: ACPI: PM: Preparing to enter system sleep state S3
May 19 10:04:31 manjaro kernel: ACPI: EC: event blocked
May 19 10:04:31 manjaro kernel: ACPI: EC: EC stopped
May 19 10:04:31 manjaro kernel: ACPI: PM: Saving platform NVS memory
May 19 10:04:31 manjaro kernel: Disabling non-boot CPUs ...
May 19 10:04:31 manjaro kernel: smpboot: CPU 1 is now offline
May 19 10:04:31 manjaro kernel: smpboot: CPU 2 is now offline
May 19 10:04:31 manjaro kernel: smpboot: CPU 3 is now offline
May 19 10:04:31 manjaro kernel: smpboot: CPU 4 is now offline
May 19 10:04:31 manjaro kernel: smpboot: CPU 5 is now offline
May 19 10:04:31 manjaro kernel: smpboot: CPU 6 is now offline
May 19 10:04:31 manjaro kernel: smpboot: CPU 7 is now offline
May 19 10:04:31 manjaro kernel: ACPI: PM: Low-level resume complete
May 19 10:04:31 manjaro kernel: ACPI: EC: EC started
May 19 10:04:31 manjaro kernel: ACPI: PM: Restoring platform NVS memory
May 19 10:04:31 manjaro kernel: Enabling non-boot CPUs ...
May 19 10:04:31 manjaro kernel: x86: Booting SMP configuration:
May 19 10:04:31 manjaro kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2
May 19 10:04:31 manjaro kernel: CPU1 is up
May 19 10:04:31 manjaro kernel: smpboot: Booting Node 0 Processor 2 APIC 0x4
May 19 10:04:31 manjaro kernel: CPU2 is up
May 19 10:04:31 manjaro kernel: smpboot: Booting Node 0 Processor 3 APIC 0x6
May 19 10:04:31 manjaro kernel: CPU3 is up
May 19 10:04:31 manjaro kernel: smpboot: Booting Node 0 Processor 4 APIC 0x1
May 19 10:04:31 manjaro kernel: CPU4 is up
May 19 10:04:31 manjaro kernel: smpboot: Booting Node 0 Processor 5 APIC 0x3
May 19 10:04:31 manjaro kernel: CPU5 is up
May 19 10:04:31 manjaro kernel: smpboot: Booting Node 0 Processor 6 APIC 0x5
May 19 10:04:31 manjaro kernel: CPU6 is up
May 19 10:04:31 manjaro kernel: smpboot: Booting Node 0 Processor 7 APIC 0x7
May 19 10:04:31 manjaro kernel: CPU7 is up
May 19 10:04:31 manjaro kernel: ACPI: PM: Waking up from system sleep state S3
May 19 10:04:31 manjaro kernel: ACPI: EC: interrupt unblocked
May 19 10:04:31 manjaro kernel: ACPI: EC: event unblocked
May 19 10:04:31 manjaro kernel: nvme nvme0: 8/0/0 default/read/poll queues
May 19 10:04:31 manjaro kernel: nvme nvme0: Ignoring bogus Namespace Identifiers
May 19 10:04:31 manjaro kernel: usb 3-9: reset full-speed USB device number 2 using xhci_hcd
May 19 10:04:31 manjaro kernel: mei_hdcp 0000:00:16.0-guid: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915])
May 19 10:04:31 manjaro kernel: mei_pxp 0000:00:16.0-guid: bound 0000:00:02.0 (ops i915_pxp_tee_component_ops [i915])
May 19 10:04:31 manjaro kernel: OOM killer enabled.
May 19 10:04:31 manjaro kernel: Restarting tasks ... done.
May 19 10:04:31 manjaro kernel: random: crng reseeded on system resumption
May 19 10:04:31 manjaro systemd-sleep[244888]: System returned from sleep state.
May 19 10:04:31 manjaro kernel: PM: suspend exit
May 19 10:04:31 manjaro systemd[1]: Starting Network Manager Wait Online...
May 19 10:04:31 manjaro systemd[1]: Starting Rotate log files...
May 19 10:04:31 manjaro systemd[1]: Started Verify integrity of password and group files.
May 19 10:04:31 manjaro systemd[1]: Finished Network Manager Wait Online.
May 19 10:04:31 manjaro systemd[1]: Reached target Network is Online.
May 19 10:04:31 manjaro systemd[1]: Starting pkgfile database update...
May 19 10:04:31 manjaro systemd[1]: logrotate.service: Deactivated successfully.
May 19 10:04:31 manjaro kernel: ish-hid {yetanotherguid}: [hid-ish]: enum_devices_done OK, num_hid_devices=1
May 19 10:04:31 manjaro pkgfile[245053]: warning: download failed: https://mirror.funami.tech/manjaro/testing/core/x86_64/core.files: Could not resolve host: mirror.funami.tech
May 19 10:04:31 manjaro pkgfile[245053]: warning: download failed: https://mirror.funami.tech/manjaro/testing/extra/x86_64/extra.files: Could not resolve host: mirror.funami.tech
May 19 10:04:31 manjaro pkgfile[245053]: warning: download failed: https://mirror.funami.tech/manjaro/testing/community/x86_64/community.files: Could not resolve host: mirror.funami.tech
May 19 10:04:31 manjaro pkgfile[245053]: warning: download failed: https://mirror.funami.tech/manjaro/testing/multilib/x86_64/multilib.files: Could not resolve host: mirror.funami.tech
May 19 10:04:32 manjaro systemd[1]: Finished Rotate log files.
May 19 10:04:32 manjaro systemd[1]: pkgfile-update.service: Main process exited, code=exited, status=1/FAILURE
May 19 10:04:32 manjaro systemd[1]: pkgfile-update.service: Failed with result 'exit-code'.
May 19 10:04:32 manjaro systemd[1]: Failed to start pkgfile database update.
May 19 10:04:32 manjaro systemd[1]: shadow.service: Deactivated successfully.
May 19 10:04:32 manjaro systemd-sleep[244888]: Entering sleep state 'hibernate'...
May 19 10:04:32 manjaro kernel: PM: hibernation: hibernation entry
May 19 10:38:25 manjaro kernel: Filesystems sync: 0.122 seconds
May 19 10:38:25 manjaro kernel: Freezing user space processes
May 19 10:38:25 manjaro kernel: Freezing user space processes completed (elapsed 0.001 seconds)
May 19 10:38:25 manjaro kernel: OOM killer disabled.
May 19 10:38:25 manjaro kernel: PM: hibernation: Marking nosave pages: [mem 0x00000000-0x00000fff]
May 19 10:38:25 manjaro kernel: PM: hibernation: Marking nosave pages: [mem 0x0009f000-0x000fffff]
May 19 10:38:25 manjaro kernel: PM: hibernation: Marking nosave pages: [mem 0x39f99000-0x3a898fff]
May 19 10:38:25 manjaro kernel: PM: hibernation: Marking nosave pages: [mem 0x3f7ea000-0x3f838fff]
May 19 10:38:25 manjaro kernel: PM: hibernation: Marking nosave pages: [mem 0x3fa82000-0x3fa82fff]
May 19 10:38:25 manjaro kernel: PM: hibernation: Marking nosave pages: [mem 0x434af000-0x45bfefff]
May 19 10:38:25 manjaro kernel: PM: hibernation: Marking nosave pages: [mem 0x45c00000-0xffffffff]
May 19 10:38:25 manjaro kernel: PM: hibernation: Basic memory bitmaps created
May 19 10:38:25 manjaro kernel: PM: hibernation: Preallocating image memory
May 19 10:38:25 manjaro kernel: PM: hibernation: Allocated 4315278 pages for snapshot
May 19 10:38:25 manjaro kernel: PM: hibernation: Allocated 17261112 kbytes in 2.57 seconds (6716.38 MB/s)
May 19 10:38:25 manjaro kernel: Freezing remaining freezable tasks
May 19 10:38:25 manjaro kernel: Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
May 19 10:38:25 manjaro kernel: printk: Suspending console(s) (use no_console_suspend to debug)
May 19 10:38:25 manjaro kernel: queueing ieee80211 work while going to suspend
May 19 10:38:25 manjaro kernel: ACPI: EC: interrupt blocked
May 19 10:38:25 manjaro kernel: ACPI: PM: Preparing to enter system sleep state S4
May 19 10:38:25 manjaro kernel: ACPI: EC: event blocked
May 19 10:38:25 manjaro kernel: ACPI: EC: EC stopped
May 19 10:38:25 manjaro kernel: ACPI: PM: Saving platform NVS memory
May 19 10:38:25 manjaro kernel: Disabling non-boot CPUs ...
May 19 10:38:25 manjaro kernel: smpboot: CPU 1 is now offline
May 19 10:38:25 manjaro kernel: smpboot: CPU 2 is now offline
May 19 10:38:25 manjaro kernel: smpboot: CPU 3 is now offline
May 19 10:38:25 manjaro kernel: smpboot: CPU 4 is now offline
May 19 10:38:25 manjaro kernel: smpboot: CPU 5 is now offline
May 19 10:38:25 manjaro kernel: smpboot: CPU 6 is now offline
May 19 10:38:25 manjaro kernel: smpboot: CPU 7 is now offline
May 19 10:38:25 manjaro kernel: PM: hibernation: Creating image:
May 19 10:38:25 manjaro kernel: PM: hibernation: Need to copy 4292951 pages
May 19 10:38:25 manjaro kernel: PM: hibernation: Normal pages needed: 4292951 + 1024, available pages: 12427159
May 19 10:38:25 manjaro kernel: ACPI: PM: Restoring platform NVS memory
May 19 10:38:25 manjaro kernel: ACPI: EC: EC started
May 19 10:38:25 manjaro kernel: Enabling non-boot CPUs ...
May 19 10:38:25 manjaro kernel: x86: Booting SMP configuration:
May 19 10:38:25 manjaro kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2
May 19 10:38:25 manjaro kernel: CPU1 is up
May 19 10:38:25 manjaro kernel: smpboot: Booting Node 0 Processor 2 APIC 0x4
May 19 10:38:25 manjaro kernel: CPU2 is up
May 19 10:38:25 manjaro kernel: smpboot: Booting Node 0 Processor 3 APIC 0x6
May 19 10:38:25 manjaro kernel: CPU3 is up
May 19 10:38:25 manjaro kernel: smpboot: Booting Node 0 Processor 4 APIC 0x1
May 19 10:38:25 manjaro kernel: CPU4 is up
May 19 10:38:25 manjaro kernel: smpboot: Booting Node 0 Processor 5 APIC 0x3
May 19 10:38:25 manjaro kernel: CPU5 is up
May 19 10:38:25 manjaro kernel: smpboot: Booting Node 0 Processor 6 APIC 0x5
May 19 10:38:25 manjaro kernel: CPU6 is up
May 19 10:38:25 manjaro kernel: smpboot: Booting Node 0 Processor 7 APIC 0x7
May 19 10:38:25 manjaro kernel: CPU7 is up
May 19 10:38:25 manjaro kernel: ACPI: PM: Waking up from system sleep state S4
May 19 10:38:25 manjaro kernel: ACPI: EC: interrupt unblocked
May 19 10:38:25 manjaro kernel: ACPI: EC: event unblocked
May 19 10:38:25 manjaro kernel: usb usb1: root hub lost power or was reset
May 19 10:38:25 manjaro kernel: usb usb2: root hub lost power or was reset
May 19 10:38:25 manjaro kernel: usb usb3: root hub lost power or was reset
May 19 10:38:25 manjaro kernel: usb usb4: root hub lost power or was reset
May 19 10:38:25 manjaro kernel: nvme nvme0: 8/0/0 default/read/poll queues
May 19 10:38:25 manjaro kernel: nvme nvme0: Ignoring bogus Namespace Identifiers
May 19 10:38:25 manjaro kernel: usb 3-10: reset high-speed USB device number 3 using xhci_hcd
May 19 10:38:25 manjaro kernel: ish-hid {guid}: [hid-ish]: enum_devices_done OK, num_hid_devices=1
May 19 10:38:25 manjaro kernel: usb 3-9: reset full-speed USB device number 2 using xhci_hcd
May 19 10:38:25 manjaro kernel: mei_hdcp 0000:00:16.0-guid: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915])
May 19 10:38:25 manjaro kernel: PM: hibernation: Basic memory bitmaps freed
May 19 10:38:25 manjaro kernel: mei_pxp 0000:00:16.0-guid: bound 0000:00:02.0 (ops i915_pxp_tee_component_ops [i915])
May 19 10:38:25 manjaro kernel: OOM killer enabled.
May 19 10:38:25 manjaro bluetoothd[713]: Endpoint unregistered: sender=:1.157 path=/MediaEndpoint/A2DPSource/ldac
May 19 10:38:25 manjaro bluetoothd[713]: Endpoint unregistered: sender=:1.157 path=/MediaEndpoint/A2DPSink/aptx_hd
May 19 10:38:25 manjaro bluetoothd[713]: Endpoint unregistered: sender=:1.157 path=/MediaEndpoint/A2DPSource/aptx_hd
May 19 10:38:25 manjaro bluetoothd[713]: Endpoint unregistered: sender=:1.157 path=/MediaEndpoint/A2DPSink/aptx
May 19 10:38:25 manjaro bluetoothd[713]: Endpoint unregistered: sender=:1.157 path=/MediaEndpoint/A2DPSource/aptx
May 19 10:38:25 manjaro bluetoothd[713]: Endpoint unregistered: sender=:1.157 path=/MediaEndpoint/A2DPSink/aac
May 19 10:38:25 manjaro rtkit-daemon[1146]: The canary thread is apparently starving. Taking action.
May 19 10:38:25 manjaro rtkit-daemon[1146]: Demoting known real-time threads.
May 19 10:38:25 manjaro bluetoothd[713]: Endpoint unregistered: sender=:1.157 path=/MediaEndpoint/A2DPSource/aac
May 19 10:38:25 manjaro rtkit-daemon[1146]: Successfully demoted thread 116484 of process 116476.
May 19 10:38:25 manjaro bluetoothd[713]: Endpoint unregistered: sender=:1.157 path=/MediaEndpoint/A2DPSink/sbc
May 19 10:38:25 manjaro bluetoothd[713]: Endpoint unregistered: sender=:1.157 path=/MediaEndpoint/A2DPSource/sbc
May 19 10:38:25 manjaro bluetoothd[713]: Endpoint unregistered: sender=:1.157 path=/MediaEndpoint/A2DPSink/sbc_xq
May 19 10:38:25 manjaro bluetoothd[713]: Endpoint unregistered: sender=:1.157 path=/MediaEndpoint/A2DPSource/sbc_xq
May 19 10:38:25 manjaro rtkit-daemon[1146]: Successfully demoted thread 4948 of process 4801.
May 19 10:38:25 manjaro bluetoothd[713]: Endpoint unregistered: sender=:1.157 path=/MediaEndpoint/A2DPSource/aptx_ll_1
May 19 10:38:25 manjaro bluetoothd[713]: Endpoint unregistered: sender=:1.157 path=/MediaEndpoint/A2DPSource/aptx_ll_0
May 19 10:38:25 manjaro rtkit-daemon[1146]: Successfully demoted thread 1947 of process 1936.
May 19 10:38:25 manjaro rtkit-daemon[1146]: Successfully demoted thread 1936 of process 1936.
May 19 10:38:25 manjaro bluetoothd[713]: Endpoint unregistered: sender=:1.157 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
May 19 10:38:25 manjaro rtkit-daemon[1146]: Successfully demoted thread 2685 of process 1934.
May 19 10:38:25 manjaro rtkit-daemon[1146]: Successfully demoted thread 1934 of process 1934.
May 19 10:38:25 manjaro bluetoothd[713]: Endpoint unregistered: sender=:1.157 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
May 19 10:38:25 manjaro bluetoothd[713]: Endpoint unregistered: sender=:1.157 path=/MediaEndpoint/A2DPSource/faststream
May 19 10:38:25 manjaro rtkit-daemon[1146]: Successfully demoted thread 1937 of process 1935.
May 19 10:38:25 manjaro rtkit-daemon[1146]: Demoted 7 threads.
May 19 10:38:25 manjaro bluetoothd[713]: Endpoint unregistered: sender=:1.157 path=/MediaEndpoint/A2DPSource/faststream_duplex
May 19 10:38:25 manjaro bluetoothd[713]: Endpoint unregistered: sender=:1.157 path=/MediaEndpoint/A2DPSink/opus_05
May 19 10:38:25 manjaro bluetoothd[713]: Endpoint unregistered: sender=:1.157 path=/MediaEndpoint/A2DPSource/opus_05
May 19 10:38:25 manjaro bluetoothd[713]: Endpoint unregistered: sender=:1.157 path=/MediaEndpoint/A2DPSink/opus_05_duplex
May 19 10:38:25 manjaro bluetoothd[713]: Endpoint unregistered: sender=:1.157 path=/MediaEndpoint/A2DPSource/opus_05_duplex
May 19 10:38:25 manjaro systemd-sleep[244888]: System returned from sleep state.
May 19 10:38:25 manjaro kernel: Restarting tasks ... done.
May 19 10:38:25 manjaro kernel: PM: hibernation: hibernation exit
May 19 10:38:25 manjaro systemd[1]: Stopped target Bluetooth Support.
May 19 10:38:25 manjaro systemd[1]: Reached target Bluetooth Support.
May 19 10:38:25 manjaro kernel: Bluetooth: hci0: Device setup in 142125 usecs
May 19 10:38:25 manjaro kernel: Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported.
May 19 10:38:25 manjaro systemd[1680]: Reached target Bluetooth.
May 19 10:38:25 manjaro systemd[1]: systemd-suspend-then-hibernate.service: Deactivated successfully.
.
.
.
Just for the info I am on intel 12th gen FW and had no issue with battery drain on kernel 5.15 ubuntu 22.04 and now on 6.1 for a week.
This morning after beeing unplugged with on USB A and USB C dongle it about full battery.
I always get “403 forbidden” when trying to post my log to this thread.
Thus I’ve posted my log to debian Pastezone
Hibernation works from command line but not via systemd. I have no idea what might be wrong.
Any hint would be welcome, Andreas.
@Andreas_Tille - I am going to set up a VM to try to see if I can get things working. I may install on an expansion card if I run into issues due to it being a VM. Which desktop environment are you using? I am most familiar with gnome so I will start with that while I wait to hear back from you. Fingers crossed…
I’m using xfce.
Thanks a lot for the attempt to help, Andreas.
@Andreas_Tille - happy to help, it’s a puzzle to solve and will help me to get better with linux. I’ll pull down the xfce iso. In the one that I have now (gnome), after updating to the testing release, I get this output showing that systemd is still v252:
username@debiantesting:~$ systemctl --version
systemd 252 (252.6-1)
+PAM +AUDIT +SELINUX +APPARMOR +IMA +SMACK +SECCOMP +GCRYPT -GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP +LIBFDISK +PCRE2 -PWQUALITY +P11KIT +QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD -BPF_FRAMEWORK -XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unified
Edit to add, the following page (assuming that it is up to date) lists systemd v253 only in the experimental release:
https://manpages.debian.org/testing/systemd/os-release.5.en.html
Argh, I should have noticed this myself. I was to sloppy checking. Sorry for the noise. Hoping even more for the new release and that systemd v253 will migrate soon to testing which I would upgrade timely.
Thanks a lot for pushing me into the right direction, Andreas.
No apology necessary! I did get things working again when I moved to v253, so hopefully you will be able to as well. Please post a follow-up once you get to that version.
Greetings! I’m looking over this thread and trying to figure out the current state of using “suspend” with Linux. I just replaced my current laptop with a Framework (hasn’t arrived yet) specifically because the old one wouldn’t effectively suspend. If this is the case with the Framework as well, it won’t work for me
So basically, I’m wondering if someone could summarize this long thread, perhaps answering the simple question: If I have a new Framework laptop running Linux, should I expect “suspend” to work?
Thank you in advance!
1 Like
The state of suspend and its variants as always varies. Depends on distro, newness of hardware, and the kernel regression of the week. If you depend on suspend you are embarking on a mission of havinig to fix it, deploy a patch, deal with a workaround, or otherwise have to fiddle with it on a very regular basis. It has not been and likely mever will be what I would consider reliable.
Why is it so important to you? Just curious, because with the speed of booting today, and the security ramifications of essentially leaving your laptop in a vulnerable state at all times I simply don’t understand why anyone would use it.
1 Like
I’m using Pop OS on the new Ryzen 7 board with battery saver power profile and powertop enabled and it is actually pretty good comparing with 11 gen intel board, I closed the lid yesterday at 11 PM and open it today at 11 AM and it went from 30% to 29%, the other day went from 82% to 80% overnight. So it is consistent it loses from 1% to 2% overnight for me.
2 Likes
Maybe there’s a misunderstanding: suspend mostly works out of the box, even on (some) unsupported distros (Intel 12th gen with Debian here). The question is only how fast it drains the battery. I do use suspend all the time, and I just try to remember to leave the power plugged overnight if the battery is not fully charged in the evening, that’s it. (And I still didn’t patch, upgrade or apply any workaround; I just replaced the old HDMI card with a version 3.0, and avoid leaving the microSD card plugged in)
1 Like
Honestly, those are great numbers. Curious if you do anything special there.
I have a 12th gen on Fedora and I usually drain a little more than that overnight if I leave it in suspend. Better than the initial ~8 - 10% when I bought it with no additional set up, but not as good as 1 - 2%.
I use all USB-C expansion cards and recommended TLP settings.
Thank you everyone for your comments. @nadb - just to answer your question of why it is important, it’s a big convenience. This laptop is for non-work related projects and my usage cycle is usually to quickly open it up, do a little work, then put it down. It’s been a while but I recall, hibernate required me to type in my password twice, once to unlock the swap partition, then once to log into Gnome.
In any case, it looks like my mileage may vary. I’ll see how it does once I get my laptop (13" ryzen) and I’ll report back on this thread.
2 Likes
I applied all there recommended setting in the TLP for ubuntu doc.
It does seem to have helped. I now have about 10% loss when suspended for a day. My experience when on battery does not seem to have been impacted… still very responsive. I am running Mint 21.2.
I’m going to keep tracking and report back after a few days.
Cheers,
Rich
1 Like
Hey @Ricardo , by “with battery saver power profile and powertop enabled”, do you mean that you’re just using powertop to monitor the situation, or that you used it to tune any settings? If it’s the latter, do you mind sharing what you changed?
Also - I little off-topic - how’s Pop!_OS been for you, on the FW13 AMD? I’m running it on my System76, but am a little concerned that it might not have the best support for the AMD.
I meant using system 76 power profiles (Battery Life option). I installed powertop and enabled the service, also did the calibrate and auto-tune option before enabling the service. Didn’t do anything else. This morning I noticed it lost 3% overnight, not bad either. I think Pop OS does have support for AMD, they also sell laptops with AMD. I do not game on it (but tempted to try), for now I just use Firefox, 1password, visual code, terminal and discord and it works fine and get between 8 and 10 hours. I think it could be better, yesterday noticed Pop Shop uses a lot of ram and resources in the background so I’m thinking on maybe remove it.
1 Like
So, the recommended TLP tweaks seem to have helped my battery life while awake. Still seeing a 30% drain when on suspend for a full day - 6 AM - 6 PM.
Does it help to be running on battery before suspending?
Cheers,
Rich
Suspending to RAM, this sound about right. We are working to continue to drill this down to a better drain rate, however it’s still a work in progress.
2 Likes