Question

1

13.04 not leaving any efibootmgr entries

rated 0 times [ 1] [ 0] / answers: 1 / hits: 4156 / 3 Years ago, mon, june 14, 2021, 10:14:26

I made a clean install of 13.04 from a flash drive, but after a reboot the only uefi boot options I have are the basic efi shell entries and the flash drive again - there's simply no entry for 13.04.

So the first thing I did was boot up the live enviroment with the flash drive, chroot into the 13.04 install and work it out with grub-efi and efibootmgr.

First thing I notice, copying the resolv.conf doesnt seem to give me wifi-access in the chroot enviroment.

Second thing, trying to create a new efibootmgr entries doesnt do anything - I've tried a few bogus entries, but the verification always only shows me the default efi shell entries.

So my main question is: did they change anything about efibootmgr? Did anyone else manage to get 13.04 to boot up with uefi?

PS: this pretty much shows what commands I used if thats helpful. and this seems to indicate the problem existed in the beta release.

Answers

Only authorized users can answer the question. Please sign in first, or register a free account.

utschang

Add To Favorites

Follow

Total Points: 357

Total Questions: 120

Total Answers: 119

Location: Croatia

Member since Sat, May 2, 2020

4 Years ago

utschang questions

1 curl dynamic linking problem in 21.10

Mon, Aug 30, 21, 14:09, 3 Years ago

1 Asus Rog Strix Scar 17 No Sound

Tue, May 17, 22, 20:44, 2 Years ago

1 The installation of the NVIDIA display driver 340 fails in Kubuntu 20.10

Sun, Jun 12, 22, 04:46, 2 Years ago

1 Ubuntu 20.04 autoinstallation LUKS

Sun, Jul 11, 21, 23:54, 3 Years ago

1 which snap command is eqivalent to `apt depends ` in apt

Tue, Sep 7, 21, 04:23, 3 Years ago

View All

answered 3 Years ago anatta · Accepted Answer

I have heard of bugs in some versions of efibootmgr that can cause this problem. You might try using efibootmgr in an older version of Ubuntu or in a rescue system like System Rescue CD to bypass this bug, if it's the cause.

If that doesn't work, you can try copying the EFI/ubuntu/grubx64.efi file on the ESP to EFI/BOOT/bootx64.efi. If no other OS is installed, that should get it working. The Boot Repair tool will do this, and more, automatically; it should work even if Windows is installed.

If you've got a Windows installation, another option is to use bcdedit in Windows: Launch an Administrator Command Prompt and then type bcdedit /set {bootmgr} path EFIubuntugrubx64.efi. (If you've got Secure Boot active, you'll need to activate shim.efi or shimx64.efi [I'm not sure which it's called in Ubuntu, offhand] instead of grubx64.efi.)