Yeah, I'm sure. The syslinux-efi package works as advertized. I mean,
you cannot boot an EFI machine via pxelinux.0. That would hang.
Are you saying that you're not seeing a request for ldlinux.e64 right
after the request for syslinux.efi? There's no error message in the tftp
logs? File not found, permission denied, something? I can't explain
that. But after all, this isn't exactly an FAI problem. When I started
experimenting with the syslinux-efi package, I set it up to boot into
the ubuntu installer. In fact, that's how I made my base file for FAI
installs of bionic. But fai isn't really involved up to this point. It
has to be some kind of problem with tftp.
You can run a tftp client and get all the files you need during a pxe
boot .On the server, I say, "tail -f /var/log/syslog | grep tftp" and
then on the target machine (assuming linux is installed somehow), I run
the tftp client and get the bootloader, either pxelinux.0 or
syslinux.efi, the library file ldlinux.e64, and the config file. You
ought to see the log entries scroll by on the fai server.
On 07/10/2018 06:02 AM, Thomas Lange wrote:
Hi John,
I didn't manage to get network booting using UEFI without grub but
with syslinux running. I copied the syslinux.efi and ldlinux.e64 into
my tftp directory. Using tcpdump I see that the UEFI is getting the
syslinux.efi file (even I use a different name and a symlink). I do
not see any request for the ldlinux.e64 file.
In your setup, are you really getting syslinux with UEFI use the
config from fai-chboot? Maybe your computer has still CSM (the legacy
mode) enabled, and you are still using pxelinux.
