On 4/30/19 18:19, John Paul Adrian Glaubitz wrote:
On 4/30/19 6:13 PM, Pedro Miguel Justo wrote:
And setup will proceed correctly. So, this is what mean by “replacing the
executable”. In a nutshell replacing bootnetia64.efi with bootnetia64.efi and
keep everything else in the tarball.
This pretty much sounds to me that the GRUB EFI executable from the netboot
image is
really just to be used for netboots and not local boots using your particular
hack.
I'd back that. To be sure one could check the TFTP requests the machine
is emitting after starting `bootnetia64.efi`:
The sequence for e.g powerpc-ieee1275 is:
```
RRQ from 172.16.2.100 filename /boot/grub/powerpc-ieee1275/normal.mod
RRQ from 172.16.2.100 filename /boot/grub/powerpc-ieee1275/crypto.mod
RRQ from 172.16.2.100 filename /boot/grub/powerpc-ieee1275/terminal.mod
RRQ from 172.16.2.100 filename /boot/grub/powerpc-ieee1275/gettext.mod
RRQ from 172.16.2.100 filename /boot/grub/powerpc-ieee1275/gzio.mod
RRQ from 172.16.2.100 filename /boot/grub/powerpc-ieee1275/command.lst
RRQ from 172.16.2.100 filename /boot/grub/powerpc-ieee1275/fs.lst
RRQ from 172.16.2.100 filename /boot/grub/powerpc-ieee1275/crypto.lst
RRQ from 172.16.2.100 filename /boot/grub/powerpc-ieee1275/terminal.lst
RRQ from 172.16.2.100 filename /boot/grub/grub.cfg
```
... though I'm not sure if `bootnetia64.efi` will behave differently if
not loaded from network.
Cheers,
Frank
