similar to: Custom ISO

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,

> > 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, > > 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, > > Ady wrote: > > This could be misinterpreted by some users as: "if > > you want to build an isohybrid image, then you cannot use > > 'syslinux.efi'". This would be incorrect. > > I don't know whether syslinux.efi can be used for booting > from ISO 9660 via UEFI. Currently there is no example > around which would succeed

I have been using syslinux-6.x along with isohybrid --mac and --efi option to create a usb hybrid iso with EFI support. The thing with EFI is that you'll need to use grub as your bootloader for EFI but isohybrid does setup the proper partition schema for EFI. You'll need to use the following to generate an iso that works. xorriso -as mkisofs -J -R -l -V some-vol-label \ -o ../image.iso

Thanks for hint. I have changed to this: genisoimage \ -v \ -J -R \ -V "$NAME" \ -b isolinux/isolinux.bin -no-emul-boot -boot-load-size 4 \ -boot-info-table -eltorito-alt-boot -b images/efiboot.img -no-emul-boot -boot-load-size 18755 \ -o $DESTINATION_FILE . it now creates the ISO and is EFI bootable. However - I have a different issue

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

I did the dd of the ISO to a 16G USB device. the second partition is FAT so I can edit it - I want to make a custom menu entry. I edited the grub.cfg - but that did not work - my menu option does not show. Then I think I need to change BOOT.cfg and generate the grub.cfg - but I dont know in this case how to generate for the USB device. What command do I use for that ? Thanks, Jerry

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, i have implemented in xorriso the equivalents of isohybrid.c options --mac and --uefi. There remains the question how to ensure that the submitted MBR is prepared for the 32 byte mock-up of an APM Block0. I see in git of may 2012 that all mbr/isohdp[fp]x*.bin begin by 33 ed 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90

Same CD. Any Linux distribution without the 5.X series boots on this machine. We can use 4.06 and it boots just fine. It's not the computer's hardware. Like I said, we can take the CD out of the GX620 and place it in the 9010 and it boots. Put 4.06 on the CD, and they both boot. Patrick On Sat, Jul 6, 2013 at 7:18 AM, Gene Cumm <gene.cumm at gmail.com> wrote: > On Fri, Jul 5,

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

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

Does anyone know if it is possible to 'hide' a grub menuentry with CentOS 7 ? I have a custom menuentry that I don't want to be seen on the grub screen - but it needs to be selectable as the entry to boot via 'grub2-reboot' I've scanned the grub2 documentation - but I can't find anything obvious - so I'm guessing it can't be done - unless someone knows

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

> 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

I've been using various versions of syslinux as the boot loader for the g4l project that I have been the maintainer of since 2004. It was already using syslinux, so I've just updated it over the years, and currently have it use 5.10 version, but have done test builds with the 6.x versions. Recently had request from to users about EFI support, and one suggested that virtualbox has

> 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. > > The reference to "above mkisofs command" anticipates the final > position of this text at the end