group.of.nepali.translators team mailing list archive

[Yuan-Chen Cheng <yc.cheng@xxxxxxxxxxxxx>]

** Also affects: oem-priority
   Importance: Undecided
       Status: New

** Changed in: oem-priority
   Importance: Undecided => Critical

** Changed in: oem-priority
       Status: New => Triaged

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1785033

Title:
  GRUB needs to support 64-bit efi linear frame buffer address

Status in HWE Next:
  In Progress
Status in OEM Priority Project:
  Triaged
Status in grub2 package in Ubuntu:
  New
Status in grub2 source package in Trusty:
  New
Status in grub2 source package in Xenial:
  New
Status in grub2 source package in Bionic:
  New
Status in grub2 source package in Cosmic:
  New

Bug description:
  [Rationale]
  More firmwares support above 4G mmio configureation and the EFI Graphics Output Protocol can return a 64-bit linear frame buffer address have been implemented in some firmware/BIOS. Grub2 currently only pass 32-bit framebuffer base to kernel. The Linux kernel has already added support to handle 64-bit linear framebuffer address in the efifb driver now. So GRUB2 should support 64-bit EFI linear frame buffer address.

  [Impact]
  Some machines block booting with firmware/bios implemented 64-bit EFI linear frame buffer address,due to Grub passing incorrect(only 32-bit) EFI linear frame buffer.

  [Test cases]

  Need Bios/Firmware support,
  1) Make sure the machine with the Bios implemented 64-bit EFI linear frame buffer address. some machine need to enable above 4G mmio on bios setup menu.
  2) Boot up.

  [Solution]
  A patch has been committed and accepted by maintainer
  http://git.savannah.gnu.org/cgit/grub.git/commit/?id=886edba8770ccbc3def0af2a7d6b346d00d0af2f

  [Regression Potential]
  Minimal, it's unlikely completing the whole framebuffer address will affect those which hasn't used above 32-bits framebuffer address.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1785033/+subscriptions