[Bug 1302939] Re: Installing Ubuntu 14.04 on Lenovo H520 leads to unbootable system

[Launchpad Bug Tracker]

[Expired for ubiquity (Ubuntu) because there has been no activity for 60
days.]

** Changed in: ubiquity (Ubuntu)
       Status: Incomplete => Expired

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

Title:
  Installing Ubuntu 14.04 on Lenovo H520 leads to unbootable system

Status in “ubiquity” package in Ubuntu:
  Expired

Bug description:
  System: Lenovo H520

  The system uses UEFI, I tried several combinations of settings.

  With UEFI mode enabled, SecureBoot enabled:

  * After the initial installer reboot the system boots with an error:
  "Invalid Signature Detected".

  With UEFI mode enabled, SecureBoot enabled and Setup Mode enabled:

  * After the initial installer reboot the system boots successfully.
  Subsequent reboots lead to the error: "Error 1962 No operating system
  found"

  With UEFI mode enabled, SecureBoot disabled:

  * The system always reboots to the error: "Error 1962 No operating
  system found"

  It appears that something in Lenovo's UEFI does not like how the efi
  boot parameters are configured by Ubuntu. On the first reboot the
  parameters display the ubuntu entry with a hard drive specification.
  On the subsequent reboots the system UEFI appears to replace the
  setting with the value "Vendor(99e275e7-75a0-4b37-a2e6-c5385e6c00cb,)
  ". I haven't been able to find out which Vendor that UUID represents.
  However, looking in the UEFI boot settings after this shows ubuntu
  listed in the boot order under an "Unknown device".

  As a workaround, I enabled CSM mode and set the system to "Legacy
  BIOS" and installed Ubuntu 14.04 successfully with no booting issues.
  However, I now lost the additional protection of a signed bootloader
  and a non-technical person would not find this fiddling in the bios
  settings to be a good user experience.

  Expected behavior:

  The Ubiquity installer could configure the EFI boot parameters in such
  a way that they are more generally recognizable by different UEFI
  implementations. In this particular case the UEFI was not
  understanding the settings as the SATA1 device but instead marked them
  as "Unknown device".

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