Gummiboot not appearing in ASUS boot options

ce1984 · 2015-01-15 21:55:34

I just replaced my motherboard with an ASUS P8P67 EVO and I'm doing an arch install on my SSD using gummiboot. After installing gummiboot, I can see the boot entry show up as the first listing when I run efibootmgr -v, but it does not appear in the boot options when I enter the UEFI/BIOS. Any ideas?

Thanks

TheSaint · 2015-01-15 22:04:13

I regret to say that we don't see here

# efibootmgr -v

So, the best answer is a just a guess, or despicable question.
Try to adjust your entry order by efibootmgr

ce1984 · 2015-01-15 23:29:40

I've disconnected all other drives except for the one I'm installing to.

After installing gummiboot, the output of efibootmgr -v is:

Timeout: 1 seconds
BootOrder: 0000
Boot0000* Linux Boot Manager    HD(1,800,100000,59724644-021c-4278-952a-759b4ef5ea3f)File(\EFI\gummiboot\gummibootx64.efi)

This matches the PARTUUID of the /boot partition.

After rebooting, the boot options menu only lists the SSD itself (not the "UEFI: Linux Boot Manager" that I expected)
After booting to the install media again, I go back and check the output of efibootmgr -v again and this is what I get (with apologies for the literal screenshot):

Somehow the entry created by gummiboot is being deleted and these strange ones are being created.

Head_on_a_Stick · 2015-01-16 08:14:22

Bloody ASUS...

Do you have an entry in your firmware (BIOS) menus to boot from "UEFI OS" os similar?

You could try copying /boot/EFI/gummiboot/gummibootx64.efi to /boot/EFI/BOOTX64.EFI (backup the original first) -- this is the default loader used by UEFI firmware.

Did you see the gummiboot menu when booting the Arch .iso?

TheSaint · 2015-01-16 12:32:27

ce1984 wrote:

(with apologies for the literal screenshot).

Agreed, but unreadable in all of its forms.
The best was to mount some HDD partition and redirect the output there. Then pick it up to post it on the forum.

ce1984 · 2015-01-16 23:46:04

Sorry about that. Here's the output of efibootmgr -v (although it's changed now as theres a new flash drive to which I wrote the output):

BootCurrent: 0002
Timeout: 1 seconds
BootOrder: 0001,0002,0003
Boot0001* Hard Drive 	BIOS(2,0,00)AMGOAMNO........o.S.a.m.s.u.n.g. .S.S.D. .8.4.0. .E.V.O. .1.2.0.G.B....................A...........................>..Gd-.;.A..MQ..L.1.S.5.D.S.N.F.A.5.2.2.3.3.8. .B. . . . ......AMBOAMNO........o.P.N.Y. .U.S.B. .2...0. .F.D. .1.1.0.0....................A.............................<..Gd-.;.A..MQ..L.P.N.Y. .U.S.B. .2...0. .F.D. .1.1.0.0......AMBOAMNO........o.W.D.C. .W.D.1.0.0.2.F.A.E.X.-.0.0.Y.9.A.0....................A...........................>..Gd-.;.A..MQ..L. . . . .W. .-.D.M.W.W.A.0.3.9.3.2.0.2.5......AMBOAMNO........o.S.T.3.5.0.0.8.3.0.A.S....................A...........................>..Gd-.;.A..MQ..L. . . . . . . . . . . . .Q.6.0.G.T.Q.W.R......AMBOAMNOq.......S. .2...0.1....................A............................. ..Gd-.;.A..MQ..L. .2...0.1......AMBO
Boot0002* UEFI: PNY USB 2.0 FD 1100	ACPI(a0341d0,0)PCI(1c,1)PCI(0,0)USB(4,0)HD(1,fc,f800,7374d02e)AMBO
Boot0003* UEFI:  2.01	ACPI(a0341d0,0)PCI(1a,0)USB(1,0)USB(2,0)HD(1,20,7757e0,00000000)AMBO
Boot0004* Hard Drive 	BIOS(2,0,00)AMGOAMNO........o.P.N.Y. .U.S.B. .2...0. .F.D. .1.1.0.0....................A.............................<..Gd-.;.A..MQ..L.P.N.Y. .U.S.B. .2...0. .F.D. .1.1.0.0......AMBOAMNO........o.W.D.C. .W.D.1.0.0.2.F.A.E.X.-.0.0.Y.9.A.0....................A...........................>..Gd-.;.A..MQ..L. . . . .W. .-.D.M.W.W.A.0.3.9.3.2.0.2.5......AMBOAMNO........o.S.T.3.5.0.0.8.3.0.A.S....................A...........................>..Gd-.;.A..MQ..L. . . . . . . . . . . . .Q.6.0.G.T.Q.W.R......AMBOAMNO........o.S.a.m.s.u.n.g. .S.S.D. .8.4.0. .E.V.O. .1.2.0.G.B....................A...........................>..Gd-.;.A..MQ..L.1.S.5.D.S.N.F.A.5.2.2.3.3.8. .B. . . . ......AMBO

