@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

Thanks everyone for the input…finally got it to work. I tried snponly.efi no go.

This is the combination that worked.
BIOS A15
Legacy mode is on
undionly.kpxe on the advanced DHCP option

@sebastian-roth

ipxe.pxe works,
I will test if with the other computers it still works.
Thank you for your help.

@sebastian-roth

Good news everyone.
Problem seems to be resolved, image is deployed normally.
Thank you for your investment and your speed.

@cello said in Dell Optiplex 7080 Network error:

First: DELL Optiplex 7080 works very well with FOG Version 5.10.34

Great to here! I should have some o7090s in the next few days (weeks) so those should work too. I don’t know why the integrated kernel update program did not work for you, but I’m glad you have it worked out.

I was getting similar myself with the ipxe Rom hanging at “iPXE initializing devices”. The solution was to build a fresh undionly.kpxe (https://wiki.fogproject.org/wiki/index.php/IPXE#Compile).
Before you bake, modify general.h to comment out or remove the following lines:
#define DOWNLOAD_PROTO_HTTPS
#define IMAGE_TRUST_CMD
#define CERT_CMD
Then compile, and copy the rom to your tftp folder.

@george1421 said in Which USB 3.0 ethernet adapter?:

@bristow-0 OK I can say I’ve never heard of an “LDLC Aurore” computer before. It must be a local French brand. If you want to pxe boot then you will need to get a usb network adapter that LDLC computer’s support.

This is Clevo. The good thing is that they provide PCs without OS.

Now for a uefi computer making the computer boot iPXE from the flash usb drive is pretty easy. https://forums.fogproject.org/topic/6350/usb-boot-uefi-client-into-fog-menu-easy-way Understand that “trick” only works for uefi based computers. BIOS computer’s can’t boot using this method.

Cool, thanks a lot !!

@sgtrice If your 7080 firmware/bios disk controller is in raid-on mode, you need to switch to ahci mode. Intel has not (even after 6 years) release the raid controller driver to the linux community. If you have only one drive and not using raid you can leave the disk mode as ahci with no loss of performance.

@thanhpn7188 I think it’s good you posted this in a new topic because it sounds like you have an issue with this hardware and we might try to help you to make it work. The other topic you posted is about hardware that does work fine with FOG.

Hint: I also renamed this topic to reflect what this seems to be about.

Now to the issue: FOG doesn’t see the disk? Often this is caused by BIOS/UEFI setting for the disk controller is RAID instead of AHCI. Be aware that this change will influence the Windows OS if it’s installed already.

@novaholic Hi,
I am facing with the same problem.
Have you managed to fix it?

Thanks

Hey I Just found a solution to this… when making the DHCP policy the snponly.efi file seemed to work (instead of ipxe.efi)… Hope this helps

@Eruthon Thanks for the quick feedback. Should be all fine now I think. No need to post partition files as long as it works for you now.

Another Lenovo device that seems to hang with that message as well: https://forums.fogproject.org/topic/15463/lenovo-81cy-stuck-on-efi-stub

@sebastian-roth we may have found a workaround since we have a uefi/bios co-existence setup, we are trying to legacy boot to capture/deploy the uefi image. It appears to have worked. I am not sure I want to pursue this issue further since it is a very old model and a one off case.

I appreciate your help on the matter regardless, thank you.