In a recent discussion I found...

> You have to start the PC using UEFI boot via PXE (instead of legacy) -
> than grub-install installs the efi-based grub when called by FAI.

...and that's exactly what I'm fighting with currently.
Has anybody done this already? Booting PXE in UEFI mode in order to run the FAI 
installation for UEFI?

I configured the BIOS settings of the client accordingly: Secure Boot off; 
Enable UEFI network stack; included NIC into boot list; etc.

On the FAI server side I can see the DHCPDISCOVER, DHCPOFFER, DHCPREQUEST and 
DHCPACK sequence with correct MAC and IP addresses in the daemon.log . This is 
followed by the usual "tftp: client does not accept options", so I assume that 
control gets handed over to tftpd. Looks like a successful PXE boot to me.

On the client side the PXE is requesting the address, waiting for some time, 
then the screen displays a generic error message and recommends to run diags, 
go to BIOS or try again.

An update of the client's BIOS to the most recent version did not help.

In my despair I even called the vendor support. They told me that I needed a 
different pxelinux image for UEFI... Can this be true?

BTW: The very same configuration booted with PXE in legacy mode works 
perfectly. It starts fine and the whole installation runs through until the 
system is installed completely. Of course, it installed a legacy system, not 
UEFI, then.

Thanks for any experience/advice/help,
Frank
--
Frank Morawietz


This message and any attachment are confidential and may be privileged or 
otherwise protected from disclosure. If you are not the intended recipient, you 
must not copy this message or attachment or disclose the contents to any other 
person. If you have received this transmission in error, please notify the 
sender immediately and delete the message and any attachment from your system. 
Merck KGaA, Darmstadt, Germany and any of its subsidiaries do not accept 
liability for any omissions or errors in this message which may arise as a 
result of E-Mail-transmission or for damages resulting from any unauthorized 
changes of the content of this message and any attachment thereto. Merck KGaA, 
Darmstadt, Germany and any of its subsidiaries do not guarantee that this 
message is free of viruses and does not accept liability for any damages caused 
by any virus transmitted therewith.



Click http://www.merckgroup.com/disclaimer to access the German, French, 
Spanish and Portuguese versions of this disclaimer.

Antwort per Email an