This bug is awaiting verification that the linux- aws-6.5/6.5.0-1008.8~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- aws-6.5' to 'verification-done-jammy-linux-aws-6.5'. If the problem still exists, change the tag 'verification-needed-jammy-linux-aws-6.5' to 'verification-failed-jammy-linux-aws-6.5'.
If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-aws-6.5-v2 verification-needed-jammy-linux-aws-6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2002226 Title: Add support for kernels compiled with CONFIG_EFI_ZBOOT Status in grub2 package in Ubuntu: Fix Released Status in grub2-unsigned package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in grub2 source package in Focal: Invalid Status in grub2-unsigned source package in Focal: Invalid Status in linux source package in Focal: Invalid Status in grub2 source package in Jammy: Invalid Status in grub2-unsigned source package in Jammy: Invalid Status in linux source package in Jammy: Invalid Status in grub2 source package in Lunar: Invalid Status in grub2-unsigned source package in Lunar: Invalid Status in linux source package in Lunar: Invalid Bug description: [Impact] Arm64 kernels compiled with CONFIG_EFI_ZBOOT=y don't use the ARM64_IMAGE_MAGIC ('ARM\x64') but LINUX_PE_MAGIC (0x818223cd) in the PE Header. Our GRUB fails to boot such a kernel. We should eliminate the following check: grub-core/loader/efi/linux.c:75: if (lh->magic != GRUB_LINUX_ARCH_MAGIC_SIGNATURE) return grub_error(GRUB_ERR_BAD_OS, "invalid magic number"); This will allow any EFI binary to be run using the linux command. [Test plan] * check that grub and EFI based ARM64 machines boot * check that MAAS deployment works [Where problems could occur] * Non-EFI bootloaders want to boot with regular vmlinuz.gz. If one is using piboot, u-boot, abootimg likely one still wants to build Image.gz and have CONFIG_EFI_ZBOOT disabled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2002226/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
