Hi, i am the developer of xorriso. If there are problems after changing the xorriso arguments i am ready to help identifying the cause.
My own opinion about how Debain (and Ubuntu) ISOs for BIOS|EFI from CD|HDD should look like is to see in https://lists.debian.org/debian-cd/2019/07/msg00007.html (It uses ISOLINUX for BIOS, but could well use GRUB software with the appropriate xorriso options for GRUB MBR code. Its main theme is to abandon the hacky layout with invalid GPT that was introduced by Fedora in 2012.) This opinion is strictly oriented towards a single ISO that is flatly copied to its storage medium. The trick (*) with just extracting the ISO into a FAT filesystem is not generically supported by my proposals. But of course it would be possible to have an unpacked copy of the EFI System Partition in ISO directory /EFI/BOOT, so that the trick works again. (*) It is not specified in UEFI which demands that the EFI partition has to be marked by type 0xEF in MBR table, or Type GUID C12A7328-F81F-11D2-BA4B-00A0C93EC93B in GPT. But Microsoft Inc. obviously supports this trick and thus firmware programmers will hardly disable it. ------------------------------------------------------------------------ My advise to developers of ISO post-processing software is to join forces and to write down a specification about what they expect from a bootable ISO which shall be subject to their activities. I am ready to participate in discussions about such a specification. Have a nice day :) Thomas -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895131 Title: Groovy Desktop *BREAKS* the most common method of creating UEFI bootable drives for Ubuntu installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1895131/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
