Originally, I had some issues with the 790 being able to boot to the primary hard drive from the fog menu. So I attempted to follow the instructions [URL=‘http://www.fogproject.org/wiki/index.php?title=Boot_looping_and_Chainloading’]here[/URL], because all of the forum posts seem to indicate that was the problem.
I had trouble finding any newer versions of syslinux that even had the chain.c32 file in them. So I used the version listed in that wiki article (4.04).
Ever since making any changes to the /tftpboot/pxelinux.cfg/default file, instead of the vesa menu pulling up like it should, whenever I PXE boot, I wind up at a screen with “boot: _” that just loops.
I have tried restoring the original file. I have rebooted the server to make sure any necessary services have restarted.
I would prefer to get the chainloading working so that I can PXE -> hard disk in my boot order, but getting the PXE menu to work at all at this point would be my primary concern.
I have included a copy of my pxelinux.cfg/default file
[CODE]
DEFAULT vesamenu.c32 MENU TITLE FOG Computer Cloning Solution MENU BACKGROUND
fog/bg.png MENU MASTER PASSWD $1$MqHtEmUa$Q.rjvHGQ1eZ0cRfBI.OIR.
menu color title 1;36;44 #ffffffff #00000000 std
LABEL fog.local
localboot 0
MENU DEFAULT
MENU LABEL Boot from hard disk
TEXT HELP
Boot from the local hard drive.
If you are unsure, select this option.
ENDTEXT[/CODE]
as well as the directory output for the tftp file.
[CODE]
root@SCDFOG01:/tftpboot# ls -la
total 260
drwxr-xr-x 5 fog root 4096 Oct 10 15:48 .
drwxr-xr-x 25 root root 4096 Oct 9 06:56 …
-rw-r–r-- 1 fog root 828 Oct 8 15:08 boot.txt
-rw-r–r-- 1 root root 20704 Oct 10 16:20 chain.c32
drwxr-xr-x 5 fog root 4096 Oct 8 15:08 fog
-rw-r–r-- 1 fog root 25340 Oct 8 15:08 memdisk
-rw-r–r-- 1 fog root 26460 Oct 10 16:20 pxelinux.0
drwxr-xr-x 2 fog root 4096 Oct 10 16:48 pxelinux.cfg
drwxr-xr-x 2 fog root 4096 Oct 8 15:08 tftpboot
-rw-r–r-- 1 fog root 155792 Oct 10 16:20 vesamenu.c32
root@SCDFOG01:/tftpboot#
[/CODE]
And for clarification, the menu (as well as things like registering) were working just fine before trying to configure chainloading.