similar to: UEFI syslinux.efi fails to download ldlinux.e64

On Sat, Oct 3, 2015 at 3:28 AM, Geert Stappers via Syslinux <syslinux at zytor.com> wrote: > On Sat, Oct 03, 2015 at 09:20:10AM +0300, Ady via Syslinux 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

> > > On Wed, Oct 07, 2015 at 05:06:41PM -0500, Clements, James via Syslinux > > wrote: > > > > On Wed, Oct 07, 2015 at 06:01:30PM +0200, Geert Stappers via Syslinux > > wrote: > > > > is for BIOS, not for EFI. So that suggestion can be scraped. > > > > > > > > Which makes > > > > * text which is on the screen of

On Sat, Oct 03, 2015 at 09:20:10AM +0300, Ady via Syslinux 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

> Hello James, > > > ----- Forwarded message from Geert Stappers via Syslinux > <syslinux at zytor.com> ----- > > Date: Thu, 8 Oct 2015 01:24:26 +0200 > From: Geert Stappers via Syslinux <syslinux at zytor.com> > To: "Clements, James" <James.Clements at affiliate.oliverwyman.com> > Cc: "syslinux at zytor.com" <syslinux at

On Tue, Oct 06, 2015 at 10:27:15PM -0400, Gene Cumm 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

On Wed, Oct 7, 2015 at 6:17 AM, Ashish, Shivendra <shivendra.ashish at hpe.com> wrote: > Gene, > > I have tested the binaries provided, it worked for me on DL380 Gen9. > I'm going to test this comprehensively in many different hardware and VM platforms. > I will get back in case I face any issue. > > Thanks a lot. I already found a regression that affects a rather

> -----Original Message----- > From: Gene Cumm [mailto:gene.cumm at gmail.com] > Sent: Wednesday, October 07, 2015 4:43 PM > To: For discussion of Syslinux and tftp-hpa; Geert Stappers > Subject: Re: [syslinux] UEFI: Failed to load ldlinux.e64/ldlinux.e32 > > On Wed, Oct 7, 2015 at 6:27 AM, Gene Cumm <gene.cumm at gmail.com> wrote: >> On Wed, Oct 7, 2015 at 2:33

On Wed, Oct 07, 2015 at 05:58:51PM -0500, Clements, James wrote: > James Clement > > Geert Stappers > > > On Wed, Oct 07, 2015 at 05:06:41PM -0500, Clements, James wrote: > > > > The screen displays the following: > > > > > > > > PXE Network Boot using IPv4 > > > > .... > > > > Station IP address is 192.168.205.50

On Wed, Oct 07, 2015 at 08:55:53AM -0500, Clements, James wrote: > On Wed, Oct 07, 2015 Geert Stappers wrote > > On Wed, Oct 07, 2015 at 01:58:51PM +0200, James Clements via Syslinux > > > On Wed, Oct 07, 2015 at 07:21:28AM -0400, Gene Cumm via Syslinux wrote: > > > > > > > > http://www.syslinux.org/archives/2015-October/024375.html

This works! Fixes my issue I have been having with the DL160s 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

> 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

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

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). > > > >

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

Gene and co, Now my pxelinux efi 64 boot is properly loading syslinux.efi (via TFTP) It then issues a TFTP file request for efi.x64/pxelinux.cfg/ldlinux.e64. (All my efi x64 content is under efi.x64/pxelinux.cfg). However, I see that it fails to properly negotiate the TFTP options with my TFTP server. so it never transfers ldlinux.e64 over. In its file request packet, it asks for these TFTP

On Wed, Oct 7, 2015 at 2:33 AM, Geert Stappers <stappers at stappers.nl> wrote: > On Tue, Oct 06, 2015 at 10:27:15PM -0400, Gene Cumm 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

H Peter, I notice the Intel Boot Agent (in the BOOT ROM) takes a different approach. When TFTP loading the initial syslinux.efi. It receives the OACK with both options set -- tsize (of 145744) and blksize (of 1408). Apparently it has challenges parsing this "two option" OACK packet. But it remembers the tsize of 145744. So it issues another read request, this time requesting only a

> On Wed, Oct 07, 2015 at 05:06:41PM -0500, Clements, James via Syslinux > wrote: > > > On Wed, Oct 07, 2015 at 06:01:30PM +0200, Geert Stappers via Syslinux > wrote: > > > is for BIOS, not for EFI. So that suggestion can be scraped. > > > > > > Which makes > > > * text which is on the screen of the netbooting (virtual) machine > > >

Phil, I gave a presentation last month on how to set up a DHCP + TFTP server. Using syslinux 6.03-pre* to support both Legacy and EFI PXE boot. Here's the link to the presentation. My slides are there. http://2014.texaslinuxfest.org/content/creating-legacy-efi-pxe-server-using-pxelinux The presentation models a small lab-sized env. I start simple; supporting legacy PXE boot only. Then

I see that there seems to be patches being accepted... Please consider committing these two: You should be able to cherry pick them from my syslinux repo at http://github.com/ppokorny/syslinux I would think? commit 64fb71b87a625d70ea8c6127f18fe96d3f4fdc89 Author: Philip Pokorny <ppokorny at penguincomputing.com> Date: Sun Mar 5 21:07:48 2017 -0800 Fix PATH parsing to match the