similar to: How to use syslinux(isolinux, etc.) for EFI?

On Wed, Dec 11, 2013 at 9:22 PM, ?? <kun.he at cs2c.com.cn> wrote: > When we meet UEFI or EFI firmware, lots of linux os release use > GRUB bootloader. But I wanna use isolinux to boot the installation > environment and also the linux os installed. Some question puzzled me. Now, > I look for your help: > > 1. I didn't found information about how to use >

On 12/13/2013 02:20 PM, Gene Cumm wrote: > On Dec 13, 2013 4:55 PM, "H. Peter Anvin" <hpa at zytor.com > <mailto:hpa at zytor.com>> wrote: >> >> On 12/12/2013 04:21 AM, Gene Cumm wrote: >> > On Wed, Dec 11, 2013 at 9:22 PM, ?? <kun.he at cs2c.com.cn > <mailto:kun.he at cs2c.com.cn>> wrote: >> >> When we meet UEFI or EFI

Hi, On 29/07/2014 21:34, Thomas Schmitt wrote: > Nevertheless i advise Didier to simply try with 0xef rather than Mac. At least the ISO will then have MBR, GPT and APM entries for the file macboot.img. I did that, and also tried the xorriso command you posted. I uploaded both ISO images on http://slint.fr/misc/MacBoot resp. renamed: slint64-14.1-Thomas_mkisofs.iso

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

Hi, i downloaded http://slint.fr/misc/testing/slint64-14.1_syslinux.6.03.iso Inspection by xorriso-1.3.8: xorriso -indev slint64-14.1_syslinux.6.03.iso \ -report_el_torito plain \ -report_system_area plain yields El Torito catalog : 46 1 El Torito cat path : /isolinux/isolinux.boot El Torito images : N Pltf B Emul Ld_seg Hdpt Ldsiz LBA El

> > I ponder whether it would be possible to create a diagnostic MBR > which does not necessarily have to boot but rather tells what the > isohybrid MBR would perceive: Presence of partition table, > EBIOS or CBIOS, block address used with INT 13, content of the block > read by the first INT 13, ... > > One could preserve the isohybrid MBR of an ISO and replace it by >

I'm going to get the hang of this mailing list eventually. Apologies for any duplicate emails.. >Ian Bannerman: >> While I did know the .exe variant was not official / untrusted, >Is there a special reason for this ? (Except the known bugs which affect Linux binaries, too.) Not really. I had never found a convincing source for it and had seen previous list entries like this

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 -

Hi, On 29/07/2014 23:19, Thomas Schmitt wrote: > A good opportunity to brag with xorriso's boot inspection > features (since xorriso-1.3.8): Yes! I've upgraded libburn, libisofs and libisoburn so now I can play with it too ;) > I forgot to advise (or misadvise) -isohybrid-apm-hfsplus with > the image /isolinux/efiboot.img . So we only got one APM > partition here. A

Hi, Didier Spaier: > I uploaded both ISO images on http://slint.fr/misc/MacBoot A good opportunity to brag with xorriso's boot inspection features (since xorriso-1.3.8): xorriso -indev slint64-14.1-Thomas_mkisofs.iso \ -report_el_torito plain \ -report_system_area plain yields (block size is 2048): El Torito images : N Pltf B Emul Ld_seg Hdpt Ldsiz

Hi, Ady wrote: > so, why the original isohybrid image from Debian and many other > isohybrid images have mostly (but not all) "00s" in place of the "90s"? That's a fake Block0 of an Apple Partition Map. Part of mjg's layout. Caused by isohybrid option --mac or xorrisofs option -isohybrid-apm-hfsplus. * Fedora has it with EFI FAT filesystem in one 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

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, we are the developers of an alternative to mkisofs: program xorriso from libburnia-project.org . The current development cycle is about support for creating bootable CDs, DVDs, BDs. So we look for testers and for advise about ISOLINUX specifics. The example from the ISOLINUX wiki is supposed to work if you replace "mkisofs" by "xorriso -as mkisofs". I.e: xorriso -as

Precis: I?m trying to debug a problem with CentOS7 failing to install from an ISO written to a USB pendrive ? anyone got suggestions? What works ? installing on a modern, ?standard PC?; the pendrive image boots and installs as I expect What does not work ? same pendrive booting in an ATCA blade. What I?ve tried is? 1. Boot the standard CentOS7 minimal image. This seems to start but then

> > I am still interested in improving the isohybrid wiki > and will watch for pointers to descriptions of the FAT > production process (with GRUB/GRUB2 if not with SYSLINUX). > > If no such descriptions appear within the next weeks, > then i plan to state in > http://www.syslinux.org/wiki/index.php/Isohybrid#UEFI > > "The SYSLINUX project cannot yet provide

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

Hello everyone, Since I have some some adventures in UEFI PXE booting ahead I tried to go with the latest syslinux development snapshot in this case 5.10pre1. But I already fail when booting from CD with Failed to load COM32 file .c32 I am a bit perplex since no name of COM32 files is given. I am trying to trace down the issue as good as I can. COM32 files present are:

Hi, piranna wrote: > > Quoting http://www.syslinux.org/wiki/index.php/Isohybrid#UEFI: > > "The additional isohybrid feature for UEFI adds a partition to the MBR > > partition table pointing to the same file in the ISO 9660 filesystem > > as does the El Torito catalog entry for EFI." Ady wrote: > IMHO, the current content of the Isohybrid page in the Syslinux