On Friday 26 Aug 2016 16:13:53 Mike Gilbert wrote:
> On Fri, Aug 26, 2016 at 4:32 AM, Peter Humphrey <pe...@prh.myzen.co.uk> wrote:
> > In my search for a suitable boot method, I'm trying Mike G's
> > systemd-boot
> > ebuild. I've installed it with no problem, and now I reach the heart-in-
> > mouth stage of actually replacing gummiboot with it. But first, the
> > backup, including dd of what used to be called the MBR (what is it
> > now?).
> It should be basically a drop-in replacement, with a slightly
> different name. It should not require any modification to your disk
> layout.
I've learned a few things over the last day, and now I have systemd-boot
installed and gummiboot gone (late and somewhat lamented).
# bootctl status
System:
Firmware: UEFI 2.31 (American Megatrends 5.09)
Secure Boot: disabled
Setup Mode: setup
Loader:
Product: systemd-boot 231
Partition: /dev/disk/by-partuuid/f3fa7b95-0a65-4716-924a-ae3f30811de5
File: └─/EFI/SYSTEMD/SYSTEMD-BOOTX64.EFI
Boot Loader Binaries:
ESP: /dev/disk/by-partuuid/f3fa7b95-0a65-4716-924a-ae3f30811de5
File: └─/EFI/systemd/systemd-bootx64.efi (systemd-boot 231)
File: └─/EFI/BOOT/BOOTX64.EFI
Boot Loader Entries in EFI Variables:
Title: Linux Boot Manager
ID: 0x0001
Status: active, boot-order
Partition: /dev/disk/by-partuuid/f3fa7b95-0a65-4716-924a-ae3f30811de5
File: └─/EFI/SYSTEMD/SYSTEMD-BOOTX64.EFI
Title: UEFI OS
ID: 0x000C
Status: active, boot-order
Partition: /dev/disk/by-partuuid/f3fa7b95-0a65-4716-924a-ae3f30811de5
File: └─/EFI/BOOT/BOOTX64.EFI
I'd still like to know where the directory /usr/lib64/systemd/boot/efi
came from though.
https://wiki.archlinux.org/index.php/systemd-boot was the last link I
needed; I hadn't realised until then that bootctl uses the same
/boot/loader/... arrangement as gummiboot, Mike's "drop-in replacement"
comment notwithstanding. I suggest that the Gentoo docs could use a version
of this web page.
> Also, you should be able to configure your firmware to load either
> gummiboot or systemd-boot, so you have a fallback if the new code
> fails.
I did that, but now I'm happy with bootctl I've removed gummiboot.
I took the opportunity of changing the partition layout somewhat. When I
restored all my backups I found errors from polkit and dbus, which were
preventing KDE from running properly. I assume this was because the
partitions had new UUIDs. A quick "emerj -1av $(eix -cI# polkit)" and ditto
dbus fixed it.
alias emerj='sudo emerge --jobs=24 --load-average=48 --keep-going --nospinner'
So thanks to Mike I now have a stable, maintainable system that suits me.
--
Rgds
Peter
