New latitude E7400. No internal NIC, Boot to USB-C Puck NIC. Gets IP from DHCP but does not connect to Fog.
I have a new Dell Latitude 7400 that does not have an internal NIC. I bought the DA300z puck that has the NIC in it. I’ve configured in the BIOS to boot to USB devices. It comes up with IPv4 as a choice. when selected it gets an IP from dhcp but then goes to press F1 to try reboot press F2 to reboot into setup, etc.
All my other devices boot and image fine.
Any help would be greatly appreciated
Diablo909 last edited by
I’m having a similar issue… What’s the best manner to turn on DCHP on my fog server after i’ve already installed it?
We have since updated our FOG DHCP boot file to ipxe.efi
FWIW: If the fog server IS your dhcp server for imaging and you had FOG install and configure the dhcp server, it should automatically manage the right boot file based on the pxe booting computer. You should not have to change anything. If you have a MS Windows dhcp server then there are somethings you can do to make it dynamic.
chris.lynn last edited by
Thank you for the quick reply! Sorry to get back to you so late here.
We were not configured for UEFI in our environment.
We have since updated our FOG DHCP boot file to ipxe.efi. Changes have been made by our Network Engineer and we are now seeing the Fog Project selection page where we can register host, deploy an image, etc.
Thank you for your guidance!
@chris-lynn There are many variables here. I can say after working with the 7400s for a bit I’ve learned their nuances. I can get a 7400 to pxe boot without issue. With both the dock and the dell usb c dongle.
Advanced boot options-> Enable uefi network stack
thunderbolt adapter turn on the 3 check boxes at the top and then set security to no security.
Secure boot disabled
Now from an infrastructure standpoint, do you already have uefi systems in your environment? How do you manage the boot file differences between bios and uefi?
chris.lynn last edited by
I have a Dell Latitude 5400 model that is new for us. I would like to get this image captured to Fog. Currently getting Onboard NIC IPV4 with the same result as the pictures from Jun 26th at 4:03pm. Were there any updates to this?
Does the USB-C type adapter resolve the PXE issue?
I just received a 7400 2-in-1 today that I was able to get into the FOG menu by using one of these:
@buercky FWIW: My guys just unpacked our order of 7400s. They would not pxe boot with the supplied K20A docks, but we were able to get them to pxe boot with the older K17A docks (which I thought were called WD10 usb-c dock at one point).
As far as we can tell there is no legacy (bios) mode on these systems, so its UEFI all the way.
@buercky Awesome! Glad to hear it’s working now.
You rock! that was it!
Thank You for all the help!
@buercky Fairly sure @jflippen is spot on here. In your screenshot we see “066 Boot Server Host Name” for UEFI being
ipxe.efi. The BIOS is not able to use that information to connect to the TFTP on your FOG server! Therefore the “PXE-E99: Unexpected network error”!
@buercky So, I see one thing in your screenshot that concerns me… you have two option 66 with one as the ipxe.efi instead of your server IP. Here’s what my DHCP options look like after applying the options from the guide:
@Sebastian-Roth here is a screen shot of the error. it gives the station IP address then the DHCP Server IP address then the error
@jflippen This is what i have in my DHCP. yes i believe that is the doc i followed to set it up
Boot server host name is the IP address of my fog server
@buercky This is probably a dumb question but your boot file is set to ipxe.efi, right?
We have our DHCP dishing out different boot files using these settings:
@buercky Can you take a video of the PXE boot. Make sure you rest the camera on a pile of books to get a steady picture and some smartphones can even do slow motion videos. That’d be great. I suspect we see a message between when it get’s the IP and skips booting that might give is a hint on what’s going wrong.
@george1421 I tried the NIC dongle no luck. It does pull an IP address This is what i get.
then it gives me an IP address. Then this
I’ve tried about every combination in BIOS
AHCI not Raid
Enable usb boot support
Enable External USB Support
Enable Thunderbolt Boot Support
Enable Thunderbolt (and PCIe behind TBT) Pre-boot modules checked and unchecked
secure boot disabled
Secure Boot mode- tried both Deploy and Audit
FOG Server Info Ver. 1.5.5 Kernel 4.19.48
Other systems image just fine
@buercky I just ordered some 7400s, they should be here by 15-Jul. I plan on testing them with the WD15 usb-c docks. From what I understand there is a few bios settings you need to make to allow these 7400s to pxe boot.
@jflippen I’m ordering one and I will find out tomorrow when it comes in. Thanks for the tip
Is this a 7400 or a E7400? I assume the 1st option since you said the device is new. I just received a 7400 2-in-1 today that I was able to get into the FOG menu by using one of these:
I had to enable booting through thunderbolt to use this. It may be possible that you can only pxe boot with the one I listed. I know we had trouble with some USB-C Precision laptops that had to use the adapter above. Then there is Microsoft and their surface. Also, mine had an nvme ssd that I had to switch from raid to ahci to get FOG to see the hard drive.
I am using 1.5.6 and bzImage Version: 4.19.48.
when selected it gets an IP from dhcp but then goes to press F1
This part confuses me then. If its getting an IP address it should then transfer the file. Is this laptop in bios (legacy) or uefi mode?