Public bug reported:
Support for the Lenovo Yoga C630 was added to mainline in v5.4.
Ubuntu Eoan will be released based on v5.3, thus the latest release will
not boot.
This would be a shame, as one of the first laptops based on AArch64 it's
a ground breaking piece of H/W.
** Affects: linux
With `set debug="chain,secureboot,dl"` added to the Grub menu entry, we
get a flash of:
SecureBoot: 0
SetupMode: 0
linuxefi_secure_validate: 1
No shimlock protocol loader/efi/chainloader: Secure boot is not enabled
Looks like Grub is insisting on Secure Boot, which we need to disable in
I should add that I experienced this on an AArch64 platform.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1839317
Title:
Grub fails to chainload the Windows Boot Manager
To manage notifications
Public bug reported:
After an update to 2.04 Grub fails to chainload into Windows.
When selecting the menu item to boot into the Windows Boot Manager, the
menu flashes and returns.
When trying to chainload/boot via the Grub command line, nothing happens
and the prompt reappears.
When using the
Private bug reported:
In the past, when booting Linux on non-(x84_64|i386) machines, it was a
requirement to configure and build Linux kernels tailored specifically
for a particular device. Now, after many efforts ("one image to rule
them all" and the like) to unify and consolidate vendor
