search for: mksiof

...hich is >the latest one available, even if I could try to get a beta one if >needed. So as a summary of what I've tried up to now: The ISO image I make with the script previously shown has now 4 different efi binaries to boot from in the same VFAT32 image embedded on the ISO with either mksiofs (from RHEL7) or upstream xorriso. With syslinux 6.03, syslinux from Gene git or syslinux with debug symbols I get the red screens previously shared, and that I've seen mentioned in some other messages here, even from people trying with PXE. With grub.efi (0.99 version from RHEL6) I can have...

...ent out those dierctives > in /EFI/BOOT/syslinux.cfgto no avail: I still get the same error message > at (failed) boot in vmplayer: > "The firmware encountered an unexpected exception" Your isohybrid ISO image will fail, as the GPT EFI bootloader that you built in your mksiofs command is inadequate. > > > If you are really trying to boot your EFI VM with a (either real or > > virtual) USB drive (instead of using a virtual fixed HDD), then some > > additional considerations might be necessary. > > I tried that too with a real USB stick,...

Thomas Schmitt via Syslinux said on Sat, Oct 24, 2015 at 12:56:49AM +0200: >Needed is a EFI FAT image > 32 MiB and a new xorriso (available >on demand). My test script on RHEL 7.1 creates that even if I could make it smaller as the kernel + initrd fits in less than 32 MB. So let me make that try first ! o I changed myline in the script to dd a 30 MB image file, burt the ISO with it, and

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

...eport_system_area plain \ > -print '' \ > -print '===== Proposed bootability options with -as mkisofs :' \ > -print '' \ > -report_el_torito as_mkisofs \ > -print '' >From an iso made with the local mksiofs: # xorriso -indev /tmp/uefi.8274/testuefi.iso -report_el_torito plain -report_system_area plain -print '' -print '===== Proposed bootability options with -as mkisofs :' -print '' -report_el_torito as_mkisofs -print '' GNU xorriso 1.4.1 : RockRidge filesystem manipu...

> Hi, > > some minor nitpicking on Ady's summary: > > > the real "genisoimage" is not really up to the task for > > UEFI-booting. > > In some distros, genisoimage offers option -e for embedding > a FAT filesystem image. > (genisoimage is a fork of mkisofs, so "real" is somewhat > misleading in respect to history.) > > For

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

...in any of the above scenarios? Yes. These are _not_ detailed step-by-step "HowTos", and I currently have no intention to write them either. The Syslinux wiki has more than 100 pages; among others: http://www.syslinux.org/wiki/index.php/Install Are the ISO image building tools (e.g. mksiofs, genisoimage, xorriso...) related to so-called "efiboot.img" files? Yes, in a similar way that they are related to any "El Torito" image. Is the isohybrid tool (in any of its variants) related to so-called "efiboot.img" files? Yes, in a similar way that the isohy...

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