Changeset 1ff0f0c for postlfs/filesystems/uefi-bootloaders/grub-setup.xml
- Timestamp:
- 09/28/2022 10:34:01 AM (18 months ago)
- Branches:
- 11.3, 12.0, 12.1, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, lazarus, lxqt, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, trunk, xry111/llvm18, xry111/xf86-video-removal
- Children:
- 3d48ae4
- Parents:
- 5fe69261 (diff), 87065037 (diff)
Note: this is a merge changeset, the changes displayed below correspond to the merge itself.
Use the(diff)
links above to see all the changes relative to each parent. - File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
postlfs/filesystems/uefi-bootloaders/grub-setup.xml
r5fe69261 r1ff0f0c 20 20 <para> 21 21 BLFS does not have the essential packages to support Secure Boot. To 22 set up the boot process with GRUB for UEFI installedin BLFS, Secure22 set up the boot process with GRUB and UEFI in BLFS, Secure 23 23 Boot must be turned off from the configuration interface of the 24 24 firmware. Read the documentation provided by the manufacturer of your … … 99 99 100 100 <para> 101 Now the USB flash drive can be used as a emergency boot disk onx86-64101 Now the USB flash drive can be used as an emergency boot disk on any x86-64 102 102 UEFI platform. It will boot the system and show the GRUB shell. Then you 103 can type commands to boot your operating system s onthe hard drive.103 can type commands to boot your operating system from the hard drive. 104 104 To learn how to select the boot device, read the manual of your 105 105 motherboard or laptop. … … 117 117 118 118 <screen><literal>Processor type and features ---> 119 [*] EFI runtime service support [CONFIG_EFI]120 [*] EFI stub support [CONFIG_EFI_STUB]119 [*] EFI runtime service support [CONFIG_EFI] 120 [*] EFI stub support [CONFIG_EFI_STUB] 121 121 Enable the block layer ---> 122 122 Partition Types ---> 123 [*] Advanced partition selection [CONFIG_PARTITION_ADVANCED]124 [*] EFI GUID Partition support [CONFIG_EFI_PARTITION]123 [*] Advanced partition selection [CONFIG_PARTITION_ADVANCED] 124 [*] EFI GUID Partition support [CONFIG_EFI_PARTITION] 125 125 Device Drivers ---> 126 126 Firmware Drivers ---> 127 [*] Mark VGA/VBE/EFI FB as generic system framebuffer [CONFIG_SYSFB_SIMPLEFB]127 [*] Mark VGA/VBE/EFI FB as generic system framebuffer [CONFIG_SYSFB_SIMPLEFB] 128 128 EFI (Extensible Firmware Interface) Support ---> 129 < > EFI Variable Support via sysfs [CONFIG_EFI_VARS] 130 [*] Export efi runtime maps to sysfs [CONFIG_EFI_RUNTIME_MAP] 129 < > EFI Variable Support via sysfs [CONFIG_EFI_VARS] 131 130 Graphics support ---> 132 <*> Direct Rendering Manager [CONFIG_DRM] 133 <*> Simple framebuffer driver [CONFIG_SIMPLEDRM] 131 <*> Direct Rendering Manager [CONFIG_DRM] 132 [*] Enable legacy fbdev support for your modesetting driver [CONFIG_DRM_FBDEV_EMULATION] 133 <*> Simple framebuffer driver [CONFIG_DRM_SIMPLEDRM] 134 134 Frame buffer Devices ---> 135 <*> Support for frame buffer devices ---> [CONFIG_FB]135 <*> Support for frame buffer devices ---> [CONFIG_FB] 136 136 Console display driver support ---> 137 [*] Framebuffer Console support [CONFIG_FRAMEBUFFER_CONSOLE]137 [*] Framebuffer Console support [CONFIG_FRAMEBUFFER_CONSOLE] 138 138 File systems ---> 139 <DOS/FAT/EXFAT/NT Filesystems ---> 140 <*/M> VFAT (Windows-95) fs support [CONFIG_VFAT_FS] 139 141 Pseudo filesystems ---> 140 <*/M> EFI Variable filesystem [CONFIG_EFIVAR_FS]</literal></screen>142 <*/M> EFI Variable filesystem [CONFIG_EFIVAR_FS]</literal></screen> 141 143 142 144 <variablelist> 143 <title>The meaning of the configur eoptions:</title>145 <title>The meaning of the configuration options:</title> 144 146 145 147 <varlistentry> … … 166 168 <parameter>CONFIG_SYSFB_SIMPLEFB</parameter>, 167 169 <parameter>CONFIG_DRM</parameter>, 168 <parameter>CONFIG_SIMPLEDRM</parameter>, 170 <parameter>CONFIG_DRM_FBDEV_EMULATION</parameter>, 171 <parameter>CONFIG_DRM_SIMPLEDRM</parameter>, 169 172 <parameter>CONFIG_FB</parameter>, and 170 173 <parameter>CONFIG_FRAMEBUFFER_CONSOLE</parameter></term> 171 174 <listitem> 172 <para>The combination of these options allows the kernel to 173 print debug messages (along with Tux logos) at the early stage of 174 the boot process with UEFI. To ensure them functional at the early 175 stage, they shouldn't be built as a kernel module unless an 176 initramfs will be used.</para> 175 <para>The combination of these options provides the Linux console 176 support on top of the UEFI framebuffer. To allow the kernel to 177 print debug messages at an early boot stage, they shouldn't be 178 built as kernel modules unless an initramfs will be used.</para> 177 179 </listitem> 178 180 </varlistentry> … … 186 188 187 189 <para> 188 On EFI based system , the bootloaders are installed in a special FAT32190 On EFI based systems, the bootloaders are installed in a special FAT32 189 191 partition called an <emphasis>EFI System Partition</emphasis> (ESP). 190 If your system supports EFI, and a recent version of Linux192 If your system supports EFI, and a recent version of some Linux 191 193 distribution or Windows is pre-installed, it's likely that the ESP 192 is alreadycreated. As the194 has already been created. As the 193 195 <systemitem class="username">root</systemitem> user, list all the 194 196 partitions on your hard drive (replace <userinput>sda</userinput> … … 204 206 205 207 <para> 206 If the system or the hard drive is new, or it's a first time207 install an UEFIbooted OS on the system, the ESP may not exist.208 If the system or the hard drive is new, or it's the first 209 installation of a UEFI-booted OS on the system, the ESP may not exist. 208 210 In that case, create a new partition, make a 209 211 <systemitem class="filesystem">vfat</systemitem> file system on it, … … 214 216 <warning> 215 217 <para> 216 Some (old) UEFI implementations may demandthe ESP to be the first218 Some (old) UEFI implementations may require the ESP to be the first 217 219 partition on the disk. 218 220 </para> … … 251 253 <filename>EFI/BOOT/BOOTX64.EFI</filename>. Normally, a boot loader 252 254 should be installed into a custom path and the path should be recorded 253 in tothe EFI variables. The use of the hardcoded path should be254 avoided as much aspossible. However, in some cases we have to use255 in the EFI variables. The use of the hardcoded path should be 256 avoided if possible. However, in some cases we have to use 255 257 the hardcoded path: 256 258 </para> … … 259 261 <listitem> 260 262 <para> 261 The system is not booted with EFI yet, causing EFI variables263 The system is not booted with EFI yet, making EFI variables 262 264 inaccessible. 263 265 </para> … … 265 267 <listitem> 266 268 <para> 267 The EFI firmware is 64-bit but the LFS system is 32-bit, causing269 The EFI firmware is 64-bit but the LFS system is 32-bit, making 268 270 EFI variables inaccessible because the kernel cannot invoke EFI 269 271 runtime services with a different virtual address length. … … 272 274 <listitem> 273 275 <para> 274 LFS is built for a Live USB, so we cannot rely on EFI variables 275 which isstored in NVRAM or EEPROM on the local machine.276 LFS is built for a Live USB, so we cannot rely on EFI variables, 277 which are stored in NVRAM or EEPROM on the local machine. 276 278 </para> 277 279 </listitem> 278 280 <listitem> 279 281 <para> 280 You are unable or unwilling to install 282 You are unable or unwilling to install the 281 283 <application>efibootmgr</application> for manipulating boot 282 284 entries in EFI variables. … … 286 288 287 289 <para> 288 In these cases, follow th is section to installGRUB EFI290 In these cases, follow these instructions to install the GRUB EFI 289 291 application into the hardcoded path and make a minimal boot 290 configuration. Otherwise it's better to skip this section and readthe291 remaining sections to set up the boot configuration in a normal way.292 </para> 293 294 <para> 295 To install GRUB with the EFI application in stalled intothe hardcoded292 configuration. Otherwise it's better to skip ahead and set up the 293 boot configuration normally. 294 </para> 295 296 <para> 297 To install GRUB with the EFI application in the hardcoded 296 298 path <filename>EFI/BOOT/BOOTX64.EFI</filename>, first ensure the boot 297 299 partition is mounted at <filename class="directory">/boot</filename> 298 and the ESP mounted at299 <filename class="directory">/boot/efi</filename>. Then as the &root;300 and the ESP is mounted at 301 <filename class="directory">/boot/efi</filename>. Then, as the &root; 300 302 user, run the command: 301 303 </para> … … 303 305 <note> 304 306 <para> 305 Th ecommand will overwrite307 This command will overwrite 306 308 <filename>/boot/efi/EFI/BOOT/BOOTX64.EFI</filename>. It may break a 307 309 bootloader already installed there. Back it up if you are not sure. … … 312 314 313 315 <para> 314 Th e command would installGRUB EFI application into the hardcoded path316 This command will install the GRUB EFI application into the hardcoded path 315 317 <filename>/boot/efi/EFI/BOOT/BOOTX64.EFI</filename>, so the EFI 316 318 firmware can find and load it. The remaining GRUB files are installed 317 in to<filename class="directory">/boot/grub</filename> directory and319 in the <filename class="directory">/boot/grub</filename> directory and 318 320 will be loaded by <filename>BOOTX64.EFI</filename> during system boot. 319 321 </para> … … 321 323 <note> 322 324 <para> 323 The EFI firmware usually prefers the EFI applications with thepath324 recorded in boot entries stored in EFI variables,to the EFI325 The EFI firmware usually prefers the EFI applications with a path 326 stored in EFI variables to the EFI 325 327 application at the hardcoded path. So you may need to invoke the 326 328 boot selection menu or firmware setting interface to select the 327 329 newly installed GRUB manually on the next boot. Read the manual of 328 your motherboard or laptop to figure outhow.330 your motherboard or laptop to learn how. 329 331 </para> 330 332 </note> 331 333 332 334 <para> 333 If you've followed th is section and set up a minimal boot334 configuration, now skip until335 If you've followed the instructions in this section and set up a minimal boot 336 configuration, now skip ahead to 335 337 <quote>Creating the GRUB Configuration File</quote>. 336 338 </para> … … 342 344 <para> 343 345 The installation of GRUB on a UEFI platform requires that the EFI Variable 344 file system, <systemitem class="filesystem">efivarfs</systemitem>, to be346 file system, <systemitem class="filesystem">efivarfs</systemitem>, is 345 347 mounted. As the <systemitem class="username">root</systemitem> user, 346 348 mount it if it's not already mounted: … … 353 355 If the system is booted with UEFI and systemd, 354 356 <systemitem class="filesystem">efivarfs</systemitem> will be mounted 355 automatically. However in the LFS chroot environment it still needs to357 automatically. However, in the LFS chroot environment it still needs to 356 358 be mounted manually. 357 359 </para> … … 374 376 <filename class="directory">/sys/firmware/efi</filename> will be 375 377 missing. In this case you should boot the system in UEFI mode with 376 the emergency boot disk or minimal boot configuration created as378 the emergency boot disk or using a minimal boot configuration created as 377 379 above, then mount 378 380 <systemitem class="filesystem">efivarfs</systemitem> and continue. … … 400 402 GRUB-2.06) so it will not use much space in the ESP. A typical ESP 401 403 size is 100 MB (for Windows boot manager, which uses about 50 MB in 402 the ESP). Once <filename>grubx64.efi</filename> loaded by the403 firmware, it will load GRUB modules inthe boot partition.404 the ESP). Once <filename>grubx64.efi</filename> has been loaded by the 405 firmware, it will load GRUB modules from the boot partition. 404 406 The default location is 405 407 <filename class="directory">/boot/grub</filename>. … … 423 425 424 426 <para> 425 Issue <command>efibootmgr | cut -f 1</command>to recheck the EFI boot427 Issue the <command>efibootmgr | cut -f 1</command> command to recheck the EFI boot 426 428 configuration. An example of the output is: 427 429 </para> … … 484 486 <para> 485 487 <literal>(hd0,2)</literal>, <literal>sda2</literal>, and 486 <literal>5.19.2-lfs-11.2</literal> should be replaced tomatch your488 <literal>5.19.2-lfs-11.2</literal> must match your 487 489 configuration. 488 490 </para> … … 490 492 <note> 491 493 <para> 492 From GRUB's perspective, the files are relative to the partition 493 areused. If you used a separate /boot partition, remove /boot from the494 From GRUB's perspective, the files are relative to the partitions 495 used. If you used a separate /boot partition, remove /boot from the 494 496 above paths (to kernel and to <filename>unicode.pf2</filename>). You 495 will also need to change the set rootline to point to the boot497 will also need to change the "set root" line to point to the boot 496 498 partition. 497 499 </para> … … 529 531 in this case the Windows Boot Manager. You may put more usable tools 530 532 in EFI executable format (for example, an EFI shell) into the ESP and 531 create GRUB entries for them .533 create GRUB entries for them, as well. 532 534 </para> 533 535
Note:
See TracChangeset
for help on using the changeset viewer.