Alan Sparks
2015-Sep-21 22:23 UTC
[syslinux] Chaining to pxelinux.0 6.0.3 from iPXE - ldlinux.c32
If this is asked before, please point me at the answer, can't find it... 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. With 6.0.3, this throws the "failed to load ldconfig.c32" error now. The files are in the right places, right versions. If I disable iPXE and just use TFTP to boot from same location, it loads fine. I see from logs that no attempt is made to load ldlinux.c32 from ipxe, via HTTP or even TFTP. Have tried combinations of preloading ldlinux.c32 in the ipxe script, changing order of loads, etc, but never get past this. Can anyone school me on how to get this to work in the new order of things? Do I have to load ldlinux.c32 myself (and maybe other modules), and if so, how can I get pxelinux to see they're loaded? Thanks in advance for any advice or redirects. -Alan
Gene Cumm
2015-Sep-21 23:44 UTC
[syslinux] Chaining to pxelinux.0 6.0.3 from iPXE - ldlinux.c32
On Mon, Sep 21, 2015 at 6:23 PM, Alan Sparks via Syslinux <syslinux at zytor.com> wrote:> If this is asked before, please point me at the answer, can't find it...I seem to recall seeing this before.> 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. Just tested from a 1 year old ipxe.iso and it just worked.> With 6.0.3, this throws the "failed to load ldconfig.c32" error now. > The files are in the right places, right versions. If I disable iPXE > and just use TFTP to boot from same location, it loads fine. > > I see from logs that no attempt is made to load ldlinux.c32 from ipxe, > via HTTP or even TFTP. Have tried combinations of preloading > ldlinux.c32 in the ipxe script, changing order of loads, etc, but never > get past this. > > Can anyone school me on how to get this to work in the new order of > things? Do I have to load ldlinux.c32 myself (and maybe other modules), > and if so, how can I get pxelinux to see they're loaded?No, you can't load it yourself. It isn't a Linux kernel.> Thanks in advance for any advice or redirects. > -AlanIf you need test binaries, please let me know. -- -Gene
Alan Sparks
2015-Sep-22 00:02 UTC
[syslinux] 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.
Possibly Parallel Threads
- Chaining to pxelinux.0 6.0.3 from iPXE - ldlinux.c32
- Chaining to pxelinux.0 6.0.3 from iPXE - ldlinux.c32
- Chaining to pxelinux.0 6.0.3 from iPXE - ldlinux.c32
- Chaining to pxelinux.0 6.0.3 from iPXE - ldlinux.c32
- Chaining to pxelinux.0 6.0.3 from iPXE - ldlinux.c32