similar to: EFI64 ISO

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/4/23 09:55, Gene Cumm wrote: > > The resulting config would require suffix-less module references, i.e. > > "UI menu" or "COM32 ls". > > > > Additionally, I documented the basics of my test system here: > > > > http://www.syslinux.org/archives/2014-February/021740.html > > > > Bear in mind, by "URL-like

On 2014/4/23 ?? 09:55, Gene Cumm wrote: > The resulting config would require suffix-less module references, i.e. > "UI menu" or "COM32 ls". > > Additionally, I documented the basics of my test system here: > > http://www.syslinux.org/archives/2014-February/021740.html > > Bear in mind, by "URL-like file locations", I mean that if we have >

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

Gene, I found a document from IBM that explains why it didn't like Vendor-Class-Identifier option I was using "PXEClient" was causing EFI boot rooms to dummy spit, that's very useful, that combined with RTFMing the PXE specs 3.0-3.2 might solve my problem if I keep at it. http://www-01.ibm.com/support/docview.wss?uid=swg21247032 Even the PXELinux docs suggest encapsulating

On Tue, Apr 22, 2014 at 8:15 PM, Steven Shiau <steven at nchc.org.tw> wrote: > > Dear Syslinux developers, > I'd like to continue the discussion about this: > http://www.syslinux.org/archives/2014-February/021659.html > i.e. different directories for *.c32 files of BIOS, EFI32, and EFI64. > I am wondering why we can not have > *.c32 for the COMBOOT files of BIOS,

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 > mboot.c32 > menu.c32 > syslinux.cfg > vesamenu.c32 > KS.CFG (vmware specific) > BOOT.CFG

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 Thu, Nov 27, 2014 at 8:59 AM, Luke Ledgerd <luke.ledgerd at niteco.se> wrote: > Gene, > > As it happened I started working on this again just as you mailed me. I saw it in IRC. > It appears that PXE-E99 may also be related to MTFTP part of the PXE spec. IBM also says it has something to do with jumbo frames. I tried setting PXE.mtcp-ip to 0.0.0.0 to disable it but still no

Dear Syslinux developers, I'd like to continue the discussion about this: http://www.syslinux.org/archives/2014-February/021659.html i.e. different directories for *.c32 files of BIOS, EFI32, and EFI64. I am wondering why we can not have *.c32 for the COMBOOT files of BIOS, *.e32 for the COMBOOT files of EFI32 *.e64 for the COMBOOT files of EFI64 As now the ldlinux file of syslinux 6.0x has,

Gene, As it happened I started working on this again just as you mailed me. It appears that PXE-E99 may also be related to MTFTP part of the PXE spec. IBM also says it has something to do with jumbo frames. I tried setting PXE.mtcp-ip to 0.0.0.0 to disable it but still no joy. The bootfile size shows up as zero because that relates to "option boot-size" in dhcp and doesn't seem to

Den 21. april 2016 kl. 22.04.37 +02.00 skrev Gene Cumm <gene.cumm at gmail.com>: > 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

On Mon, Nov 24, 2014 at 3:24 AM, Luke Ledgerd <luke.ledgerd at niteco.se> wrote: > http://www.niallbrady.com/2014/06/11/when-uefi-network-booting-on-a-hyperv-gen-2-vm-you-might-get-pxe-e99-unexpected-network-error/ > > P.S. It's not this and I'm getting a PXE-E99 tftp failure "Unexepected Network Error", so I'll guess I'll need to investigate what kind of

On Wed, Apr 20, 2016 at 5:03 AM, Atle Holm <atle at team-holm.net> wrote: > I recognize hardware with Lua and execute the ESXi installer with > configuration files for that hardware. > This works fine with normal Syslinux boot, but I want to get it working for > UEFI boot as well. > > I found efi64/efi/syslinux.efi and efi32/efi/syslinux.efi in the installer > source,

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 mboot.c32 menu.c32 syslinux.cfg vesamenu.c32 KS.CFG (vmware specific) BOOT.CFG (vmware specific) autoselect.lua These files are also all under the root of the partition (except BOOTIA32.EFI and BOOTX64.EFI) and work fine

To share with you the result of testing, Syslinux EFI x64 It actually works pretty solid. Starting graphical installation $ liveinst -G ... As seen on the screens [1], it is unnecessary to install a boot loader thus Grub 2, through the installer, but upon successful completion, it will be done manually - Syslinux EFI x64 installation. Do not reboot. Switching to a freshly installed system $

I recognize hardware with Lua and execute the ESXi installer with configuration files for that hardware. This works fine with normal Syslinux boot, but I want to get it working for UEFI boot as well. I found?efi64/efi/syslinux.efi and efi32/efi/syslinux.efi in the installer source, copied them and named them respectively?BOOTX64.EFI and?BOOTIA32.EFI in USBDISK:\EFI\BOOT. These were also the

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