Arch Linux

Pr0Wolf29

Member

Registered: 2012-03-30

Posts: 25

gummiboot returns to boot menu

When I hit F11 and go to "Linux Boot Manager", and select that as the boot device, it goes black momentarily, and then back to the menu. There is no text displayed, not even momentarily. I can't boot to it for anything. I installed to /boot on a fresh installation. I tried resetting CMOS, and reinstalling gummiboot, but that does nothing. I keep getting that. I installed from a burned CD from the newest ISO. I also have the Win10 preview on another drive. I know someone with the same motherboard, and it works just fine for him.  Here are my configs for gummiboot:

arch.conf

title Arch Linux
linux /vmlinuz-linux
initrd /initramfs-linux.img
options root=/dev/sdb3 rw libata.atapi_passthru16=0

loader.conf

timeout 3
default arch

Is there something out of place here? How fix?

Last edited by Pr0Wolf29 (2015-03-28 18:44:09)

jasonwryan

Anarchist

From: .nz

Registered: 2009-05-09

Posts: 30,426

Website

Re: gummiboot returns to boot menu

Your default is "arch" but your config is called loader... Presumably, you have that back to front.

---

Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Pr0Wolf29

Member

Registered: 2012-03-30

Posts: 25

Re: gummiboot returns to boot menu

arch.conf is in /boot/loader/entries and loader.conf is in /boot/loader.

nullified

Member

From: Massachusetts, USA

Registered: 2013-12-09

Posts: 468

Re: gummiboot returns to boot menu

This is a case for the wiki: https://wiki.archlinux.org/index.php/Gu … figuration

---

"We may say most aptly, that the Analytical Engine weaves algebraical patterns just as the Jacquard-loom weaves flowers and leaves." - Ada Lovelace

Pr0Wolf29

Member

Registered: 2012-03-30

Posts: 25

Re: gummiboot returns to boot menu

I just realized I had the names wrong in my post. I didn't get the configuration files mixed up location-wise.

jasonwryan

Anarchist

From: .nz

Registered: 2009-05-09

Posts: 30,426

Website

Re: gummiboot returns to boot menu

What is your partition table? Where is your ESP? Have you considered using UUID's, they are much more reliable...

---

Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Pr0Wolf29

Member

Registered: 2012-03-30

Posts: 25

Re: gummiboot returns to boot menu

sdb1 = 512MB FAT32 ESP /boot
sdb2 = swap
sdb3 = /

I was using a UUID for root before, but it still didn't work then.

Head_on_a_Stick

Member

From: The Wirral

Registered: 2014-02-20

Posts: 8,778

Website

Re: gummiboot returns to boot menu

Try creating an NVRAM entry manually:

# efibootmgr -d /dev/sdb -p 1 -c -L "Arch" -l /vmlinuz-linux -u "root=/dev/sdb3 rw initrd=/initramfs-linux.img"

Your motherboard may be getting confused by the presence of two EFI system partitions and the above command specifies which one to use.

You could also use `efibootmgr` to specify the ESP & load gummiboot:

# efibootmgr -d /dev/sdb -p 1 -c "Gummiboot" -l /EFI/gummiboot/gummibootx64.efi

(change "64" to "32" if you have a 32-bit system)

---

Jin, Jîyan, Azadî

Pr0Wolf29

Member

Registered: 2012-03-30

Posts: 25

Re: gummiboot returns to boot menu

Both of those commands did the same as trying to use the entry gummiboot created.

Head_on_a_Stick

Member

From: The Wirral

Registered: 2014-02-20

Posts: 8,778

Website

Re: gummiboot returns to boot menu

Please post the output of:

# parted -l
# efibootmgr -v

You can use the Arch live ISO and the "sprunge" pastebin:

<command> | curl -F 'sprunge=<-' http://sprunge.us

https://wiki.archlinux.org/index.php/Li … in_clients

---

Jin, Jîyan, Azadî

Pr0Wolf29

Member

Registered: 2012-03-30

Posts: 25

Re: gummiboot returns to boot menu

parted -l : http://sprunge.us/VNSQ
efibootmgr -v : http://sprunge.us/ZJUW

Head_on_a_Stick

Member

From: The Wirral

Registered: 2014-02-20

Posts: 8,778

Website

Re: gummiboot returns to boot menu

Your Windows system is booting in non-EFI mode and your Arch system is booting in EFI-mode.

You can make your Arch system boot by disabling "CSM" or "Legacy" mode in your firmware (BIOS) options.

However, you will then have to switch between Legacy & UEFI booting when you change between the two operating systems.

I recommend installing GRUB to /dev/sda in non-EFI mode:

# pacman -S grub os-prober
# grub-install --target=i386-pc --recheck /dev/sda
# grub-mkconfig -o /boot/grub/grub.cfg

https://wiki.archlinux.org/index.php/Be … therboards

This will over-write the Windows bootloader and allow booting of both operating systems from GRUB.

It would be wise to backup the Windows bootloader first in case I am wrong here:

# dd if=/dev/sda of=windows.bak bs=512 count=1

EDIT: If it does go pear-shaped* you can restore the bootloader using:

# dd if=windows.bak of=/dev/sda bs=512 count=1

* Pete Tong == wrong

Last edited by Head_on_a_Stick (2015-03-28 23:55:03)

---

Jin, Jîyan, Azadî