@***Redbob in the file /tftpboot/default.ipxe
edit it with a text editor like nano or vi

@Wayne-Workman a couple minor corrections. the last official release to capture using partimage was 0.32, i think. images have always been gzip compressed. between 1.2 and 1.3 the program for decompressing was switched to pigz. pigz is a parallel (multi-threading) implementation of gzip compression, which sped it up a bit.

@bertalanimre first off, i think you may have a misunderstanding of what fog is. fog isn’t used for “installing” operating systems. it’s for deploying pre-configured images of systems. you install your system to a computer, configure it the way you want, then capture it with fog. then you can deploy that image to other systems.

with that out of the way, have you set your DHCP 66/67 options?

@bertalanimre that doesn’t look correct. options 66 and 67 aren’t just things you have to enable, they’re configured. dnsmasq calls these options next-server and filename, i believe.
try adding this line to your config

dhcp-boot=undionly.kpxe,,<fog_server_IP>

@rwakc well, it would be technically possible to set up a method where you could be automatically imaging any device pxe booted from the network, and set up multiple dhcp scopes on different network ports, serving out different pxe boot files with embedded scripts. that way, you’d be able to choose what image the system gets imaged with by choosing what network you plug the device into.

@vascomorais fog configuration > ipxe general configuration > advanced menu settings
there should be a text box at the “Advanced menu command” line

@PITSKing fog pulls that information from the database, not the files. if you recreate the “profiles” for the images and point them to the existing files, they should work.

is the drive encrypted?

@Beyondlimitation the version of dnsmasq you’re running is old. old versions only allowed .0 to be on the tail end of a file name

https://serverfault.com/questions/882554/when-configuring-dnsmasq-for-pxe-booting-why-do-i-need-to-change-undionly-kpxe/882697#882697

@george1421 one option for eliminating the network card as the source of the problem (not completely, but mostly) is to boot with a usb adapter plugged in as well, both plugged into the network, and after ipxe loads unplug the network from the built in adapter.

@THEMCV You need to update a FOG Configuration->Fog Settings parameter->TFTP Server->KERNEL RAMDISK SIZE set it to 275000 from the original value of 127000

@THEMCV to be honest, i’m not sure. i haven’t been involved much between the new kernel size being experimental to it being in production. i just recognized the problem.