[syslinux] gpxe + SYSLINUX menus = Fail?
Shao Miller
Shao.Miller at yrdsb.edu.on.ca
Tue Mar 16 15:16:56 PDT 2010
Andrew Stuart wrote:
>
> That works as expected. What did you have to change?
>
I tried to reproduce your challenge. I built the gPXE 1.0.0+
10ec8029.rom build target, swapped it in for QEmu's pxe-ne2k_pci.bin
file, ran QEmu.
$ qemu -boot n
Hit Control-B to get the gPXE CLI. From there,
gPXE> dhcp net0
...ok
gPXE> chain http://10.0.2.2/boot/menu.c32 pxelinux.cfg/default
...Initial menu has no LABEL entries!
I looked at the source code and decided to enable debugging by changing
syslinux/com32/MCONFIG's CFLAGS to include -DDEBUG near the
-D__COM32__. Upon re-testing, everything worked as expected. This is
the build you just tested, from Syslinux 3.86-pre1. Now I'm just
looking through the history of the syslinux/com32/menu/ directory
http://git.kernel.org/?p=boot/syslinux/syslinux.git;a=history;f=com32/menu;h=38fb9a714798efcdc00adc2c1e8b3b45bb56e8f7;hb=cdfd4a411a53fc128591c1fe2b93580cf210c1da
I do notice some build warnings in 3.86-pre1, several of which are
related to setjmp/longjmp "clobbering." In this particular instance,
modifying the offending code to include "volatile" did not cure
menu.c32, so I'm not yet sure what will, other than enabling debugging
output...
- Shao Miller
More information about the Syslinux
mailing list