On 2020-08-02 17:08 +0200, Alexey Orishko via lfs-dev wrote: > On Sat, Aug 1, 2020 at 11:49 PM Bruce Dubbs via lfs-dev > <lfs-dev@lists.linuxfromscratch.org> wrote: > > The only reason to use uefi is if you want to dual boot to Windows. It > > complicates LFS and will interfere with learning how simple a boot can be. > > > > -- Bruce > > I was about to post a question, when I saw this discussion. There > might be other reasons > beyond dual-boot - incompatibility with legacy boot devices. > I've recently got Lenovo Thinkbook 13s-IML laptop and I'm unable to > boot LFS 9.1 on it at all. > I planned to replace W10 with BLFS build, but decided to try USB stick > first. It boots fine > on ThinkPad T450s, but Thinkbook 13s. This laptop has NVMe as a boot > disk with W10, > secure boot=off, boot mode legacy first. > Each time I end up in Boot manager GUI with USB stick as an option, > but after a few > seconds it returns to the same screen. Grub stage 1 never shown. > There only one thing I didn't try is EFI boot option in LFS due to > fragmented info > and time required to make it right.
> Since majority of new laptops have EFI, it would really help to have > EFI section as a > default option in the book. It's nearly impossible. If we do that we'll have to introduce at least five new packages: dosfstools, popt, pciutils, efivar, and efibootmgr. Pciutils is recommended to be installed along with "which" (it's a package's name), and one of wget/curl/lynx to make update-pciids script usable. And, to make grub menu "showing normal" we'll need freetype. Freetype has a circular dependency with harfbuzz. Harfbuzz requires glib, graphite, and ICU to be fully functional. We have two options: (1) Add all these packages into LFS. (2) Install an "incomplete" version of pciutils/freetype in LFS, and rebuild/tweak them in BLFS. Both of them are stupid IMO. And, if we add some packages to LFS, every LFS user will have to build them. The readers who don't need EFI will be annoyed. meson/ninja already annoyed the readers using sysvinit. If we try not to annoy people, and put some "optional" packages in LFS, the same package must be in LFS and BLFS at same time. Then the maintainance burden and confusion would be unacceptable. > Another suggestion I have regarding initrd: since grub config is > created in LFS book, > it would be nice to move initramfs from BLFS ch.5 to ch8 LFS. It would > make changing > of boot procedure complete in LFS instead of BLFS. > Due to dependency cpio has to be built in LFS as well (and possible > lz4 for future compatibility). In this case I'm annoyed :). I don't use initramfs and why should I install cpio? > I could try EFI variant on Thinkbook 13s laptop if you decide to > include EFI in the new book > (or dev. version of the book) I'll update the hint after I build LFS with Glibc-2.32. We can't just squeeze everything into LFS because it's needed in some situation. I can assure that wpa-supplicant and make-ca are more widely used than efi-grub. But we don't move them into LFS. -- Xi Ruoyao <xry...@mengyan1223.wang> School of Aerospace Science and Technology, Xidian University -- http://lists.linuxfromscratch.org/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
