grub2-signed (1.142.8) focal; urgency=medium
* Rebuild against grub2 2.04-1ubuntu26.6.
-- Dimitri John Ledkov Thu, 01 Oct 2020 23:30:47
+0800
Has been in focal-updates since 2020-10-26.
** Changed in: grub2-signed (Ubuntu Focal)
Status: Fix Committed => Fix Released
--
You receive
This bug was fixed in the package grub2 - 2.04-1ubuntu26.6
---
grub2 (2.04-1ubuntu26.6) focal; urgency=medium
* postinst.in, grub-multi-install: fix logic of skipping installing onto
any device, if one chose to not install bootloader on any device. LP:
#1896608
* Do not fi
setup the VM and enrolled keys.
Checked that grub live-server iso arm64 boots; and focal 20.04.1 does
not.
Disabled secureboot, installed focal; upgraded to grub2 packages from
proposed i.e. 2.04-1ubuntu26.6 & 1.142.8+2.04-1ubuntu26.6.
rebooted, enabled secureboot.
horay system boots correctly
** Tags added: fr-23
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1862279
Title:
arm64 Secure Boot fails w/ "error: cannot load image."
To manage notifications about this bug go to:
https://bugs.l
Hello dann, or anyone else affected,
Accepted grub2 into focal-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/grub2/2.04-1ubuntu26.6
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.u
** Changed in: grub2 (Ubuntu Focal)
Status: Won't Fix => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1862279
Title:
arm64 Secure Boot fails w/ "error: cannot load image."
To manage
Marking verification-failed due to bug 1897819
** Tags removed: verification-done verification-done-focal
** Tags added: verification-failed verification-failed-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
Finally ...
4a) Verify that it's broken after rollback of grub:
```
$ sudo eatmydata apt install ~i~ngrub/focal -V
[...]
The following packages will be DOWNGRADED:
grub-common (2.04-1ubuntu26.5 => 2.04-1ubuntu26.4)
grub-efi-arm64 (2.04-1ubuntu26.5 => 2.04-1ubuntu26.4)
grub-efi-arm64-bin
WIP, current state:
$ sudo dpkg -l grub-efi-arm64-signed shim-signed
[...]
ii grub-efi-arm64-signed 1.142.7+2.04-1ubuntu26.5 arm64 [...]
ii shim-signed 1.40.4+15+1552672080.a4a1fbe-0ubuntu2 arm64 [...]
ubuntu@instance-1:~$ sudo mokutil --sb-state
SecureBoot enabled
ubuntu@
Hello dann, or anyone else affected,
Accepted grub2 into focal-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/grub2/2.04-1ubuntu26.5
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.u
This bug was fixed in the package grub2 - 2.04-1ubuntu34
---
grub2 (2.04-1ubuntu34) groovy; urgency=medium
* configure.ac: one more dejavu font search path
-- Dimitri John Ledkov Mon, 14 Sep 2020 10:53:07
+0100
** Changed in: grub2 (Ubuntu Groovy)
Status: Fix Committed =
** Changed in: grub2-signed (Ubuntu Focal)
Status: Triaged => In Progress
** Changed in: grub2 (Ubuntu Focal)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
** Description changed:
[Impact]
Kernels are not loaded on arm64 since grub2 2.04 rebase
[Test case]
1. Boot qemu
qemu-system-aarch64 -m 1024 -cpu cortex-a53 -M virt -pflash
~/AAVMF_CODE.fd -pflash ~/AAVMF_VARS.fd -drive
if=none,file=/home/jak/Downloads/focal-server-cloudimg
** Description changed:
- I tested out the new shim-signed (1.41+15+1552672080.a4a1fbe-0ubuntu1)
- on arm64 today. Unfortunately, I was unable to boot a kernel. I tried
- manually running commands in the GRUB shell to try and get more info,
- and here's the error I get:
+ [Impact]
+ Kernels are no
After working on LP: #1892770, I think that this is the same problem.
grub in focal/arm64 is trying to use EFI boot services to start the
kernel, after having verified the kernel with the shim. EFI does not
have access to the cert in the shim so it refuses to load the kernel.
There is a workaround
See ubuntu-bug 1890983
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1862279
Title:
arm64 Secure Boot fails w/ "error: cannot load image."
To manage notifications about this bug go to:
https://bugs
Robert Browne (rob): Please open a separate issue with ubuntu-bug
grub-efi-amd64-signed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1862279
Title:
arm64 Secure Boot fails w/ "error: cannot loa
Upgraded grub-efi-amd64 to 2.04-1ubuntu26.2
4 kernels and recovery in menu none boot
So also effects AMD64
Disable secureboot allows kernel to boot
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1862279
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: grub2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1862279
Title:
arm6
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: grub2-signed (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1862279
Title:
** Tags added: id-5e67b5f44d0dff7b9bbf1d1a
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1862279
Title:
arm64 Secure Boot fails w/ "error: cannot load image."
To manage notifications about this bug
I've nearly completed the rebase - here's what I have so far:
https://git.launchpad.net/~dannf/grub/log/?h=secureboot-rebase
However, it fails to build on armhf now due to the changes in how the fdt
module is built:
https://launchpad.net/~dannf/+archive/ubuntu/test/+build/18793364
(That's a l
** Changed in: shim (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1862279
Title:
arm64 Secure Boot fails w/ "error: cannot load image."
To manage notification
I've compared the list of patches squashed into the ubuntu-
linuxefi.patch we have in focal with the current set of patches in the
fedora-32 branch of https://github.com/rhboot/grub2, which is the
upstream for our SB patches AIUI. There has been some rework of the
linuxefi command since the version
I've got a hacked together focal-based GRUB I created by replacing some
patches w/ updated versions from the rhboot repository. It still need
quite a bit of cleanup though.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
also note that the previous version of shim did not work on arm64 AT
ALL. This version of shim we just got signed is the first one with
arm64 support.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/186
@juliank: The shim build is the same in both cases. The only difference
is that one is signed by MS, the other self-signed. I did notice that
key enrollment didn't work in my guest, which maybe a failure to execute
mma64.efi, and therefore maybe related to bug 1864223.
My hypothesis is that the SB
Does it work with new grub and old shim, though? As we think new shim is
somewhat buggy, it also fails to load fwupd on x86.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1862279
Title:
arm64 Secure
Upstream GRUB 2.02 also fails - so there's likely something in the disco
patchset that is required.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1862279
Title:
arm64 Secure Boot fails w/ "error: ca
The issue seems to be related to GRUB. If I upgrade my working-in-SB-
disco VM to focal's grub-efi-arm64-signed, it now fails. If I downgrade
my *not*-working-in-SB-focal VM to disco's grub-efi-arm64-signed, it now
boots in SB mode.
** Also affects: grub2 (Ubuntu)
Importance: Undecided
S
It does not appear to be an issue with the signed kernel - the same one
that fails to build in my focal/MS-signed VM does boot when installed in
the disco/self-signed VM.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
I dug up my arm64/disco VM that I had hacked up to test this shim build
before MS had signed it:
ubuntu@disco:~$ sudo mokutil --sb-state
SecureBoot enabled
So what's the relevant difference between this working config and the
broken one?
Looks like I had set it up following:
https://wiki.archl
le sigh
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1862279
Title:
arm64 Secure Boot fails w/ "error: cannot load image."
To manage notifications about this bug go to:
https://bugs.launchpad.net/
33 matches
Mail list logo
