search for: report_system_area

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

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 Torito boot img : 1 BIOS y none 0x0000 0x00 4 22645 El Torito boot img : 2 UEFI y none 0x0000 0x00...

...RE' encountered 'FAILURE So the efi-boot option is not known. >In any case i would be interested to see what xorriso reports >about the boot equipment of your already existing ISO > > $xorriso -indev ...path.to.ISO... \ > -report_el_torito plain \ > -report_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: # xorri...

On 05/03/2016 02:31 AM, Thomas Schmitt via Syslinux wrote: > Hi, > > John Lewis wrote: >> https://help.ubuntu.com/community/LiveCDCustomizationFromScratch >> >> The show stopper for me was the mkisofs because the closest command I >> had available was xorrisofs and I think a switch was different. > If you have questions about xorrisofs, then just ask me. :))

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 LBA El Torito boot img : 1 BIOS y none 0x0000 0x00 4 767 El Torito boot img : 2 UEFI y none 0x0000 0x00 2880 47 El Torito boot img : 3 UEFI...

.../2014 10:46, Thomas Schmitt wrote: > 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 Torito boot img : 1 BIOS y none 0x0000 0x00 4 22645 > El Torito boo...

> Hi, > > > Not being compatible with EFI/GPT is already a problem for the Perl > > variant. > > The relation of both is: > > isohybrid.in/.pl is being left behind. > http://git.kernel.org/cgit/boot/syslinux/syslinux.git/tree/utils/Makefile > has: > SCRIPT_TARGETS += isohybrid.pl # about to be obsoleted > > isohybrid.c replaces it feature-wise

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

...s ...your.genisoimage.arguments... Let's see whether my emulation knows all your options. In any case i would be interested to see what xorriso reports about the boot equipment of your already existing ISO $xorriso -indev ...path.to.ISO... \ -report_el_torito plain \ -report_system_area plain \ -print '' \ -print '===== Proposed bootability options with -as mkisofs :' \ -print '' \ -report_el_torito as_mkisofs \ -print '' In case it does not like your options, have a look at the proposed ones....

...hare/syslinux/isohdpfx.bin <remaining options> In case of BIOS + EFI you could add options like: eltorito-alt-boot -e isolinux/efiboot.img \ isohybrid-gpt-basdat -no-emul-boot To check the content of the ISO image: xorriso -hfsplus on -indev <your ISO image> \ -report_el_torito plain -report_system_area plain That's what I learned from Thomas Schmitt. Maybe he will step in and tell you more. Didier

...They can be combined with ISOLINUX in the same ISO image. Examples are netinst ISOs of Debian (not their LiveCDs), or ISOs of Archlinux, Gentoo, Fedora, or openSuSE. xorriso-1.4.2 will show you their equipment by xorriso -indev debian-8.4.0-amd64-netinst.iso \ -report_el_torito plain -report_system_area plain It will make proposals of boot related xorrisofs options to reproduce the shown equipment by xorriso -indev debian-8.4.0-amd64-netinst.iso \ -report_el_torito as_mkisofs > I would > need to get an Electrical Engineer to translate the parts I don't > understand. T...

...d.exe from SliTaz, no EFI/GPT support ---------------------------------------------------------------- If somebody wants to assess the quality, i would propose to inspect the resulting ISOs by xorriso >= 1.3.7 xorriso -indev image.iso \ -report_el_torito plain \ -report_system_area plain It knows El Torito, MBR, GPT, and APM and complains about some known flaws or pitfalls. Have a nice day :) Thomas

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

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

...------------------------------- Good _starting_ point for documentation. > > If somebody wants to assess the quality, i would propose to inspect > the resulting ISOs by xorriso >= 1.3.7 > > xorriso -indev image.iso \ > -report_el_torito plain \ > -report_system_area plain > > It knows El Torito, MBR, GPT, and APM and complains about some known > flaws or pitfalls. That's great. Since xorriso is not always an available option for some users (e.g. other OS), I hope for The Syslinux Project to still get help from developers (regarding isohybrid...