EFI BootOrder not written correctly after installation

Bug #1255368 reported by Chun Li
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

I recently installed Ubuntu 13.10 on a new MacBook Pro (Late 2013, 13-inch Haswell retina). After installation, I could not boot to Ubuntu. It turns out that the installation correctly added an EFI boot entry, Boot0000, for ubuntu, but did not update the EFI BootOrder. The BootOrder was set to be 0080, a boot entry for MacOS. The correct BootOrder should be 0000,0080. I used the command 'sudo efibootmgr -o 0,80' to fix it. The installation should have set the boot order information. I observed the same problem on a second laptop.

Other information that might be helpful: 1) My installation media was a USB drive created using the standard iso image, not the MAC iso. The latest Apple hardware can boot the UEFI/BIOS hybrid image. 2) If a user never booted to MacOS before installing Ubuntu, the EFI would not have any boot entries and the BootOrder would be empty. But if a user had booted to MacOS, the EFI would have two identical boot entries Boot0080 and BootFFFF and the BootOrder would be 0080.

Another issue is that the grub entries Ubuntu created for MacOS can not boot to MacOS. I "solved" this by creating a grub entry to have a single command "exit". This way, the system would exit grub, and EFI would boot the second in line according to BootOrder.

Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1255368/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
Revision history for this message
John Kim (kotux) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue that you reported is one that should be reproducible with the live environment of the Desktop ISO of the development release - Trusty Tahr. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/ . Thanks again and we appreciate your help.

tags: added: macbookpro
affects: ubuntu → ubiquity (Ubuntu)
Changed in ubiquity (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in ubiquity (Ubuntu):
status: Incomplete → Expired
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.