[syslinux] PXELINUX and http?

Gene Cumm gene.cumm at gmail.com
Wed Mar 5 11:49:44 PST 2014


On Wed, Mar 5, 2014 at 12:40 PM, Virtual Xmas <luvs.christmas at gmail.com> wrote:
> On 3/5/2014 4:21 AM, Gene Cumm wrote:
>> tp.  But I can't get it to work.

>> 5.10 introduced lpxelinux.0, a variant that uses UNDI+lwIP instead of PXE
>> calls.

> Ah, ok, the wording in 5.10 change log is a little ambiguous then...It seems
> to imply (to me at least) that http support was added to pxelinux.0 with an
> old TCP stack, but lpxelinux.0 has http with a new TCP stack.

>>> I am using syslinux 6.03pre-6, but get the same errors with 6.02.
>>
>> Thanks for testing the latest pre-release.  If there's a bug here,
>> this is the best to test with.
>>
>> For starters, you should see more.  If you haven't used any 5.xx+
>> version before, please ensure you have lib*.c32 copied to the same
>> location as [l]pxelinux.0 ldlinux.c32 and (vesa)menu.c32.  This will
>> likely resolve your issue.

> This is the script I use to update the pxelinux files in /tftpboot....Am I
> missing anything?
> #!/bin/bash
>
> T=/tftpboot
>
> cp bios/core/pxelinux.0 ${T}
> cp bios/core/lpxelinux.0 ${T}
> cp bios/com32/modules/linux.c32 ${T}
> cp bios/com32/lib/libcom32.c32 ${T}
> cp bios/com32/libutil/libutil.c32 ${T}
> cp bios/com32/cmenu/libmenu/libmenu.c32 ${T}
> cp bios/com32/gpllib/libgpl.c32 ${T}
> cp bios/com32/elflink/ldlinux/ldlinux.c32 ${T}
> cp bios/com32/hdt/hdt.c32 ${T}
> cp bios/memdisk/memdisk ${T}
> cp bios/com32/mboot/mboot.c32 ${T}
> cp bios/com32/menu/vesamenu.c32 ${T}/pxelinux.cfg

Should be good.

> If I boot to pxelinux.0 I get my menu.  If I change my boot-file to
> lpxelinux.0, I just get the boot: prompt after lpxelinux.0 loads. Network

Any other output on the screen?

> tracings shows lpxelinux.0 attempting to search for the menu files(via
> tftp), but something seems to be broken in that it's not picking one up.  I
> have both a default and a 01-mac-address file for this client, and it's
> loading neither one (pxelinux.0 is loading the 01-mac-address one).

If you get a "boot: " prompt, it must have some config.

> If I specify my menu file over HTTP with DHCP options 209 and 210, I get the
> menu.  And network tracing shows all the .c32 files and everything else
> coming over http at that point....

Awesome.  So it's just with the TFTP code.  Good job on narrowing that down.

-- 
-Gene


More information about the Syslinux mailing list