That did the trick! Thanks, Paul

The kickstart installation is humming along nicely until the bootloader is 
being installed. It errors out and I have to manually select "yes" to continue. 
The system is still installed fine and starts without problems but it's not 
unattended:

21:33:35,996 DBG bootloader.installation: Configuring the boot loader.
21:33:36,003 DBG bootloader.installation: Collecting the OS images for: 
5.1.5-300.fc30.aarch64
21:33:36,006 DBG bootloader.base: new default image: 
<pyanaconda.bootloader.image.LinuxBootLoaderImage object at 0xffffa2472eb8>
21:33:36,010 DBG bootloader.installation: Writing to /etc/sysconfig/kernel.
21:33:36,083 DBG bootloader.installation: Installing the boot loader.
21:33:36,085 INF bootloader.installation: boot loader stage1 target device is 
mmcblk0p1
21:33:36,086 INF bootloader.installation: boot loader stage2 target device is 
mmcblk0p2
21:33:36,754 INF bootloader.grub2: bootloader.py: used boot args:
21:33:51,449 ERR bootloader.installation: bootloader.write failed: Failed to 
set new efi boot target. This is most likely a kernel or firmware bug.

In my kickstart I'm using this to configure the bootloader:

bootloader --location=mbr --timeout=1 --boot-drive=mmcblk0

which is exactly the same that is in the KS file that can be found in the 
official AARCH64 image.

My uneducated guess is that GRUB has some sort of beef with the lack of a EFI 
ROM so it can't register a boot entry. Can that be disabled somehow? Haven't 
found an option for that in the man pages.
I tried  --location=none which clears the error but it also doesn't generate 
the grub.cfg so maybe I need to call grub2-mkconfig in my %post section to 
compensate for that. Any other ideas?
_______________________________________________
arm mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/[email protected]

Reply via email to