Cannot boot into fog menu in UEFI mode

[Sebastian Roth]

@Wayne-Workman said:

Are you purposely trying to UEFI boot? Have you not tried to put the laptops into legacy mode, or turn legacy option ROM support on?

Definitely a good point. But shouldn’t we be working towards better UEFI support in FOG?

@Charlee593 There is a setting to enable kernel debug output on the console for booting. Please enable KERNEL_DEBUG and crank up the LOGLEVEL in your FOG Settings (FOG Boot Settings) to 7. Hope we see more messages than just this.

[Wayne Workman]

@Sebastian-Roth said:

Definitely a good point. But shouldn’t we be working towards better UEFI support in FOG?

100% agree, but I had to ask.

[Sebastian Roth]

@Tom-Elliott He already tried snp.efi and snponly.efi. Do you really think that iPXE is having an issue that can be fixed by using a different binary? Kernel and init ram disk are being loaded. So NIC capability in iPXE is definitely fine…

[Tom Elliott]

@Sebastian-Roth It’s not always about the nic capability, but rather the memory segment to be used to load the init/kernel.

That said, of course there’s always the possibility that it’s loading is just taking a while. Not everything is instant. So how long are these sitting there?

[Charlee593]

Thanks for the replies.
@Wayne-Workman said:

Are you purposely trying to UEFI boot? Have you not tried to put the laptops into legacy mode, or turn legacy option ROM support on?

We are purposely trying UEFI boot, the software that we are testing require window 8 or 10 in UEFI mode. We tried legacy mode and it works.

@Sebastian-Roth said:

There is a setting to enable kernel debug output on the console for booting. Please enable KERNEL_DEBUG and crank up the LOGLEVEL in your FOG Settings (FOG Boot Settings) to 7. Hope we see more messages than just this.

We set it to 7 and it show no more than previous message, no difference.

@Tom-Elliott said:

Can you try some of the other .efi files, for example, try the snp.efi, or snponly.efi.
I tried snp.efi, snponly.efi, intel.efi this time, they all stuck on “init.xz”

@Tom-Elliott said:

That said, of course there’s always the possibility that it’s loading is just taking a while. Not everything is instant. So how long are these sitting there?

It sit on the “init.xz” for around 5 minutes then it goes back to the boot manager of the laptop. Then I check the fog manager, no host has been registered.

[Sebastian Roth]

Debug enabled (DEBUG=image) ipxe.efi binary to try: ipxe.efi

[Sebastian Roth]

Might this change have anything to do with it?? http://sourceforge.net/p/freeghost/code/4302/tree//trunk/src/ipxe/src-efi/config/general.h?diff=4031

I kind of doubt it but it still jumped at me when I looked through the recent changes on ipxe in our code.

The binary I compiled is without those defines…

[Tom Elliott]

I suppose it could, I can remove it and try again.

[Charlee593]

It is able to register the device now. I reinstalled the fog server and run Sebastian’s ‘ipxe.efi’. Running Fog version 5291. Thanks for the help

[Wayne Workman]

@Charlee593 Way to go! and thank you @Sebastian-Roth !!!

I must now try this version of ipxe.efi and see if I can UEFI boot a Dell

[Charlee593]

@Wayne-Workman I gonna try capture and deploy an UEFI Window 8 enterprise image.

Fog version 5291

[Tom Elliott]

Can you re-retry with latest trunk? I’ve removed the image lines as @Sebastian-Roth suggested and pushed it out.

[Charlee593]

@Tom-Elliott
Capture and Deploy window 8 in UEFI mode works. ( Fog version 5291 )
Now I gonna try the Fog version 5293.

[Charlee593]

@Tom-Elliott The latest Fog can register the host too ( Fog version 5293 ). Thanks for the help

[Wayne Workman]

Good news is I just UEFI network booted a Optiplex 9020 for the first time EVER! Awesome!!!

Bad news is our network manager goofed the entire district’s dhcp… I told him not to set options for our administration center in the super scope because it’d interfere… gah…

[Wayne Workman]

So… interesting…

with the Ad-Center goofing the DHCP, and this one computer pulling a lease from the ad-center’s DHCP coincidentally, it booted over UEFI. Ad-Center has FOG SVN 4103, cloud 4848…

I had our network manager change it back to point to our local fog server, which is running cloud 5293 svn 4323 and now UEFI network booting on the same machine is not working…

Sucks that it worked and then broke, but that’s a solid place to start looking…

-------------EDIT--------------

I’m a moron, I didn’t have a task queued for our local FOG server. Did that and network booted over UEFI.

IT’S IMAGING, NO PROBLEMS !!!

I’m going to have all our sites update to the latest now after snap-shoting.

[Sebastian Roth]

Thanks guys for testing and reporting back that quickly! Sounds great from my point of view. Still I wonder why those config changes made a difference. @Tom-Elliott Why did you add those?

[Tom Elliott]

@Sebastian-Roth to be honest, it was an attempt at comminizing the files so they were very similar between efi and non efi. It was not to hurt anything, but a way to make things more similar.

It’s this separation that you see two ipxescript files as well.