Doesn't support UEFI installation.

Bug #1300910 reported by Blake Rouse
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
curtin
Fix Released
High
Unassigned
curtin (Ubuntu)
Fix Released
High
Unassigned

Bug Description

Running the curt installer on a machine that was booted with UEFI fails to partition and install grub correctly. For UEFI support curt installer needs to handle UEFI booting machines, and UEFI booting with SecureBoot.

curt installer does not error on installation, but the machine will fail to boot with UEFI. Machines that support UEFI and legacy BIOS, will boot correctly, due to the legacy support.

Related branches

Scott Moser (smoser)
Changed in curtin:
status: New → Confirmed
importance: Undecided → High
Changed in curtin (Ubuntu):
status: New → Confirmed
importance: Undecided → High
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package curtin - 0.1.0~bzr124-0ubuntu1

---------------
curtin (0.1.0~bzr124-0ubuntu1) trusty; urgency=medium

  * New upstream snapshot.
    * install correctly on UEFI booted systems (LP: #1300910)
      [Blake Rouse]
    * whitespace fixes and other small fixes.
 -- Scott Moser <email address hidden> Thu, 03 Apr 2014 14:47:01 -0400

Changed in curtin (Ubuntu):
status: Confirmed → Fix Released
Scott Moser (smoser)
Changed in curtin:
status: Confirmed → Fix Committed
Revision history for this message
Steve Si (steve2926) wrote :

Ubuntu Desktop amd64 16.04.01

Install in UEFI VirtualBox VM to new unformatted .vdi virtual disk. (also had 'press ENTER after remove CD' bug and I had to reset VM after install) \EFI\boot\bootx64.efi was not written so after shutdown of VM and reboot, it booted to UEFI shell.

If there is no \EFI\boot\bootx64.efi present on the boot partition - why not write the .efi boot files to \EFI\boot folder as well as \EFI\ubuntu ???

VBox has no non-volatile storage for efibootmgr to write to, so \EFI\boot\bootx64.efi must be present.

Revision history for this message
Scott Moser (smoser) wrote : Fixed in Curtin 17.1

This bug is believed to be fixed in curtin in 17.1. If this is still a problem for you, please make a comment and set the state back to New

Thank you.

Changed in curtin:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.