[syslinux] Chaining to pxelinux.0 6.0.3 from iPXE - ldlinux.c32

Alan Sparks asparks at doublesparks.net
Thu Sep 24 07:03:46 PDT 2015

On 9/24/2015 4:33 AM, Gene Cumm wrote:
> On Wed, Sep 23, 2015 at 5:43 PM, Alan Sparks via Syslinux
> <syslinux at zytor.com> wrote:
> Although it means another round of testing, you could also consider
> lpxelinux.0 which can support HTTP URLs on its own and probably
> interacts differently with iPXE.  I am curious about a quantifiable
> description of "an odd delay".

think I mentioned testing lpxelinux in previous response... It did work
better (e.g. work period) in the KVM instance.   It however hung for a
couple of minutes on the Mellanox (hardware) ipxe setup (HP hardware),
before the machine just reset.   Not sure why lpxelinux wouldn't work on
the hardware instance.   I didn't measure the delay, but just sort of
added 5 seconds to the period between pxelinux banner and menu display...

> "DEFAULT menu.c32" is not a good habit.  DEFAULT should point to a
> real label and you should use the UI directive to call menu.c32 at
> start  ( "UI menu.c32" ), introduced in 3.74.

Granted.   Old people have deep habits.   I had swapped it out for UI
for testing, to no betterment.

> Now I have something I can reproduce.  Booting my same ipxe.iso to
> perform an initial TFTP load shows what I saw already.  Attempting to
> load a file via http results in an immediate error message with no
> resulting traffic as far as I can see.

Very positive development...

More information about the Syslinux mailing list