| |
@@ -82,7 +82,7 @@
|
| |
|
| |
subnet 192.168.1.0 netmask 255.255.255.0 {
|
| |
if option arch = 00:07 {
|
| |
- filename "uefi/shim.efi";
|
| |
+ filename "uefi/shim64.efi";
|
| |
} else {
|
| |
filename "pxelinux.0";
|
| |
}
|
| |
@@ -137,16 +137,16 @@
|
| |
[subs="quotes, macros"]
|
| |
----
|
| |
# [command]#mkdir -p `/var/lib/tftpboot/pxelinux.cfg`pass:attributes[{blank}]#
|
| |
- # [command]#cp `/usr/share/syslinux/{pxelinux.0,vesamenu.c32,ldlinux.c32,libcom32.c32,libutil.c32}` `/var/lib/tftpboot/`pass:attributes[{blank}]#
|
| |
+ # [command]#cp `/usr/share/syslinux/{pxelinux.0,menu.c32,vesamenu.c32,ldlinux.c32,libcom32.c32,libutil.c32}` `/var/lib/tftpboot/`pass:attributes[{blank}]#
|
| |
----
|
| |
|
| |
. Get the bootloader files for UEFI systems
|
| |
+
|
| |
- .. Install the [package]*shim* and [package]*grub2-efi* packages. If your server is a BIOS system, you *must install the packages to a temporary install root*. Installing them directly on a BIOS machine will attempt to configure the system for UEFI booting and cause problems.
|
| |
+ .. Install the [package]*shim-x64* and [package]*grub2-efi-x64* packages. If your server is a BIOS system, you *must install the packages to a temporary install root*. Installing them directly on a BIOS machine will attempt to configure the system for UEFI booting and cause problems.
|
| |
+
|
| |
[subs="attributes"]
|
| |
----
|
| |
- # dnf install shim grub2-efi-x64 --installroot=/tmp/fedora --releasever {PRODVER}
|
| |
+ # dnf install shim-x64 grub2-efi-x64 --installroot=/tmp/fedora --releasever {PRODVER}
|
| |
----
|
| |
+
|
| |
.. Create a directory for the bootloader files, and make them available there.
|
| |
@@ -154,7 +154,7 @@
|
| |
[subs="quotes, macros"]
|
| |
----
|
| |
# [command]#mkdir -p `/var/lib/tftpboot/uefi`pass:attributes[{blank}]#
|
| |
- # [command]#cp `/tmp/fedora/boot/efi/EFI/fedora/{shim.efi,grubx64.efi}` `/var/lib/tftpboot/uefi/`pass:attributes[{blank}]#
|
| |
+ # [command]#cp `/tmp/fedora/boot/efi/EFI/fedora/{shimx64.efi,grubx64.efi}` `/var/lib/tftpboot/uefi/`pass:attributes[{blank}]#
|
| |
----
|
| |
|
| |
.Configuring client bootloaders
|
| |
@@ -168,24 +168,23 @@
|
| |
prompt 1
|
| |
timeout 600
|
| |
|
| |
+ label local
|
| |
+ menu label Boot from ^local drive
|
| |
+ menu default
|
| |
+ localboot 0xffff
|
| |
+
|
| |
label linux
|
| |
menu label ^Install Fedora {PRODVER} 64-bit
|
| |
- menu default
|
| |
kernel f{PRODVER}/vmlinuz
|
| |
append initrd=f{PRODVER}/initrd.img inst.stage2=https://download.fedoraproject.org/pub/fedora/linux/releases/{PRODVER}/Server/x86_64/os/ ip=dhcp
|
| |
|
| |
label server
|
| |
menu label ^Install Fedora {PRODVER} ( Minimal Image )
|
| |
- menu default
|
| |
kernel f{PRODVER}/vmlinuz
|
| |
append initrd=f{PRODVER}/initrd.img inst.stage2=https://download.fedoraproject.org/pub/fedora/linux/releases/{PRODVER}/Server/x86_64/os/ ip=dhcp ks=https://example.com/fedora/kickstarts/minimal.ks
|
| |
-
|
| |
- label local
|
| |
- menu label Boot from ^local drive
|
| |
- localboot 0xffff
|
| |
----
|
| |
|
| |
- . Create a boot menu for UEFI clients at `/var/lib/tftpboot/pxelinux/uefi`.
|
| |
+ . Create a boot menu for UEFI clients at `/var/lib/tftpboot/uefi/grub.cfg`.
|
| |
+
|
| |
[subs="attributes"]
|
| |
----
|
| |
@@ -201,6 +200,10 @@
|
| |
set gfxpayload=keep
|
| |
insmod gzio
|
| |
|
| |
+ menuentry 'Exit this grub' {
|
| |
+ exit
|
| |
+ }
|
| |
+
|
| |
menuentry 'Install {PRODUCT} 64-bit' --class fedora --class gnu-linux --class gnu --class os {
|
| |
linuxefi f{PRODVER}/vmlinuz ip=dhcp inst.repo=https://download.fedoraproject.org/pub/fedora/linux/releases/{PRODVER}/Server/x86_64/os/
|
| |
initrdefi f{PRODVER}/initrd.img
|
| |
pcfe
commented 4 years ago
retiring an old el6 host to do DHCP and TFTP from a shiny new el8 machine, I ran into a few issues when going through the PXE setup guide.
This MR has 4 commits with 4 separate changes I had to make to what was documented.
- for old clients, I find it useful to also have menu.c32 available over TFTP
- on both Fedora 31 and el8 the names of shim an and grub-efi now contain -x64
- the config file path for UEFI clients did not work for me
- since this is a worry I encoutre often (and also have), the default targets were changed so that a user is forced to actively select an install target
Shout if you prefer each of these four to be in a separate MR. I figured since the changes were small I'd just try to do clean commits but only one PR