Replying to my own question in case anyone else is looking at this
thread for answers...
As Sven Schumacher confirmed (messages with blank subject so they may
not be part of this thread), yes the client needs to PXE boot with UEFI.
Once I adjusted my dhcpd.conf and added the efi versions of syslinux my
PXE client booted in UEFI mode and FAI completed a deployment with the
target configured to boot in UEFI mode also.
Thanks all. One more issue down on the path to deploying Buster.
Cheers,
Merlin.
On 11/26/19 10:28 AM, CSCI Technician wrote:
On 11/26/19 6:08 AM, Thomas Lange wrote:
On Mon, 25 Nov 2019 16:53:24 -0800, CSCI Technician
<t...@csci.viu.ca> said:
> The related classes defined are GRUB and GRUB_EFI. GRUB_PC is not
> defined. What I'm not sure how to fix is to get grub-install
to realize
> this is an efi and not a bios install so that it should be
using the efi
> path instead of the i386-pc path.
I do not know how grub decides or detects when to use EFI. In FAI we
check if /sys/firmware/efi exists. Is /sys mounted to /target during
the installation? Otherwise this is a grub, not a FAI problem.
This is likely a dumb/obvious question but do you need to be booted in
uefi mode for the the install to use uefi?
I don't have a /sys/firmware/efi or a /target/sys/firmware/efi during
the install. I had thought there was a way to tell FAI to configure
the boot on the target for uefi regardless of what FAI is running in.
In looking at grub-install it also looks for /sys/firmware/efi.
Cheers,
Merlin.
--
Merlin Hansen
Department of Computing Science
Vancouver Island University
900 Fifth Street
Nanaimo BC V9R 5S5
250-753-3245 x 2321
t...@csci.viu.ca
