Hello Thomas,
Thomas Schmitt via Syslinux said on Sun, Oct 25, 2015 at 04:35:57PM
+0100:>I assume you can boot Fedora Live CD on the same (virtual) hardware.
Not sure for Fedora, but the system is installed with either RHEL6,
RHEL7 or Ubuntu 14.04 depending on the Lab I'm making on it without
issue.
>Just to make sure that the firmware works so far.
Globally they do ;-)
> xorriso version : 1.4.1
> Version timestamp : 2015.10.25.123601
Yep.
> $xorriso -as mkisofs ...your.genisoimage.arguments...
>Let's see whether my emulation knows all your options.
# ./mkisouefi
30000+0 records in
30000+0 records out
30720000 bytes (31 MB) copied, 0.0786484 s, 391 MB/s
mkfs.fat 3.0.20 (12 Jun 2013)
GNU xorriso 1.4.1 : RockRidge filesystem manipulator, libburnia project.
Drive current: -outdev 'stdio:testuefi.iso'
Media current: stdio file, overwriteable
Media status : is blank
Media summary: 0 sessions, 0 data blocks, 0 data, 33.0g free
xorriso : WARNING : -volid text does not comply to ISO 9660 / ECMA 119 rules
xorriso : FAILURE : -as mkisofs: Unrecognized option '-efi-boot'
xorriso : aborting : -abort_on 'FAILURE' 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:
# 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 manipulator, libburnia project.
xorriso : NOTE : Loading ISO image tree from LBA 0
xorriso : UPDATE : 6 nodes read in 1 seconds
xorriso : NOTE : Detected El-Torito boot information which currently is
set to be discarded
Drive current: -indev '/tmp/uefi.8274/testuefi.iso'
Media current: stdio file, overwriteable
Media status : is written , is appendable
Boot record : El Torito
Media summary: 1 session, 26722 data blocks, 52.2m data, 32.9g free
Volume id : 'Mindi_Image'
El Torito catalog : 34 1
El Torito cat path : /boot.cat
El Torito images : N Pltf B Emul Ld_seg Hdpt Ldsiz LBA
El Torito boot img : 1 BIOS y none 0x0000 0x00 4 15035
El Torito boot img : 2 UEFI y none 0x0000 0x00 60000 35
El Torito img path : 1 /isolinux.bin
El Torito img opts : 1 boot-info-table isohybrid-suitable
El Torito img path : 2 /1.img
xorriso : NOTE : No System Area was loaded
===== Proposed bootability options with -as mkisofs :
-V 'Mindi_Image'
--modification-date='2015102801315800'
-c '/boot.cat'
-b '/isolinux.bin'
-no-emul-boot
-boot-load-size 4
-boot-info-table
-eltorito-alt-boot
-e '/1.img'
-no-emul-boot
-boot-load-size 60000
>In case it does not like your options, have a look at the proposed
>ones. (Be mistrusting. It's advise from an automat.)
So back to the xorriso command replacing -efi-boot with -e:
# ./mkisouefi
30000+0 records in
30000+0 records out
30720000 bytes (31 MB) copied, 0.0783567 s, 392 MB/s
mkfs.fat 3.0.20 (12 Jun 2013)
GNU xorriso 1.4.1 : RockRidge filesystem manipulator, libburnia project.
Drive current: -outdev 'stdio:testuefi.iso'
Media current: stdio file, overwriteable
Media status : is blank
Media summary: 0 sessions, 0 data blocks, 0 data, 32.8g free
xorriso : WARNING : -volid text does not comply to ISO 9660 / ECMA 119
rules
Added to ISO image: directory '/'='/tmp/uefi.8294'
xorriso : UPDATE : 5 files added in 1 seconds
xorriso : UPDATE : 5 files added in 1 seconds
ISO image produced: 26721 sectors
Written to medium : 26721 sectors at LBA 0
Writing to 'stdio:testuefi.iso' completed successfully.
/tmp/uefi.8294
total 106532
drwxr-xr-x. 3 root root 4096 Oct 28 01:36 .
drwxrwxrwt. 19 root root 4096 Oct 28 01:36 ..
-rw-r--r--. 1 root root 30720000 Oct 28 01:36 1.img
-rw-r--r--. 1 root root 18557142 Oct 28 01:36
initramfs-3.10.0-229.el7.x86_64.img
-rw-r--r--. 1 root root 40960 Oct 28 01:36 isolinux.bin
drwxr-xr-x. 2 root root 4096 Oct 28 01:36 mnt
-rw-r--r--. 1 root root 54724608 Oct 28 01:36 testuefi.iso
-rwxr-xr-x. 1 root root 5026624 Oct 28 01:36 vmlinuz-3.10.0-229.el7.x86_64
So works fine this time :-)
But booting from the generated ISO doesn't change anything. Still the
red screen, no syslinux menu or text displayed.
Is there a way to increase the debug level of syslinux.efi in order to
check what it tries to do and diagnose more precisely what happens ?
Thanks again for your help Thomas,
bruno.
--
Open Source Profession, Linux Community Lead WW http://opensource.hp.com
HP EMEA EG Open Source Technology Strategist http://hpintelco.net
FLOSS projects: http://mondorescue.org http://project-builder.org
Musique ancienne? http://www.musique-ancienne.org http://www.medieval.org