[Kernel-packages] [Bug 1528345] Re: grub or kernel update broke Secure Boot by putting grubx64.efi instead of shimx64.efi in EFI boot order
This seems to have been an update publication issue in a version of
Ubuntu that is no longer supported (14.10), I don't think there is bug
described here that still exists.
I am setting this to "Incomplete" to give some time for anyone to
confirm being affected by this, I am also downgrading severity from
"Critical".
** Changed in: grub2 (Ubuntu)
Status: Triaged => Incomplete
** Changed in: hundredpapercuts
Status: Confirmed => Incomplete
** Changed in: grub2 (Ubuntu)
Importance: Critical => Medium
** No longer affects: linux (Ubuntu)
--
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/1528345
Title:
grub or kernel update broke Secure Boot by putting grubx64.efi instead
of shimx64.efi in EFI boot order
Status in One Hundred Papercuts:
Incomplete
Status in grub2 package in Ubuntu:
Incomplete
Bug description:
I've been running Ubuntu on a Lenovo ThinkPad X240. I initially
installed 14.10 when I got the machine in January. I then upgraded to
15.04, and on Monday evening (late December 14) I upgraded to 15.10.
I rebooted once right after the update to make sure some postfix and
opendkim configuration changes I made worked correctly after
rebooting.
Then between Monday evening and Friday evening (December 19) there
were a bunch of system updates that I installed. On Friday evening I
decided to reboot to boot into the updated kernel. (There were also
grub updates in that interval.)
When I rebooted, the laptop said:
Secure Boot
Image failed to verify with *ACCESS DENIED*
Press any key to continue.
See the image (posted by somebody else) of this error in
http://askubuntu.com/questions/710146/how-to-fix-secure-boot-error-
image-failed-to-verify-with-access-denied-on-st
I had to disable secure boot to make the system boot.
Based on the discussion in
http://askubuntu.com/questions/710146/how-to-fix-secure-boot-error-image-failed-to-verify-with-access-denied-on-st
it appears that the problem is that the updates caused it to try to boot
directly to grub (File(\EFI\ubuntu\grubx64.efi)) rather than via the shim
(File(\EFI\ubuntu\shimx64.efi)). I don't know for sure what sequence of
events caused that, nor did I verify for certain that it was booting via the
shim before. However, I know that this reboot on Friday was the first time I
had a secure boot failure since installing Ubuntu on the laptop (and using only
Ubuntu; no other OSes involved) in January.
I'll attach a list of the system updates that were applied in the
interval between the successful boot and the failed one from
/var/log/dpkg.log . Note that the log is in UTC but my description
above ("evening", etc., is in UTC-8, so the evening of December 14 is
actually around 07:00 UTC on December 15). Note that this log
contains a grub update, two kernel updates, and the removal of the
first of those kernel updates via apt-get autoremove.
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: grub-common 2.02~beta2-29ubuntu0.2
ProcVersionSignature: Ubuntu 4.2.0-22.27-generic 4.2.6
Uname: Linux 4.2.0-22-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Dec 21 15:39:21 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-01-25 (330 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
SourcePackage: grub2
UpgradeStatus: Upgraded to wily on 2015-12-15 (6 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1528345/+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
[Kernel-packages] [Bug 2051999] Re: Grub2 2.06 has upstream bug that results in Non-booting with ZFS after snapshot of bpool.
Update: Instead of my name space, I have uploaded a 2.12 version to this PPA: https://launchpad.net/~ubuntu-uefi-team/+archive/ubuntu/backports- build If it builds correctly, it can be used on Jammy with less fear by adding: "deb [trusted=yes] https://ppa.launchpadcontent.net/ubuntu-uefi-team/backports-build/ubuntu/ jammy main" The caveat of this being non-validated development software, and it not being compatible with Secure Boot are still there, but at least it should avoid the shlibs breakage. (Please note I have only uploaded grub2-unsigned, which only includes grub-efi-*, but that's all you need to test EFI changes). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/2051999 Title: Grub2 2.06 has upstream bug that results in Non-booting with ZFS after snapshot of bpool. Status in grub2 package in Ubuntu: Confirmed Status in grub2-unsigned package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: New Bug description: There is an upstream Bug with Grub where if you create snapshots of bpool, it results in a non-booting System. The problem was found to be an upstream Bug with Grub2: https://savannah.gnu.org/bugs/index.php?64297 Multiple Ubuntu 22.04.3 Users Affected: https://ubuntuforums.org/showthread.php?t=2494397=zfs+grub+bug https://ubuntuforums.org/showthread.php?t=2494957 Brought up as an issue at OpenZFS: https://github.com/openzfs/zfs/issues/13873 If you look at this comment (https://github.com/openzfs/zfs/issues/13873#issuecomment-1892911836), if was found the Savanaugh at GNU released a fix for it in Grub2 2.12, here: https://git.savannah.gnu.org/cgit/grub.git/log/grub-core/fs/zfs/zfs.c Ubuntu Jammy 22.04.3 is Grub2 2.06. We need to backported this patch to Grub2 2.06 so that Users are not caught of in this bug for or currently supported LTS Release. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: grub-efi-amd64 2.06-2ubuntu14.4 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu Feb 1 16:40:28 2024 InstallationDate: Installed on 2021-09-23 (861 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: grub2-unsigned UpgradeStatus: Upgraded to jammy on 2022-08-17 (533 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2051999/+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
[Kernel-packages] [Bug 2051999] Re: Grub2 2.06 has upstream bug that results in Non-booting with ZFS after snapshot of bpool.
1. Doing 2.12 backports to Jammy will happen, but it's not an overnight process. The delta from 2.06 to 2.12 is large, and even though it might work on your and my machine. We are hoping that the 2.12 release to Debian testing now, upload to Debian -backports later, and release to Noble in April will give us more time to see the effect in the field. Some minor breakage on old and odd machines will happen, I know that, as we have changed the entire kernel loading mechanism going from 2.12 -> 2.06, but hopefully it can be kept as minimal as possible. I am already in the process of integrating patches for issues reported in reaction to the Debian testing roll-out. 2. The PPA breaking Jammy has an additional very different reason to not doing 2.12 backports right now, it's because of the wrong build OS being used, basically: If you only install grub-efi-* from the PPA it's less likely to break, but the problem is `grub*-common` is linked against user-space shlibs from Noble which can and will be newer than Jammy's, and ABI backwards compatibility isn't exactly always a guarantee. The correct solution for Jammy would be to upload the same package with a slightly different version number and `jammy` as the series in d/changelog to a PPA, and then have "deb [trusted=yes] https://ppa.launchpadcontent.net/your_user_here/ppa_here/ubuntu/ jammy main" in sources. If you want a GRUB 2.12 build for Jammy right now, I can upload that to a PPA in my namespace. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/2051999 Title: Grub2 2.06 has upstream bug that results in Non-booting with ZFS after snapshot of bpool. Status in grub2 package in Ubuntu: Confirmed Status in grub2-unsigned package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: New Bug description: There is an upstream Bug with Grub where if you create snapshots of bpool, it results in a non-booting System. The problem was found to be an upstream Bug with Grub2: https://savannah.gnu.org/bugs/index.php?64297 Multiple Ubuntu 22.04.3 Users Affected: https://ubuntuforums.org/showthread.php?t=2494397=zfs+grub+bug https://ubuntuforums.org/showthread.php?t=2494957 Brought up as an issue at OpenZFS: https://github.com/openzfs/zfs/issues/13873 If you look at this comment (https://github.com/openzfs/zfs/issues/13873#issuecomment-1892911836), if was found the Savanaugh at GNU released a fix for it in Grub2 2.12, here: https://git.savannah.gnu.org/cgit/grub.git/log/grub-core/fs/zfs/zfs.c Ubuntu Jammy 22.04.3 is Grub2 2.06. We need to backported this patch to Grub2 2.06 so that Users are not caught of in this bug for or currently supported LTS Release. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: grub-efi-amd64 2.06-2ubuntu14.4 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu Feb 1 16:40:28 2024 InstallationDate: Installed on 2021-09-23 (861 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: grub2-unsigned UpgradeStatus: Upgraded to jammy on 2022-08-17 (533 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2051999/+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
[Kernel-packages] [Bug 2051999] Re: Grub2 2.06 has upstream bug that results in Non-booting with ZFS after snapshot of bpool.
GRUB 2.12 isn't going into the updates channel anywhere at this point. (It's going in proposed then release on Noble soon however) The question is, are we going to backport the fix to 2.06 and push that to the updates channel, or can this wait for the 2.12 SRU sometimes after April? It's good to confirm that this works btw, but I wouldn't recommend installing the "noble" series from that PPA on anything but noble, it can and will break things. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/2051999 Title: Grub2 2.06 has upstream bug that results in Non-booting with ZFS after snapshot of bpool. Status in grub2 package in Ubuntu: Confirmed Status in grub2-unsigned package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: New Bug description: There is an upstream Bug with Grub where if you create snapshots of bpool, it results in a non-booting System. The problem was found to be an upstream Bug with Grub2: https://savannah.gnu.org/bugs/index.php?64297 Multiple Ubuntu 22.04.3 Users Affected: https://ubuntuforums.org/showthread.php?t=2494397=zfs+grub+bug https://ubuntuforums.org/showthread.php?t=2494957 Brought up as an issue at OpenZFS: https://github.com/openzfs/zfs/issues/13873 If you look at this comment (https://github.com/openzfs/zfs/issues/13873#issuecomment-1892911836), if was found the Savanaugh at GNU released a fix for it in Grub2 2.12, here: https://git.savannah.gnu.org/cgit/grub.git/log/grub-core/fs/zfs/zfs.c Ubuntu Jammy 22.04.3 is Grub2 2.06. We need to backported this patch to Grub2 2.06 so that Users are not caught of in this bug for or currently supported LTS Release. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: grub-efi-amd64 2.06-2ubuntu14.4 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu Feb 1 16:40:28 2024 InstallationDate: Installed on 2021-09-23 (861 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: grub2-unsigned UpgradeStatus: Upgraded to jammy on 2022-08-17 (533 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2051999/+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
[Kernel-packages] [Bug 2051999] Re: Grub2 2.06 has upstream bug that results in Non-booting with ZFS after snapshot of bpool.
@mafoelffen You can find builds of GRUB 2.12 for Ubuntu in this PPA: https://launchpad.net/~ubuntu-uefi-team/+archive/ubuntu/build NOTE that the stuff in that PPA isn't signed, so you need to disable UEFI secure boot to test it easily. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/2051999 Title: Grub2 2.06 has upstream bug that results in Non-booting with ZFS after snapshot of bpool. Status in grub2 package in Ubuntu: Confirmed Status in grub2-unsigned package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: New Bug description: There is an upstream Bug with Grub where if you create snapshots of bpool, it results in a non-booting System. The problem was found to be an upstream Bug with Grub2: https://savannah.gnu.org/bugs/index.php?64297 Multiple Ubuntu 22.04.3 Users Affected: https://ubuntuforums.org/showthread.php?t=2494397=zfs+grub+bug https://ubuntuforums.org/showthread.php?t=2494957 Brought up as an issue at OpenZFS: https://github.com/openzfs/zfs/issues/13873 If you look at this comment (https://github.com/openzfs/zfs/issues/13873#issuecomment-1892911836), if was found the Savanaugh at GNU released a fix for it in Grub2 2.12, here: https://git.savannah.gnu.org/cgit/grub.git/log/grub-core/fs/zfs/zfs.c Ubuntu Jammy 22.04.3 is Grub2 2.06. We need to backported this patch to Grub2 2.06 so that Users are not caught of in this bug for or currently supported LTS Release. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: grub-efi-amd64 2.06-2ubuntu14.4 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu Feb 1 16:40:28 2024 InstallationDate: Installed on 2021-09-23 (861 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: grub2-unsigned UpgradeStatus: Upgraded to jammy on 2022-08-17 (533 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2051999/+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
[Kernel-packages] [Bug 1215411] Re: libcpupower.so is not installed from linux-tools
I'm looking at this on +1, and there don't seem to be an obvious forward. Debian has their own SONAME versioning for when the kernel package breaks libcpupower's ABI, but we only have per-kernel-versioned packages. * Do we want to provide an unversioned linux-tools-dev with a similar ABI-breakage SONAME versioning? * Do we want to patch these packages (if possible) to not depend on libcpupower? * Or if no one seems to mind (as it seems from the age of this), how about blocklisting the packages depending on libcpupower-dev from Ubuntu? -- 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/1215411 Title: libcpupower.so is not installed from linux-tools Status in cpufreqd package in Ubuntu: Confirmed Status in gkrellm2-cpufreq package in Ubuntu: Confirmed Status in linux package in Ubuntu: In Progress Status in opa-ff package in Ubuntu: New Bug description: The patch for bug 1158668 installs cpupower_$(abi_version) command- line tool as well as libcpupower.so.$(abi_version). This isn't particularly suitable for projects that previously used libcpufreq and intend to migrate to libcpupower, because the libcpupower.so symlink is no longer installed. The command-line tools can also have symlinks (e.g. cpupower -> cpupower_$(abi_version)). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cpufreqd/+bug/1215411/+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
[Kernel-packages] [Bug 2002226] Re: Add support for kernels compiled with CONFIG_EFI_ZBOOT
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 those old loaders.
--
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:
Triaged
Status in grub2 source package in Focal:
New
Status in grub2-unsigned source package in Focal:
New
Status in linux source package in Focal:
New
Status in grub2 source package in Jammy:
New
Status in grub2-unsigned source package in Jammy:
New
Status in linux source package in Jammy:
New
Status in grub2 source package in Lunar:
New
Status in grub2-unsigned source package in Lunar:
New
Status in linux source package in Lunar:
New
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
[Kernel-packages] [Bug 2002226] Re: Add support for kernels compiled with CONFIG_EFI_ZBOOT
** 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 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:
Triaged
Status in grub2 source package in Focal:
New
Status in grub2-unsigned source package in Focal:
New
Status in linux source package in Focal:
New
Status in grub2 source package in Jammy:
New
Status in grub2-unsigned source package in Jammy:
New
Status in linux source package in Jammy:
New
Status in grub2 source package in Lunar:
New
Status in grub2-unsigned source package in Lunar:
New
Status in linux source package in Lunar:
New
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
[Kernel-packages] [Bug 2002226] Re: Add support for kernels compiled with CONFIG_EFI_ZBOOT
** 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 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:
Triaged
Status in grub2 source package in Focal:
New
Status in grub2-unsigned source package in Focal:
New
Status in linux source package in Focal:
New
Status in grub2 source package in Jammy:
New
Status in grub2-unsigned source package in Jammy:
New
Status in linux source package in Jammy:
New
Status in grub2 source package in Lunar:
New
Status in grub2-unsigned source package in Lunar:
New
Status in linux source package in Lunar:
New
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
[Kernel-packages] [Bug 2002226] Re: Add support for kernels compiled with CONFIG_EFI_ZBOOT
** 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 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:
Triaged
Status in grub2 source package in Focal:
New
Status in grub2-unsigned source package in Focal:
New
Status in linux source package in Focal:
New
Status in grub2 source package in Jammy:
New
Status in grub2-unsigned source package in Jammy:
New
Status in linux source package in Jammy:
New
Status in grub2 source package in Lunar:
New
Status in grub2-unsigned source package in Lunar:
New
Status in linux source package in Lunar:
New
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
