Hi, John Paul Adrian Glaubitz: > xorriso -as mkisofs -r -checksum_algorithm_iso md5,sha1 > -V 'Debian 10.0 sparc64 n' > -o /home/glaubitz/debian-cd-test/debian-10.0-sparc64-NETINST-1.iso > -J -joliet-long -cache-inodes > -G /home/glaubitz/tmp/sid/CD1/../CD1/boot/grub/sparc64-ieee1275/cdboot.img > -B '...' > --grub2-sparc-core /boot/grub/core.img > -graft-points > /boot/core.img=/home/glaubitz/tmp/sid/CD1/../CD1/boot/grub/core.img > CD1
Now you first insert .../core.img as /boot/core.img. Then you insert it again by its role as sub-file of "CD1" as ISO file /boot/grub/core.img. To the latter you refer by --grub2-sparc-core . So this is without much effect (except adding a file copy to the ISO): -graft-points /boot/core.img=/home/glaubitz/tmp/sid/CD1/../CD1/boot/grub/core.img > {0} ok boot cdrom > Boot device: /virtual-devices@100/channel-devices@200/disk@1 File and args: > WARNING: Unsupported bootblk image, can not extract fcode > WARNING: Bootblk fcode extraction failed > The file just loaded does not appear to be executable. Is this the SUN firmware speaking ? Google "sun bootblk" yields https://www.thegeekdiary.com/howto-verify-if-a-bootblk-is-installed-on-the-boot-disk-sparc/?PageSpeed=noscript where block 1 (i.e. byte 512 ff.) is inspected for "Bootblk". So it would be about block 1 of your disk file for -G /home/glaubitz/tmp/sid/CD1/../CD1/boot/grub/sparc64-ieee1275/cdboot.img That's where --grub2-sparc-core inserts its numbers. But i guess it is about the other bytes in there. Have a nice day :) Thomas