Arch & UEFI [Was: Bug on missing staging modules rpm]

[Janina Sajka]

Hi,

Just last night I finally got my system booting successfully. It turns
out that swapping usb sticks on this particular board could cause the
UEFI boot order settings to get shuffled. One of these shuffles appears
to have put me back in legacy mode, so I took advantage of that to have
gdisk return me to mbr. A quick install of grub, and I'm booting just
fine.

Further searching turns up people with similar boards having issues with
UEFI as well--so clearly not something Arch related. I may try again
after, and if I get my firmware fully updated. Unfortunately, Asrock's
support pages aren't very friendly to work with, so that will have to
await sighted assistance.

Thanks for your help. I feel I've a pretty good handle on efistub and
systemd booting. I just can't do it on this machine. But, I'm at least
up and running, which is what really matters!

Janina

Alonzo Cuellar writes:
> Hi
> Yes that is what it does. Sorry for the long response. I've been on the
> road.
> 
> On Jul 20, 2016 17:11, "Jason White" <jason at jasonjgw.net> wrote:
> >
> > Janina Sajka <janina at rednote.net> wrote:
> > > A couple specific questions below ...
> > >
> > > Alonzo Cuellar writes:
> > > > ...
> > > > After that I just configure /boot/loader/entries/arch.conf
> > > >
> > > >
> > > > title   Arch Linux
> > > > linux   /vmlinuz-linux
> > > > initrd  /intel-ucode.img
> > > I didn't have this entry, but I do see the file in the directory. So, I
> > > added it as you have it. But, I'm curious. What does it do?
> >
> > According to the bootctl manual page:
> > "A copy of systemd-boot will be stored as the EFI default/fallback loader
> at
> > /EFI/Boot/boot*.efi. A systemd-boot entry in the EFI boot variables is
> created
> > and added to the top of the boot order list."
> >
> > I strongly suspect the configuration file, as above, then enables the boot
> > loader to find the kernel and the initrd. Thus the start-up order is:
> >
> > EFI firmware -> boot loader -> kernel.
> >
> > and the kernel is not booted directly by the EFI firmware in this
> > configuration, but by the *.efi boot loader executable specified in the
> EFI
> > boot variable.
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup at linux-speakup.org
> > http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
> _______________________________________________
> Speakup mailing list
> Speakup at linux-speakup.org
> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

-- 

Janina Sajka,	Phone:	+1.443.300.2200
			sip:janina at asterisk.rednote.net
		Email:	janina at rednote.net

Linux Foundation Fellow
Executive Chair, Accessibility Workgroup:	http://a11y.org

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Chair, Accessible Platform Architectures	http://www.w3.org/wai/apa