Greg KH schrieb: > On Mon, Dec 10, 2012 at 12:21:29AM +0100, Chí-Thanh Christopher Nguyễn wrote: >> Greg KH schrieb: >>>> No, all we need is to enable EFI stub support in the kernel, and >>>> integrate the initramfs using CONFIG_INITRAMFS_SOURCE and place it in >>>> some location where UEFI looks for it (/efi/boot/bootx64.efi). >>>> >>>> This has the disadvantage of not allowing to pass additional kernel >>>> parameters during boot. But it might still be an acceptable stopgap >>>> measure if the alternative is to not boot at all. >>> No, don't do that for an "install" kernel, that way is madness, just use >>> a real UEFI bootloader which can handle an initrd and the like properly >> Can you explain what problems you see with that? How does >> CONFIG_INITRAMFS_SOURCE handle initrd improperly? > Ah, didn't notice that, it might work, have you tried it?
Yes, it works here. This is the kernel which I used to boot my development box at work (including genkernel initramfs for mdraid+luks+lvm): http://dev.gentoo.org/~chithanh/efi/boot/bootx64.efi It has hardcoded crypt_root and real_root via CONFIG_CMDLINE, and initramfs executables are built with -march=bdver2 so this particular file will probably not be useful to many people. Best regards, Chí-Thanh Christopher Nguyễn