search for: sl390

...ux.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.c...

...ipt, 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). Quiet unfortunate. I'm presuming you tried the lpxelinux.0 test binary? > 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...

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