mirror of
https://github.com/Zeckmathederg/glfs.git
synced 2025-02-07 09:37:17 +08:00
aebcd92ce0
Add "| cut -f 1" to efibootmgr command for checking the configuration, so long boring paths will not show up. Update unifont version, and kernel version (in example) by the way.
439 lines
16 KiB
XML
439 lines
16 KiB
XML
<?xml version="1.0" encoding="ISO-8859-1"?>
|
|
<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
|
|
"http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
|
|
<!ENTITY % general-entities SYSTEM "../../../general.ent">
|
|
%general-entities;
|
|
]>
|
|
|
|
<sect1 id="grub-setup" xreflabel="Using GRUB to Set Up the Boot Process with UEFI">
|
|
<?dbhtml filename="grub-setup.html"?>
|
|
|
|
<sect1info>
|
|
<date>$Date$</date>
|
|
</sect1info>
|
|
|
|
<title>Using GRUB to Set Up the Boot Process with UEFI</title>
|
|
|
|
<sect2>
|
|
<title>Turn Off Secure Boot</title>
|
|
|
|
<para>
|
|
BLFS does not have the essential packages to support Secure Boot. To
|
|
set up the boot process with GRUB for UEFI installed in BLFS, Secure
|
|
Boot must be turned off from the configuration interface of the
|
|
firmware. Read the documentation provided by the manufacturer of your
|
|
system to find out how.
|
|
</para>
|
|
</sect2>
|
|
|
|
<sect2>
|
|
<title>Create an Emergency Boot Disk</title>
|
|
|
|
<para>
|
|
Ensure that an emergency boot disk is ready to <quote>rescue</quote>
|
|
the system in case the system becomes un-bootable. To make an
|
|
emergency boot disk with GRUB for an EFI based system, find a spare
|
|
USB flash drive and create a
|
|
<systemitem class="filesystem">vfat</systemitem> file system on it.
|
|
Install <xref linkend="dosfstools"/> first, then
|
|
as the <systemitem class="username">root</systemitem> user:
|
|
</para>
|
|
|
|
<warning>
|
|
<para>
|
|
The following command will erase all directories and files in the
|
|
partition. Make sure your USB flash drive contains no data which
|
|
will be needed, and change <userinput>sdx1</userinput> to the
|
|
device node corresponding to the first partition of the USB flash
|
|
drive. Be careful not to overwrite your hard drive with a typo!
|
|
</para>
|
|
</warning>
|
|
|
|
<screen role="nodump"><userinput>mkfs.vfat /dev/sdx1</userinput></screen>
|
|
|
|
<para>
|
|
Still as the <systemitem class="username">root</systemitem> user, use
|
|
the <command>fdisk</command> utility to set the first partition
|
|
of the USB flash drive to be an <quote>EFI system</quote> partition
|
|
(change <userinput>sdx</userinput> to the device node corresponding
|
|
to your USB flash drive):
|
|
</para>
|
|
|
|
<screen role="nodump"><userinput>fdisk /dev/sdx</userinput>
|
|
<literal>
|
|
Welcome to fdisk (util-linux 2.37.4).
|
|
Changes will remain in memory only, until you decide to write them.
|
|
Be careful before using the write command.
|
|
|
|
|
|
Command (m for help): </literal><userinput>t</userinput>
|
|
<literal>Partition number (1-9, default 9): </literal><userinput>1</userinput>
|
|
<literal>Partition type or alias (type L to list all): </literal><userinput>uefi</userinput>
|
|
<literal>Changed type of partition 'Linux filesystem' to 'EFI System'.
|
|
|
|
Command (m for help): </literal><userinput>w</userinput>
|
|
<literal>The partition table has been altered.
|
|
Calling ioctl() to re-read partition table.
|
|
Syncing disks.</literal></screen>
|
|
|
|
<para>
|
|
Still as the <systemitem class="username">root</systemitem> user,
|
|
create a mount point for the EFI partition on the USB flash drive
|
|
and mount it:
|
|
</para>
|
|
|
|
<screen role="nodump"><userinput>mkdir -pv /mnt/rescue &&
|
|
mount -v -t vfat /dev/sdx1 /mnt/rescue</userinput></screen>
|
|
|
|
<para>
|
|
Install GRUB for EFI on the partition:
|
|
</para>
|
|
|
|
<screen role="nodump"><userinput>grub-install --removable --efi-directory=/mnt/rescue --boot-directory=/mnt/rescue/grub</userinput></screen>
|
|
|
|
<para>
|
|
Unmount the partition:
|
|
</para>
|
|
|
|
<screen role="nodump"><userinput>umount /mnt/rescue</userinput></screen>
|
|
|
|
<para>
|
|
Now the USB flash drive can be used as a emergency boot disk on x86-64
|
|
UEFI platform. It will boot the system and show the GRUB shell. Then you
|
|
can type commands to boot your operating systems on the hard drive.
|
|
To learn how to select the boot device, read the manual of your
|
|
motherboard or laptop.
|
|
</para>
|
|
|
|
</sect2>
|
|
|
|
<sect2 role="kernel" id="uefi-kernel">
|
|
<title>Kernel Configuration for UEFI support</title>
|
|
|
|
<para>
|
|
Enable the following options in the kernel configuration and recompile
|
|
the kernel if necessary:
|
|
</para>
|
|
|
|
<screen><literal>Processor type and features --->
|
|
[*] EFI runtime service support [CONFIG_EFI]
|
|
[*] EFI stub support [CONFIG_EFI_STUB]
|
|
Enable the block layer --->
|
|
Partition Types --->
|
|
[*] Advanced partition selection [CONFIG_PARTITION_ADVANCED]
|
|
[*] EFI GUID Partition support [CONFIG_EFI_PARTITION]
|
|
Device Drivers --->
|
|
Firmware Drivers --->
|
|
[*] Mark VGA/VBE/EFI FB as generic system framebuffer [CONFIG_SYSFB_SIMPLEFB]
|
|
EFI (Extensible Firmware Interface) Support --->
|
|
< > EFI Variable Support via sysfs [CONFIG_EFI_VARS]
|
|
[*] Export efi runtime maps to sysfs [CONFIG_EFI_RUNTIME_MAP]
|
|
Graphics support --->
|
|
<*> Direct Rendering Manager [CONFIG_DRM]
|
|
<*> Simple framebuffer driver [CONFIG_SIMPLEDRM]
|
|
Frame buffer Devices --->
|
|
<*> Support for frame buffer devices ---> [CONFIG_FB]
|
|
Console display driver support --->
|
|
[*] Framebuffer Console support [CONFIG_FRAMEBUFFER_CONSOLE]
|
|
File systems --->
|
|
Pseudo filesystems --->
|
|
<*/M> EFI Variable filesystem [CONFIG_EFIVAR_FS]</literal></screen>
|
|
|
|
<variablelist>
|
|
<title>The meaning of the configure options:</title>
|
|
|
|
<varlistentry>
|
|
<term><parameter>CONFIG_EFI_STUB</parameter></term>
|
|
<listitem>
|
|
<para>Although the EFI stub is designed to boot a kernel directly from
|
|
the UEFI firmware (without a bootloader like GRUB), GRUB needs the
|
|
kernel to be loaded to support the EFI handover protocol enabled by
|
|
this option.</para>
|
|
</listitem>
|
|
</varlistentry>
|
|
|
|
<varlistentry>
|
|
<term><parameter>CONFIG_EFI_VARS</parameter></term>
|
|
<listitem>
|
|
<para>Don't use this deprecated option because of a 1024-byte
|
|
variable size limit. Its function is replaced by
|
|
<parameter>CONFIG_EFIVAR_FS</parameter>.</para>
|
|
</listitem>
|
|
</varlistentry>
|
|
|
|
<varlistentry>
|
|
<term>
|
|
<parameter>CONFIG_SYSFB_SIMPLEFB</parameter>,
|
|
<parameter>CONFIG_DRM</parameter>,
|
|
<parameter>CONFIG_SIMPLEDRM</parameter>,
|
|
<parameter>CONFIG_FB</parameter>, and
|
|
<parameter>CONFIG_FRAMEBUFFER_CONSOLE</parameter></term>
|
|
<listitem>
|
|
<para>The combination of these options allows the kernel to
|
|
print debug messages (along with Tux logos) at the early stage of
|
|
the boot process with UEFI. To ensure them functional at the early
|
|
stage, they shouldn't be built as a kernel module unless an
|
|
initramfs will be used.</para>
|
|
</listitem>
|
|
</varlistentry>
|
|
|
|
</variablelist>
|
|
|
|
</sect2>
|
|
|
|
<sect2>
|
|
<title>Find or Create the EFI System Partition</title>
|
|
|
|
<para>
|
|
On EFI based system, the bootloaders are installed in a special FAT32
|
|
partition called an <emphasis>EFI System Partition</emphasis> (ESP).
|
|
If your system supports EFI, and a recent version of Linux
|
|
distribution or Windows is pre-installed, it's likely that the ESP
|
|
is already created. As the
|
|
<systemitem class="username">root</systemitem> user, list all the
|
|
partitions on your hard drive (replace <userinput>sda</userinput>
|
|
with the device corresponding to the appropriate hard drive):
|
|
</para>
|
|
|
|
<screen role="nodump"><userinput>fdisk -l /dev/sda</userinput></screen>
|
|
|
|
<para>
|
|
The <quote>Type</quote> column of the ESP should be
|
|
<literal>EFI System</literal>.
|
|
</para>
|
|
|
|
<para>
|
|
If the system or the hard drive is new, or it's a first time
|
|
install an UEFI booted OS on the system, the ESP may not exist.
|
|
In that case, create a new partition, make a
|
|
<systemitem class="filesystem">vfat</systemitem> file system on it,
|
|
and set the partition type to <quote>EFI system</quote>. See the
|
|
instructions for the emergency boot device above as a reference.
|
|
</para>
|
|
|
|
<warning>
|
|
<para>
|
|
Some (old) UEFI implementations may demand the ESP to be the first
|
|
partition on the disk.
|
|
</para>
|
|
</warning>
|
|
|
|
<para>
|
|
Now, as the <systemitem class="username">root</systemitem> user,
|
|
create the mount point for the ESP, and mount it (replace
|
|
<userinput>sda1</userinput> with the device node corresponding to
|
|
the ESP):
|
|
</para>
|
|
|
|
<screen role="nodump"><userinput>mkdir -pv /boot/efi &&
|
|
mount -v -t vfat /dev/sda1 /boot/efi</userinput></screen>
|
|
|
|
<para>
|
|
Add an entry for the ESP in
|
|
<filename>/etc/fstab</filename>, so it will be mounted automatically
|
|
during system boot:
|
|
</para>
|
|
|
|
<screen role="nodump"><userinput>cat >> /etc/fstab << EOF</userinput>
|
|
<literal>/dev/sda1 /boot/efi vfat defaults 0 1</literal>
|
|
<userinput>EOF</userinput></screen>
|
|
|
|
</sect2>
|
|
|
|
<sect2>
|
|
<title>Mount the EFI Variable File System</title>
|
|
|
|
<para>
|
|
The installation of GRUB on a UEFI platform requires that the EFI Variable
|
|
file system, <systemitem class="filesystem">efivarfs</systemitem>, to be
|
|
mounted. As the <systemitem class="username">root</systemitem> user,
|
|
mount it if it's not already mounted:
|
|
</para>
|
|
|
|
<screen role="nodump"><userinput>mountpoint /sys/firmware/efi/efivars || mount -v -t efivarfs efivarfs /sys/firmware/efi/efivars</userinput></screen>
|
|
|
|
<note revision="systemd">
|
|
<para>
|
|
If the system is booted with UEFI and systemd,
|
|
<systemitem class="filesystem">efivarfs</systemitem> will be mounted
|
|
automatically. However in the LFS chroot environment it still needs to
|
|
be mounted manually.
|
|
</para>
|
|
</note>
|
|
|
|
<para revision="sysv">
|
|
Now add an entry for the
|
|
<systemitem class="filesystem">efivarfs</systemitem> in
|
|
<filename>/etc/fstab</filename> so it will be mounted automatically
|
|
during system boot:
|
|
</para>
|
|
|
|
<screen revision="sysv" role="nodump"><userinput>cat >> /etc/fstab << EOF</userinput>
|
|
<literal>efivarfs /sys/firmware/efi/efivars efivarfs defaults 0 0</literal>
|
|
<userinput>EOF</userinput></screen>
|
|
|
|
<warning>
|
|
<para>
|
|
If the system is not booted with UEFI, the directory
|
|
<filename class="directory">/sys/firmware/efi</filename> will be
|
|
missing. In this case you should boot the system in UEFI mode with
|
|
the emergency boot disk created as above.
|
|
</para>
|
|
</warning>
|
|
</sect2>
|
|
|
|
<sect2>
|
|
<title>Setting Up the Configuration</title>
|
|
|
|
<para>
|
|
On UEFI based systems, GRUB works by installing an EFI application
|
|
(a special kind of executable) into
|
|
<filename class="directory">/boot/efi/EFI/[id]/grubx64.efi</filename>,
|
|
where <filename class="directory">/boot/efi</filename> is the mount
|
|
point of the ESP, and <literal>[id]</literal> is replaced with an
|
|
identifier specified in the <command>grub-install</command> command
|
|
line. GRUB will create an entry in the EFI variables containing
|
|
the path <literal>EFI/[id]/grubx64.efi</literal> so the EFI firmware
|
|
can find <filename>grubx64.efi</filename> and load it.
|
|
</para>
|
|
|
|
<para>
|
|
<filename>grubx64.efi</filename> is very lightweight (136 KB with
|
|
GRUB-2.06~rc1) so it will not use much space in the ESP. A typical ESP
|
|
size is 100 MB (for Windows boot manager, which uses about 50 MB in
|
|
the ESP). Once <filename>grubx64.efi</filename> loaded by the
|
|
firmware, it will load GRUB modules in the boot partition.
|
|
The default location is
|
|
<filename class="directory">/boot/grub</filename>.
|
|
</para>
|
|
|
|
<para>
|
|
As the <systemitem class="username">root</systemitem> user, install
|
|
the GRUB files into <filename>/boot/efi/EFI/LFS/grubx64.efi</filename>
|
|
and <filename class="directory">/boot/grub</filename>. Then set up the
|
|
boot entry in the EFI variables:
|
|
</para>
|
|
|
|
<screen role="nodump"><userinput>grub-install --bootloader-id=LFS --recheck</userinput></screen>
|
|
|
|
<para>
|
|
If the installation is successful, the output should be:
|
|
</para>
|
|
|
|
<screen role="nodump"><literal>Installing for x86_64-efi platform.
|
|
Installation finished. No error reported.</literal></screen>
|
|
|
|
<para>
|
|
Issue <command>efibootmgr | cut -f 1</command> to recheck the EFI boot
|
|
configuration. An example of the output is:
|
|
</para>
|
|
|
|
<screen role="nodump"><literal>BootCurrent: 0000
|
|
Timeout: 1 seconds
|
|
BootOrder: 0005,0000,0002,0001,0003,0004
|
|
Boot0000* ARCH
|
|
Boot0001* UEFI:CD/DVD Drive
|
|
Boot0002* Windows Boot Manager
|
|
Boot0003* UEFI:Removable Device
|
|
Boot0004* UEFI:Network Device
|
|
Boot0005* LFS</literal></screen>
|
|
|
|
<para>
|
|
Note that <literal>0005</literal> is the first in the
|
|
<literal>BootOrder</literal>, and <literal>Boot0005</literal>
|
|
is <literal>LFS</literal>. This means that on the next boot, the
|
|
version of GRUB installed by LFS will be used to boot the system.
|
|
</para>
|
|
|
|
</sect2>
|
|
|
|
<sect2>
|
|
<title>Creating the GRUB Configuration File</title>
|
|
|
|
<indexterm zone="grub-setup grub-video">
|
|
<primary sortas="e-boot-grub-grub-cfg">/boot/grub/grub.cfg</primary>
|
|
</indexterm>
|
|
|
|
<para>
|
|
Generate <filename>/boot/grub/grub.cfg</filename> to configure the
|
|
boot menu of GRUB:
|
|
</para>
|
|
|
|
<screen role="nodump"><userinput>cat > /boot/grub/grub.cfg << EOF</userinput>
|
|
<literal># Begin /boot/grub/grub.cfg
|
|
set default=0
|
|
set timeout=5
|
|
|
|
insmod part_gpt
|
|
insmod ext2
|
|
set root=(hd0,2)
|
|
|
|
if loadfont /boot/grub/fonts/unicode.pf2; then
|
|
set gfxmode=auto
|
|
insmod all_video
|
|
terminal_output gfxterm
|
|
fi
|
|
|
|
menuentry "GNU/Linux, Linux 5.18.8-lfs-r11.1-147" {
|
|
linux /boot/vmlinuz-5.18.8-lfs-r11.1-147 root=/dev/sda2 ro
|
|
}
|
|
|
|
menuentry "Firmware Setup" {
|
|
fwsetup
|
|
}</literal>
|
|
<userinput>EOF</userinput></screen>
|
|
|
|
<para>
|
|
<literal>(hd0,2)</literal>, <literal>sda2</literal>, and
|
|
<literal>5.18.8-lfs-r11.1-147</literal> should be replaced to match your
|
|
configuration.
|
|
</para>
|
|
|
|
<note>
|
|
<para>
|
|
From GRUB's perspective, the files are relative to the partition
|
|
are used. If you used a separate /boot partition, remove /boot from the
|
|
above paths (to kernel and to <filename>unicode.pf2</filename>). You
|
|
will also need to change the set root line to point to the boot
|
|
partition.
|
|
</para>
|
|
</note>
|
|
|
|
<para>
|
|
The <literal>Firmware Setup</literal> entry can be used to enter the
|
|
configuration interface provided by the firmware (sometimes called
|
|
<quote>BIOS configuration</quote>).
|
|
</para>
|
|
</sect2>
|
|
|
|
<sect2>
|
|
<title>Dual-booting with Windows</title>
|
|
|
|
<para>
|
|
Add a menu entry for Windows into <filename>grub.cfg</filename>:
|
|
</para>
|
|
|
|
<screen role="nodump"><userinput>cat >> /boot/grub/grub.cfg << EOF</userinput>
|
|
<literal># Begin Windows addition
|
|
|
|
menuentry "Windows 10" {
|
|
insmod fat
|
|
insmod chain
|
|
set root=(hd0,1)
|
|
chainloader /EFI/Microsoft/Boot/bootmgfw.efi
|
|
}</literal>
|
|
<userinput>EOF</userinput></screen>
|
|
|
|
<para>
|
|
<literal>(hd0,1)</literal> should be replaced with the GRUB
|
|
designated name for the ESP. The <literal>chainloader</literal>
|
|
directive can be used to tell GRUB to run another EFI executable,
|
|
in this case the Windows Boot Manager. You may put more usable tools
|
|
in EFI executable format (for example, an EFI shell) into the ESP and
|
|
create GRUB entries for them.
|
|
</para>
|
|
|
|
</sect2>
|
|
|
|
</sect1>
|