I do see the gummiboot menu when booting the install media, and can confirm that efivars does list the variables correctly.

ce1984 · 2015-01-16 23:56:46

Head_on_a_Stick wrote:

You could try copying /boot/EFI/gummiboot/gummibootx64.efi to /boot/EFI/BOOTX64.EFI (backup the original first) -- this is the default loader used by UEFI firmware.

The wiki says that:

You should however still be able to boot gummiboot as it copies the binary to the default EFI binary location on your ESP ($esp/EFI/boot/bootx64.efi on x64 systems)

so I believe it should already be there, but I'll give it a try. EDIT: Just checked and the files are identical as per cmp

Last edited by ce1984 (2015-01-17 00:00:00)

TheSaint · 2015-01-17 01:37:03

Your NVRAM entries are hieroglyphs for me. I don't see any pointer to a boot file.
As you chroot into installation try to reinstall gummiboot after mounting ESP on /boot.
Got that done, check again

# efibootmgr -v

It would be worth a check to UEFI wiki for troubleshooting.

ce1984 · 2015-01-17 02:02:20

After running (in the arch-chroot environment)

gummiboot --path=/boot update

the boot entry reappears in the output of efibootmgr -v:

BootCurrent: 0002
Timeout: 1 seconds
BootOrder: 0001,0002,0000
Boot0000* Linux Boot Manager	HD(1,800,100000,59724644-021c-4278-952a-759b4ef5ea3f)File(\EFI\gummiboot\gummibootx64.efi)
Boot0001* Hard Drive 	BIOS(2,0,00)AMGOAMNO........o.S.a.m.s.u.n.g. .S.S.D. .8.4.0. .E.V.O. .1.2.0.G.B....................A...........................>..Gd-.;.A..MQ..L.1.S.5.D.S.N.F.A.5.2.2.3.3.8. .B. . . . ......AMBOAMNO........o.P.N.Y. .U.S.B. .2...0. .F.D. .1.1.0.0....................A.............................<..Gd-.;.A..MQ..L.P.N.Y. .U.S.B. .2...0. .F.D. .1.1.0.0......AMBOAMNO........o.W.D.C. .W.D.1.0.0.2.F.A.E.X.-.0.0.Y.9.A.0....................A...........................>..Gd-.;.A..MQ..L. . . . .W. .-.D.M.W.W.A.0.3.9.3.2.0.2.5......AMBOAMNO........o.S.T.3.5.0.0.8.3.0.A.S....................A...........................>..Gd-.;.A..MQ..L. . . . . . . . . . . . .Q.6.0.G.T.Q.W.R......AMBO
Boot0002* UEFI: PNY USB 2.0 FD 1100	ACPI(a0341d0,0)PCI(1c,1)PCI(0,0)USB(4,0)HD(1,fc,f800,7374d02e)AMBO
Boot0004* Hard Drive 	BIOS(2,0,00)AMGOAMNO........o.P.N.Y. .U.S.B. .2...0. .F.D. .1.1.0.0....................A.............................<..Gd-.;.A..MQ..L.P.N.Y. .U.S.B. .2...0. .F.D. .1.1.0.0......AMBOAMNO........o.W.D.C. .W.D.1.0.0.2.F.A.E.X.-.0.0.Y.9.A.0....................A...........................>..Gd-.;.A..MQ..L. . . . .W. .-.D.M.W.W.A.0.3.9.3.2.0.2.5......AMBOAMNO........o.S.T.3.5.0.0.8.3.0.A.S....................A...........................>..Gd-.;.A..MQ..L. . . . . . . . . . . . .Q.6.0.G.T.Q.W.R......AMBOAMNO........o.S.a.m.s.u.n.g. .S.S.D. .8.4.0. .E.V.O. .1.2.0.G.B....................A...........................>..Gd-.;.A..MQ..L.1.S.5.D.S.N.F.A.5.2.2.3.3.8. .B. . . . ......AMBO

