Unable to boot in UEFI mode.

flounders · 2015-03-01 17:17:05

After looking around at the wiki for a few days and playing around with Arch in VirtualBox I went to see if it would boot on my native hardware, and all the turns up is a black screen. Legacy mode is not an option as I am dual booting Windows 8.1 64 bit. I suspect this is related to my issues with Fedora as the Fedora installation media will not boot either, though it once did. Fedora used to work on my machine until it got dropped one day. After the drop I started having some strange issues and tried reinstalling Fedora, only to find that once it hit the bootloader I would face a black screen that never goes away until I power the system down. I sent my laptop in to Lenovo to be serviced and they replaced the optical drive, hard drive and did a reinstall of Windows 8. Fedora still would not boot after I got the machine back. I tried Ubuntu after the drop before sending it off and it worked, and that is what I currently have installed. My knowledge of UEFI is limited. Any ideas? My laptop is a Thinkpad L440 by the way.

Head_on_a_Stick · 2015-03-01 17:28:25

When you try to boot the Arch live ISO, does the gummiboot menu or the HashTool enroller (if you have Secure Boot enabled) show up?

If so, from Ubuntu, look at the output of:

cat /proc/cmdline

You could try appending the same kernel parameters to the Arch gummiboot entry (press "e" to edit the kernel command line and <Ctrl>+x to boot it).

Just to note: you could install Arch in non-EFI mode but this would require you to switch between "Legacy" and EFI-mode (and you would also need a BIOS boot partition).

flounders · 2015-03-01 17:40:32

The menu does show up, and I can even get into the UEFI shell from there. I can try the kernel parameters from Ubuntu, but it doesn't look very promising as the only differences I can see are quiet splash and vt.handoff=7.

swilliams@speedy:~$ cat /proc/cmdline 
BOOT_IMAGE=/boot/vmlinuz-3.13.0-46-generic.efi.signed root=UUID=29152acf-a04f-41ca-8020-3492f8057ad7 ro quiet splash vt.handoff=7

Head_on_a_Stick · 2015-03-01 17:52:59

Try disabling Secure Boot (you will have to do this for the installed system anyway [1]); you could also try the "nomodeset" parameter (you never know).

Will it boot to the log in if you enable "Legacy" mode?

[1] http://kroah.com/log/blog/2013/09/02/bo … ux-kernel/

flounders · 2015-03-01 20:15:04

Secure boot has been disabled since I installed Ubuntu back in October. It does boot to the normal, expected root shell in legacy. Also I tried the nomodeset parameter and no such luck. I am also about to read Greg's blog post.

Head_on_a_Stick · 2015-03-01 20:19:45

flounders wrote:

Secure boot has been disabled since I installed Ubuntu back in October. It does boot to the normal, expected root shell in legacy. Also I tried the nomodeset parameter and no such luck. I am also about to read Greg's blog post.

Actually, Ubuntu will install and run with Secure Boot enabled (as will the Arch live ISO) -- the blog post is just about making your own Secure Boot keys.

From Ubuntu, post the output of:

# efibootmgr -v

flounders · 2015-03-01 20:22:40

Head_on_a_Stick wrote:

Actually, Ubuntu will install and run with Secure Boot enabled (as will the Arch live ISO) -- the blog post is just about making your own Secure Boot keys.
From Ubuntu, post the output of:
# efibootmgr -v

Yeah I know that, but I left it off to save the extra hassle.

Here is the output for the command:

