Re: Net-boot arm64 with nfsroot, Re: Create fai-cd for other architecture?

On Thu, 2023-01-26 at 12:15:07 +0100, Thomas Lange wrote:
> >>>>> On Thu, 26 Jan 2023 11:06:14 +0100, Steffen Grunewald <[email protected]> said:
> 
>     > Which info do you need? Would the output of `ls -lR /boot` (on a booting
>     > machine) be sufficient, or even too much? Any selections from dpkg output?
> I'm not sure which infos I need. Maybe the pathes for grub.
> I also need to know if some grub commands in fai-cd need to be called
> with different parameters. What about --format=x86_64-efi? Do we need
> to add some grub modules for --install-modules=...?
> What about the xorriso call? There are also intel arch specific options.

This seems to be more complicated than I expected :(

There's good news though: PXE is not *broken* on the machine, it's just *different*.
Different in terms of the "PXEClient:ARCH:xxxxx" magic number it sends to the DHCP
server.
Now knowing that xxxxx is 00011 (0x0b), I could assign an initial bootloader for
UEFI, like I'm doing with my x86_64 machines. If I only knew which file to use...

Jan 27 13:18:39 faiserver dhcpd[125420]: DHCPOFFER on 10.150.100.100 to 1c:1b:0d:ef:76:7a via eth2
Jan 27 13:18:43 faiserver dhcpd[125420]: DHCPREQUEST for 10.150.100.100 (10.150.100.109) from 1c:1b:0d:ef:76:7a via eth2
Jan 27 13:18:43 faiserver dhcpd[125420]: DHCPACK on 10.150.100.100 to 1c:1b:0d:ef:76:7a via eth2
Jan 27 13:18:43 faiserver in.tftpd[76654]: RRQ from 10.150.100.100 filename grubnetaa64.efi
Jan 27 13:18:43 faiserver in.tftpd[76654]: tftp: client does not accept options
Jan 27 13:18:43 faiserver in.tftpd[76899]: RRQ from 10.150.100.100 filename grubnetaa64.efi
Jan 27 13:18:47 faiserver in.tftpd[80100]: RRQ from 10.150.100.100 filename /grub/arm64-efi/command.lst
Jan 27 13:18:47 faiserver in.tftpd[80100]: sending NAK (1, File not found) to 10.150.100.100
Jan 27 13:18:47 faiserver in.tftpd[80102]: RRQ from 10.150.100.100 filename /grub/arm64-efi/fs.lst
Jan 27 13:18:47 faiserver in.tftpd[80102]: sending NAK (1, File not found) to 10.150.100.100
Jan 27 13:18:47 faiserver in.tftpd[80142]: RRQ from 10.150.100.100 filename /grub/arm64-efi/crypto.lst
Jan 27 13:18:47 faiserver in.tftpd[80142]: sending NAK (1, File not found) to 10.150.100.100
Jan 27 13:18:47 faiserver in.tftpd[80192]: RRQ from 10.150.100.100 filename /grub/arm64-efi/terminal.lst
Jan 27 13:18:47 faiserver in.tftpd[80192]: sending NAK (1, File not found) to 10.150.100.100
Jan 27 13:18:47 faiserver in.tftpd[80298]: RRQ from 10.150.100.100 filename /grub/grub.cfg
Jan 27 13:18:47 faiserver in.tftpd[80298]: sending NAK (1, File not found) to 10.150.100.100

So "grubnetaa64.efi" (as suggested for RasPi PXE boot) doesn't seem to be the right one.
The debian-installer-11-netboot-arm64 contains "bootnetaa64.efi" which looks a bit better,
but the second-step loader will be "grubaa64.efi", which gets me to the "grub> " prompt
again.

I feel I'm getting closer but I'm not there yet... back to reading now.

- S