Hi, i uploaded a new GNU xorriso development tarball for the next experiment with the Dell XPS 15 L502X of Dominik 'Rathann' Mierzejewski. The program will not interfere with the libraries or the /usr/bin/xorriso binary which gets installed by Fedora from the xorriso package. There are no special hard dependencies. But i assume that the Fedora xorriso gets built with these optional dependencies: - libreadline development package - zlib development package - libacl development package None of them should be needed for the experiment. Download: https://www.gnu.org/software/xorriso/xorriso-1.5.5.tar.gz MD5: e622b2547202529fbee6c9186fe39c40 (This might change with future uploads of the xorriso-1.5.5 snapshot. The next stable release will be 1.5.6.) Build: cd /...some.../...playground.../...directory... tar xzf /...where_it_was_downloaded.../xorriso-1.5.5.tar.gz cd xorriso-1.5.5 ./configure --prefix=/usr make This will produce a binary named ./xorriso/xorriso Installation is not necessary. Just execute the path that is given by ls $(pwd)/xorriso/xorriso Check whether it is willing to run: /...path.../xorriso/xorriso -version It should report: GNU xorriso 1.5.5 : RockRidge filesystem manipulator, libburnia project. GNU xorriso 1.5.5 ISO 9660 Rock Ridge filesystem manipulator and CD/DVD/BD burn program Copyright (C) 2021, Thomas Schmitt <scdbackup@xxxxxxx>, libburnia project. xorriso version : 1.5.5 Version timestamp : 2022.04.22.113324 Build timestamp : -none-given- libisofs in use : 1.5.5 (min. 1.5.5) libjte in use : 2.0.0 (min. 2.0.0) libburn in use : 1.5.5 (min. 1.5.5) libburn OS adapter: internal GNU/Linux SG_IO adapter sg-linux libisoburn in use : 1.5.5 (min. 1.5.5) License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>. This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. The "libjte" line will only appear if zlib development was present at compile time. All reported libraries are part of the tarball and linked statically. ------------------------------------------------------------------------- Now for the partition layout with GRUB which comes nearest to the layout that was produced with ISOLINUX (quite like the result of isoybrid --uefi). Begin like with the last experiment: # Extract the EFI partition dd if=boot-grub2-f36.iso bs=512 skip=1313268 count=20288 of=test_efi.img # Extract the MBR code dd if=boot-grub2-f36.iso bs=1 count=446 of=test_mbr.img # Pad MBR up to 32768 bytes, so that it overwrites the loaded system area dd if=/dev/zero bs=1 count=32322 >>test_mbr.img The xorriso run shall bring the ISO as near to the old layout as possible: xorriso=/...path.../xorriso/xorriso new_iso=test_oldlayout.iso # xorriso in its native mode does not truncate -outdev test -e "$new_iso" && rm "$new_iso" "$xorriso" \ -indev boot-grub2-f36.iso \ -outdev "$new_iso" \ -map test_efi.img /images/efiboot.img \ -as mkisofs \ -part_like_isohybrid \ --grub2-mbr test_mbr.img \ --boot-catalog-hide \ -b /images/eltorito.img \ -no-emul-boot -boot-load-size 4 -boot-info-table \ --grub2-boot-info \ -eltorito-alt-boot \ -e images/efiboot.img \ -no-emul-boot -isohybrid-gpt-basdat \ -R -J \ -- \ -padding included \ -compliance no_emul_toc \ -stdio_sync off Inspect the resulting boot equipment and partition layout: "$xorriso" -indev "$new_iso" -report_el_torito plain -report_system_area plain This should report: El Torito catalog : 71 1 El Torito images : N Pltf B Emul Ld_seg Hdpt Ldsiz LBA El Torito boot img : 1 BIOS y none 0x0000 0x00 4 72 El Torito boot img : 2 UEFI y none 0x0000 0x00 20288 328252 El Torito img path : 1 /images/eltorito.img El Torito img opts : 1 boot-info-table grub2-boot-info El Torito img path : 2 /images/efiboot.img System area options: 0x00004a00 System area summary: MBR grub2-mbr cyl-align-off GPT ISO image size/512 : 1333960 Partition offset : 0 MBR heads per cyl : 64 MBR secs per head : 32 MBR partition table: N Status Type Start Blocks MBR partition : 1 0x80 0x00 0 1333960 MBR partition : 2 0x00 0xef 1313008 20288 MBR partition path : 2 /images/efiboot.img GPT : N Info GPT disk GUID : 2040609c42db0e43ad879c51ee608215 GPT entry array : 2 248 separated GPT lba range : 64 1333896 1333959 GPT partition name : 1 490053004f004800790062007200690064003100 GPT partname local : 1 ISOHybrid1 GPT partition GUID : 1 2040609c42db0e43ad869c51ee608215 GPT type GUID : 1 a2a0d0ebe5b9334487c068b6b72699c7 GPT partition flags: 1 0x1000000000000001 GPT start and size : 1 1313008 20288 GPT partition path : 1 /images/efiboot.img ------------------------------------------------------------------------- (For now i have to thank the starter of this thread for causing me to test above unusual setup and to run my big regression test for the first time since february 2021. Three bugs showed up and are now hopefully fixed.) Have a nice day :) Thomas _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
