@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.

@george1421 When I renamed refind.efi to refind_x64.efi, it worked as intended. Thank you for your help, I really appreciate it.

@george1421
im just getting chain loading errors - we have the usbc to ethernet. that will have to do meantime.

Cheers for the help there. much appreciated.

Duncan

@chris_unit As long as it is default NO. Otherwise you have to change it to bzimage and bzimage32 in fog system settings TFTP Server

@eduardotseoane @sebastian-roth @george1421 @Fernando-Gietz

Problem solved with last development ipxe.efi

https://github.com/FOGProject/fogproject/tree/dev-branch/packages/tftp

@saad-naeem
@dustindizzle11

Thank you guys both for the heads up!
Just got more of these models in stock.
Didn’t think about it until the imaging hung. (I have not updated FOG kernel…)

Using USB-C LAN adapters and those are helping to get the job done.

I may try updating the FOG kernel, in which case I’ll post here about results.

-Maurice

@kwalker said in Dell Latitude 3520 won't boot into PXE IPv4:

@sebastian-roth I’d like to join this chain since I’m running into these issues with the 7320s. As the previous models we’ve used had legacy boot, I believe I’ll need to configure the DHCP server to provide iPXE binaries. Is there a how-to you can recommend for this process?

MOD Note: In your case the issue is different than the OP of this thread. So with that in mind I would like you to start a new thread to discuss the issue. If we mix issues in one thread people who find the thread later on will get confused because the subject is X and then people start talking about Y. But to give you a little light reading before you create your own thread on the problem, look over this article. https://wiki.fogproject.org/wiki/index.php/BIOS_and_UEFI_Co-Existence#Using_Windows_Server_2012_.28R1_and_later.29_DHCP_Policy

in your most recent post make sure the policies are enabled on the dhcp server as well as you have all of the right hardware types defined both type 7 and 9 for 64 bit uefi.

@george1421 Yeah, it seems it was the drivers for the ethernet port itself that needed to be updated. So weird. You’d think that would have been tested before the device was even shipped out, too, but evidently not… It really is an odd one.

Thanks for sticking it out with us! The help is much appreciated.

@sebastian-roth
thought it is not too old. My fault…
We will update the server and see what happens.
Thanks meanwhile.
Have a nice week
Greets
JT