similar to: Fail to boot ISOs using EFI

EFI systems typically don't support booting off ISO 9660 filesystems, even if written to USB sticks. This patch adds support for generating a GPT that covers the stick as well, with an additional partition entry pointing purely at the secondary El Torito image. When burned to CD the secondary El Torito will be used as an EFI boot image, and when written to a USB stick the GPT partition

> Hi, > > Pascal wrote: > > mkisofs -o core.iso -b boot/core.img -c boot/boot.cat -hard-disk-boot core/ > > my iso image is ok with qemu on bios and uefi, > > Astounding. As CD-ROM this is not supposed to work with UEFI unless the > firmware emulates BIOS. What particular UEFI firmware did you use ? > > > and with qemu as hard disk on uefi but not on

Hi, > Unfortunately I get the error message: > isohybrid: slint64-14.1.iso: unable to find mac efi image This is probably due to El Torito Platform id "Mac" in -eltorito-alt-boot -no-emul-boot -eltorito-platform Mac \ -eltorito-boot isolinux/macboot.img \ This caused in the image http://slint.fr/misc/MacBoot/slint64-14.1.iso platform id 1 with the third image. (I would

> Hi, > > Ady wrote: > > cdrtools.sourceforge.net/private/man/cdrtools-3.01axx/mkisofs.8.html > > Mac Boot entries for the Apple Mac platform. > > Interesting feature. But the El Torito specs of Phoenix and > IBM of 1994 state that "Mac" would be Platform Id 2. > http://download.intel.com/support/motherboards/desktop/sb/specscdrom.pdf > Page

I posted this on the bugzilla page but I figured that on the mailing list it would get more attention. Please see http://bugzilla.syslinux.org/show_bug.cgi?id=49 for a description of my current issue. -- Thank you, Fernando Reyes GPG BDD75DD7 Mission Accomplish, Inc. http://missionaccomplish.com Email:design at missionaccomplish.com Tel: 7187100008 Cell: 3479275477

> Hi, > > > Unfortunately I get the error message: > > isohybrid: slint64-14.1.iso: unable to find mac efi image > > This is probably due to El Torito Platform id "Mac" in > > -eltorito-alt-boot -no-emul-boot -eltorito-platform Mac \ > -eltorito-boot isolinux/macboot.img \ > > This caused in the image >

> Hi, > > Ady: > > _ Wiki should use more user-friendly language and "less deep" > > technical information. > > I tried to stay at the surface of isohybrid. > (Didier already asked for more depth about expert options.) My interpretation of Didier's questions is less depth and more user-friendly practical commands for end-users. Our points of view

HI, In http://slint.fr/misc/MacBoot/ you'll find all context information. All files referenced here are stored there. Long story short: once dd-ed on an USB stick the ISO image can boot on a BIOS or EFI machine, but I want it to be able to boot on most x86_64 Macs with an EFI firmware. Unfortunately I get the error message: isohybrid: slint64-14.1.iso: unable to find mac efi image The

Hi, Ady wrote: > the UEFI specs do state that the ESP is supposed > to be set/used as no-emulation mode > ... > the UEFI specs should tolerate / accept this situation, rather than < restricting the ESP to no-emulation mode. My criticism towards this UEFI implementation is that it probably cannot serve as realistic test bed for the first stage of UEFI booting. It seems far too

Hello Thomas, Thomas Schmitt via Syslinux said on Sun, Oct 25, 2015 at 04:35:57PM +0100: >I assume you can boot Fedora Live CD on the same (virtual) hardware. Not sure for Fedora, but the system is installed with either RHEL6, RHEL7 or Ubuntu 14.04 depending on the Lab I'm making on it without issue. >Just to make sure that the firmware works so far. Globally they do ;-) >

Hi, > I don't understand why you say "*But* the El Torito...". I don't see > a difference with what the mkisofs manual says. The manual announces "Mac" for Apple Mac. The program obviously writes Platform Id 1 in this case. The El Torito specs say "Platform ID 0 = 80x86 1=Power PC 2=Mac". In the sum this does not match. A bug in mkisofs would be the

I have just created an ISO containing Fedora and ISOLinux as the bootloader. This is the ISO creation command: genisoimage -U -r -v -T -J -joliet-long -V "Fedora-WS-Live-31-1-9" -volset "Fedora-WS-Live-31-1-9" -A "Fedora-WS-Live-31-1-9" -b isolinux/isolinux.bin -c isolinux/boot.cat -no-emul-boot -boot-load-size 4 -boot-info-table -eltorito-alt-boot -e

hello every body, I'm trying to build an isohybrid image based on syslinux able to boot on bios and uefi with optical disk or usb key. I've build a 16Mb hard disk image (core.img) with necessary parts for bios (legacy bootable partition, protective mbr, gptmbr.bin & syslinux installation) and for uefi (gpt, esp, /efi/boot/bootx64.efi & syslinux files). my hard disk image is ok -

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, 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, > > > I don't understand why you say "*But* the El Torito...". I don't see > > a difference with what the mkisofs manual says. > > The manual announces "Mac" for Apple Mac. > The program obviously writes Platform Id 1 in this case. > The El Torito specs say "Platform ID 0 = 80x86 1=Power PC 2=Mac". > In the sum this

Hi, I run a distro that uses Syslinux and I'm failing to see a way to boot an ISO using EFI. I noticed no other distro that uses Syslinux managed to accomplish that. 1. booting Syslinux using EFI on a system copied to a storage unit works just fine -- Syslinux menu shows up; it's all good 2. booting the ISO using EFI via, let's say VirtualBox, fails -- VirtualBox says it can't

Hi, On 23/06/2014 12:07, Thomas Schmitt wrote:> Hi, > > i have written an introduction to isohybrid and put it on > the discussion page of the ISOLINUX wiki. > > http://www.syslinux.org/wiki/index.php/Talk:ISOLINUX#Proposal_for_description_of_isohybrid > > Review and proposals are appreciated. Caveat emptor: this is a review by an end user (not a developer), who

Hi, H. Peter Anvin: > It means that the .iso can be booted from a partition using any of the > standard MBRs (not necessarily altmbr), But the --partok MBRs (isohdpp*) stem from altmbr ? If so: don't they need the partition number patched in ? (If not: i have to rethink the link to article "Mbr" at http://www.syslinux.org/wiki/index.php/Isohybrid#MBR_selection ) >

Hi, i am trying to document the MBR selection by isohybrid option --partok. I assume it is related to "altmbr.bin" as described in http://www.syslinux.org/wiki/index.php/Mbr But there i read "altmbr.bin [...] boots from a partition with fixed number, see below." The "see below" probably refers to "The altmbr.bin (all 3 variants) is only 439 bytes long, -- one