However after booting, the entry is not in the boot menu, and when I then boot to the install media and run efibootmgr, the listing is identical to that in my previous post #6. Somehow the entry is being deleted during the boot process.

Head_on_a_Stick wrote:

Do you have an entry in your firmware (BIOS) menus to boot from "UEFI OS" os similar?

There are two things that I think could be related:
PCI ROM Priority, which gives options:
Legacy ROM (Currently selected)
EFI Compatible ROM

I'm about to chroot in and reinstall gummiboot again, then I'll change the setting and see what happens.

EDIT:
Well, after selecting EFI compatible ROM and resetting, it goes to the "Press DEL to enter UEFI BIOS setting" screen (but I'm not able to enter the BIOS; hitting DEL does nothing) and then proceeds to a black screen and blinking underscore cursor. Looks like I'll be resetting the CMOS and starting over.

EDIT: Just found this thread which I think is more or less the same problem, but I'm not 100% sure what the solution is. The OP recreated the disk GPT and that solved the problem, so I guess I'll wipe the disk and start over and hope that solves the problem. Something wrong with the protective MBR I guess?

Last edited by ce1984 (2015-01-17 02:50:42)

TheSaint · 2015-01-17 06:33:54

ce1984 wrote:

After running (in the arch-chroot environment)However after booting, the entry is not in the boot menu

My experience, told me that I can't have much long entries in the BIOS (AMI Aptios). It's advisable to cut down the number of entries. Maybe using efibootmgr -O. Actually are 3.
Then, even I wrote one new entry and verified (strange report), then at the new boot was gone. The issue is NVRAM capacity. So, remove meaningless entry, retry to set gummiboot and crossed finger && reboot.
To access the BIOS, press F2 just after the optical drive spinning. It's a very short time. But I think you won't find any boot options. Some firmware is set automatically to a list of UEFI boot, according whether a ESP is found (I suppose) (see BIOS manual).
GPT or MBR are not that much issue here. It's important that there is the ESP.
If you wan't use legacy boot method, then gummiboot is not suitable, because is based on ESP existence.

pgoetz · 2015-01-17 09:19:26

Question: does your MB firmware include an UEFI shell? If so, try the following experiment:

From the firmware interface boot into the UEFI shell
If necessary, type mark -r to get a listing of possible boot devices
If you don't see your device, the firmware isn't seeing it either; check to make sure it's FAT32 formatted and of type EF00
If you do see it listed, say as fs0, then type fs0: to change to that filesystem
You can now use ls and cd. Use these to navigate to the location of either gummibootx64.efi or BOOTX64.EFI
just type gummibootx64.efi (or BOOTX64.EFI) to run the file

How your boot device gets listed in the UEFI firmware seems to be very implementation dependent, but at least this will tell you if your firmware even sees the boot device.

Last edited by pgoetz (2015-01-17 09:20:02)

TheSaint · 2015-01-17 11:58:00

So, would be necessary to see

$ blkid

.

ce1984 · 2015-01-19 21:54:40

The motherboard has an option to "launch EFI shell from filesystem device" but I haven't managed to make that work. I put shellx64.efi on a FAT32 formatted USB stick and had it as the only drive connected (and the drive was listed in the boot options, so it could be seen at least) but selecting to launch the EFI shell only produces a "not found" message.

blkid:

/dev/sda1: UUID="F452-9FAB" TYPE="vfat" PARTUUID="59724644-021c-4278-952a-759b4ef5ea3f"
/dev/sda2: UUID="b05fec64-e7d1-4564-bcb3-dfecb15d5619" TYPE="crypto_LUKS" PARTUUID="ef4c37fb-375c-4848-b177-84a3b10e6b53"
/dev/sdb1: UUID="2015-01-01-09-54-22-00" LABEL="ARCH_201501" TYPE="iso9660" PTUUID="7374d02e" PTTYPE="dos" PARTUUID="7374d02e-01"
/dev/sdb2: SEC_TYPE="msdos" LABEL="ARCHISO_EFI" UUID="9051-9287" TYPE="vfat" PARTUUID="7374d02e-02"
/dev/loop0: TYPE="squashfs"
/dev/loop1: UUID="ad4406c8-5ffe-491b-b696-0c3aa0b7a085" TYPE="ext4"
/dev/loop2: UUID="ad4406c8-5ffe-491b-b696-0c3aa0b7a085" TYPE="ext4"
/dev/mapper/arch_airootfs: UUID="ad4406c8-5ffe-491b-b696-0c3aa0b7a085" TYPE="ext4"
/dev/sdc1: UUID="D39B-2861" TYPE="vfat"

My experience, told me that I can't have much long entries in the BIOS (AMI Aptios). It's advisable to cut down the number of entries. Maybe using efibootmgr -O. Actually are 3.
Then, even I wrote one new entry and verified (strange report), then at the new boot was gone. The issue is NVRAM capacity. So, remove meaningless entry, retry to set gummiboot and crossed finger && reboot.
To access the BIOS, press F2 just after the optical drive spinning. It's a very short time. But I think you won't find any boot options. Some firmware is set automatically to a list of UEFI boot, according whether a ESP is found (I suppose) (see BIOS manual).
GPT or MBR are not that much issue here. It's important that there is the ESP.
If you wan't use legacy boot method, then gummiboot is not suitable, because is based on ESP existence.

I had completely removed all boot entries and created only the one I need with gummiboot update. I don't see how 1 basic entry could cause my problem. I've also reset cmos during this process so I'm confident I removed any excess data. For some reason it's deleting the new entry and creating ones from the disks during boot.

F2 doesn't do anything on this motherboard, it's the del key to access the UEFI/BIOS.

There is an ESP in that it: 1.) Is on a GPT disk and has type code of C12A7328-F81F-11D2-BA4B-00A0C93EC93B 2.) Is formatted as FAT32 3.) Is 512MiB in Size 4.) Contains /EFI/gummiboot/gummibootx64.efi and /EFI/boot/BOOTX64.EFI

