On Mon, 11 Jun 2018 21:24:08 +0800 niuneilneo <[email protected]> wrote:
> This most updated UEFI installation guide is mainly contributed by Xi > and already committed to LFS knowledge base. That is a good one. I missed the importance of the earlier post to it. Thanks for the tip! But, my post was not about using grub under EFI, but rather about doing away with grub entirely. What advantage is there to retaining the use of grub when the EFI system and efibootmgr does not need it? If I were going to use a bootloader under EFI, I would use Rod Smith's rEFInd: http://www.rodsbooks.com/efi-bootloaders/refind.html As you might guess, I'm not a big fan of grub. There is a reason it has been said of grub by the gummiboot developers: "gummiboot is intended to be a minimal alternative to GNU GRUB that 'just works'" https://en.wikipedia.org/wiki/Gummiboot_(software) I went from BIOS-lilo to pure-EFI without ever using anything in between. On Mon, 11 Jun 2018 23:13:29 +0800 Xi Ruoyao <[email protected]> wrote: > If EFI is used, the BIOS boot partition is unnecessary. It is > used to workaround issues caused by GPT with Legacy Boot. OK, but if they ever need to boot in BIOS mode under a GPT disk, they will need that partition to hold grub's second stage loader. In Rob's case, I can now see he definitely does not need it because his system does not even support booting using BIOS mode. Nevertheless, it's good to know that grub won't complain if it does not find that partition as long as it does not actually need the second stage loader. > Using /dev/sd* works, but your computer may refused to boot > with a USB stick. Yes, and there was something else that trips up /dev/sd* specifiers before udev can become active - IIRC, I think if a multicore machine has more than one SATA controller/card/chip, the order of the device detection/naming can vary between boots. So, for anything prior to udev's control, we have to use persistant device naming for it to be reliable. FWIW, I dislike this design choice of the linux kernel. > Now we use CONFIG_EFIVAR_FS (y or m), instead of CONFIG_EFI_VARS, Do you know if efibootmgr will autodetect (at run time) between the two kernel interfaces (and if this is a recent feature, what version starting supporting that)? AFAIK, they both can be enabled at the same time. As you mentioned, EFIVAR_FS is a more modern interface, but it does require that a special efivarfs filesystem be (re)mounted r/w: mount -o rw -t efivarfs efivarfs /sys/firmware/efi/efivars So, Rob will have to add that to his start scripts - maybe mount it read-only and then manually remount r/w as needed: mount -o remount,rw -t efivarfs efivarfs /sys/firmware/efi/efivars Thanks for the tips and info! Cheers, Mike -- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page Do not top post on this list. A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? http://en.wikipedia.org/wiki/Posting_style
