|
28 | 28 | <para> |
29 | 29 | This section explains creating &grub; NetBoot directories for PXE servers using |
30 | 30 | <command>grub2-mknetdir</command>, which generates architecture-specific directories for |
31 | | - &x86-64; (UEFI and BIOS), &aarch64;, and &ppc64le; systems. For &uefisecboot; support, |
| 31 | + &x86-64; (UEFI and BIOS), &aarch64;, and &ppc64le; systems. For Secure Boot support, |
32 | 32 | administrators must copy signed EFI files from installation media or use the |
33 | 33 | <package>shim</package> package to replace the default unsigned bootloader files. |
34 | 34 | </para> |
|
43 | 43 | different platforms. For example, &x86-64; systems generate both UEFI |
44 | 44 | (<filename>x86_64-efi</filename>) and legacy BIOS (<filename>i386-pc</filename>) directories, |
45 | 45 | and &aarch64; create their UEFI directory |
46 | | - <filename>arm64-efi</filename>. &ppc64le; systems (<filename>powerpc-ieee1275</filename>) supports secure boot too, but not UEFI; the grub bootloader is in <filename>/boot/grub2/grub.elf</filename> on the ISOs. |
| 46 | + <filename>arm64-efi</filename>. &ppc64le; systems (<filename>powerpc-ieee1275</filename>) supports secure boot too; the &grub; bootloader is in <filename>/boot/grub2/grub.elf</filename> on the ISOs. |
47 | 47 | </para> |
48 | 48 | <important> |
49 | 49 | <para> |
50 | | - In the context of this section, Secure Boot refers to &uefisecboot; as supported on &x86-64; and &aarch64; architectures. &grub; PXE Secure Boot for &ppc64le; (which uses a different platform-specific mechanism) is not covered here. |
| 50 | + In the context of this section, Secure Boot applies to &x86-64; and &aarch64; architectures. &grub; PXE Secure Boot for &ppc64le; (which uses a different platform-specific mechanism) is not covered here. |
51 | 51 | </para> |
52 | 52 | </important> |
53 | 53 | <para> |
54 | | - For &uefisecboot; support, which is not provided by the default unsigned |
55 | | - <filename>core.efi</filename> files, administrators can obtain signed EFI files for &uefisecboot; from either of the following sources: |
| 54 | + For Secure Boot support, which is not provided by the default unsigned |
| 55 | + <filename>core.efi</filename> files, administrators must obtain signed EFI files. |
| 56 | + The signed files can be obtained from either of the following sources: |
56 | 57 | </para> |
57 | 58 | <itemizedlist> |
58 | 59 | <listitem> |
59 | 60 | <para> |
60 | | - The <package>shim</package> package installed on the PXE server itself (<command>zypper |
61 | | - install shim</command>), which provides <filename>shim.efi</filename>, |
62 | | - <filename>grub.efi</filename>, and <filename>MokManager.efi</filename> under |
63 | | - <filename>/usr/share/efi/<replaceable>${ARCH}</replaceable>/</filename>. This is the |
64 | | - preferred method on a registered &productnameshort; &productnumber; system and does not require access to |
65 | | - installation media. |
| 61 | + The <package>shim</package> package installed on the PXE server (<command>zypper install |
| 62 | + shim</command>), which provides <filename>shim.efi</filename>, <filename>grub.efi</filename>, |
| 63 | + and <filename>MokManager.efi</filename> under |
| 64 | + <filename>/usr/share/efi/<replaceable>ARCH</replaceable>/</filename>. Note that the |
| 65 | + <package>shim</package> package provides files only for the architecture of the PXE server |
| 66 | + itself. To support a different architecture, use the installation media ISO or manually |
| 67 | + extract the files from the architecture-specific <package>shim</package> package. |
66 | 68 | </para> |
67 | 69 | </listitem> |
68 | 70 | <listitem> |
69 | 71 | <para> |
70 | | - The installation media ISO (mounted and copied from <filename>/mnt/EFI/BOOT/*.efi</filename>), which is useful when the PXE server is not registered or the shim package is not available. |
| 72 | + The installation media ISO (mounted and copied from <filename>/mnt/EFI/BOOT/*.efi</filename>), |
| 73 | + which provides signed EFI files for the target architecture regardless of the PXE server |
| 74 | + architecture. |
71 | 75 | </para> |
72 | 76 | </listitem> |
73 | 77 | </itemizedlist> |
|
174 | 178 | <para> |
175 | 179 | Replace <filename><replaceable>ARCH</replaceable>-efi</filename> with |
176 | 180 | <filename>x86_64-efi</filename> or <filename>arm64-efi</filename>—the |
177 | | - supported architectures for &uefisecboot;. |
| 181 | + supported architectures for Secure Boot. |
178 | 182 | </para> |
179 | 183 | </callout> |
180 | 184 | </calloutlist> |
|
0 commit comments