[13.10 64Bit Beta1]-UEFI GRUB Not Working After Install?

I had the same problem on my Intel Haswell + Intel DH87RL Motherboard. Fixed it with boot-repair just like NoWorries did.

[SteveRiley]

@tanasinn: Is SecureBoot enabled or disabled in your firmware settings?

[NoWorries]

For Boot-Repair to work it necessary to install files on the installation USB. The instructions on how to do this were previously described by me on this topic.

Boot-repair will not do anything unless you follow the instructions it gives you. I found these quite clear and easy to follow. Unfortunately, the images to illustrate what to do are not shown in the order in which they were loaded.

The initial window for boot repair is the bottom one and after you select the top option to use the "Recommended repair", it will then give a window with the text to copy into Konsole. This is shown in the next one up. After copying the highlighted text into Konsole and getting it to complete all the operatons, the forward button is selected to get the next window which is shown in the second graphic from the top. Use ctrl A to select all the text to copy into Konsole. After these operations are complete, and the forward button is selected, boot-repair will do all the necessary Grub changes. When complete the final window, on the top is shown. Here you see that it detected my 256GB SSD disc.

I have always found that on reboot, I can start Kubuntu on sda as well as choose the recovery mode if needed.

One final comment is that the 12 October iso still does not handle EFI

[tanasinn]

What's the output of

sudo efibootmgr -v

It outputs:

BootCurrent: 0000
Timeout: 1 seconds
BootOrder: 0002,0000,0001
Boot0000* kubuntu       HD(1,800,f3800,3c584895-f46c-49e1-a0f9-205ab86e2e72)File(\EFI\kubuntu\shimx64.efi)
Boot0001* Hard Drive    BIOS(2,0,00)..GO..NO........o.I.N.T.E.L. .S.S.D.S.A.2.M.0.8.0.G.2.G.C....................A...........................>..Gd-.;.A..MQ..L.V.C.O.P.5.9.1.2.2.0.F.Y.8.0.B.0.N.G. . ........BO..NO........o.W.D.C. .W.D.2.0.E.A.R.S.-.0.7.M.V.W.B.0....................A...........................>..Gd-.;.A..MQ..L. . . . .W. .-.D.C.W.Z.A.4.A.1.2.8.0.7.8........BO..NO........o.S.T.3.3.2.0.6.2.0.A.S....................A...........................>..Gd-.;.A..MQ..L. . . . . . . . . . . . .Q.5.1.F.2.K.J.3........BO..NO........o.S.T.3.2.5.0.8.2.4.N.S....................A...........................>..Gd-.;.A..MQ..L. . . . . . . . . . . . .N.5.3.D.Y.1.2.9........BO                                                        
Boot0002* ubuntu        HD(1,800,f3800,3c584895-f46c-49e1-a0f9-205ab86e2e72)File(\EFI\Ubuntu\grubx64.efi)

[Edit]
Interesting that it loads grubx64.efi from the ubuntu folder and shimx64.efi from the kubuntu folder.
Removing the copied folder from my fix (/boot/efi/EFI/ubuntu) and rebooting gives me the exact same output.

I tried boot-repair before, just after installing, but it didn't help. I don't remember doing any Konsole inputs though, so I might have done something wrong.

