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
This bug is awaiting verification that the linux-
azure-6.5/6.5.0-1007.7~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-
azure-6.5' to
** Tags removed: foundations-todo
--
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
This bug was fixed in the package linux - 6.5.0-7.7
---
linux (6.5.0-7.7) mantic; urgency=medium
* mantic/linux: 6.5.0-7.7 -proposed tracker (LP: #2037611)
* kexec enable to load/kdump zstd compressed zimg (LP: #2037398)
- [Packaging] Revert arm64 image format to Image.gz
@mate I agree with that concern w.r.t. sending random pe binaries to
linux code path.
Separately in Mantic we are reverting zimg boot image format. Kernel
itself fails to kexec it correctly. And mantic kexec tools do not
support this image format correctly. Thus at this point grub 2.12 has
best
Do we use ZBOOT kernels anywhere in old releases where this is really
necessary?
Is this something we really want in older GRUBs at all?
Removing the magic number check is easy enough, but I am not sure of the
ramifications of allowing random signed EFI binaries through the linux
codepath with
** Changed in: grub2-unsigned (Ubuntu Jammy)
Assignee: (unassigned) => Mate Kukri (mkukri)
** Changed in: grub2-unsigned (Ubuntu Lunar)
Assignee: (unassigned) => Mate Kukri (mkukri)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
** Changed in: grub2-unsigned (Ubuntu Focal)
Assignee: (unassigned) => Mate Kukri (mkukri)
--
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
** Changed in: grub2-unsigned (Ubuntu)
Assignee: (unassigned) => Mate Kukri (mkukri)
--
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
** Also affects: grub2 (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: grub2-unsigned (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: grub2 (Ubuntu Jammy)
** Description changed:
[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:
** Tags added: patch
--
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:
Triaged
>> Kernels that use u-boot (direct), abootimg, piboot will have to stay
as they are - unless they gain zboot image format boot support.
Hello Dimitri,
zboot kernels are regualr EFI binaries. Where did you see problems in
booting them with U-Boot's bootefi command?
Best regards
Heinrich
--
** Patch added: "0001-UBUNTU-Config-Turn-on-CONFIG_EFI_ZBOOT-on-ARM64.patch"
https://bugs.launchpad.net/ubuntu/+source/grub2-unsigned/+bug/2002226/+attachment/5686814/+files/0001-UBUNTU-Config-Turn-on-CONFIG_EFI_ZBOOT-on-ARM64.patch
** Changed in: linux (Ubuntu)
Importance: Undecided =>
14 matches
Mail list logo
