similar to: VMware with UEFI fails to boot

On Sat, Feb 1, 2014 at 21:07, Gene Cumm <gene.cumm at gmail.com> wrote: > Known issue. http://bugzilla.syslinux.org/show_bug.cgi?id=35 and perhaps a few others but this should be resolved in the master branch. > I just committed my fix this morning so there's no -pre release yet. Is that really fixed in git? I've checkout syslinux about one hour ago from git. I ran a make all

On Sun, Feb 2, 2014 at 7:18 AM, Conrad Kostecki <ck at conrad-kostecki.de> wrote: > On Sat, Feb 1, 2014 at 8:50 PM, Ady <ady-sf at hotmail.com> wrote: >> >>> On Sat, Feb 1, 2014 at 21:07, Gene Cumm <gene.cumm at gmail.com> wrote: >>> > Known issue. http://bugzilla.syslinux.org/show_bug.cgi?id=35 and >>> perhaps a few others but this should

On Sun, Feb 2, 2014 at 12:34 PM, Conrad Kostecki <ck at conrad-kostecki.de> wrote: > On Sun, Feb 2, 2014 at 7:18 AM, Conrad Kostecki <ck at conrad-kostecki.de> wrote: >> On Sat, Feb 1, 2014 at 8:50 PM, Ady <ady-sf at hotmail.com> wrote: >>> >>>> On Sat, Feb 1, 2014 at 21:07, Gene Cumm <gene.cumm at gmail.com> wrote: >>>> > Known

Hi there, I am trying to setup a bootable PXELinux (Using 6.02) over UEFI. Currently, I am using DNSMasq for this. PXE with BIOS works perfectly fine for me. As I don't have any UEFI devices here, I am using VMware Workstation 10.0.1 for testing. My DNSMasq setup has been extended, to load also UEFI: dhcp-boot=pxelinux.0 dhcp-match=set:efi-ia32,option:client-arch,6

On Sun, Feb 2, 2014 at 7:18 AM, Conrad Kostecki <ck at conrad-kostecki.de> wrote: > On Sat, Feb 1, 2014 at 8:50 PM, Ady <ady-sf at hotmail.com> wrote: >> >>> On Sat, Feb 1, 2014 at 21:07, Gene Cumm <gene.cumm at gmail.com> wrote: >>> > Known issue. http://bugzilla.syslinux.org/show_bug.cgi?id=35 and >>> perhaps a few others but this should

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

On Sun, Feb 2, 2014 at 1:53 PM, Conrad Kostecki <ck at conrad-kostecki.de> wrote: > On Sun, Feb 2, 2014 at 12:34 PM, Conrad Kostecki <ck at conrad-kostecki.de> wrote: Gene wrote: >>> Yes however I have no clue on the reliability of your system for building Syslinux. I can provide some test binaries if you would like. >> That would be a good idea! >> I've

On Feb 1, 2014 4:37 PM, "Conrad Kostecki" <ck at conrad-kostecki.de> wrote: > > On Sat, Feb 1, 2014 at 21:07, Gene Cumm <gene.cumm at gmail.com> wrote: > > Known issue. http://bugzilla.syslinux.org/show_bug.cgi?id=35 and perhaps a few others but this should be resolved in the master branch. > > I just committed my fix this morning so there's no -pre

Quoting Reindl Harald <h.reindl at thelounge.net>: > Am 18.03.2015 um 20:56 schrieb Conrad Kostecki: >> Am 2015-03-18 20:46, schrieb Reindl Harald: >>> Am 18.03.2015 um 20:40 schrieb Conrad Kostecki: >>>> Hi! >>>> Currently, the passwords are stored in plaintext for my dovecot, as I >>>> am >>>> still using cram-md5 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

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

> On Mon, Dec 8, 2014 at 10:44 AM, Leenders, Peter > <Peter.Leenders at computacenter.com> wrote: > > > This look promising, if I could separate the config files for the different > > boot architectures Bios and UEFI. I have 2 different boot files in 2 > > different locations, but after startup they both refer to the > > tftproot/pxlinux.cfg/default config

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

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

>I could be wrong about this, but... I think that it could still be possible to get multiple architectures / firmwares mixed together >while using c32 modules, without dhcp options, and perhaps even without applying pxelinux-options. > >If I understood correctly, this tftp server can choose between 2 boot files, depending on BIOS/UEFI client, and the problem is >choosing a

Ady Ady via Syslinux wrote: > >> We're using a CentOS 6 server running its native (ISC) dhcpd (v4.1.1) >> and tftpd (v 0.49). I've installed syslinux.efi and ldlinux.e64 from the >> syslinux-6.04-pre2 distro alongside the existing pxelinux.0 > > > Please avoid the official binaries from Syslinux 6.04-pre2 and > 6.04-pre3. Additionally, the current git

On Thu, Apr 21, 2016 at 6:39 AM, Gene Cumm <gene.cumm at gmail.com> wrote: > On Thu, Apr 21, 2016 at 3:29 AM, Atle Holm <atle at team-holm.net> wrote: >> Under EFI/BOOT are the following files: >> BOOTIA32.EFI (from efi32/efi/syslinux.efi) >> BOOTX64.EFI (from efi64/efi/syslinux.efi) >> ldlinux.sys (copied from root of partition) >> lua.c32 >>

DHCP seems to be working properly - returning the correct boot file for the architecture of the PXE client, but when I try to boot syslinux.efi, it gets the file then keeps requesting ldinux.e64 over and over again. The file is there and available. A wireshark trace shows it keeps requesting the file, followed by the server responding to the blksize and tsize options, but then the client just

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

Gene Cumm wrote: > > On Fri, Oct 4, 2019 at 7:47 AM James Pearson via Syslinux > <syslinux at syslinux.org> wrote: >> >> Ady Ady via Syslinux wrote: >>> >>>> We're using a CentOS 6 server running its native (ISC) dhcpd (v4.1.1) >>>> and tftpd (v 0.49). I've installed syslinux.efi and ldlinux.e64 from the >>>>