On 2018-06-11 03:01 -0400, Michael Shell wrote: > On Sun, 10 Jun 2018 07:27:53 -0500 > "Rob" <captinlo...@gmail.com> wrote: > > > I just want to make sure this partition layout is correct before > > doing grub. > > . > . > > Device Start End Sectors Size Type > > /dev/sdb1 2048 1050623 1048576 512M EFI System > > /dev/sdb2 1050624 32507903 31457280 15G Linux filesystem > > /dev/sdb3 32507904 66062335 33554432 16G Linux swap > > > Rob, > > With grub, you should have a grub, aka BIOS boot, partition of about > 128.0 MiB, code EF02, after the first, EFI (code EF00) partition. It > is always a good idea to have the BIOS boot partition in case you > ever need grub. IIRC, the grub partition does not need to be > formatted.
Nope. If EFI is used, the BIOS boot partition is unnecessary. It is used to workaround issues caused by GPT with Legacy Boot. > The EFI partition, the very first one, is FAT32 and is usually mounted > on /boot/efi when servicing. > > Your kernel will have to be compiled with an EFI stub. Under the kernel > menuconfig setup, in "Processor type and features" enable: > > [*] EFI runtime service support > [*] EFI stub support > > You should not enable mixed mode support: > > [ ] EFI mixed-mode support > > > For the Built-in kernel command line (also under "Processor type and > features", you should specify the PARTUUID of your linux filesystem > that is to become /root when booted, > e.g., > root=PARTUUID=1234567a-af67-4c97-8154-438376dc7113 ro log_buf_len=262144 > video=DVI-I-1:1024x768-16@60 > fbcon=font:VGA8x16 Using /dev/sd* works, but your computer may refused to boot with a USB stick. (My laptop make USB stick /dev/sda if it's detected on boot.) > You can get the PARTUUID of the target partition via blkid, e.g., > > blkid /dev/sdb1 > > The kernel builtin settings can be overridden at load time by another > specification of these kernel parameters, say, from the boot loader > or loader command prompt. This is helpful in emergencies when the > kernel has to be told to use a different partition for /root. > > To allow such an override, do not select the kernel config option > [ ] Built-in command line overrides boot loader arguments > under "Processor type and features" > > > In the kernel config under "Firmware Drivers", enable: > EFI (Extensible Firmware Interface) Support > <*> EFI Variable Support via sysfs > <*> Register efivars backend for pstore Nope. Now we use CONFIG_EFIVAR_FS (y or m), instead of CONFIG_EFI_VARS, as the kernel config interface says: │ efivarfs is a replacement filesystem for the old EFI │ │ variable support via sysfs, as it doesn't suffer from the │ │ same 1024-byte variable size limit. │ -- Xi Ruoyao <r...@stu.xidian.edu.cn> School of Aerospace Science and Technology, Xidian University -- 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
