Ubuntu UEFI Installation Image
Ubuntu UEFI Installation Image
preseed, but with 20.10 my previous used process and commands did not work.
But 20.10 doesn't seem to use isolinux(syslinux) at all, as I can't spot the
directory. The files in the boot direkctory have changed too.
The BIOS boot image and MBR are now from GRUB.
The EFI System Partition is not a file in the ISO any more.
But the ISO keeps its old jackalope style by an additional MBR partition of type 00
and size 1.
This nearly not existing partition holds the boot flag for some few old BIOS
machines which boot only if this flag is present in some MBR partition entry.
The protective MBR partition of type EE is not allowed to bear this flag.
fdisk -l ubuntu-23.04-desktop-legacy-amd64.iso
You may extract MBR and EFI partition image from the original ISO:
orig=ubuntu-23.04-desktop-legacy-amd64.iso
mbr=ubuntu-23.04-desktop-legacy-amd64.mbr
efi=ubuntu-23.04-desktop-legacy-amd64.efi
new=ubuntu-23.04-desktop-legacy-amd64.iso
disk=Ubuntu 23.04 amd64
Regrettably xorriso <= 1.5.2 has a bug in the output of this command with ISOs
using --mbr-force-bootable, by also reporting -as mkisofs option
-part_like_isohybrid
which would spoil the ISO for booting from new Lenovo laptops. The newest GNU
xorriso-1.5.3 tarball has this bug fixed.
Edit on request:
The set of boot lures is as crammed as in the the old ISOs: El Torito for BIOS and
EFI from optical media, MBR x86 code for BIOS from USB stick, a partition table
with EFI partition for EFI from USB stick.
Reason to give up SYSLINUX/ISOLINUX was probably its poor maintainance state and
the fact that one needs GRUB anyways for booting via EFI from optical media. The
old partition layout mix of ISOLINUX and GRUB did not work with GRUB+GRUB on some
modern EFI laptops. My suspicion is that they tolerate MBR partition table only if
an ISOLINUX MBR is present. That old layout was quite an abominality if seen from
the UEFI specs.
So Ubuntu went to appended partitions and GPT as partition table. Some old HP
laptops bailed out and had to be dragged in by a boot flag in the MBR partition
table.