Geert Stappers
2015-Oct-03 06:36 UTC
[syslinux] UEFI: Failed to load ldlinux.e64/ldlinux.e32
On Fri, Oct 02, 2015 at 01:46:19PM -0700, Derrick M via Syslinux wrote:> On Fri, Oct 2, 2015 at 4:07 AM, Gene Cumm <gene.cumm at gmail.com> wrote: > > > I have a patch that I think may help your situation of syslinux.efi > > being unable to load ldlinux.e64/ldlinux.e32 (though I don't know if > > any of you are using an EFI ia32 platform). > > > > The basics are that we try to enable UseDefaultAddress as it helps > > certain clients with routing and works on numerous other clients. If > > we timeout on receiving a packet and have never received any packets, > > disable UseDefaultAddress and set the addresses manually. > > > > > > git://github.com/geneC/syslinux.git > > https://github.com/geneC/syslinux.git > > > > Branch 1efipxe > > > > > > My test x86-64 binaries: > > > > https://sites.google.com/site/genecsyslinux/sl604p0g17-x64.tgz?attredirects=0&d=1 > > > > This works! Fixes my issue I have been having with the DL160s >Thanks for reporting. Where is message is mostly to recover the original To: ( Hi Oscar @ Bright Computing ) Some questions: * Tested with the downloaded binary? * If self build, in which environment? * any of you are using an EFI ia32 platform? Groeten Geert Stappers Still some what worried about 64bit versus 32bit build environments as raised in previous discussion. E.g. http://www.syslinux.org/archives/2015-September/024185.html -- Leven en laten leven
On Sat, Oct 3, 2015 at 2:36 AM, Geert Stappers <stappers at stappers.nl> wrote:> On Fri, Oct 02, 2015 at 01:46:19PM -0700, Derrick M via Syslinux wrote: >> On Fri, Oct 2, 2015 at 4:07 AM, Gene Cumm <gene.cumm at gmail.com> wrote: >> >> > I have a patch that I think may help your situation of syslinux.efi >> > being unable to load ldlinux.e64/ldlinux.e32 (though I don't know if >> > any of you are using an EFI ia32 platform). >> > >> > The basics are that we try to enable UseDefaultAddress as it helps >> > certain clients with routing and works on numerous other clients. If >> > we timeout on receiving a packet and have never received any packets, >> > disable UseDefaultAddress and set the addresses manually. >> > >> > >> > git://github.com/geneC/syslinux.git >> > https://github.com/geneC/syslinux.git >> > >> > Branch 1efipxe >> > >> > >> > My test x86-64 binaries: >> > >> > https://sites.google.com/site/genecsyslinux/sl604p0g17-x64.tgz?attredirects=0&d=1 >> > >> >> This works! Fixes my issue I have been having with the DL160s >> > > Thanks for reporting. > > Where is message is mostly to recover the original To: ( Hi Oscar @ Bright Computing ) > > Some questions: > > * Tested with the downloaded binary? > * If self build, in which environment? > * any of you are using an EFI ia32 platform?Also, could you try to test HTTP transfer? I've only patched the UDP code for now. -- -Gene
On 10/3/2015 5:58 AM, Gene Cumm via Syslinux wrote:> On Sat, Oct 3, 2015 at 2:36 AM, Geert Stappers <stappers at stappers.nl> wrote: >> On Fri, Oct 02, 2015 at 01:46:19PM -0700, Derrick M via Syslinux wrote: >>> On Fri, Oct 2, 2015 at 4:07 AM, Gene Cumm <gene.cumm at gmail.com> wrote: >>> >>>> I have a patch that I think may help your situation of syslinux.efi >>>> being unable to load ldlinux.e64/ldlinux.e32 (though I don't know if >>>> any of you are using an EFI ia32 platform). >>>> >>>> >>>> git://github.com/geneC/syslinux.git >>>> https://github.com/geneC/syslinux.git >>>> >>>> Branch 1efipxe> > Also, could you try to test HTTP transfer? I've only patched the UDP > code for now. >Didn't see you get any feedback on this. I've tested the HTTP URLs with this test binary, and they worked. Significantly faster than with the equivalent TFTP transfer, in fact. -Alan
Back in 2013 time frame, as in the thread: http://www.syslinux.org/archives/2013-August/020655.html For doing a local disk boot on EFI systems, the "localboot -1" command was suggested, to force the system to fail to the (as I understand) next item in the boot order (hopefully the hard disk). I've seen some issues with this in preliminary testing, specifically around whether the boot order had network first or disk first; and if the system was set to a one-time boot from network. In this case, I saw syslinux (6.03) go into a boot loop, just going back to the syslinux menu. Are there any more recent thoughts about the best way to handle local disk boots from EFI syslinux PXE? Thanks in advance. -Aan