A few more observations below. Running the file command on both gives us:
linux/arch/arm64/boot$ file Image.gz Image.gz: gzip compressed data, max compression, from Unix, original size modulo 2^32 63220224 linux/arch/arm64/boot$ file vmlinuz.efi vmlinuz.efi: PE32+ executable (EFI application) Aarch64 (stripped to external PDB), for MS Windows, 2 sections This change does not change the binary size: -rw-r--r-- 1 user ubuntu 19M Feb 18 12:34 Image.gz -rwxr-xr-x 1 user ubuntu 19M Feb 16 16:16 vmlinuz.efi Compared to the uncompressed image: -rw-r--r-- 1 user ubuntu 61M Feb 16 16:16 Image As described in the initial report, Image.gz compresses the whole binary, vmlinuz.efi only compresses the payload to be decompressed by the stub. The stub code size is negligible so they are roughly the same size. Heinrich mentioned that there was a similar with Risc-V kernels in the past where they tried to run the kernel directly from u-boot EFI. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2098111 Title: arm64: kernel image cannot be booted in UEFI despite EFI stub and ZBOOT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2098111/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