If I have to I'll go back to a BIOS boot, but I'd really rather not. Part of why I bought this MB was issues with UEFI on my old one. If I decide to shell out even more cash and get a new LGA 1150 setup, anyone have recommendations for a more trouble-free board?

TheSaint · 2015-01-20 06:53:52

In ESP you should have also the kernel, as well. Gummiboot can't go beyond ESP to find kernel's vmlinuz-linux.
So according the blkid and last efibootmgr -v the addressing is correct.
If you want to have shellx64.efi, just copy it in ESP. Then you may setup a startup.nsh to boot the kernel directly

But you preferred to pay for a new solution. Some time we pay for what our knowledge can't fulfill.

pgoetz · 2015-01-20 15:49:57

Check to see if there is a firmware upgrade for your MB. Recently I couldn't get the UEFI shell to work on a thinkmate server. I upgraded the firmware, and then it worked fine.

Alfie_89 · 2015-01-26 08:28:13

ce1984 wrote:

There are two things that I think could be related:
PCI ROM Priority, which gives options:
Legacy ROM (Currently selected)
EFI Compatible ROM

When you installed Arch, did you boot with UEFI on your installation device?
If not, try doing it and install gummiboot again.

Arch Linux

#1 2015-01-15 21:55:34

Gummiboot not appearing in ASUS boot options

#2 2015-01-15 22:04:13

Re: Gummiboot not appearing in ASUS boot options

#3 2015-01-15 23:29:40

Re: Gummiboot not appearing in ASUS boot options

#4 2015-01-16 08:14:22

Re: Gummiboot not appearing in ASUS boot options

#5 2015-01-16 12:32:27

Re: Gummiboot not appearing in ASUS boot options

#6 2015-01-16 23:46:04

Re: Gummiboot not appearing in ASUS boot options

#7 2015-01-16 23:56:46

Re: Gummiboot not appearing in ASUS boot options

#8 2015-01-17 01:37:03

Re: Gummiboot not appearing in ASUS boot options

#9 2015-01-17 02:02:20

Re: Gummiboot not appearing in ASUS boot options

#10 2015-01-17 06:33:54

Re: Gummiboot not appearing in ASUS boot options

#11 2015-01-17 09:19:26

Re: Gummiboot not appearing in ASUS boot options

#12 2015-01-17 11:58:00

Re: Gummiboot not appearing in ASUS boot options

#13 2015-01-19 21:54:40

Re: Gummiboot not appearing in ASUS boot options

#14 2015-01-20 06:53:52

Re: Gummiboot not appearing in ASUS boot options

#15 2015-01-20 15:49:57

Re: Gummiboot not appearing in ASUS boot options

#16 2015-01-26 08:28:13

Re: Gummiboot not appearing in ASUS boot options

Board footer