[SOLVED] EFI stub boot

ymf331 · 06-11-2014, 08:36 PM

Hi. I want to do away with bootloaders and initial ramdisks and all that but I can't seem to find the information I need. Will I need to build anything into the kernel? Like filesystem mods or anything? I read that the support for efi stub is already built into the kernel. I'm going to look up what I do after that but anything helpful will help. Thanks.

colorpurple21859 · 06-11-2014, 09:07 PM

You will need to rebuild your kernel with drivers and file sytems required for booting without a initial ramdisk, along with the options needed to boot as efi stub. Here is some info on setting the kernel up as an EFI stub. http://www.rodsbooks.com/efi-bootloaders/efistub.html. The drivers and filesystems that have to build into the kernel will depend on your hardware and file systems. You may need a larger EFI partition to hold the efi stub kernel.

ymf331 · 06-11-2014, 09:37 PM

That and the archlinux wiki were the two places that had at least some information. I have been trying but there really isn't a detailed guide anywhere. I got my kernel to boot by using efibootmgr and feeding it an initrd with jbd2 and ext4 mods. For some reason the root lv in the partition that I just formatted is being mistaken for a luks device? And /dev/system/slackroot won't mount, but I'm making progress.

Edit: oyea the efi stub options are enabled in the generic configuration.

colorpurple21859 · 06-11-2014, 09:50 PM

Quote:

I got my kernel to boot by using efibootmgr

Well at least this part is working. This

Quote:

For some reason the root lv in the partition that I just formatted is being mistaken for a luks device? And /dev/system/slackroot won't mount

and still having to use an initrd is most likley from not having everything you need built into your kernel.

ymf331 · 06-11-2014, 09:51 PM

Unedited: No wait. I don't understand why my lvm partition with my root on it is being recognized as a luks device. I can mount it myself no problem. It was encrypted 2 repartition/full reinstalls ago. Is there something that I need to do there?

Edit: Yep. I'm saving compiling my first kernel for after I get my system to boot, but I think the initrd will work for now.

ymf331 · 06-11-2014, 10:42 PM

Okay, I had accidentally put the -C option into mkinitrd out of habit. Finally got everything to boot so I guess tomorrow I'll try to figure out how to compile a kernel.