similar to: Syslinux-6.00-pre1

Finally, the Syslinux 6.00 release is out. This release includes support for booting from EFI, both from disk-based media and over the network via PXE. Thanks to everyone who has been testing this out. There are some EFI bugs that I'm aware of, * booting Linux kernels without CONFIG_RELOCATABLE doesn't work * 64-bit syslinux.efi cannot boot 32-bit kernels and vice versa *

On Fri, Feb 20, 2015 at 8:08 AM, Patrick Masotta via Syslinux <syslinux at zytor.com> wrote: > 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. If you've made any changes to this, I'd

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

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

Tested with a Dell Vostro 1320 laptop. After booting with 'MENU RESOLUTION 1280 800' in config file, this is the ouput of 'hwinfo --framebuffer': 02: None 00.0: 11001 VESA Framebuffer [Created at bios.459] Unique ID: rdCR.fRULN9k9OD4 Hardware Class: framebuffer Model: "Intel(r)Cantiga Graphics Controller" Vendor: "Intel Corporation" Device:

This patch adds to Com32 modules the capabilities of accessing the EFI environment The idea is simple, the EFI parameters "image" and "table" received by syslinux.efi's efi_main() are stored in the "firmware" structure, next they are retrieved from the Com32 module which is linked against the gnu-efi static library. The Com32 module can use the EFI

Hi, Matt Fleming wrote: > 'make efi64' will build just for x86-64. Likewise, 'make efi32' will > build just for i386. You can combine these, so to build BIOS and efi64 > you'd do, > > make bios efi64 'make efi64' failed with: ld -T /tmp/syslinux/efi/x86_64/syslinux.ld -Bsymbolic -pie -nostdlib -znocombreloc -L/usr/lib64 --hash-style=gnu -m elf_x86_64

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

hi i'm about to upgrade systems. yesterday i got https://www.zytor.com/pub/syslinux/Testing/6.04/syslinux-6.04-pre3.tar.xz in order to upgrade 6.04-pre1 version. i first was upgrading a usb-disk which was booting smootly with a simple configuration. i changed the EFI installation in /EFI/BOOT: efi64/efi/syslinux.efi (UEFI bootloader for EFI X64 (x86_64) firmware) ?

Den 21. april 2016 kl. 14.21.04 +02.00 skrev Geert Stappers <stappers at stappers.nl>: > On Thu, Apr 21, 2016 at 06:39:44AM -0400, Gene Cumm via Syslinux 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)

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

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

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

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

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

> 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?) > > > > > > Yes, those 2 files came from your 'syslinux' command (in your other > > email). We don't want anything

This patch changes only strings, no program code. It is would be nice if it goes in the 6.04 release. Reported-by: Ady <ady-sf at hotmail.com> How this patch was prepared, how the editting for this patch was done Where is auxiliary written with double l? git grep -i auxilliary Which files are effect git grep -li auxilliary Changing the those files with the streaming editor sed

Hi Peter, Please pull the following changes. Paulo, I had to revert your "pxe: resolve names via DNS from protected-mode code" change because dns_resolv() is only implemented for PXELINUX and causes undefined symbol references for ISOLINUX, etc. Feel free to make the change again on top of the revert. The following changes since commit e7bd19def830e8341b1a100956345f1028740b9e:

Modern distributions are moving toward a common boot scheme called "The Boot Loader Specification". This patch enables syslinux to parse the drop-in files that are defined by this new specification. Link to documentation of the options added to syslinux by this patch: https://drive.google.com/uc?export=download&id=1nuRISVJeE1whYggFURywoQFpPzc6s1MC MD5 (syslinux-bls1.txt) =

Gregory Bartholomew wrote: > On Sat, May 25, 2019 at 3:42 PM Sebastian Herbszt <herbszt at gmx.de> > wrote: > > > > Gregory Lee Bartholomew wrote: > > > Modern distributions are moving toward a common boot scheme called > > > "The Boot Loader Specification". > > > > Which distributions are using this yet? [copy & paste from other