@dbrilliant Can’t see what your post has to do with the original indeed very old topic. We have enough room in our forums for everyone to open fresh specific topics and I ask you to do so. Tell us about your setup, FOG version, OS and so on…
@Steve_BBA You did find one of the limitations with memdisk, in that the iso image has to fit in the 32 bit address space and have enough space left over to run what ever kernels is on the iso image. The other limitation you will have with memdisk is that its bios mode only. There isn’t an equivalent boot environment for uefi AFAIK.
But well done getting it worked out.
From your initial error message was that it can’t find the initrd to boot from. This is me just guessing but I don’t see a kernel parameter in the imgargs that points to your initrd image. Also be aware that the format you used in your initial post isn’t sufficient for uefi booting. You need to use the -n <file_name> option for each line.
ref: https://forums.fogproject.org/topic/10944/using-fog-to-pxe-boot-into-your-favorite-installer-images/10
@george1421 Have you followed the link I attached and tried the process of creating the USB? I made numerous attempts at creating a USB that allowed Macs to PXE boot. But here’s what I ended up having to change on the iPXE.iso taken from the iPXE website.
First I was able to open the iPXE.iso with winrar, then I logged onto my fog server and went to the /tftpboot folder. I then copied the IPXE.krn, and replaced the existing one on the iso. For whatever reason, the fog’s /tftpboot folder had a newer version of the file which allowed my devices to correctly boot.
The link I attached has the iso with the changes I made attached as well as the steps for creating a bootable usb for it.
@george1421 OK this problem is making my head explode.
In your main pxe boot server, I assume you have a menu entry that points to the FOG server. The issue we have is we need to replace the in memory iPXE kernel with the FOG iPXE kernels (like what you did when you changed the dhcp option 66 and 67).
So in your main pxe boot server for the menu entry for FOG see if this replaces iPXE with FOG’s iPXE.
:call_fog
set next-server <fog_server_ip>
iseq ${platform} efi && set filename ipxe.efi || set filename undionly.kpxe
chain tftp://${next-server}/${filename}
That should chain load the fog iPXE kernel. There is an embedded script in the FOG iPXE kernel here: https://github.com/FOGProject/fogproject/blob/master/src/ipxe/src/ipxescript
Its a generic script, the only thing we have to pay attention to is line 29.
chain tftp://${next-server}/default.ipxe ||
What that script will do is again acquire the pxe boot server {next-server} from dhcp, which will point back to your main pxe boot server, but ignores dhcp option 67 and calls default.ipxe. On your main dhcp server you need to create a new text file called default.ipxe and in it place this script
#!ipxe
chain tftp://<fog_server_ip>/default.ipxe
That should call the fog based ipxe boot script, you will be running under the FOG iPXE kernel done by the fist chain, and the second chain will jump you into the FOG iPXE menu.
Will it work?? Maybe /maybe not but it sounds good on paper.
