Difficulties booting from luks encrypted root, raspi5, dietpi test image with 2 kernels

[abusr]

Hello,

I've been trying to boot a dietpi test image (with 2 kernels and 2 initramfss) in my raspi5.
No matter what I've tried, I cannot reach the prompt to unlock the cryptrootfs (luks, one partition formatted with ext4). So, kernel panics. Indicatively, in I've tried things in cmdline.txt like:

set root=/dev/mapper/cryptroot, root=UUID=uuid_of_encrypted_partition, root=PARTUUID=part_uuid_of_encrypted_partition, root=UUID=uuid_of_decrypted_partition

set cryptdevice=UUID=uuid_of_encrypted_partition, cryptdevice=PARTUUID=part_uuid_of_encrypted_partition

disabled logo of course

have even tried device names directly. No matter, same.

I have observed cryptsetup is already present in the initramfs. Inside the luks encrypted root my crypttab and fstab are checked to be ok, as I have adapted them from one of the ubuntus I am setting up from time to time. I have tried update-initramfs -u and updateiniramfs -c -k all from chroot, with the (system's I am preparing) boot partition mounted on chroot's /boot/firmware.

No matter what, the kernel panics because it cannot find root device. Am I missing something or is any kind of support missing from the dietpi kernels and is causing so much refusal??

[Joulinar]

or is any kind of support missing from the dietpi kernels

We don't have own kernel on RPi devices, it's the original one provided by RPi foundation.

[MichaIng]

If cryptsetup support was added to the initramfs properly, please also assure the RPi is using it. See /etc/default/raspi-firmware. At least SKIP_INITRAMFS_GEN=no would need to be set, so any /boot/initrd-* is moved to the right place on the boot partition to be loaded by the RPi bootloader.