I’ve been trying to set up hibernation on my laptop while also maintaining an encrypted root partition and swap using secure boot and my laptop’s TPM. I’ve documented the steps I’ve followed below, but I still am unable to enable hibernation.
I was under the impression that the only reason you can’t normally have both an encrypted harddrive and hibernation was because swap had to be encrypted as well, but if both the root partition and the swap are encrypted, I’m using UEFI secure boot, and they are automatically decrypted at boot using the TPM, shouldn’t that relieve those security concerns?
After completing the below, entering systemctl hibernate errors saying hibernation is not set up for the system. Am I missing something or is it just not possible? I can confirm not needing to enter passwords for my swap or root FS due to the TPM unlock.
My personal documentation below:
Drop into root shell
sudo su -
Setup LUKS encryption with automatic unlock with TPM
Install necessary components, regenerate initramfs and reboot
dnf install -y clevis clevis-luks clevis-dracut clevis-udisks2 clevis-systemd
dracut -fv --regenerate-all && systemctl reboot
Identify swap and root partition devices, names, and luks UUIDs…
lsblk -f
cryptsetup luksUUID <UUID>
In my case, my home partition is on /dev/nvme0n1p4 and my swap is /dev/nvme0n1p3
# the encrypted home partition
clevis luks bind -d /dev/nvme0n1p4 tpm2 '{"pcr_ids":"1,4,5,7"}'
# the encrypted swap
clevis luks bind -d /dev/nvme0n1p3 tpm2 '{"pcr_ids":"1,4,5,7"}'
Set a timeout before the system asks for a password, to allow time for the TPM to load and enter the password for you
systemctl edit systemd-ask-password-plymouth.service
Add the below then ctrl+o ctrl+x to save and exit
[Service]
ExecStartPre=/bin/sleep 10
Create a dracut configuration file to install the systemd-ask-password-plymouth service: vi /etc/dracut.conf.d/systemd-ask-password-plymouth.conf
Add the below, ensure there are spaces inside the quotation marks on either side of the filename
install_items+=" /etc/systemd/system/systemd-ask-password-plymouth.service.d/override.conf "
Regenerate initramfs and reboot
dracut -fv ‐‐regenerate-all && systemctl reboot
Edit crypttab file (/etc/crypttab)to specify decryption of swap file at boot, duplicate the already present line for your root FS crypttab entry and change the UUIDs to reflect the swap file, use cryptsetup luksUUID /dev/nvme0n1p3 and cryptsetup luksUUID /dev/nvme0n1p4 to get the luks UUIDs for your root and swap partitions.
<swap LUKS UUID> UUID=<swap UUID> none x-initrd.attach
<root FS LUKS UUID> UUID=<root FS UUID> none x-initrd.attach
Regenerate initramfs and reboot: dracut -fv --regenerate-all && systemct reboot
Edit fstab to include swap, append the following to /etc/fstab:
UUID=<swap UUID> none swap defaults,x-systemd.device-timeout=0 1 1
Rebind your home and swap partitions. You will have to do this every time you update the kernel.
# encrypted home partition
clevis luks regen -d /dev/nvme0n1... -s 1
# encrypted swap
clevis luks regen -d /dev/nvme0n1... -s 1


I actually just did this recently with a BTRFS subvolume using a swap file and LUKS encryption.
The old Fedora magazine article has the overall steps required and someone also made a guide for secure boot on I think the
spiceworksframework forum.The catch is that secure boot will only allow signed images to be loaded which includes the hibernation swap image, meaning you have to use a customized kernel that allows unsigned hibernation images to load.
I’ll share both links when I get a chance.
EDIT:
Fedora Magazine guide: https://fedoramagazine.org/hibernation-in-fedora-36-workstation/
This is slightly outdated as Fedora now uses a proper zram.swap definition with systemd, so you can also do a systemctl edit to disable and enable zram0 with post/pre start on the hibernate service directly instead of using swapon/swapoff. I’ll make a second edit with my example I’ll have to dig out of some poorly documented notes lol.
https://community.frame.work/t/guide-fedora-36-hibernation-with-enabled-secure-boot-and-full-disk-encryption-fde-decrypting-over-tpm2/25474
This is the full forum post guide for FDE + TPM + secure boot. I’m not entirely sure of the kernel patch specific but it seems that the hibernate swap image is technicallly signed because if the bootloader process, but the kernel lockdown mode rejects it regardless by default because there’s no guarantee that the swap image was configured with FDE and not tampered with, which would be a vulnerability.
Quick glance at the kernel patch makes it seem like it’s just a flag check to allow hibernate in lockdown mode, so I assume the secure boot signature check is still completed.
Oh awesome I had seen the Fedora Magazine article but not the framework guide. I’ll give that a shot, thank you!