FOG menu don't boot Windows - Chainloading failed

[Sebastian Roth]

@thomasdec This is another very weird thing here LoadImage (EFI) function is not able to lead the bzImage although it seams to be intact (file size and signature checked)! So we need to dig into the EFI calls. Please try this ipxe.efi (compiled with DEBUG=efi_wrap)

[Sebastian Roth]

@thomasdec Have you ever tried booting other UEFI machines?? Please do so! We wanna make sure if this is an issue with FOG/network/setup or if it is a client/Yoga issue!?

[Sebastian Roth]

@thomasdec As well please run the following ipxe.efi (compiled with DEBUG=efi_image) to see what the exact error from LoadImage call is.

[thomasdec]

@Sebastian-Roth I tested with other Yoga 11e and ThinkPad E550 in UEFI mode, I have the same result.
Picture from test with DEBUG=efi_image :

In Legacy mode I can image my windows, so for now I will use this solution to develop my sysprep.

[Sebastian Roth]

@thomasdec Getting there step by step (I hope…). Please try this ipxe.efi where I added output of the “real” UEFI return code - iPXE usually only prints their own error codes which don’t give us more information. Mind you the output will be very similar to the last one but it should say:

EFIIMAGE 0x... could not load, efirc=??: Error...

I tested with other Yoga 11e and ThinkPad E550 in UEFI mode, I have the same result.

This - and the fact that the kernel booted from USB key - make me think that this is NOT an iPXE/UEFI issue but just some weird problem in your setup - hope we will find it soon!!!

[thomasdec]

@Sebastian-Roth I haveefirc=1 on all EFIIMAGE message.

[george1421]

@thomasdec Hey, I’d just like to thank you for hanging in here with us. We really need to get to the root of the issue with these “broken” efi firmware. Its not really broken, there is just something that iPXE is not handing off correctly under all efi firmware. Most efi firmware works correctly, there are a few systems that it is not. To get to the root of the problem we need people like you who are willing to hang in there with us to see if we can pinpoint the conflict.

Again I’d like to say thank you for helping with the try this, change that process. In the end this info will help the iPXE project as well as the FOG project to deliver a better product.

[thomasdec]

I found why the .efi file doesn’t work !
The problem come from an boot option.
I disable Security Chip in Security tab in Lenovo BIOS and now it’s work.
I can access FOG menu and image my computer.
Sorry for not finding it sooner !

@Sebastian-Roth @george1421 thanks again so much for your help !

[george1421]

Marking this Solved.

Great job finding that setting. I’m sure it will help someone else. I think there is another thread that will end up at this conclusion too.

[Sebastian Roth]

@thomasdec Thank god you found this. Looking at the PCAP file we captured I was pretty much convinced that it’s something weird on the file transfer as I saw retransmissions and as well missing packets… (possibly just a screwed packet dump?!?).

[george1421]

@Sebastian-Roth Is there something we can learn/document from this issue?

i.e. if you do X and you get results Y and Z and you are running hardware X, please check the security chip setting? There has to be a learning point in this thread.

[Raymond Bell]

@george1421 Is this what you are looking for?

https://wiki.fogproject.org/wiki/index.php?title=WorkingDevices