swilliams@speedy:~/Videos$ sudo efibootmgr -v
[sudo] password for swilliams: 
BootCurrent: 0014
Timeout: 0 seconds
BootOrder: 0014,0013,0000,0001,0002,0003,0007,0008,0009,000A,000B,000C,000D,0012
Boot0000  Setup
Boot0001  Boot Menu
Boot0002  Diagnostic Splash Screen
Boot0003  Lenovo Diagnostics
Boot0004  Startup Interrupt Menu
Boot0005  Rescue and Recovery
Boot0006  MEBx Hot Key
Boot0007* USB CD        030a2400d23878bc820f604d8316c068ee79d25b86701296aa5a7848b66cd49dd3ba6a55
Boot0008* USB FDD       030a2400d23878bc820f604d8316c068ee79d25b6ff015a28830b543a8b8641009461e49
Boot0009* ATAPI CD0     030a2500d23878bc820f604d8316c068ee79d25baea2090adfde214e8b3a5e471856a35400
Boot000A* ATA HDD0      030a2500d23878bc820f604d8316c068ee79d25b91af625956449f41a7b91f4f892ab0f604
Boot000B* ATA HDD1      030a2500d23878bc820f604d8316c068ee79d25b91af625956449f41a7b91f4f892ab0f605
Boot000C* USB HDD       030a2400d23878bc820f604d8316c068ee79d25b33e821aaaf33bc4789bd419f88c50803
Boot000D* PCI LAN       030a2400d23878bc820f604d8316c068ee79d25b78a84aaf2b2afc4ea79cf5cc8f3d3803
Boot000E* IDER BOOT CDROM       ACPI(a0341d0,0)PCI(16,2)ATAPI(0,1,0)
Boot000F* IDER BOOT Floppy      ACPI(a0341d0,0)PCI(16,2)ATAPI(0,0,0)
Boot0010* ATA HDD       030a2400d23878bc820f604d8316c068ee79d25b91af625956449f41a7b91f4f892ab0f6
Boot0011* ATAPI CD      030a2400d23878bc820f604d8316c068ee79d25baea2090adfde214e8b3a5e471856a354
Boot0012* PCI LAN       030a2400d23878bc820f604d8316c068ee79d25b78a84aaf2b2afc4ea79cf5cc8f3d3803
Boot0013* Windows Boot Manager  HD(2,1f4800,82000,e2e20688-f616-4344-9acc-e7ae20c772e3)File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}....................
Boot0014* ubuntu        HD(2,1f4800,82000,e2e20688-f616-4344-9acc-e7ae20c772e3)File(\EFI\ubuntu\shimx64.efi)

Head_on_a_Stick · 2015-03-01 20:27:38

Try removing some of the entries:

# efibootmgr -b xxxx -B

Where "xxxx" is the bootnumber you wish to delete.

flounders · 2015-03-01 20:47:32

Ran the command on 000F and 0008 which brought up an error message on boot about the EFI information being corrupted which it claimed it was able to repair. Now Ubuntu is missing out of the boot entries (I installed it with a separate EFI system partition). Also I am still unable to boot Arch in EFI mode.

Head_on_a_Stick · 2015-03-01 20:54:33

Oh dear -- sorry!
https://help.ubuntu.com/community/Boot-Repair

It does sound to me that your NVRAM entries are full up and your firmware implementation is crappy (very common) -- the only solution I know of is to delete the excess entries; if you cannot do this I am at a loss as to what else to suggest...

flounders · 2015-08-18 08:04:26

After running efibootmgr, my headphone jack would no longer put out sound after resuming from suspend. A reboot would fix this and make the sound jack usable again. I reinstalled Ubuntu to make sure it wasn't a software issue and it came back on the fresh install. So I tested this out in Windows, and in Windows sound doesn't work at all after resuming from suspend. Lenovo changed out the motherboard and now I am posting this on Arch from this laptop. While you weren't able to directly help with my booting Arch, messing with efibootmgr made the problem bad enough that Lenovo just authorized a straight motherboard replacement. So thanks.

Last edited by flounders (2015-08-18 08:05:48)

Arch Linux

#1 2015-03-01 17:17:05

Unable to boot in UEFI mode.

#2 2015-03-01 17:28:25

Re: Unable to boot in UEFI mode.

#3 2015-03-01 17:40:32

Re: Unable to boot in UEFI mode.

#4 2015-03-01 17:52:59

Re: Unable to boot in UEFI mode.

#5 2015-03-01 20:15:04

Re: Unable to boot in UEFI mode.

#6 2015-03-01 20:19:45

Re: Unable to boot in UEFI mode.

#7 2015-03-01 20:22:40

Re: Unable to boot in UEFI mode.

#8 2015-03-01 20:27:38

Re: Unable to boot in UEFI mode.

#9 2015-03-01 20:47:32

Re: Unable to boot in UEFI mode.

#10 2015-03-01 20:54:33

Re: Unable to boot in UEFI mode.

#11 2015-08-18 08:04:26

Re: Unable to boot in UEFI mode.

Board footer