similar to: Syslinux 6.00 released

I've just pushed out a 6.00-pre1 release. This release includes support for booting EFI machines. The code is currently in the alpha stage. Having said that, you should expect most things to work correctly, including things like the graphical menu. Please help test if you can, and if you find any bugs, please report them. To facilitate building different versions of syslinux.efi (32-bit and

On Sat, 22 Jun, at 05:24:21PM, Ferenc Wagner wrote: > Matt Fleming <matt at console-pimps.org> writes: > > > Please do test out the release and report any regressions. > > Unfortunately, I can't make it under Debian wheezy + experimental > gnu-efi (ie. 3.0u+debian-1): > > $ make installer [...] > make[3]: *** No rule to make target

On Tue, 25 Jun, at 01:52:00PM, Helmut Hullen wrote: > Thanks - now it crashes later ... What crash are you seeing? > I don't have the ia64 files which are needed for a complete binary. But > maybe that's only my special problem. You shouldn't need ia64 files to build ia32 and x86-64 versions of gnu-efi or Syslinux. -- Matt Fleming, Intel Open Source Technology Center

On Fri, Jan 10, 2014 at 2:53 AM, Ferenc Wagner <wferi at niif.hu> wrote: > Gene Cumm <gene.cumm at gmail.com> writes: > >> On Sat, Jan 4, 2014 at 6:39 AM, Gene Cumm <gene.cumm at gmail.com> wrote: >>> On Tue, Dec 17, 2013 at 8:39 AM, Ferenc Wagner <wferi at niif.hu> wrote: >>> >>>> * make spotless still fails after working around

This patch adds to the core EFI image booting capabilities. It was tested on VMware EFI clients and HP Elitebook EFI notebooks, only on PXE environments but it should work on non-PXE scenarios as well. Feedback appreciated. Best, Patrick Signed-off-by: Patrick Masotta <masottaus at yahoo.com> --- diff -uprN a/com32/elflink/ldlinux/execute.c b/com32/elflink/ldlinux/execute.c ---

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

On 01/07/2013 12:51 PM, syslinux-bot for Matt Fleming wrote: > Commit-ID: 15a67011987c341814533ac4d8e23c9a72dc7605 > Gitweb: http://www.syslinux.org/commit/15a67011987c341814533ac4d8e23c9a72dc7605 > Author: Matt Fleming <matt.fleming at intel.com> > AuthorDate: Mon, 7 Jan 2013 14:42:16 +0000 > Committer: Matt Fleming <matt.fleming at intel.com> > CommitDate:

On Sat, 29 Jun, at 01:57:58AM, Igor Sverkos wrote: > Hi, > > Matt Fleming wrote: > > On Tue, 25 Jun, at 01:52:00PM, Helmut Hullen wrote: > >> Thanks - now it crashes later ... > > > > What crash are you seeing? > > > >> I don't have the ia64 files which are needed for a complete binary. But > >> maybe that's only my special

Matt Fleming <matt at console-pimps.org> writes: > Please do test out the release and report any regressions. Unfortunately, I can't make it under Debian wheezy + experimental gnu-efi (ie. 3.0u+debian-1): $ make installer [...] make[3]: Entering directory `/home/wferi/syslinux/syslinux-6.00/efi32/efi' gcc -I/usr/include/efi -I/usr/include/efi/ia32 -DEFI_FUNCTION_WRAPPER -fPIC

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

Hi folks, There are enough changes on the 'firmware' branch to warrant another prerelease. Things that jump out are the changes to update the current working directory when executing syslinux.efi (previously .c32 failed to load if installed to a non-standard directory such as /boot/syslinux, because the current working directory wasn't correct), the realloc() fix from Shao and a new

Hi, The internal Gnu-EFI build gives me grief: * efi/check-gnu-efi.sh: uses realpath, which is not available on my Debian wheezy system. I now use readlink -f, but wonder if it's needed at all. * efi/build-gnu-efi.sh: uses realpath, like above, and also pushd/popd, which is not built into a standard Bourne shell invoked by #!/bin/sh. Again I wonder what's the point of it, as

On Thu, 19 Dec, at 02:39:23AM, Celelibi wrote: > > Hello, > I confirm the command realpath wasn't installed by default on my > debian either. And it seems it can be easily replaced by readlink -f. > And actually I find its use doubtful. > > However, as you may have seen, these scripts are quite new and may > have bugs. Using pushd/popd in a /bin/sh script is a bug.

On Sat, Jan 4, 2014 at 6:39 AM, Gene Cumm <gene.cumm at gmail.com> wrote: > On Tue, Dec 17, 2013 at 8:39 AM, Ferenc Wagner <wferi at niif.hu> wrote: > >> * make spotless still fails after working around the above: >> [...] >> make -r -C efi SRC="/home/wferi/syslinux/syslinux/efi" OBJ="/home/wferi/syslinux/syslinux/efi32/efi" \ >>

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

Hi all - I'm not sure if it's appropriate to ask this here, but I don't see this question explicitly answered anywhere. Is there an EFI version of "pxelinux.0" that will function basically the same way and read the same pxelinux.cfg/default menu files? I've got a really dodgy grubx64.efi EFI PXE menu up at work, but it can't load the 1.2 gigabyte LiveCD that we use

Hello, A `make efi32` yeilds me make[3]: *** No rule to make target `efi32/com32/lib/memcmp.o', needed by `syslinux.so'. Stop. make[3]: Leaving directory `efi32/efi' make[2]: *** [efi] Error 2 Output of `ls -Gl efi32/com32/lib/mem*.o`: -rw-r--r-- 1 stappers 2812 Jun 10 22:06 efi32/com32/lib/memcpy.o -rw-r--r-- 1 stappers 3620 Jun 10 22:06 efi32/com32/lib/memmem.o

On Mon, Dec 3, 2018 at 10:02 AM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > Now it is just dd, mkfs and copy in the files we need. > > One less thing to worry about keeping versions consistent. > > > > > > I just noticed those 2 files that were added by > > > > syslinux -i boot.img > > > > (right?) > > > >

I've been trying to get syslinux.efi working in my environment again... Found what look like a bunch of little bugs that are very frustrating... First, the documentation on the Wiki says that as of 5.11, the list separator is space, not colon. But I can find no evidence that 5.11 was ever officially released or that a commit to git was made to make this change. 6.00 and following still use