You are not logged in.
If I have all required drivers and kernel code built into the static kernel image I still need an initrd for cryptdevice=device don't I?
When I build custom kernels I disable module support with all other stuff I don't use or need and failed to boot archlinux luks root partition without modules support.
How can I do that?
Offline
As far as i know the encrypt hook in the initrd unlocks the LUKS container, that means you need to have an initrd to boot.
Offline
Tried booting a custom kernel without module support and besides mkinitcpio finishing with errors and the kernel image not booting properly by not loading enough drivers to boot no other kernel whatsoever (reinstall or not) booted on that arch install afterwards. Found no cause and had to format the install. Now I cannot install because this is on a 32-bit efi mac mini and the steps to modify the iso to boot don't produce a working iso.
Last edited by cm (2014-01-30 22:08:30)
Offline