Arch Linux

shadman

Member

Registered: 2025-05-03

Posts: 1

systemd-boot loader lists dupes

oh boy never thought id be posting here one day after being a lurker for so long. haha
yes, i have RTFM(s) to the best of my ability and cannot figure it out.

desire
systemd-boot loader loads on system startup and offers "archryzen", "win10" and "reboot to firmware interface" options.

current situation
systemd-boot loader lists all of the following -

sudo bootctl list
         type: Boot Loader Specification Type #2 (.efi)
        title: Arch Linux
           id: arch-linux.efi
       source: /boot//EFI/Linux/arch-linux.efi (on the EFI System Partition)
     sort-key: arch
      version: 6.14.5-arch1-1
        linux: /boot//EFI/Linux/arch-linux.efi
      options: root=PARTUUID=a18f498f-xxx-8fb8b68ddd34 rw rootfstype=ext4

         type: Boot Loader Specification Type #1 (.conf)
        title: win10
           id: win10.conf
       source: /boot//loader/entries/win10.conf (on the EFI System Partition)
          efi: /boot//EFI/Microsoft/Boot/bootmgfw.efi

         type: Boot Loader Specification Type #1 (.conf)
        title: archryzen (default) (selected)
           id: archryzen.conf
       source: /boot//loader/entries/archryzen.conf (on the EFI System Partition)
        linux: /boot//EFI/Linux/arch-linux.efi
      options: root=PARTUUID=a18f498f-6de1-xxx-8fb8b68ddd34 rw rootfstype=ext4

         type: Reported by Boot Loader
        title: arch-linux-fallback.efi (reported/absent)
           id: arch-linux-fallback.efi
       source: /sys/firmware/efi/efivars/LoaderEntries-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f (on the EFI System Partition)

         type: Automatic
        title: Reboot Into Firmware Interface
           id: auto-reboot-to-firmware-setup
       source: /sys/firmware/efi/efivars/LoaderEntries-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f (on the EFI System Partition)

yes, i have deleted the fallback for testing purposes a few minutes ago and im aware the entry will be gone next boot.

output of efibootmgr:

efibootmgr
BootCurrent: 0001
Timeout: 1 seconds
BootOrder: 0001
Boot0001* systemd-boot    HD(1,GPT,cb5680ed-5287-47aa-8691-342113e7e390,0x800,0x200000)/\EFI\BOOT\BOOTX64.EFI

my loader.conf:

default archryzen.conf
timeout 10
console-mode max
editor no
auto-entries no

the auto-entries switch did nothing, i had to manually delete the auto generated windows entry through efibootmgr. not doing it for the unwanted arch entry cos yk same file path and allzat

the reason im going down this rabbit-hole is for aesthetic reasons. yes, im stupid.
save me tom cruise (v1del).

ive read that type 2 entries are inherited automatically. i cannot find a way in the docs to disable these entries. i have not tested relocating the .efi elsewhere because of pacman considerations (see next line).

bonus question, when there's a kernel update/pacman hook invocations, will it undo whatever fix you all provide and revert back to having duplicate entries with squiggly lines in my boot menu?

i imagine the simplest way would have been to change the title of the type 2 entries at production and not had to have made entries and loader files (entries directory was empty and loader.conf was barebones) but i cannot find where to do that and i am cautious of undertaking future maintenance responsibilities in the event of an update.

ps. ill look into formatting the snippets after posting and update if i figure it out.

thank you.

Last edited by shadman (2025-05-03 23:06:04)