similar to: UEFI: Failed to load ldlinux.e64/ldlinux.e32

Displaying 20 results from an estimated 2000 matches similar to: "UEFI: Failed to load ldlinux.e64/ldlinux.e32"

2015 Oct 07
5
UEFI: Failed to load ldlinux.e64/ldlinux.e32
> 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 >>
2015 Oct 07
4
UEFI: Failed to load ldlinux.e64/ldlinux.e32
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
2015 Oct 03
3
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). > > > >
2015 Oct 03
2
UEFI: Failed to load ldlinux.e64/ldlinux.e32
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
2015 Oct 07
0
UEFI: Failed to load ldlinux.e64/ldlinux.e32
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
2015 Oct 02
0
UEFI: Failed to load ldlinux.e64/ldlinux.e32
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
2015 Oct 03
0
UEFI: Failed to load ldlinux.e64/ldlinux.e32
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
2015 Oct 07
2
Hyper-V Gen 2 waiting for ldlinux.e64
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 > <syslinux at zytor.com> wrote: > > Hi, > > > > I am using a Windows Server 2012 R2 Hyper-V Generation 2 VM as a > > PXE client (no physical machines available). This is a UEFI VM, and > > as per instructions I've read
2015 Oct 07
2
Hyper-V Gen 2 waiting for ldlinux.e64
Hi, I am using a Windows Server 2012 R2 Hyper-V Generation 2 VM as a PXE client (no physical machines available). This is a UEFI VM, and as per instructions I've read I have disabled secure boot on this VM for the installation of Linux. I am using the latest tftp-hpa package with the following config: # /etc/default/tftpd-hpa TFTP_USERNAME="tftp"
2015 Oct 07
4
UEFI: Failed to load ldlinux.e64/ldlinux.e32
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
2015 Oct 07
0
UEFI: Failed to load ldlinux.e64/ldlinux.e32
> -----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
2015 Oct 07
0
UEFI: Failed to load ldlinux.e64/ldlinux.e32
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
2015 Oct 03
0
UEFI: Failed to load ldlinux.e64/ldlinux.e32
> 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
2015 Oct 09
1
syslinux64.efi boot problems
Hi there, I've been trying to boot some new machines via uEFI and it does not work, as you can see below. From my hunting around on the mailing list, there may have been a bunch of fixes that have been committed that have some bearing on uEFI, and even some on the mailing list that appear to be aimed at solving similar problems. However, I can't manage to build a new one based on the
2016 Feb 24
6
[PATCH 2/5] ntfs: remove unused variable and have ntfssect use char API calls
The variable 'ok' is never used and generates a warning. Remove it. Also ntfssect.c is designed to be compiled in non Unicode mode when using MSVC compilers, so remove all ambiguity about it (LPCTSTR -> LPCSTR, use of 'A' API calls) so that it doesn't break when compiled in Unicode mode, which is what Rufus uses with MSVC. -------------- next part --------------
2015 Oct 07
2
Hyper-V Gen 2 waiting for ldlinux.e64
> 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 > > > >
2015 Oct 11
4
UEFI: Failed to load ldlinux.e64/ldlinux.e32
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: > >
2016 Feb 29
1
[PATCH 0/1] UEFI UDP/TFTP
On Sun, Feb 28, 2016 at 11:26 AM, Patrick Masotta via Syslinux <syslinux at zytor.com> wrote: > b) "UEFI: Failed to load ldlinux.e64/ldlinux.e32" > http://www.syslinux.org/archives/2015-October/024341.html > This report has led to Gene's patch: > > https://github.com/geneC/syslinux/commit/9e0926bb338deb5c634ccb4ee29eb4577158cfdc > it was reported working but
2015 Oct 09
5
lpxelinux.0 does not set the port number in the http Host: header
Hello all, I think I may have found a bug with the way lpxelinux.0 sends http requests. Specifically when I trace the requests I notice that the Host: header does not contain the port that was used to make the request. Here's my scenario. I have a python Flask app that dynamically generates the PXE menu for kickstarts. When I request a URL the server responds with a file containing more
2015 Mar 05
4
Problem boot PXE UEFI on HP ML350 Gen9
Hi All, My PXE configurations works fine for a bios PXE (the server in legacy mode) but hangs in an EUFI mode. Look like it can transfer the bootx64.efi but not the next one ldlinux.e64 Any ideas? Thanks Software> syslinux ver 6.3 atftp 7.1 Log server side >> Booting Embedded LOM 1 Port 1 : HP Ethernet 1Gb 4-port 331i Adapter - NIC (PXE IPv4) >> Booting PXE over