similar to: facing problem with UEFI pxe boot with syslinux 6.03

Gene wrote: > On Wed, Oct 7, 2015 at 7:58 AM, Ashish, Shivendra <shivendra.ashish at hpe.com> wrote: >> Still getting error >> >> Disable uderdefault address > > 1) I'm presuming this is actually "disable UseDefaultAddress" > >> Core_udp_sento: udp->configure unsuccessful >> >> This message lopping in console > > Not

On Wed, Oct 7, 2015 at 6:09 PM, Gene Cumm <gene.cumm at gmail.com> wrote: >> -----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

I'm setting up UEFI booting and got to the point of having the system talk to the dhcpd/tftpd server, grab the first image files (syslinux.efi) and then continuously request the secondary image file (ldlinux.e64). I'm wondering if I'm missing something or if someone can point me in the right direction of trouble shooting this. The tftp root has all the files to boot a BIOS type

On Thu, Jun 19, 2014 at 2:51 PM, Andrew Rae <A.M.Rae at leeds.ac.uk> wrote: > Hi all, > > wasnt sure whether this was the best place to put this information; but something seems to have gone 'backwards' in the later pre-releases of 6.03 regarding network booting. I'd say this is an excellent place to start. I'm getting some similar results here with the precompiled

> Hi all, > > wasnt sure whether this was the best place to put this information; but something seems to have gone 'backwards' in the later pre-releases of 6.03 regarding network booting. > > below are results of me testing - i did each a few times to make sure they are valid results. > > hope it helps identify something that's gone awry ? > so far, 6.03

Gene Cumm wrote: > >> My test x86-64 binaries: > >> > >> https://sites.google.com/site/genecsyslinux/sl604p0g17-x64.tgz?attredirects=0&d=1 > > On Fri, Oct 2, 2015 at 4:46 PM, Derrick M <derrick.martinez at gmail.com> wrote: > > This works! Fixes my issue I have been having with the DL160s > > Further testing, preferably of the above binaries,

I've found a problem, and I think it is in syslinux (specifically when it tries to load ldlinux.e64 under hyper-V). I have a physical computer with a Gigabyte GA-P85-D3 motherboard that successfully pxeboots using the EFI images, and I hold that up as exhibit 1 that my deployment environment works. It also implies that the syslinux.efi image works in some cases, but not in all. My Hyper-V

Hi all, wasnt sure whether this was the best place to put this information; but something seems to have gone 'backwards' in the later pre-releases of 6.03 regarding network booting. below are results of me testing - i did each a few times to make sure they are valid results. hope it helps identify something that's gone awry ? so far, 6.03 pre11 and pre13 (excluding efi32) seem most

On 2014?03?07? 18:24, Ady wrote: > Hi Steven, > > Perhaps this could be of some basic sample/help, being based on > Debian: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720589 > > where: > _ if gpxelinux.0 is needed, it should probably be replaced by ipxe. > _ lpxelinux.0 (from official Syslinux archive) could optionally be > added. > > _ from the

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

On Oct 11, 2015 1:26 AM, "Michael Glasgow" <glasgow at beer.net> wrote: > > Gene Cumm wrote: > > >> My test x86-64 binaries: > > >> > > >> https://sites.google.com/site/genecsyslinux/sl604p0g17-x64.tgz?attredirects=0&d=1 > > > > On Fri, Oct 2, 2015 at 4:46 PM, Derrick M <derrick.martinez at gmail.com> wrote: > >

On 7/1/2015 12:00 PM, Nelson, Ryan M. (ARC-TI)[SGT, INC] via Syslinux wrote: >>> I'm setting up UEFI booting and got to the point of having the >>> system talk >>> >to the dhcpd/tftpd server, grab the first image files >>> (syslinux.efi) and >>> >then continuously request the secondary image file (ldlinux.e64). >> So it appears to go

On Wed, Oct 07, 2015 at 01:58:51PM +0200, James Clements via Syslinux wrote: > On Wed, Oct 07, 2015 at 07:21:28AM -0400, Gene Cumm via Syslinux wrote: > > On Wed, Oct 7, 2015 at 6:40 AM, Clements, James via Syslinux wrote: > > > Hi, > > > > > > I am using a Windows Server 2012 R2 Hyper-V Generation 2 VM as a > > > PXE client (no physical machines

(SNIP) > > 6.03-pre11 EFI64: fails - gets stuck in a loop downloading files - > > differs each boot > > 6.03-pre12 EFI64: fails - downloads /pxelinux.e64 & /ldlinux.e64 - > > then continually retries to download ldlinux.e64 > > 6.03-pre13 EFI64: boots OK TFTP & HTTP > > 6.03-pre14 EFI64: fails - downloads /pxelinux.e64 & /ldlinux.e64 - > > then

> On Wed, Oct 07, 2015 at 01:58:51PM +0200, James Clements via Syslinux > wrote: > > On Wed, Oct 07, 2015 at 07:21:28AM -0400, Gene Cumm via Syslinux wrote: > > > On Wed, Oct 7, 2015 at 6:40 AM, Clements, James via Syslinux wrote: > > > > Hi, > > > > > > > > I am using a Windows Server 2012 R2 Hyper-V Generation 2 VM as a > > > >

Hi good day, can anybody please assist me to get PXE booting with syslinux, and EFI systems. PXE EFI Architecture-7 (64bit)? What I have tried: 1) Syslinux 6.03 -> Looks like a bug -> does not work because syslinux.efi tries to download ldlinux.e64 but from the DHCP server, in stead of the PXE boot server (the server that provided "option 60" and the boot file

>>According to prior pcap reports, syslinux.efi searches for syslinux.cfg (too), while (l)pxelinux.0 will be searching for "default". >This means that using something *similar* to: >> pxelinux.cfg/default: >> PATH bios >> CONFIG common-config.cfg ::bios >> # the bios modules should be located in the bios subdir >> >>and >>

On 7/1/2015 2:58 AM, Gene Cumm wrote: >> I'm setting up UEFI booting and got to the point of having the system talk >> >to the dhcpd/tftpd server, grab the first image files (syslinux.efi) and >> >then continuously request the secondary image file (ldlinux.e64). > So it appears to go deaf. > >> >I'm wondering if I'm missing something or if someone

On Thu, Mar 6, 2014 at 10:55 AM, Bryan Romine <bromine1027 at gmail.com> wrote: > Sorry for the confusion, I am actually using 6.02. It turns out that I was > trying to use the 32-bit efi binary to load 64-bit kernels. I switched to > using "syslinux64.efi" but it hangs during boot, just before loading the > menu. I have not been able to get it to load the menu

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