Donald,
I'm very sorry that you're having this experience. It is definitely
unrelated to the particular bug this report is about, which, if you were
experiencing, would prevent you from ever seeing a GRUB menu.
Have you tried booting the older 5.8.0-59-generic kernel that is still
installed on
^ Shot showing both failed Ubuntu recovery modes
-D.
** Attachment added: "ubuntu_recovery.jpeg"
https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1925010/+attachment/5508619/+files/ubuntu_recovery.jpeg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925010
Title:
shim-signed 15.4 does not boot on EFI 1.10 systems
To manage notifications about this bug go to:
^ Here are some screenshots.
-D.
** Attachment added: "stuck_loading_ram_disk.jpeg"
https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1925010/+attachment/5508617/+files/stuck_loading_ram_disk.jpeg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hi Julian,
I tried booting Windows via grub and EFI, and Windows tries to repair
itself unsuccessfully.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925010
Title:
shim-signed 15.4 does not boot
Hi, Donald: Your issue is different. Here you can't even get to the grub
menu. If you can't boot into Windows either (did you try that from grub,
or directly from the EFI boot menu [I think it's F12 or F10 or something
you need to press at startup and select Windows]), that sounds more like
a
Hi -
I believe I'm experiencing this issue on my Thinkpad X1 Extreme (Gen1).
I set up a dual-boot, Ubuntu (Groovy) and Win11 beta. I'd be able to
select my OS in a Grub2 menu, after the Lenovo splash screen on start
up.
When I was navigating Ubuntu today, I was notified of the available
upgrade
Same binaries across all releases, so the verification on hirsute is
valid elsewehre too.
** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Please open a new bug for that pfaelzerchen, using ubuntu-bug shim on
your home server, and provide appropriate logs as documented in
https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1928434
Also check if shim actually loaded grub, and if so, enable grub debug mode, set
debug=all
- maybe
Sorry, to bother you. I am not sure, if this relates to this bug.
After Upgrades from 20.10 to 21.04 were enabled, I upgraded both of my
20.10 systems to 21.04. On my Intel NUC10 everything worked fine. But my
home server were not able to boot anymore. The above-mentioned
workaround (replace
** Changed in: shim (Ubuntu Xenial)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925010
Title:
shim-signed 15.4 does not boot on EFI 1.10 systems
To
We are blocked on
https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1928434
and resolving
https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1924605
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Should I still be getting "No new release found." when trying to upgrade
an xubuntu 20.10 system to 21.04?
It's a bit odd since I have two systems running xubuntu, I upgraded one
a few days ago from 20.10 to 21.04 (using do-release-upgrade) but the
other system still keeps saying "No new release
Possibly related - https://bugs.launchpad.net/ubuntu/+bug/1928455
(hirsute, user failing 'fix' causes system to not boot)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925010
Title:
shim-signed
Hello Balint, or anyone else affected,
Accepted shim into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/shim/15.4-0ubuntu2 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
No. Shim 15.4 upstream is broken. The 15.4-0ubuntu2 includes an
additional patch that fixes the problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925010
Title:
shim-signed 15.4 does not boot
I think the title of this bus is misleading, isn't it?
"shim-signed 15.4 does not boot on EFI 1.10 systems"
shim-signed 15.4 is not affected, it's the fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thank you!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925010
Title:
shim-signed 15.4 does not boot on EFI 1.10 systems
To manage notifications about this bug go to:
This bug was fixed in the package shim-signed - 1.47
---
shim-signed (1.47) impish; urgency=medium
[ Balint Reczey ]
* Fix boot on EFI 1.10 machines, for example on some MacBooks (LP: #1925010)
[ Dimitri John Ledkov ]
* Fix kernel warning when allocating MOK table (LP:
This bug was fixed in the package shim - 15.4-0ubuntu2
---
shim (15.4-0ubuntu2) hirsute; urgency=medium
[ Balint Reczey ]
* Fix boot on EFI 1.10 machines, for example on some MacBooks (LP: #1925010)
[ Dimitri John Ledkov ]
* Fix kernel warning when allocating MOK table (LP:
Fresh installed HH final ISO alongside Windows 10 secure boot enabled.
Proposed must be enabled in Hirsute (9 packages):
sudo apt install shim-signed
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages will be upgraded:
Verified 1.47+15.4-0ubuntu2 on Hirsute on the MacBook Air (MBA 5,2) I
have first observed the problem:
rbalint@chaos:~$ sudo apt install shim-signed
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages will be upgraded:
I tested on a MacBookPro9,2 (13-Inch, Mid-2012).
0. I clean installed from the 21.04 release image
(http://releases.ubuntu.com/21.04/ubuntu-21.04-desktop-amd64.iso). FWIW
I made my usual choices
- Minimal installation
- Download updates…
- Install third-party software…
On Fri, May 07, 2021 at 03:24:15PM -, Alexander Browne wrote:
> If I do the workaround described in comment #14 in order to get my
> MacBook to boot, and then install the shim-signed package from
> -proposed, will that be a valid test that the new package is working?
Yes.
--
You received
If I do the workaround described in comment #14 in order to get my
MacBook to boot, and then install the shim-signed package from
-proposed, will that be a valid test that the new package is working?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hello Balint, or anyone else affected,
Accepted shim into hirsute-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/shim/15.4-0ubuntu2 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
This bug was fixed in the package shim-signed - 1.47
---
shim-signed (1.47) impish; urgency=medium
[ Balint Reczey ]
* Fix boot on EFI 1.10 machines, for example on some MacBooks (LP: #1925010)
[ Dimitri John Ledkov ]
* Fix kernel warning when allocating MOK table (LP:
** Description changed:
The latest update on Hirsute made the MacBook Air from 2012 unbootable.
It could be recovered by booting a 20.04 live CD, downloading 20.04's
shim package and overwriting the files in EFI/ubuntu and EFI/BOOT with
the files shipped in the shim package.
By now, the package is available in Impish-Proposed only. Tested today
in Ubuntu 21.10 (20210501 ISO). All good for a second time. EFI 2.60
Lenovo/Ryzen 2700.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
So the question remains, when the normal upgrade path from 20.10 to
21.04, that was stopped because of this bug, will be available.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925010
Title:
This new shim package fixes secure boot when booting an unsigned Kernel.
Impish Indru Kubuntu 21.10. Thanks for the fix
2021-04-30 18:34:28 upgrade shim-signed:amd64 1.46+15.4-0ubuntu1
1.47+15.4-0ubuntu2
mokutil --sb
SecureBoot enabled
SecureBoot validation is disabled in shim
uname -srm
Linux
This bug was fixed in the package shim - 15.4-0ubuntu2
---
shim (15.4-0ubuntu2) hirsute; urgency=medium
[ Balint Reczey ]
* Fix boot on EFI 1.10 machines, for example on some MacBooks (LP: #1925010)
[ Dimitri John Ledkov ]
* Fix kernel warning when allocating MOK table (LP:
For your information, I have an HP EliteBook 840 G2, I did a fresh
install of 21.04 and had the same issue, it uses an "EFI v2.31 by HPQ".
I used following work around which worked.
What made the trick was the following changes in the BIOS Setup (after computer
start push F10 - go to System
> Anyone think these are the same bug?
No. This bug only affects very old EFI implementations (over a decade old).
To my knowledge, only Apple ever shipped hardware using such
implementations. Certainly, any Lenovo systems from 2015 were shipping EFI
2.0.
--
You received this bug notification
This bug seems quite similar to the one I reported:
Ubuntu 20.04 LTS Fails to boot on Lenovo Flex 3-1480 laptop: Bug #1925710
As my bug explains, my 2015 Flex 3-1480 has a similar boot issue
problem, though my 2019 Acer E15 Aspire E5-576 boots just fine.
Anyone think these are the same bug?
--
FWIW, "during the life cycle" = "today" - the revocations for the old
shims have been published today: https://uefi.org/revocationlistfile
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925010
Title:
> Yes, and why can't we use the old binaries that worked before?
That's exactly what we're recommending you do by not upgrading to Ubuntu
21.04 until a newer fixed version is available.
We did not roll back shim in hirsute to the previous version because
that version is expected to be revoked by
Yes, and why can't we use the old binaries that worked before?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925010
Title:
shim-signed 15.4 does not boot on EFI 1.10 systems
To manage
The Ubuntu shim binaries must be signed by microsoft in order to be
useable on SecureBoot-enabled systems. We are currently waiting for
these binaries to work through the process.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
So couldn't we just put that version of shim into Ubuntu 21.04, or do we
have to wait for the maintainers to do a release first? (Just curious
about this.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Yes, it's exactly the same.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925010
Title:
shim-signed 15.4 does not boot on EFI 1.10 systems
To manage notifications about this bug go to:
Is this bug related, by any chance to this patch
(https://github.com/rhboot/shim/pull/364)?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925010
Title:
shim-signed 15.4 does not boot on EFI 1.10
That is not the same issue. Please file a separate bug report.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925010
Title:
shim-signed 15.4 does not boot on EFI 1.10 systems
To manage
I have the same issue with secure boot enabled. Unsigned kernel
5.12-rc7+8 won't boot unless secure boot is disabled: invalid signature.
Mok manager is not responding. ThinkPad Kubuntu or Ubuntu 21.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This was a problem for me with kubuntu 21.04 as well on a MacBookPro
11,2. The workaround did the trick. Exact workaround command follows:
/boot/efi/EFI# cp -b ubuntu/grubx64.efi ubuntu/shimx64.efi
/boot/efi/EFI# cp -b ubunt/grubx64.efi BOOT/BOOTX64.EFI
This works immediately.
--
You
** Changed in: shim (Ubuntu Hirsute)
Status: Confirmed => In Progress
** Changed in: shim-signed (Ubuntu Hirsute)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
FWIW Upgrading worked fine, system boots normally and everything works
apart from a Failed to start MokListXRT, out of resources message before
the window manager loads.
This is on a Thinkpad with EFI v2.31 by Lenovo
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Seems that my late-2012 Mac Mini is also suffering the same problem.
I'll try the fixes as described above later on.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925010
Title:
shim-signed 15.4
Comment #2 also fixed this issue for my MacBookAir4,2 machine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925010
Title:
shim-signed 15.4 does not boot on EFI 1.10 systems
To manage
Also got hit with this on my MacBookAir4,2 machine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925010
Title:
shim-signed 15.4 does not boot on EFI 1.10 systems
To manage notifications about
** Also affects: shim (Ubuntu Hirsute)
Importance: High
Status: Confirmed
** Also affects: shim-signed (Ubuntu Hirsute)
Importance: Undecided
Status: Confirmed
** Changed in: shim (Ubuntu Hirsute)
Milestone: None => hirsute-updates
** Changed in: shim-signed (Ubuntu
** Summary changed:
- shim-signed does not boot on MBA 5,2
+ shim-signed 15.4 does not boot on EFI 1.10 systems
** Description changed:
The latest update on Hirsute made the MacBook Air from 2012 unbootable.
It could be recovered by booting a 20.04 live CD, downloading 20.04's
shim
52 matches
Mail list logo
