[Bug 1091464] Re: Unable to chainload Windows 8 with Secure Boot enabled

[Ubfan]

On a just updated 13.10 (Nov 15) getting shim-signed 1.5 and a new signed grubx64.efi 2.00..-19 I see no change in the error.
The UnknownMessage (hex 12)  or decimal 18 is indeed an invalid subtype for the messaging type (last valid subtype is decimal 15), so looks like leftover garbage in the path buffer?  Why is grub even in the messaging type anyway for a hard disk boot?  The beginning of the reported path looks just like a network boot looks from efibootmgr -v output.  Should the valid path start at the /HD...?  If someone without the problem could look at what the actual path chainloader is using could confirm that the /ACPI is present and working on their system we could eliminate leftover garbage in the grub path buffer as the problem.

-- 
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/1091464

Title:
  Unable to chainload Windows 8 with Secure Boot enabled

Status in “grub2” package in Ubuntu:
  Incomplete

Bug description:
  I've been working with Yannubuntu and he suggested I post a bug here.
  Here's what I did.

  Received a brand new Dell XPS13 laptop with Windows8 pre-installed
  with both UEFI and SecureBoot enabled.    After playing around,
  decided to wipe everything and create a dual boot configuration with
  both Windows 8 and Ubuntu 12.10.  Steps:

  1. Install Windows 8 via Dell supplied recovery media in UEFI mode.  The installer will create the /boot/efi, recovery and main partition.  
  2. Use Windows 8 to resize hard drive down to 50GB.  Use the rest for Ubuntu.
  3. Verify the computer boots successfully to Windows 8 with UEFI and Secure Boot enabled.
  4. Boot with USB Ubuntu install media and select 'do something else' to create partitions and indicate /boot/efi
  5. Let the install complete.  Normally here, I run boot repair because the signed bootloader doesn't seem to install.  In boot repair, I use advance options, indicate where the EFI boot should go, primary OS (ubuntu) and select SecureBoot.
  6. Now, everything is configured as I want it.  Upon boot up, the computer will boot to grub and then I can go to either Ubuntu or Windows UEFI.  
  7. Upon selecting Windows UEFI, I get the error:

   /EndEntire
  file path: /ACPI(a0341d0,0)/PCI(2,1f)/UnknownMessaging(12)/HD(2,96800,32000,7c043777b8608641,87,f6)/File(\EFI\Microsoft\Boot)/File(bootmgfw.efi)/EndEntire
  error: cannot load image

  8.  If I swap the order in the BIOS to boot to Windows first (with UEFI and Secure Boot) it directly boots to Windows so I know the EFI boot files are working.
  9. If I go back to my original configuration (e.g. Ubuntu first) with UEFI, but Secure Boot disabled, then the system is able to successfully chainload the MSFT boot files.

  My gut tells me that grub is unable to chainload to an OS (or maybe
  just windows 8) which is expecting a secure boot to be initiated from
  the UEFI bios.

  As a work around, I have disabled Secure Boot, but I'd like my
  ultimate configuration to support Secure Booting to either Ubuntu or
  Windows 8 via grub.

  Thanks,

  Neeraj

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