I have been trying to configure suspend-then-hibernate but I am afraid I don’t find any way to do it. The following is an excerpt from man systemctl:
suspend-then-hibernate
Suspend the system and hibernate it after the delay specified in systemd-sleep.conf. This will trigger activation of
the special target unit suspend-then-hibernate.target. This command is asynchronous, and will return after the hybrid
sleep operation is successfully enqueued. It will not wait for the sleep/wake-up or hibernate/thaw cycle to complete.
Having searched for systemd-sleep.conf the only hit seems to be:
NAME
systemd-suspend.service, systemd-hibernate.service, systemd-hybrid-sleep.service, systemd-suspend-then-hibernate.service,
systemd-sleep - System sleep state logic
DESCRIPTION
systemd-suspend.service is a system service that is pulled in by suspend.target and is responsible for the actual system
suspend. Similarly, systemd-hibernate.service is pulled in by hibernate.target to execute the actual hibernation. Finally,
systemd-hybrid-sleep.service is pulled in by hybrid-sleep.target to execute hybrid hibernation with system suspend and
pulled in by suspend-then-hibernate.target to execute system suspend with a timeout that will activate hibernate later.
Immediately before entering system suspend and/or hibernation systemd-suspend.service (and the other mentioned units,
respectively) will run all executables in /usr/lib/systemd/system-sleep/ and pass two arguments to them. The first argument
will be "pre", the second either "suspend", "hibernate", "hybrid-sleep", or "suspend-then-hibernate" depending on the
chosen action. Immediately after leaving system suspend and/or hibernation the same executables are run, but the first
argument is now "post". All executables in this directory are executed in parallel, and execution of the action is not
continued until all executables have finished.
Note that scripts or binaries dropped in /usr/lib/systemd/system-sleep/ are intended for local use only and should be
considered hacks. If applications want to react to system suspend/hibernation and resume, they should rather use the
Inhibitor interface[1].
Note that systemd-suspend.service, systemd-hibernate.service, systemd-hybrid-sleep.service, and
systemd-suspend-then-hibernate.service should never be executed directly. Instead, trigger system sleep with a command such
as systemctl suspend or systemctl hibernate.
Internally, this service will echo a string like "mem" into /sys/power/state, to trigger the actual system suspend. What
exactly is written where can be configured in the [Sleep] section of /etc/systemd/sleep.conf or a sleep.conf.d file. See
systemd-sleep.conf(5).
OPTIONS
systemd-sleep understands the following commands:
-h, --help
Print a short help text and exit.
--version
Print a short version string and exit.
suspend, hibernate, hybrid-sleep, suspend-then-hibernate
Suspend, hibernate, suspend then hibernate, or put the system to hybrid sleep.
SEE ALSO
systemd-sleep.conf(5), systemd(1), systemctl(1), systemd.special(7), systemd-halt.service(8)
Excerpt from man systemd-sleep:
Note that systemd-suspend.service, systemd-hibernate.service, systemd-hybrid-sleep.service, and
systemd-suspend-then-hibernate.service should never be executed directly. Instead, trigger system sleep with a command such
as systemctl suspend or systemctl hibernate.
Running systemctl suspend-then-hibernate will immediately turn off the screen but the power button of the laptop is still on. So I am not sure how to take this any further. Otherwise the system hibernate and wakes up successfully to and from a swapfile.
I didn’t find anything relative this alternative mode of suspension-hibernation in ArchWiki. Maybe I overlooked something.
I’ll appreciate greatly any pointers to a solution.
I found the file sleep.conf in/etc/systemd with this content.
This file is part of systemd.
systemd is free software; you can redistribute it and/or modify it
under the terms of the GNU Lesser General Public License as published by
the Free Software Foundation; either version 2.1 of the License, or
(at your option) any later version.
Entries in this file show the compile time defaults.
You can change settings by editing this file.
Defaults can be restored by simply deleting this file.
B4. Make your changes permanent (update the “/etc/fstab” file)
Make sure Linux Operating System knows to use your swap file every single time it boots up. Do this by running the following command which posts an entry in the /etc/fstab file:
(2) Configure system to use SWAP for Suspend then Hibernate
Using a swap file requires also setting the resume=swap_device and additionally a resume_offset=swap_file_offset kernel parameters. See the kernel documentation.
swap_device is the the volume where the swap file resides and it follows the same format as for the root parameter. The value of swap_file_offset can be obtained by running filefrag -v swap_file, the output is in a table format and the required value is located in the first row of the physical_offset column.
(a) Get swap_device (findmnt -no UUID -T /swapfile).
(d) Final Grub Configuration line.
GRUB_CMDLINE_LINUX_DEFAULT=“resume=UUID=c9244e6e-3127-4c6e-99f1-f61c0efa81eb resume_offset=6600704… i915.enable_psr=1 apparmor=1 lsm=lockdown,yama,apparmor”
(b2) From there, you can start hibernating by adding the MAJ:MIN values for the swap partition to /sys/power/resume with the following command[2]:
sudo echo 259:2 > /sys/power/resume
(c3) Configure the initramfs
When an initramfs with the base hook is used, which is the default, the resume hook is required in /etc/mkinitcpio.conf. Whether by label or by UUID, the swap partition is referred to with a udev device node, so the resume hook must go after the udev hook. This example was made starting from the default hook configuration:
(c6) Reboot the Operating System to apply the changes.
(D) Configure Suspend-Then-Hibernate
Once it’s possible to enter & wake from the hibernation state, we can then transition to the suspend-then-hibernate step. For this, we have to configure systemd to handle entering hibernation from the suspend state after a given period.
(D1) Set a delay in the sleep.conf, which will inform systemd how long to stay in the suspend state before hibernating.
(a) Add the following to the “/etc/systemd/sleep.conf” file.
[Sleep]
AllowSuspendThenHibernate=yes
HibernateState=disk #Suspend then Hibernate after 15 min
HibernateDelaySec=15min
(D2) Inform systemd the behavior of the power switch, lid closing, and suspend state.
(a) Add the following to “/etc/systemd/logind.conf”
100% correct on your part sir. I had tailored the notes for myself and reduced the swap size. I corrected it (thank you for the catch and keeping me honest).
Additionally I notice for allocating the swap file the Arch wiki uses the ‘dd’ command. This example allocated 16 GB
Use dd to create a swap file the size of your choosing. For example, creating a 16 GB swap file:
You need to edit sleep.conf and logind.conf. Here is what works for me:
sleep.conf
# This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it under the
# terms of the GNU Lesser General Public License as published by the Free
# Software Foundation; either version 2.1 of the License, or (at your option)
# any later version.
#
# Entries in this file show the compile time defaults. Local configuration
# should be created by either modifying this file, or by creating "drop-ins" in
# the sleep.conf.d/ subdirectory. The latter is generally recommended.
# Defaults can be restored by simply deleting this file and all drop-ins.
#
# See systemd-sleep.conf(5) for details.
[Sleep]
#AllowSuspend=yes
#AllowHibernation=yes
AllowSuspendThenHibernate=yes
#AllowHybridSleep=yes
#SuspendMode=
#SuspendState=mem standby freeze
#HibernateMode=platform shutdown
#HibernateState=disk
#HybridSleepMode=suspend platform shutdown
#HybridSleepState=disk
HibernateDelaySec=30min
logind.conf
# This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it under the
# terms of the GNU Lesser General Public License as published by the Free
# Software Foundation; either version 2.1 of the License, or (at your option)
# any later version.
#
# Entries in this file show the compile time defaults. Local configuration
# should be created by either modifying this file, or by creating "drop-ins" in
# the logind.conf.d/ subdirectory. The latter is generally recommended.
# Defaults can be restored by simply deleting this file and all drop-ins.
#
# Use 'systemd-analyze cat-config systemd/logind.conf' to display the full config.
#
# See logind.conf(5) for details.
[Login]
#NAutoVTs=6
#ReserveVT=6
#KillUserProcesses=no
#KillOnlyUsers=
#KillExcludeUsers=root
#InhibitDelayMaxSec=5
#UserStopDelaySec=10
#HandlePowerKey=poweroff
HandleSuspendKey=ignore
HandleHibernateKey=ignore
HandleLidSwitch=suspend-then-hibernate
#HandleLidSwitchExternalPower=suspend
#HandleLidSwitchDocked=ignore
#HandleRebootKey=reboot
#PowerKeyIgnoreInhibited=no
#SuspendKeyIgnoreInhibited=no
#HibernateKeyIgnoreInhibited=no
#LidSwitchIgnoreInhibited=yes
#RebootKeyIgnoreInhibited=no
#HoldoffTimeoutSec=30s
#IdleAction=ignore
#IdleActionSec=30min
#RuntimeDirectorySize=10%
#RuntimeDirectoryInodes=400k
#RemoveIPC=yes
#InhibitorsMax=8192
#SessionsMax=8192
One key item to testing this is how you suspend your laptop. I notice my system would hibernate if I closed the lid of the laptop. But not hibernate if I manually suspended the laptop. After allot of playing around I just accept closing the lid and it suspending then hibernating was good enough for me.