You are not logged in.
Here's a strange bug if I've ever heard of one: after running pacman -Syu and rebooting my machine, gummiboot's prompt to select different operating sytems doesn't show up anymore. I don't know if this is just a strange regression, or if I should be concerned, but it's odd (and annoying!).
Any suggestions? I'm not sure how to go look what packages were updated when I ran pacman -Syu.
Offline
You can read pacman's log to see what was updated (/var/log/pacman.log).
Also, check your NVRAM entries to see if they were inadvertently blitzed; that has been reported previously.
Offline
Configuration
Basic Configuration
The basic configuration is kept in $esp/loader/loader.conf, with just two possible configuration options:
default – default entry to select (without the .conf suffix); can be a wildcard like arch-*
timeout – menu timeout in seconds. If this is not set, the menu will only be shown when you hold the space key while booting.
?
ezik
Offline
See loader.conf, mostly the timeout's changed.
do it good first, it will be faster than do it twice the saint
Offline
My firmware has a habit of "forgetting" new NVRAM entries and defaults back to the first entries made (fortunately by me using EFISTUB), I then have to re-install gummiboot.
If you hold down the space bar during the booting process, the gummiboot menu will show even if the timeout is set to zero (you can also set the default from the menu by pressing "d" over the entry, very useful) -- try that.
EDIT: you can check the NVRAM entries by running:
efibootmgr -v
Last edited by Head_on_a_Stick (2015-01-03 13:38:06)
Offline
You guys are all awesome!
efibootmgr -v
gives me:
BootCurrent: 0001
Timeout: 0 seconds
BootOrder: 0001,0003,0002,0007
Boot0001* Linux Boot Manager HD(1,800,f4000,3b875fff-1d74-4b2d-a2f1-f94fc59d9b00)File(\EFI\gummiboot\gummibootx64.efi)
Boot0002* Hard Drive BIOS(2,0,00)AMGOAMNO........o.M.u.l.t.i.p.l.e.C.a.r.d. .R.e.a.d.e.r............^?........A........................^?.....<..Gd-.;.A..MQ..L.M.u.l.t.i.p.l.e.C.a.r.d. .R.e.a.d.e.r...^?...AMBOAMNO........o.M.4.-.C.T.1.2.8.M.4.S.S.D.2............^?........A......................^?.....>..Gd-.;.A..MQ..L.0.0.0.0.0.0.0.0.2.1.9.0.9.0.7.0.8.C.2.0...^?...AMBOAMNO........o.S.T.2.4.0.H.M.0.0.0.-.1.G.5.1.5.2............^?........A......................^?.....>..Gd-.;.A..MQ..L. . . . . . . . . . . . .4.Z.0.N.D.0.0.7...^?...AMBOAMNO........o.S.T.1.0.0.0.D.M.0.0.3.-.9.Y.N.1.6.2............^?........A......................^?.....>..Gd-.;.A..MQ..L. . . . . . . . . . . . .1.S.5.D.5.E.9.9...^?...AMBO
Boot0003* CD/DVD Drive BIOS(3,0,00)AMGOAMNO........o.A.S.U.S. . . . .D.R.W.-.2.4.B.1.S.T. . . .a............^?........A......................^?.....>..Gd-.;.A..MQ..L.A.B.0.D.L.C.9.1.2.5.5.9. . . . . . . . ...^?...AMBO
Boot0007* UEFI OS HD(1,800,f4000,3b875fff-1d74-4b2d-a2f1-f94fc59d9b00)File(\EFI\BOOT\BOOTX64.EFI)
Not sure what I'm reading here, but I feel like the timeout being set to 0 seconds has something to do with it?
Loader.conf states:
default arch
timeout 10
Going to try to hold down spacebar, will be back soon.
Edit: holding down spacebar does nothing
Last edited by rocktone (2015-01-03 18:46:11)
Offline
Re-install gummiboot
# gummiboot install
Offline
Question, do I really need gumminoot? I was under the impression that gummiboot or some other bootmgr was required for Arch to boot at all. I'm confused. Perhaps it boots without it? Gummiboot install did nothing, but I'll try again.
Offline
You don't need it -- direct NVRAM entries can be made using efibootmgr.
Entry "Boot0007" is the default boot option for UEFI firmware (it will boot this up in the absence of other boot loaders/managers) -- my firmware has the same entry & it seems to boot up the gummiboot default (I've just tried it):
empty@Arch ~ % efibootmgr -v
BootCurrent: 0004
Timeout: 0 seconds
BootOrder: 0001,0003,0002,0004,0001,0000,0000
Boot0000 Debian HD(1,de95000,ffb8f,50b97d29-e1fb-49ac-ae7e-b8f44a1002ba)File(\EFI\debian\vmlinuz-3.14-1-rt-amd64)r.o.o.t.=./.d.e.v./.s.d.a.4. .i.n.i.t.=./.b.i.n./.s.y.s.t.e.m.d. .r.w. .i.n.i.t.r.d.=./.E.F.I./.d.e.b.i.a.n./.i.n.i.t.r.d...i.m.g.-.3...1.4.-.1.-.r.t.-.a.m.d.6.4.
Boot0001* Linux Boot Manager HD(1,de95000,ffb8f,50b97d29-e1fb-49ac-ae7e-b8f44a1002ba)File(\EFI\gummiboot\gummibootx64.efi)
Boot0002* Arch HD(1,de95000,ffb8f,50b97d29-e1fb-49ac-ae7e-b8f44a1002ba)File(\vmlinuz-linux)r.o.o.t.=./.d.e.v./.s.d.a.2. .r.w. .i.n.i.t.r.d.=./.i.n.i.t.r.a.m.f.s.-.l.i.n.u.x...i.m.g.
Boot0003* Arch LTS HD(1,de95000,ffb8f,50b97d29-e1fb-49ac-ae7e-b8f44a1002ba)File(\vmlinuz-linux-lts)r.o.o.t.=./.d.e.v./.s.d.a.2. .r.w. .i.n.i.t.r.d.=./.i.n.i.t.r.a.m.f.s.-.l.i.n.u.x.-.l.t.s...i.m.g.
Boot0004* UEFI OS HD(1,de95000,ffb8f,50b97d29-e1fb-49ac-ae7e-b8f44a1002ba)File(\EFI\BOOT\BOOTX64.EFI)
However, as you can see my "BootCurrent" is correctly identified as that entry whereas your efibootmgr output claims you are booting from the standard gummiboot NVRAM entry ("Linux Boot Manager").
You could try setting the timeout value directly using efibootmgr:
# efibootmgr -t 10
Last edited by Head_on_a_Stick (2015-01-04 21:55:19)
Offline
Still no luck
I got the boot menu to appear once by striking the del key repeatedly. Not sure what that is about.
Offline
Well if it appeared then you must be using gummiboot to start up.
Maybe there is a problem with your keyboard -- is it wireless?
Offline
No, I am using a wired keyboard.
How would I go about removing gummiboot and bypassing it altogether?
Offline
You can just clear the relevant NVRAM entry using:
# efibootmgr -b xxxx -B
The entry is called "Linux Boot Manager"
EDIT: In your case:
# efibootmgr -b 0001 -B
Last edited by Head_on_a_Stick (2015-01-07 20:52:47)
Offline