[Bug 1242417] [NEW] UEFI install broken when GRUB_DISTRIBUTOR!=Ubuntu (e.g. Kubuntu/UbuntuStudio)
Launchpad Bug Tracker
1242417 at bugs.launchpad.net
Thu Oct 24 12:29:08 UTC 2013
You have been subscribed to a public bug by Howard Chan (smartboyhw):
[Impact]
After a installation of Kubuntu rebooting will leave the user with a unusable system since the relevant EFI files are not found. The uploaded package will fix this issue for all Kubuntu users and allow them to be able to boot their system.
[Test Case]
--General: Verfiy UEFI bootmanager Entries--
If one has access to a UEFI shell that should be used to confirm UEFI bootmanager entries. When in need for a shell binary one can use [1] and place it as /boot/efi/shellx64.efi. Please note that unsigned shells will not work while SecureBoot is active.
To print the image table use:
bcfg boot dump
Output should contain an entry with
Desc - kubuntu
and DevPath should contain \EFI\ubuntu (not \EFI\kubuntu)
If a shellx64.efi cannot be used use the command line tool efibootmgr instead:
* sudo efibootmgr -v
One of the entires should again be called kubuntu and contain \EFI\ubuntu in the File defintion. For example:
Boot0002* kubuntu HD(1,800,96000,e3e31484-1b57-40b2-a4b0-942debc6bea9)File(\EFI\ubuntu\grubx64.efi)
--Upgrade Test Case--
* Deactivate SecureBoot in BIOS
* Boot
* Verfiy UEFI bootmanager Entries (see above; should be broken and point to \EFI\kubuntu)
* Make sure there is no EFI/ubuntu present on your EFI partition (mv /boot/efi/EFI/ubuntu /boot/efi/EFI/ubuntu-bak)
* sudo apt-get update
* sudo apt-get install grub2-common grub-efi-amd64 grub-eif-amd64-signed
* Verfiy UEFI bootmanager Entries (see above)
* Verify that /boot/efi/EFI/ubuntu exists (again)
* Reboot and boot into the 'kubuntu' entry.
* Shutdown
* Activate SecureBoot in BIOS
* Boot
--Installation Test Case--
* Deactivate SecureBoot in BIOS
* Boot 13.10 ISO
* When doing a completely clean install:
* Delete all paritions using gparted or partitionmanager
* When NOT doing a completely clean install:
** Find your EFI partition (will be a rather small FAT partition); usually /dev/sda1 or sda2
** sudo mount /dev/$DEVICE /mnt
** Make sure there is no EFI/ubuntu present (mv /mnt/EFI/ubuntu /mnt/EFI/ubuntu-bak)
** sudo umount /mnt
* Ensure there are no 'kubuntu' UEFI boot manager entires
** sudo efibootmgr -v |grep kubuntu
** If there is one, delete it first
** sudo efibootmgr -b $NUMBER_PRECEDING_THE_NAME_IN_THE_DUMP -B
** Confirm .... sudo efibootmgr -v |grep kubuntu
* Ensure there is an active internet connection
* Install
* Verfiy UEFI bootmanager Entries (see above)
* Reboot and boot into the 'kubuntu' entry.
* Shutdown
* Activate SecureBoot in BIOS
* Boot
[Regression Potential]
TBD
[1]
http://sourceforge.net/apps/mediawiki/tianocore/index.php?title=UEFI_Shell
-------------- original report
Kubuntu 13.10 is broken for UEFI installs. You will just get the grub2
cli after reinstall..
Its a really stupid bug - with a really easy fix - you just need to copy
the kubuntu folder in the efi directory to ubuntu.
i.e
sudo cp -rv /boot/efi/EFI/kubuntu /boot/efi/EFI/ubuntu
Will 'fix' it.
It looks like its effecting various people
i.e - randomly found this.
http://www.kubuntuforums.net/showthread.php?63589-13-10-64Bit-Beta1
-UEFI-GRUB-Not-Working-After-Install
To fix this surely the 13.10 .iso will have to be rebuilt?
This is a Kubuntu speficic bug - Ubuntu 13.10 is fine.
------------------------
1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu
13.10 - kubuntu
2) The version of the package you are using, via 'apt-cache policy
pkgname' or by checking in Software Center
$ dpkg -l |grep grub
ii grub-common 2.00-19ubuntu2 amd64 GRand Unified Bootloader (common files)
ii grub-efi-amd64 2.00-19ubuntu2 amd64 GRand Unified Bootloader, version 2 (EFI-AMD64 version)
ii grub-efi-amd64-bin 2.00-19ubuntu2 amd64 GRand Unified Bootloader, version 2 (EFI-AMD64 binaries)
ii grub-efi-amd64-signed 1.22+2.00-19ubuntu2 amd64 GRand Unified Bootloader, version 2 (EFI-AMD64 version, signed)
ii grub2-common 2.00-19ubuntu2 amd64 GRand Unified Bootloader (common files for version 2)
3) What you expected to happen
The install to work
4) What happened instead
Install not able to boot - just grub2 cli - had to manually copy the efi
directory to 'ubuntu' to 'fix' it
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: grub-efi-amd64 2.00-19ubuntu2
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
Uname: Linux 3.11.0-12-generic x86_64
ApportVersion: 2.12.5-0ubuntu2
Architecture: amd64
Date: Sun Oct 20 20:00:54 2013
InstallationDate: Installed on 2013-10-20 (0 days ago)
InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MarkForUpload: True
ProcEnviron:
LANGUAGE=en_GB:en
TERM=xterm
PATH=(custom, no user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
SourcePackage: grub2
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: grub2 (Ubuntu)
Importance: High
Status: In Progress
** Affects: grub2-signed (Ubuntu)
Importance: Undecided
Status: New
** Affects: kubuntu-settings (Ubuntu)
Importance: Critical
Status: Confirmed
** Affects: ubuntustudio-default-settings (Ubuntu)
Importance: Critical
Assignee: Howard Chan (smartboyhw)
Status: In Progress
** Affects: grub2 (Ubuntu Saucy)
Importance: Undecided
Status: Fix Committed
** Affects: grub2-signed (Ubuntu Saucy)
Importance: Undecided
Status: New
** Affects: kubuntu-settings (Ubuntu Saucy)
Importance: Undecided
Status: Fix Committed
** Affects: ubuntustudio-default-settings (Ubuntu Saucy)
Importance: Undecided
Status: Confirmed
** Affects: grub2 (Ubuntu Trusty)
Importance: High
Status: In Progress
** Affects: grub2-signed (Ubuntu Trusty)
Importance: Undecided
Status: New
** Affects: kubuntu-settings (Ubuntu Trusty)
Importance: Critical
Status: Confirmed
** Affects: ubuntustudio-default-settings (Ubuntu Trusty)
Importance: Critical
Assignee: Howard Chan (smartboyhw)
Status: In Progress
** Tags: amd64 apport-bug saucy verification-needed
--
UEFI install broken when GRUB_DISTRIBUTOR!=Ubuntu (e.g. Kubuntu/UbuntuStudio)
https://bugs.launchpad.net/bugs/1242417
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.
More information about the Ubuntu-sponsors
mailing list