Posts made by swhite

@Sebastian-Roth I took over for dbridges on this issue. Last I heard Tom wanted me to call him but I wasn’t sure how so I sent him a chat with my info. I am available Monday - Friday 9:00 am to 6:00 pm if someone would like to chat.

Sure thing. I am about to leave the office but I will be back Tuesday at 9:00 am EST. Just let me know what time is good for you.

I renamed my file to ipxe.pxe.old and added the new one from the link provided. When I attempted to boot the computer it hung in the same spot. Just with a little more info on the screen.

I currently have it set to ipxe.pxe but I have tried all of the files listed below in my earlier post. I am not sure what you mean about what mode they are in unless you are asking if I am using the legacy boot options instead of UEFI. If so yes I am legacy booting. Also it is not getting past the iPXE Initializing Devices so I did not think I was at the point where the boot kernel would matter.

Yes I have option 67 set. All of my other machines work just fine with fog. Only the HP Compaq Pro 4300 are having issues.

Basically I tried everything under the tftpboot directory.

ipxe.pxe
default.ipxe
ipxe.kkpxe
ipxe.kpxe
ipxe.krn
ipxe.pxe
snponly.efi
undionly.kkpxe
undionly.kpxe
undionly.kpxe.INTEL
undionly.pxe
vesamenu.c32

Hi Tom,

I work with the original poster and took over on this issue since he did not have the necessary rights to change the settings necessary. I took your advice and tried changing from the undionly.kpxe file, however, none of them would work. In fact the only way we could get the system to boot any further was to use the old pxelinux.0 but I get an unable to load configuration file error. Any advice on this issue?

@UCJared @Sebastian-Roth
I was able to get my ProDesk 600 G2 to upload using the Kernel - 4.1.2 TomElliott.

@Sebastian-Roth Hi Sebastian,
The NIC on my ProDesk is listed as Intel I219-LM and the hardware ID is PCI\VEN_8086&DEV_15B7&SUBSYS_805D103C&REV_31

I am running Fog 1.2.0 with kernel version 3.15.6

@UCJared Did you ever find an solution to this issue? I am having the same problem with the ProDesk.