similar to: Syslinux 6.03-pre7: EFI64 broken

Still interested in pre-compiled binaries for 6.03-pre6. But my comment about 6.02 TFTP brokenness may speak more to my lack of understanding of the TFTP protocol than to any pxelinux 6.02 code problems. It seems that when TFTP sends an OACK back to syslinux.efi, it sends it from another port than 69. So, it seems to be opening a data connection back to the TFTP client off an ephemeral port.

Gene, Where did you find the precompiled binaries for syslinux 6.03-pre7? Actually, I'm interested in the pre-compiled binaries for syslinux 6.03-pre6. I went out to kernel.org, but the latest they have is 6.02. Which appears to have an endian problem in its TFTP client code (when syslinux.efi tries to connect to the TFTP server, attempts to connect to UDP port 17664 instead of 69).

> > > On 2014/3/7 05:23, Gene Cumm wrote: > > 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,

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

Most excellent! The pre-compiled syslinux6.03-pre6 binaries work great! I'm able to load syslinux.efi and all necessary support libs. I get my expected syslinux boot menu. I've used syslinux 5 / vesamenu for yrs (Legacy PXE boots). So I know my way around from here. Thanks Gene & Feri. And thanks Peter, for making me feel better -- it's the TFTP protocol that's bizarre, I

On Fri, Mar 7, 2014 at 12:34 PM, Bryan Romine <bromine1027 at gmail.com> wrote: > I'm convinced that my Syslinux install may be broken with all the hacking > around and testing I have been doing. If I were to install fresh from the > syslinux-6.03-pre7 archive, what would I need to do. I do not see any > documentation on installation other than "make installer" in

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

On Thu, Mar 6, 2014 at 6:45 PM, Bryan Romine <bromine1027 at gmail.com> wrote: > Yes, I am using efi64/efi/syslinux.efi and > efi64/com32/elflink/ldlinux/ldlinux.e64. I tried binaries from 6.03-pre7 and > it gets farther along but brings up the error "Default boot device missing > or boot failed". Maybe I am not installing all of the required dependencies? > Are

On 2014?03?08? 20:57, Gene Cumm wrote: > Please try 6.03-pre6. I see a regression on 6.03-pre7 with EFI64 netboot > >> > Another thing you I'd like to mentioned is, after bootx64.efi was >> > downloaded, the next download for ldlinux.e64 was about 15 secs later. >> > Is that normal? > When it's successful for me, it takes 0.2s from the beginning of >

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 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 Mon, Mar 10, 2014 at 8:50 PM, Spike White <spikewhitetx at gmail.com> wrote: > There are no pre-compiled binaries (official or otherwise) on kernel.org. The Syslinux archives at kernel.org are source and binary. Extract them and you'll see. > I assume what is meant is > https://www.kernel.org/pub/linux/utils/boot/syslinux/ > At least, that is where the

There are no pre-compiled binaries (official or otherwise) on kernel.org. I assume what is meant is https://www.kernel.org/pub/linux/utils/boot/syslinux/ At least, that is where the "downloads" page of syslinux.org directs you. Under there are the various source tarballs (tar.gz format, tar.bz2 format). Also a directory called RPMS/. But that kernel.org RPMS/ directory is devoid of

On Sat, Mar 8, 2014 at 2:05 AM, Steven Shiau <steven at nchc.org.tw> wrote: > Hi Gene, > Thanks. As you mentioned, atftpd has better logging, and my files are > smaller than 92 MB, so I switched to atftpd for testing. Now I could > find that somehow after bootx64.efi is downloaded by client, the next > ldlinux.e64 has never been fetched by client: > ====================

On Mar 8, 2014 8:36 AM, "Steven Shiau" <steven at nchc.org.tw> wrote: > > > On 2014?03?08? 20:57, Gene Cumm wrote: > > Please try 6.03-pre6. I see a regression on 6.03-pre7 with EFI64 netboot > > > >> > Another thing you I'd like to mentioned is, after bootx64.efi was > >> > downloaded, the next download for ldlinux.e64 was about 15

On 2014/3/7 ?? 05:23, Gene Cumm wrote: > 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 >>

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.... I am trying to TFTP netboot a 32bit linux kernel (4.11.3) via efi64 syslinux.efi. If I build a 64 bit version of the same kernel, it TFTP netboots fine, but if I build the kernel (same config options as 64 bit working version) as 32 bit, the PC reboots almost immediately after loading the kernel over TFTP. I read before that support for loading 32 bit kernels in efi64 had been added in

Op 2014-08-01 om 20:35 schreef Ady: > Goal: To have one USB drive capable of booting UEFI IA32 and UEFI X64 > (with an optional Syslinux menu containing multiple entries). What I would like to have is the same thing for network boot. So having one topdirectory on the TFTP server that can serve several "architectures". > Problem (solved) #1: The default directory location for

On 2014?03?08? 05:56, Gene Cumm wrote: > In /etc/vmware/vmnet8/dhcpd/dhcpd.conf I added the following: > > host 7x { > hardware ethernet 00:0C:29:38:6B:6E; > filename "e6/bootx64.efi"; > next-server 172.21.1.1; > # option vendor-encapsulated-options >