Arch & UEFI [Was: Bug on missing staging modules rpm]
mariachiac at gmail.com
Fri Jul 22 18:51:57 EDT 2016
Yes that is what it does. Sorry for the long response. I've been on the
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
> /EFI/Boot/boot*.efi. A systemd-boot entry in the EFI boot variables is
> 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
> boot variable.
> Speakup mailing list
> Speakup at linux-speakup.org
More information about the Speakup