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 21 d?cembre 2016, Ady Ady via Syslinux <syslinux at zytor.com> a ?crit :> > > 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 - eg. bootable - with qemu on bios and uefi > > (vmlinux & core.gz from tinylinux 7.2 are used). > > > > I've generated an iso image with : > > > > 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, and with qemu as hard disk > > on uefi but not on bios. > > > > for the last case, I've use : > > > > isohybrid core.iso > > > > but I've this error : > > > > isohybrid: core.iso: unexpected boot catalogue parameters > > > > what's my problem :-) > > > > regards. > > isohybrid is for "El Torito no-emulation" boot images (such as those > using isolinux.bin) and you are using "El Torito hard disk emulation". > > Unfortunately, syslinux.efi v.6.03 is not capable of booting optical > media in UEFI mode. Please read the wiki (and the "FAQ" link posted in > the isohybrid wiki page). > > Regards, > Ady. > > > _______________________________________________ > > Syslinux mailing list > > Submissions to Syslinux at zytor.com <javascript:;> > > Unsubscribe or set options at: > > http://www.zytor.com/mailman/listinfo/syslinux > > > > _______________________________________________ > Syslinux mailing list > Submissions to Syslinux at zytor.com <javascript:;> > Unsubscribe or set options at: > http://www.zytor.com/mailman/listinfo/syslinux >
Le 22/12/2016 ? 08:53, Pascal via Syslinux a ?crit :> 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). >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. Didier> Le mercredi 21 d?cembre 2016, Ady Ady via Syslinux <syslinux at zytor.com> a > ?crit : > >> >>> 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 - eg. bootable - with qemu on bios and uefi >>> (vmlinux & core.gz from tinylinux 7.2 are used). >>> >>> I've generated an iso image with : >>> >>> 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, and with qemu as hard disk >>> on uefi but not on bios. >>> >>> for the last case, I've use : >>> >>> isohybrid core.iso >>> >>> but I've this error : >>> >>> isohybrid: core.iso: unexpected boot catalogue parameters >>> >>> what's my problem :-) >>> >>> regards. >> >> isohybrid is for "El Torito no-emulation" boot images (such as those >> using isolinux.bin) and you are using "El Torito hard disk emulation". >> >> Unfortunately, syslinux.efi v.6.03 is not capable of booting optical >> media in UEFI mode. Please read the wiki (and the "FAQ" link posted in >> the isohybrid wiki page). >> >> Regards, >> Ady. >> >>> _______________________________________________ >>> Syslinux mailing list >>> Submissions to Syslinux at zytor.com <javascript:;> >>> Unsubscribe or set options at: >>> http://www.zytor.com/mailman/listinfo/syslinux >> >> >> >> _______________________________________________ >> Syslinux mailing list >> Submissions to Syslinux at zytor.com <javascript:;> >> Unsubscribe or set options at: >> http://www.zytor.com/mailman/listinfo/syslinux >> > _______________________________________________ > Syslinux mailing list > Submissions to Syslinux at zytor.com > Unsubscribe or set options at: > http://www.zytor.com/mailman/listinfo/syslinux >
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 boot success with UEFI and -cdrom must have other reasons. I suspect the BIOS emulation of the firmware. About SYSLINUX EFI: Do we really have confirmed examples where SYSLINUX EFI software works from qemu DVD-ROM ? Decisive test would be to make an ISO which offers no El Torito boot image for BIOS, but only an EFI System Partition image as El Torito boot image for Platform Id 0xef. In that partiton image there would have to be SYSLINUX stuff - not GRUB or a directly bootable kernel. Why i doubt: When it comes to reading data, there should be no perceivable difference between a real optical drive at a real computer and the virtual DVD-ROM of qemu. Both get operated in the end by SCSI commands. Of course there could be some driver shortage in SYSLINUX which does not show up with qemu DVD-ROM but prevents use of modern hardware. But i understand that EFI itself is a little operating system, which is supposed to operate hardware, and that SYSLINUX EFI software uses the API of EFI to perform its hardware operations. Have a nice day :) Thomas