You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been following this guide to get root partition encryption working on a RBPI CM4 using RBPI OS Lite 64 2023-12-11 (i.e. Debian 12 Bookworm).
Everything works until I get to the point where I want to unlock the LUKS volume from initramfs, where it fails with a missing cipher.
When I run cryptsetup benchmark -c xchacha20,aes-adiantum-plain64 (again, from initramfs) I get the same error. Obviously the ciphers are available from RBPI OS itself, and I made sure I created an updated initramfs and checked if the resulting file contains the modules with lsinitramfs . I also checked the modules folder after booting into initramfs just to be sure, and the modules algif_skcipher, adiantum etc. are present (so they have been copied).
Do you happen to have any idea what the problem could be, or have you tested your guide with Debian 12?
The text was updated successfully, but these errors were encountered:
Thanks for a great guide!
I've been following this guide to get root partition encryption working on a RBPI CM4 using RBPI OS Lite 64 2023-12-11 (i.e. Debian 12 Bookworm).
Everything works until I get to the point where I want to unlock the LUKS volume from initramfs, where it fails with a missing cipher.
When I run
cryptsetup benchmark -c xchacha20,aes-adiantum-plain64
(again, from initramfs) I get the same error. Obviously the ciphers are available from RBPI OS itself, and I made sure I created an updated initramfs and checked if the resulting file contains the modules withlsinitramfs
. I also checked the modules folder after booting into initramfs just to be sure, and the modulesalgif_skcipher
,adiantum
etc. are present (so they have been copied).Do you happen to have any idea what the problem could be, or have you tested your guide with Debian 12?
The text was updated successfully, but these errors were encountered: