@slang said in Fujitsu A3510 PXE UEFI Boot:

10EC&DEV_8168&

Thank you for sharing your experiences here. For new hardware we are seeing that iPXE needs to be rebuilt with the latest code from the iPXE project (different from FOG Project). That program manages the iPXE menu. For FOG, you also need to make sure you update the FOS Linux kernel (FOG Web UI->FOG Configuration->Kernel update) to at least the 5.10.x version of the kernel. This will allow FOS Linux (the engine that clones hard drives) to support the latest hardware too.

One last bit of information, you might want to upgrade to the dev-branch of FOG to bring your fog install up to 1.5.9.114 to address an issue if you plan on cloning Windows 20H2 or later. Microsoft changed the disk structure that requires the upgrade to FOG.

I just found this thread whilst searching for the “Stuck on EFI Stub” error which I also have on a Lenovo V130-151KB Laptop.

I changed our dhcp boot option 67 to point at the ncm–ecm–axge.efi file.

This resulted in my being able to re-image a laptop with a broken LAN port via a Dell USB Lan adapter.

I hope this might be of use to fellow victims of Lenovo. 😀

@austinjt01 The error message in the pictures does not seem to be the same than the one you describe via text. Please be more specific on what exactly the issue is.

I’ve been having the same issue with the G8 ProBooks and have finally got one to image throught the NIC however I’ve been through many steps so I followed this guide
https://docs.fogproject.org/en/latest/reference/compile_ipxe_binaries.html
I then re-downloaded & re-installed FogProject from github.
PXE is noticably faster and so far so good.
Whether compiling and copying the ipxe worked or whether it was the re-install or a bit of both I cannot say.

@george1421 Thanks so much @george1421 ! That fixed my issue.

@TKurtz12 Ok, there you go. Found several topics on this issue:
https://forums.fogproject.org/topic/15779/deploy-image-menu-not-coming-up
https://forums.fogproject.org/topic/15778/hp-elitebook-840-g8
https://forums.fogproject.org/topic/15940/hp-probook-g8-issues-imaging
https://forums.fogproject.org/topic/15715/problem-i-can-t-restore-image-on-hp-probook-450-g8-650-g8-430-g8

Carefully read through all those and you’ll see that some people even contacted HP support on this already. But I don’t think we have any positive feedback from them yet.

@george1421 i had the same problem like this guy here https://forums.fogproject.org/topic/15755/your-kernel-is-most-likely-missing-the-correct-driver

the steps in the thread worked fine for me and solved the problems, now it works on both models

sorry for the extra thread

@rango said in can't get into ipxe console with uefi:

burn the rom into card

What exactly do you mean when you say this? “Burn the rom” is a very specific action.

@Julien-asv Well I suggest you do some testing before January because if there is still something we need to fix then…

@tformentini Yes you are running 4.19.x series. That is a little old and does not have the drivers built in for the latest hardware.

To update you do this from inside the FOG Web user interface. It is easy. Go to FOG Configuration -> Kernel update. You will see a listing of kernels. Select 5.10.71 for both 64 bit and 32 bit. Once that is done you can verify by running the same command line command as you did before. It should confirm as 5.10.71

@george1421 said in Mixed driver environment:

Talk about worked like a champ!
Wasn’t sure if recompiling would cause more headaches, or not.

We have been trying to find a way to get UEFI to play nice, we didn’t find your post from Nov 2…

@george1421, THANK YOU!!!
!SOLVED!

@pcrispim So if on the fog server you navigate to /var/www/html/fog/service/ipxe/ and key in file bzImageB851 what does it report?

@perler https://forums.fogproject.org/post/145882

This problem is mostly due to an memory error or disk error on the machine your fogging to.
Try swapping ram or disk on the target machine.

@pierre-baylet Are all the machines in the exact same BIOS/UEFI firmware version?

@Dungody Please keep us posted on your findings. As soon as there is a fix in iPXE we cann add the to the dev-branch version.

Also feel free to ask here if you need help with providing the information the iPXE developers will definitely ask you for.

@LuisTemporal What kind of failures do you think might occur? Can’t promise you FOG will work with each and every hardware out there but as we rely on the Linux kernel as a basis the list of supported hardware is immense. It’s up to you though. FOG is open source and you can ask for help with specific hardware or even get your hands dirty and compile you own kernel with added drivers if needed.

@george1421

We found that we had to fiddle with a good many settings in the bios including UEFI boot path security and a few others. Even then the only way we can get to it is by doing “F12” and manually choosing PXE Boot which is very strange. It works after that however. This can be closed out.

@MedericLPS As you can see in the last post by @Captain_Adam the update to dev-branch fixed the issue.

@george1421 Thank you for the assistance you have provided in this. , I can’t thank you guys enough for your support and hard work you guys do for the community.