[Edit #2]
Opening grub64.efi in a hex editor I can find a string reference to "/EFI/ubuntu" but none to "/EFI/kubuntu". Relevant?

[NoWorries]

I have found that even beta2 does not handle UEFI as well. I use a usb for installation and after the installation is complete, I get the familiar grub prompt when I reboot. I then reboot with the "installation disc" which is really the usb installation. I then bring up Konsole and enter the following

sudo add-apt-repository http://ppa.launchpad.net/yannubuntu/boot-repair/ubuntu
sudo apt-get update
sudo apt-get install boot-repair

I then use the K menu to launch boot repair and follow the prompts. These require Konsole inputs to be made. After completion, I then reboot and I have always found that I get a Grub Menu with Kubuntu at the top followed by Advanced Options for Kubuntu. The first launches Kubuntu from the "Hard Disc". The second gives options for repair.

I hope this works for you as well.

[SteveRiley]

Seems simply renaming it does not work, grub gets stuck at the blinking cursor/line. The kubuntu folder is still needed for some reason.

What's the output of

sudo efibootmgr -v

[tanasinn]

I seem to have solved my problem by copying /boot/efi/EFI/kubuntu/ to /boot/efi/EFI/ubuntu/. Simply renaming it should also work.
Will test it more later and maybe file a bug report (if none exists).

[Edit]
Seems simply renaming it does not work, grub gets stuck at the blinking cursor/line. The kubuntu folder is still needed for some reason.

[tanasinn]

I have got the same problem on my machine (with 64bit version of Beta 2). It seems to get stuck when trying to boot from the partition containing the EFI .

I haven't yet found the cause or a way to fix it, but I found how to manually boot into Kubuntu from the prompt:
1. Find the disk partition with the EFI folder (first run just ls to list all disks, then check all of them with ls (partitionname)/EFI (ex. ls (hd0,gpt1)/EFI) etc. until you find the partition that has that folder. Note the name of it so you don't have to search for it again.
2. Use the configfile commando to boot into Kubuntu with the grub.conf file, like this: configfile (hd0,gpt1)/EFI/kubuntu/grub.conf

[SteveRiley]

The installer actually uses confusing language. It really should never present an option to install on MBR when the disk is GPT.

At this point, I have decided to take on a project this weekend. We have so many reports of borked installing that I need to try to replicate the failures myself. I will wipe my spare laptop, install Windows 8, then try to set up dual boot. I will try with 13.04 first. Then I will wipe again and try with 13.10.

I will place the machine's firmware into the mode that allows both UEFI and BIOS compatibility booting, and I will document what happens when the firmware's preferences are set to try UEFI first, then when the preferences are set to try BIOS compatibility mode first. I will not be trying with Secure Boot enabled. Also, I cannot replicate firmware support for Fast Boot, as none of my machines have that facility.

[mvaar]

>> In UEFI mode with GPT disks, do not install GRUB to the MBR. (GPT disks have no MBR. But they do have "protective" MBRs, which are on-disk structures that fake MBR-only utilities into ignoring the entire disk.) Instead, GRUB should be installed in the EFI system partition, a small FAT-32 partition with type EF00.

This may be the mistake I have been making, assuming that it needs grub on MBR. I thought that the installer would figure out the correct place to install the correct code because it DOES ask me for an EFI partition- don't know why it doesn't use that information.

If MBR does get grub, what happens then ? Also, am I supposed to clear the MBR then ?

[mvaar]

The disk was already GPT partitioned. It came that way from HP with windows 8 installed. When I was having problems with the kubuntu installation, I even changed the partition table to the old kind, at which point it refused to install. complaining about the lack of the fat EFI partition.

My bios settings are such that only one of legacy or secure boot options are active at a time; I set it to use legacy mode. I assume this is what you are referring to.

Kubuntu WANTS to always use EFI boot loader, even if it CANNOT get it to work ! I wonder why the hell does it not default to something that works and let the more adventurous user try the non default set up ?!

And I am not EVEN trying to dual boot with windows .

I finally reverted back to opensuse 12.3, where it allows me to choose between grub/grub-efi and selecting plain grub installs everything fine- it replaces the crap on the MBR so I can get a graphical boot screen as before.

[SteveRiley]

The installer should follow whatever mode your firmware is configured for.

• If the firmware is in UEFI mode and its boot priority is UEFI first, BIOS compatibility second, the installation media boots in UEFI mode.
• If the firmware is in UEFI mode and its boot priority is BIOS compatibility first, UEFI second, the installation media boots in BIOS compatibility mode.
• If the firmware is in BIOS compatibility mode, the installation media boots in BIOS compatibility mode.

If this is not the actual behavior, then indeed there's a bug.

In UEFI mode with GPT disks, do not install GRUB to the MBR. (GPT disks have no MBR. But they do have "protective" MBRs, which are on-disk structures that fake MBR-only utilities into ignoring the entire disk.) Instead, GRUB should be installed in the EFI system partition, a small FAT-32 partition with type EF00.

[Buddlespit]

Did you fill out a bug report?

[mvaar]

Nothing was broken on opensuse beta1?

opensuse 12.3 release grub/installer works as long as I don't enable EFI. Kubuntu 13.04 doesn't and it doesn't offer a choice of non EFI grub.

opensuse 13.1 'factory' and kubuntu 13.10 beta are in somewhat similar states. I haven't tried either of them with EFI enabled in bios. I don't understand why kubuntu INSISTS on the EFI booting process when it cannot work with it ?


Not everyone who runs linux wants to dual boot with windows 8 ( in fact, IMO very few people who want to run linux want to have anything to do with windows 8).

[Buddlespit]

I have the same problem. With boot repair, I just installed grub to MBR. Doesn't solve the problem.

UEFI has been broken in kubuntu 13.04 and 13.10. Unfortunately, kubuntu doesn't give the option of non EFI grub at all- opensuse gives you that.

Nothing was broken on opensuse beta1?