Syslinux - Sep 2015 - Chaining to pxelinux.0 6.0.3 from iPXE - ldlinux.c32

On 9/21/2015 5:44 PM, Gene Cumm wrote:
> On Mon, Sep 21, 2015 at 6:23 PM, Alan Sparks via Syslinux
>> With pxelinux 3.8.6 (or, < 5.x), I was able to chain boot pxelinux.0
>> from ipxe, having set appropriate values for DHCP options 210 and 209
>> for the remote file path and the config file.  This doesn't work
with 6.0.3.
> 
> I thought I recall a newer commit working nicely.
> 
> If you need test binaries, please let me know.
> 
Newer than .0.3 stable?  I would really like to get the test binaries,
if you can forward me a link.   I can't get it to "just work," on
several different types of physical hardware, or KVM instances booting
kvm-ipxe.   Thanks.

> On 9/21/2015 5:44 PM, Gene Cumm wrote:
> > On Mon, Sep 21, 2015 at 6:23 PM, Alan Sparks via Syslinux
> >> With pxelinux 3.8.6 (or, < 5.x), I was able to chain boot
pxelinux.0
> >> from ipxe, having set appropriate values for DHCP options 210 and
209
> >> for the remote file path and the config file.  This doesn't
work with 6.0.3.
> > 
> > I thought I recall a newer commit working nicely.
> > 
> > If you need test binaries, please let me know.
> > 
> 
> Newer than .0.3 stable?  I would really like to get the test binaries,
> if you can forward me a link.   I can't get it to "just
work," on
> several different types of physical hardware, or KVM instances booting
> kvm-ipxe.   Thanks.
> 
> 
 
There are no official binaries for testing yet. Gene is offering to 
build binaries for you to test (and, I would add, to report back with 
feedback).

Regarding KVM, some users reported some problems when testing Syslinux 
6.03, but the result might also depend on how the binary files were 
built (e.g. which versions of gcc and/or nasm).

Just to be clear, are you using official binaries of version 6.03? Or 
are you building your own? If the latter, from which source code, 
exactly?

For those building their own binaries, building 6.03 (and/or current 
git HEAD) has been known to have some issues when building with gcc 5+. 
Also NASM 2.11.6 has some bug and building Syslinux with it will fail, 
so it is recommended to avoid such version.

If relevant for you, see also 
http://www.syslinux.org/wiki/index.php/Development 

Regards,
Ady.
> _______________________________________________
> Syslinux mailing list
> Submissions to Syslinux at zytor.com
> Unsubscribe or set options at:
> http://www.zytor.com/mailman/listinfo/syslinux
>

On Mon, Sep 21, 2015 at 8:02 PM, Alan Sparks <asparks at doublesparks.net>
wrote:
> On 9/21/2015 5:44 PM, Gene Cumm wrote:
>> On Mon, Sep 21, 2015 at 6:23 PM, Alan Sparks via Syslinux
>>> With pxelinux 3.8.6 (or, < 5.x), I was able to chain boot
pxelinux.0
>>> from ipxe, having set appropriate values for DHCP options 210 and
209
>>> for the remote file path and the config file.  This doesn't
work with 6.0.3.
>>
>> I thought I recall a newer commit working nicely.
>>
>> If you need test binaries, please let me know.
>>
>
> Newer than .0.3 stable?  I would really like to get the test binaries,
> if you can forward me a link.   I can't get it to "just
work," on
> several different types of physical hardware, or KVM instances booting
> kvm-ipxe.   Thanks.
Test binaries.  There has not been an official pre-release or release
since 6.03 however there has been quite a bit of development and I
have published test binaries in order to ask for feedback and to be
consistent.  The first is the ones you'll want.  The second is for
anyone wanting to test EFI on x86-64 (aka x64).

https://sites.google.com/site/genecsyslinux/sl604p0g15-bios.tgz?attredirects=0&d=1
https://sites.google.com/site/genecsyslinux/sl604p0g15-x64.tgz?attredirects=0&d=1

-- 
-Gene

On 9/22/2015 4:33 AM, Gene Cumm wrote:
> 
>
https://sites.google.com/site/genecsyslinux/sl604p0g15-bios.tgz?attredirects=0&d=1
>
https://sites.google.com/site/genecsyslinux/sl604p0g15-x64.tgz?attredirects=0&d=1
> 
Tried these new binaries this morning.   No change, still will not
attempt to load ldlinux.c32.

As a context, what I'm really trying to do is get a newer version of
menu.c32 that doesn't hang in some of my customers' contexts -
they're
creating KVM/QEMU instances with no graphics, just text console, and for
them menu.c32 is printing exactly the first character of the text menu,
then hanging.   The menu.c32 in 6.0.3 doesn't seem to cause that...

But upgrading the pxelinux binaries - I forgot to mention, am running
the official binaries - will not attempt to load ldlinux.c32.   On my
ipxe script, I set the 210 and 209 options (see below) as works for 4.x
and 3.x, I see the Web server log the hit for pxelinux.0, but never for
ldlinux.c32.

I did try lpxelinux.0 - this does work (with an odd delay) for the
KVM/QEMU instance - but hangs on my hardware test of an HP SL390 with a
Mellanox 10G NIC (older pxelinux.0 versions do work on that).

Any advice on any other debugging, strategies?   Or how I can just fix
the older menu.c32 to work around the above issue and forget the 6.x
upgrade?
-Alan

===============# set up pxelinux boot:
# 209: the URL of the pxelinux.cfg
set 209:string
http://{{site}}/ipxe/menu.cfg?uuid=${uuid}&mac=${netX/mac}&serial=${serial}
# 210: root URL where pxelinux will get files
set 210:string http://{{site}}/tftpboot/bios.604/
set filename ${210:string}pxelinux.0
chain ${filename} ||
#kernel ${210:string}/pxelinux.0

#boot