[Bug 1845289] Re: Grub EFI amd64 no longer start EFI/Microsoft/Boot/bootmgfw.efi

Ivan Larionov 1845289 at bugs.launchpad.net
Wed Oct 30 20:50:15 UTC 2019


This patch may be wrong but it fixes the issue for me. I already tested
it on my actual system (not just VirtualBox).

Now to your comments:


1. shim is not dependency of grub2. My 18.04, 18.10 and 19.04 installations had only these packages and no shim:

grub-common, grub2-common, grub-efi-amd64, grub-efi-amd64-bin

Shim is not required on non-SB systems. Ubuntu supported direct usage of
grub without shim since forever and I see no reason to drop such
support. If you're sure shim is required then make it dependency of the
grub.

I didn't use boot-repair. I simply updated from 19.04 (without shim) to
19.10 (still without shim) which broke chainload.


2. You're right. While I don't exactly understand what grub_loader_set() does:

grub_loader_set (grub_secureboot_chainloader_boot,
grub_secureboot_chainloader_unload, 0);

but I took a look at grub_secureboot_chainloader_boot() and it indeed
gets 0 from handle_image()/read_header() and expected to call
grub_load_and_start_image(). However on my system the latest log record
comes from:

grub_dprintf ("chain", "Secure Boot is not enabled\n");

and then I guess from grub_load_and_start_image() it immediately goes
back to the menu.

This is the last page of logs with "debug=all" –
https://i.imgur.com/PFRSqg8.png

This screenshot has been taken using the latest grub2 from eoan without
any custom patches. If you want to see full video of boot process send
me a message using https://launchpad.net/~xeron-oskom/+contactuser.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to grub2 in Ubuntu.
https://bugs.launchpad.net/bugs/1845289

Title:
  Grub EFI amd64 no longer start EFI/Microsoft/Boot/bootmgfw.efi

Status in grub2 package in Ubuntu:
  Incomplete
Status in grub2 source package in Eoan:
  Confirmed

Bug description:
  On a dual boot computer with Windows 10 Pro and Ubuntu 19.10, since a
  month, Grub was unable to boot Windows 10. Hitting the Windows entry
  line give me a 0.1s black screen and get me back to Grub Menu.

  sudo update-grub give me :

  Sourcing file `/etc/default/grub'
  Sourcing file `/etc/default/grub.d/init-select.cfg'
  Generating grub configuration file ...
  Found linux image: /boot/vmlinuz-5.3.0-10-generic
  Found initrd image: /boot/initrd.img-5.3.0-10-generic
  Found Windows Boot Manager on /dev/sda1@/EFI/Microsoft/Boot/bootmgfw.efi
  Adding boot menu entry for EFI firmware configuration
  done

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: grub-efi-amd64 2.04-1ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 25 08:01:05 2019
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: grub2
  UpgradeStatus: Upgraded to eoan on 2018-11-14 (314 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1845289/+subscriptions



More information about the foundations-bugs mailing list