Lately, I wanted to install Fedora 27 on the above HW. It uses UEFI
instead of BIOS. Install, that means:
1. Download the Fedora Server Netinstall
Fedora-Server-netinst-x86_64-27-1.6.iso and dd it to a micro SD card.
2. Create an approp ks file on the local Web http://install.lan
3. Boot from the micro SD card and add the ks file link to the linux
4. Let nature take its course
5. Reboot into runlevel 3
6. dnf -y update
7. dnf -y groupinstall “Xfce Desktop”
8 dnf -y install sddm
9. systemctl enable –force sddm
But when rebooting (setp 5) the laptop went into a boot loop. There was
a message showing up for about half a second, which said:
System BootOrder not found. Initializing default.
Creating boot file BOOT0000 with Fedora on file abcdefghik.
Fortunately there is a Boot-Option “Boot from EFI file”, which let me
select the grubx64.efi file as boot file. Using this, the laptop booted
Using efibootmgr (efibootmgr -o 0,1,2)I could not set the BootOrder,
i.e. I could set it, but it was lost across the BootProcess. The only
thing, which was saved across the BootProcess was the BootNext option
(set with efibootmgr -n 3).
To automate the BootProcess I did the following:
cp fedora/grubx64.efi BOOT
efibootmgr -b 0 -l EFI/BOOT/grubx64.efi
because: apparently the laptop booted from BOOT0000. The above sequence
made it take the file grubx64.efi from BOOT0000 and boot into fedora.
That was, however, not the end of the troubles: After fedora had booted
and the sddm DisplayManager showed up, I could not enter the password,
because the keyboard was irresponsive. But this is another story, which
I solved by installing Centos 7 on the laptop.