*** This bug is a duplicate of bug 1845289 ***
https://bugs.launchpad.net/bugs/1845289
Still broken here(which includes an apt-get update and apt-get dist-
upgrade today).
Versions of grub installed:
ii grub-common2.04-1ubuntu12.1
ii grub-efi-amd64
*** This bug is a duplicate of bug 1845289 ***
https://bugs.launchpad.net/bugs/1845289
The issue has been resolved for me when in grub version
2.04-1ubuntu12.1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1845289 ***
https://bugs.launchpad.net/bugs/1845289
** This bug has been marked a duplicate of bug 1845289
Grub EFI amd64 no longer start EFI/Microsoft/Boot/bootmgfw.efi
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I tested 2.04-1ubuntu12.1 with ubuntu-linuxefi.patch on Lenovo Yoga C630
WOS and I can confirm that booting Windows 10 works fine now.
--
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:
activated the proposed deposits and updated.
now with grub 2.04-1ubuntu12.1 all right
--
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
thank you
Il giorno dom 10 nov 2019 alle ore 04:45 Steve Langasek <
steve.langa...@canonical.com> ha scritto:
> ok if this is reproducible for you even using the unsigned shim from the
> ppa, then this seems to require further investigation.
>
> ** Changed in: grub2 (Ubuntu)
>Status:
To answer my own comment #23.
I managed to work around this like this:
* Forcing Windows 10 to use \EFI\ubuntu\shimx64.efi as in "bcdedit /set
{bootmgr} path \EFI\ubuntu\shimx64.efi"
* Changing BIOS setup to use Secure Boot (Didn't have it, didn't want it. never
had it).
Not both ubuntu and
I can confirm it happens to me to in amd64 PC.
Here is the info of the package installed right now:
Package: grub2
Version: 2.04-1ubuntu12
Priority: extra
Section: universe/admin
Origin: Ubuntu
Maintainer: Ubuntu Developers
Original-Maintainer: GRUB Maintainers
Bugs:
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/1839317
Title:
ok if this is reproducible for you even using the unsigned shim from the
ppa, then this seems to require further investigation.
** Changed in: grub2 (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
thanks for the support.
I tried to install shim unsigned but without success.
if the secure boot is active, grub works correctly.
if inactive grub does not launch windows.
tried on my 2 acer notebooks (Aspire E 5 and the v-371)
Il giorno lun 4 nov 2019 alle ore 21:30 Steve Langasek <
The standard UEFI boot path for Ubuntu is always to boot via shim and
then to grub.
But we also know that the signed shim binary we currently have for arm64
is broken on this architecture.
The fixed shim is in the process of being signed and in the meantime
this is simply an unsupported
I have the same issue. Dual boot does not work anymore, Windows does not
boot.My notebooks are acer aspire e 15 and acer - 371
if active, secure boot grub works
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have the same issue. Dual boot does not work anymore, Windows does not
boot.My notebooks are acer aspire e 15 and acer - 371
--
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
I'm testing the fix for a similar amd64 bug 1845289 but I have a feeling
it may also help on arm64. Feel free to test it https://launchpad.net
/~xeron-oskom/+archive/ubuntu/grub2.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
My notebook is HP ProBook 470 G4
--
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 on aarch64 laptops
To manage notifications about this
I have the same issue. Dual boot does not work anymore, Windows does 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/1839317
Title:
Grub fails to chainload the Windows Boot Manager on
** Summary changed:
- Grub fails to chainload the Windows Boot Manager
+ Grub fails to chainload the Windows Boot Manager on aarch64 laptops
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1839317
I have the same problem. To clarify, I can't boot into Windows from
Grub, but can boot into Ubuntu. When I get into Ubuntu, I run the Boot
Repair application, and after I shut down or restart, I can get into
Windows. But once, I shut down Windows or restart, Grub won't allow me
to reboot into
> I'm also facing the same problem and I found a solution which worked
for me on amd64.
Doesn't work for me on aarch64: Bug 1849863
--
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:
I'm also facing the same problem and I found a solution which worked for
me on amd64. My system is using UEFI without secure boot from a gpt
partitioned drive.
Please try to install the package shim-signed.
This fixed the problem for me. Chainloading Windows even works after
uninstalling the
I am facing the same bug, can't boot into windows.
After updating to Ubuntu 19.10.
--
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
I have the same issue.
I can boot Windows 10 from BIOS/EFI boot menu, but can't boot it from
grub. Setting debug=chain shows that grub tries to use SecureBoot, but
it's disabled.
Wiping my grub installation, downgrading to 2.02 from disco and
reinstalling it fixed the issue.
--
You received
** Tags added: eoan
--
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 about this bug go to:
Tried with
set debug=chain
got the following messages (grub 2.04-1ubuntu5, AMD64 arch, ubuntu
19.10):
loader/efi/chainloader.c:1057: linuxefi_secure_validate: 1
loader/efi/chainloader.c:262: No shimlock protocol
loader/efi/chainloader.c:537: Secure boot is not enabled
alloc magic is broken at
> Worked with 2.0.2?
Worked with 2.0.2 from ppa:aarch64-laptops/grub
--
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
For me is reproducible on AMD64: windows 10 EFI boot entry not boots any
more. Worked with 2.0.2?
--
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
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
** Tags added: id-5d54272634ee9a39ad7f9cb3
--
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 about this bug go
I also found this bug is reproducible on my Lenovo Yoga C630 WOS with
grub2 from Eoan repository.
--
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
I have also experienced this issue on AArch64 Lenovo C630 - using Eoan
Grub.
--
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
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
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/1839317
Title:
** Package changed: grub (Ubuntu) => grub2 (Ubuntu)
** Changed in: grub2 (Ubuntu)
Importance: Undecided => Critical
--
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
34 matches
Mail list logo
