public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Arsen Arsenović" <arsen@gentoo.org>
To: Alan Mackenzie <acm@muc.de>
Cc: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Fun with systemd-boot
Date: Wed, 18 Dec 2024 13:50:09 +0100	[thread overview]
Message-ID: <86bjx917ge.fsf@gentoo.org> (raw)
In-Reply-To: <Z2K8h7XOdQZC-7TZ@MAC.fritz.box> (Alan Mackenzie's message of "Wed, 18 Dec 2024 12:13:59 +0000")

[-- Attachment #1: Type: text/plain, Size: 2794 bytes --]

Hi Alan,

Alan Mackenzie <acm@muc.de> writes:

> Hello, Gentoo.
>
> I've been having fun with systemd-boot.
>
> On my new (2024-08) machine, on Friday 2024-12-06, I suddenly noticed
> that my /boot partition was empty, I can't remember why I looked at it.
> I am quite sure I didn't empty it myself.  There then followed a couple
> of hours where I restored the boot manager, kernels, and the boot
> configuration.  Thankfully, it booted again the next time I tried.
>
> On my old machine, I've been noticing over the past weeks that only two
> older kernels have been offered for booting, despite me installing later
> kernels to /boot/EFI/gentoo, and configuring them in /boot/loader.

You don't need to do that manually, installkernel should handle it for
you.  You should get installkernel[systemd,systemd-boot].

> It all became clear yesterday and today.  bootctl install had
> installed itself to /dev/nvme1n1p1 rather than /boot (which I have
> mounted on /dev/nvme0n1p1).

This would mean you mounted /dev/nvme1n1p1 on /efi:

       --esp-path=
           Path to the EFI System Partition (ESP). If not specified,
           /efi/, /boot/, and /boot/efi/ are checked in turn. It is
           recommended to mount the ESP to /efi/, if possible.

You should have one ESP mounted at any time, and mounted at /efi.  The
rest should work fine.

> Both of these partitions are EFI system partitions.  It also clogged
> up my UEFI boot sequence with lots of extra entries, leaving nvme1
> rather than nvme0 the prime EFI system partition for booting with.

UEFI boot order entries are only created as part of 'bootctl install' so
this would mean you ran it many times.  It only needs to be ran once.
To update the bootloader, you'd use 'bootctl update', to add/remove
entries you'd use kernel-install.

> I've had a look at the manual page for bootctrl.  It doesn't mention any
> way of specifying which EFI partition will get written to, and doesn't
> seem to mention that it changes the UEFI BIOS settings.  Or maybe it
> does.  It's a vague, poor quality manual.

That'd be --esp-path.

WRT changing UEFI settings, this is a necessity for UEFI boot -
grub-install does the same thing.

> I don't need all this.  Booting should not be fun.  It should be boring,
> boring, boring.  Boring and dependable.
>
> Could somebody perhaps suggest a better boot loader to me?  I need to be
> able to chose between several kernels at booting time, but I certainly
> don't want something "refined" like grub - I just need what I thought
> systemd-boot actually was before yesterday.

I suspect your problem lies elsewhere.  What partitions are you
mounting?  How are you installing kernels?

Have a lovely day!
-- 
Arsen Arsenović

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 381 bytes --]

  reply	other threads:[~2024-12-18 12:50 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-18 12:13 [gentoo-user] Fun with systemd-boot Alan Mackenzie
2024-12-18 12:50 ` Arsen Arsenović [this message]
2024-12-18 13:41   ` Alan Mackenzie
2024-12-18 14:18   ` Joost Roeleveld
2024-12-18 14:30 ` Peter Humphrey
2024-12-18 15:58   ` Michael
2024-12-18 21:31     ` Alan Mackenzie
2024-12-18 21:47       ` Re[2]: " Stefan Schmiedl
2024-12-19 10:59       ` Michael
2024-12-19 15:46         ` Alan Mackenzie
2024-12-19 16:38           ` Michael
2024-12-28 22:01           ` Wols Lists
2024-12-19 11:36     ` Peter Humphrey
2024-12-28 21:53   ` Wols Lists
2024-12-29 12:51     ` Peter Humphrey
  -- strict thread matches above, loose matches on Subject: below --
2024-12-18 12:57 Joost Roeleveld

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86bjx917ge.fsf@gentoo.org \
    --to=arsen@gentoo.org \
    --cc=acm@muc.de \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox