Hi Chris,

----- Original Message -----

Hey All,

Sorry if I have missed this someplace obvious. But I am trying to test a pxe install on a Mustang (xgene-1) board with F27 using the grubaa64.efi acquired from here: http://dl.fedoraproject.org/pub/fedora-secondary/releases/27/Server/aarch64/...

We did have some issues with grub in F27 but I thought it was all fixed for GA. I have my dhcp server setup to offer BOOTAA64.EFI, which then loads grubaa64.efi and displays the grub.cfg . I changed it to offer grubaa64.efi instead and it also worked. Here is the snippet from my dhcpd.conf:

host mustang { option host-name "mustang"; hardware ethernet 00:01:73:02:0c:cb; fixed-address 192.168.0.74; filename "BOOTAA64.EFI"; # filename "grubaa64.efi"; }

from logs: Feb 14 13:59:58 rhel in.tftpd[21762]: tftp: client does not accept options Feb 14 13:59:58 rhel in.tftpd[21763]: Client 192.168.0.74 finished BOOTAA64.EFI Feb 14 13:59:58 rhel in.tftpd[21764]: Client 192.168.0.74 finished grubaa64.efi Feb 14 13:59:59 rhel in.tftpd[21765]: Client 192.168.0.74 finished /grub.cfg

Using only grubaa64.efi: Feb 14 14:01:33 rhel in.tftpd[21803]: tftp: client does not accept options Feb 14 14:01:33 rhel in.tftpd[21804]: Client 192.168.0.74 finished grubaa64.efi Feb 14 14:01:33 rhel in.tftpd[21805]: Client 192.168.0.74 finished /grub.cfg

Are you using a mix of BOOTAA64.EFI/grubaa64.efi from different releases?

md5sum of F27 files tested: cc51ffe02728a744f32bb4f5a604730b BOOTAA64.EFI 8e19492e08d15297f4735f1f9381896a grubaa64.efi

Paul

After being handed off this file from my dhcp server, the system drops down into a 'grub>' shell awaiting my input. But if I then replace the F27 grubaa64.efi file with the known good grubaa64.efi from RHEL-alt-7.4, the system boots as normal and loads my grub.cfg menu and I am allowed to choose an install option:

---

  Install Red Hat Enterprise Linux for ARM 7.4 GA
  Install Fedora 27


  Use the  and  keys to change the selection.
  Press 'e' to edit the selected item, or 'c' for a command prompt.

The selected entry will be started automatically in 2s.

However, as you can imagine, this does not work if I select the Fedora 27 install. It halts and tells me I need to load the correct kernel:

---

error: invalid magic number. error: you need to load the kernel first.

---

This I assume is b/c I am using the incorrect grubaa64.efi to hand off to the F27 install kernel.

So, is this a bug in the F27 grubaa64.efi? I have a pxe server that has been working for me with UEFI systems for a couple years now. All I normally do to test a a new OS is swap out the grubaa64.efi as I have done here. But, I admit that my experience is with different versions of RHEL and cetos. This is my first time doing this with Fedora. Thanks in advance for any tips! _______________________________________________ arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-leave@lists.fedoraproject.org