[Bug 1591818] Re: Add support for running a 64-bit Linux kernel on a 32-bit EFI.

[Adam Conrad]

Hello Shih-Yuan, or anyone else affected,

Accepted grub2-signed into trusty-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/grub2-signed/1.34.13 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: grub2-signed (Ubuntu Trusty)
       Status: New => Fix Committed

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

Title:
  Add support for running a 64-bit Linux kernel on a 32-bit EFI.

Status in OEM Priority Project:
  New
Status in OEM Priority Project trusty series:
  New
Status in grub2 package in Ubuntu:
  Fix Released
Status in grub2-signed package in Ubuntu:
  Fix Released
Status in grub2 source package in Trusty:
  Fix Committed
Status in grub2-signed source package in Trusty:
  Fix Committed

Bug description:
  [Impact]

  * Some platforms only have 32-bit EFI BIOS. When executing `grub-
  install` on them, it will make the system can not boot up again
  because of the wrong GRUB EFI payload and UEFI boot entry.

  [Test Case]

  * Executing `grub-install` on a 32-bit EFI platform should appear the
  following results.

  $ sudo grub-install
  Installing for i386-efi platform.
  Installation finished. No error reported.

  $ sudo efibootmgr -v
  BootCurrent: 0000
  Timeout: 0 seconds
  BootOrder: 0000
  Boot0000* ubuntu	HD(1,GPT,b8d7d8e9-4ac4-46cc-8bd0-8d90d6df1df4,0x800,0x100000)/File(\EFI\ubuntu\grubia32.efi)

  * Executing `grub-install` on a 64-bit EFI platform should appear the
  following results.

  $ sudo grub-install
  Installing for x86_64-efi platform.
  Installation finished. No error reported.

  $ sudo efibootmgr -v
  BootCurrent: 0000
  Timeout: 0 seconds
  BootOrder: 0000
  Boot0000* ubuntu	HD(1,GPT,b8d7d8e9-4ac4-46cc-8bd0-8d90d6df1df4,0x800,0x100000)/File(\EFI\ubuntu\shimx64.efi) or \EFI\ubuntu\grubx64.efi if there is no grub-efi-amd64-signed installed.

  [Regression Potential]

  * This patch is directly backported from Ubuntu 16.04 so it should be
  OK without any regression.

  [Other Info]

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu
  Ubuntu 14.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center
  grub2 2.02~beta2-9ubuntu1.8

  3) What you expected to happen
  Executing `grub-install` will install platform files by i386-efi on 32-bit UEFI BIOS.

  4) What happened instead
  It installed platform files by x86_64-efi instead.

  P.S. Ubuntu 16.04 doesn't have this issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1591818/+subscriptions