similar to: boot fails in a VMware player

> > In other words, I was only referring to the limitation of Syslinux in > > UEFI mode about being able to boot *optical media*. Expressing this > > (current) limitation as "[not] able to boot in UEFI and BIOS modes > > using Syslinux" is inaccurate. > > Thanks Ady, I appreciate your accuracy and stand corrected. > > However, in my use cases at

Hi, Ady wrote: > I very much doubt that there is any ISO image, publicly > available or not, that can boot optical media in UEFI mode by means of > Syslinux for EFI as of today. I hope this status will change at some > point. > [...] > I doubt that syslinux.efi (renamed as "EFI/BOOT/BOOT<arch>.EFI") > is capable of booting optical media in UEFI mode at

Hi, On 13/11/2014 19:17, Ady wrote: >> Hi, >> >> On 11/11/2014 02:55, Ady wrote: >> > Again, dd'ing your isohybrid image onto your (virtual or real) drive >> > will fail to boot in EFI mode. Your "syslinux.efi-based" >> > "/isolinux/efiboot.img" will not be capable of booting. This is one >> > of the steps

On 10/11/2014 04:02, Ady wrote: > >> Hi there, >> >> I failed to boot an installer in a VMware player (Version6.0.3 >> build-1895310) >> using syslinux 6.03, be it off an hybrid ISO image and an USB stick. >> >> Booting succeeds if the VM is set to use a BIOS firmware with both media, >> but fails using an efi firmware. >>

> Hi there, > > I failed to boot an installer in a VMware player (Version6.0.3 > build-1895310) > using syslinux 6.03, be it off an hybrid ISO image and an USB stick. > > Booting succeeds if the VM is set to use a BIOS firmware with both media, > but fails using an efi firmware. > > Trying to boot off the ISO image I get an error message "The firmware >

Hi, On 11/11/2014 02:55, Ady wrote: > Again, dd'ing your isohybrid image onto your (virtual or real) drive > will fail to boot in EFI mode. Your "syslinux.efi-based" > "/isolinux/efiboot.img" will not be capable of booting. This is one > of the steps that corresponds to grub2, not to whichever other EFI > bootloader you use (e.g. syslinux.efi). So,

> > You are probably imitating / following some procedure used by > > Slackware to create EFI-compatible ISO images. The problem, as > > mentioned in a recent email this last week, is the particularities of > > the documents regarding, in this case, grub2 as EFI bootloader (as > > oppose to documents covering EFI bootloaders in general and clearly > >

> On 01/06/2016 00:28, H. Peter Anvin via Syslinux wrote: > > There seem to be a bunch of bug fixes in the 6.04 branch that people > > really need. Do we know of any current regressions? Otherwise we > > really ought to just push the button... > > I am a user of syslinux 4.0.7 to boot installers on BIOS aka Legacy. > > Knowing that 4.0.7 has been released on

Hi, On 02/04/2016 11:10, Thomas Schmitt via Syslinux wrote: > Hi, > > Ady wrote: >> I very much doubt that there is any ISO image, publicly >> available or not, that can boot optical media in UEFI mode by means of >> Syslinux for EFI as of today. I hope this status will change at some >> point. >> [...] >> I doubt that syslinux.efi (renamed as

Hi, Didier Spaier wrote: > http://slint.fr/testing/slint64-14.1_syslinux.6.03/slint64-14.1_syslinux.6.03.img This looks like the content of an EFI system partition. Exactly what i need for experiments. Thanks a lot. (slint64-current-goofiboot.iso and slint64-current-efi-stub.iso were already in my collection.) It boots to "Slint installer for Slackware64-14.1" by:

Hi there, I failed to boot an installer in a VMware player (Version6.0.3 build-1895310) using syslinux 6.03, be it off an hybrid ISO image and an USB stick. Booting succeeds if the VM is set to use a BIOS firmware with both media, but fails using an efi firmware. Trying to boot off the ISO image I get an error message "The firmware encountered an unexpected exception" Trying to

On 22/03/2016 16:35, Thomas Schmitt via Syslinux wrote: ... > How can we augment > http://www.syslinux.org/wiki/index.php?title=ISOLINUX > http://www.syslinux.org/wiki/index.php?title=Isohybrid > so that users do not believe to have missed the trick for UEFI booting > from optical media ? +1. I have read Ady's answer to this message, but still: why not just state clearly in

> > Hi, > > On 11/11/2014 02:55, Ady wrote: > > Again, dd'ing your isohybrid image onto your (virtual or real) drive > > will fail to boot in EFI mode. Your "syslinux.efi-based" > > "/isolinux/efiboot.img" will not be capable of booting. This is one > > of the steps that corresponds to grub2, not to whichever other EFI > >

Hi, Didier Spaier wrote: > The issue is the inability of booting of a *physical* (not virtual) optical > media, like for instance a DVD or a CD, using syslinux.efi. Actually firmware cannot find any UEFI specified booting starting points in an ISO 9660 filesystem that was created with mkisofs -b and -hard-disk-boot, but without a boot image which was marked as EFI System Partition. The

Hi, H. Peter Anvin wrote: > Look for a "legacy boot" option; otherwise you need the CD-ROM to have > the EFI version of Syslinux or another bootloader on it The "another bootloader" is clear to me. But what are the prescriptions for preparing a SYSLINUX EFI System Partition that boots out of a CD ? (Those built according to

when you say """ Unfortunately, syslinux.efi v.6.03 is not capable of booting optical """, you talk about isolinux.bin ? because my iso image with a "good" alternate eltorito boot image (eg. "uefi ready") is booting with qemu (qemu -cdrom core.iso -bios uefi.fd) and is also booting in hard disk mode (qemu -hda core.iso -bios uefi.fd). Le mercredi

Hi all, I have requested tests of this USB installer: http://slint.fr/testing/slint64-14.1_syslinux.6.03.img in both BIOS and UEFI modes. A test in UEFI mode: http://www.linuxquestions.org/questions/slackware-14/%5Bann%5D-syslinux-6-03-has-been-released-4175521209/#post5270515 leaded to this message: "Cannot relocate kernel, bailing out" That leaded me to this post in the ML:

> > On 16/11/2014 18:33, Didier Spaier wrote: > > Hi all, > > > > I have requested tests of this USB installer: > > http://slint.fr/testing/slint64-14.1_syslinux.6.03.img > > in both BIOS and UEFI modes. > > > > A test in UEFI mode: > >

On 16/11/2014 18:33, Didier Spaier wrote: > Hi all, > > I have requested tests of this USB installer: > http://slint.fr/testing/slint64-14.1_syslinux.6.03.img > in both BIOS and UEFI modes. > > A test in UEFI mode: > http://www.linuxquestions.org/questions/slackware-14/%5Bann%5D-syslinux-6-03-has-been-released-4175521209/#post5270515 > > leaded to this message: >

Hi, Le 18/06/2020 ? 22:24, Tom Huibregtse via Syslinux a ?crit?: > I am a UEFI/BIOS developer. We UEFI PXE boot dozens of times per night. We have run into this error more than a couple of times. We have also done thousands of UEFI PXE boots with debug statements to prove that the patch works. <snip> As far as I can tell, the development of Syslinux has stalled since more than one