Arch Linux

TheSaint

Member

From: my computer

Registered: 2007-08-19

Posts: 1,535

[Solved] Booting wrong bootloader

Hello,
I made a way to skip any bootloader but BIOS.
Actually this fails but I can't find the culprit, because I prefer that it start by the EFI stub. Just in case of maintenance I'd stop the BIOS to boot and select the other chance listed.

$ bootctl status
System:
      Firmware: UEFI 2.70 (Acer Inc. 5.12)
 Firmware Arch: x64
   Secure Boot: disabled
  TPM2 Support: yes
  Measured UKI: no
  Boot into FW: supported

Current Boot Loader:
      Product: systemd-boot 257.4-1-arch
     Features: ✓ Boot counting
               ✓ Menu timeout control
               ✓ One-shot menu timeout control
               ✓ Default entry control
               ✓ One-shot entry control
               ✓ Support for XBOOTLDR partition
               ✓ Support for passing random seed to OS
               ✓ Load drop-in drivers
               ✓ Support Type #1 sort-key field
               ✓ Support @saved pseudo-entry
               ✓ Support Type #1 devicetree field
               ✓ Enroll SecureBoot keys
               ✓ Retain SHIM protocols
               ✓ Menu can be disabled
               ✓ Multi-Profile UKIs are supported
               ✓ Boot loader set partition information
    Partition: /dev/disk/by-partuuid/d4f6063a-1a75-442c-bda4-2953681950f6
       Loader: └─/EFI/systemd/systemd-bootx64.efi
Current Entry: arch.conf

Random Seed:
 System Token: set
       Exists: yes

Available Boot Loaders on ESP:
          ESP: /boot (/dev/disk/by-partuuid/d4f6063a-1a75-442c-bda4-2953681950f6)
         File: ├─/EFI/systemd/systemd-bootx64.efi (systemd-boot 257.4-1-arch)
               └─/EFI/BOOT/BOOTX64.EFI (systemd-boot 257.4-1-arch)

Boot Loaders Listed in EFI Variables:
        Title: Linux Boot Manager
           ID: 0x0000
       Status: active, boot-order
    Partition: /dev/disk/by-partuuid/d4f6063a-1a75-442c-bda4-2953681950f6
         File: └─/EFI/systemd/systemd-bootx64.efi

        Title: EFISTUB Arch
           ID: 0x0002
       Status: inactive, boot-order
    Partition: /dev/disk/by-partuuid/d4f6063a-1a75-442c-bda4-2953681950f6
         File: └─/vmlinuz-linux

Boot Loader Entries:
        $BOOT: /boot (/dev/disk/by-partuuid/d4f6063a-1a75-442c-bda4-2953681950f6)
        token: arch

Default Boot Loader Entry:
         type: Boot Loader Specification Type #1 (.conf)
        title: Linux
           id: arch.conf
       source: /boot//loader/entries/arch.conf (on the EFI System Partition)
        linux: /boot//vmlinuz-linux
       initrd: /boot//intel-ucode.img
               /boot//initramfs-linux.img
      options: root=LABEL=LinuxRoot rw quiet

Last edited by TheSaint (2025-03-19 07:44:53)

---

do it good first, it will be faster than do it twice the saint

Scimmia

Fellow

Registered: 2012-09-01

Posts: 12,717

Re: [Solved] Booting wrong bootloader

I have no idea what you're asking. "bootloader but BIOS" makes no sense at all, this appears to be a UEFI system so BIOS never enters the picture at all. BIOS and UEFI also aren't bootloaders. Even making a wild guess that you're trying to use direct EFI stub loading, I have no idea what the issue/question is.

Last edited by Scimmia (2025-03-18 22:17:20)

mackin_cheese

Member

Registered: 2025-01-07

Posts: 467

Re: [Solved] Booting wrong bootloader

What are you even stating?

TheSaint

Member

From: my computer

Registered: 2007-08-19

Posts: 1,535

Re: [Solved] Booting wrong bootloader

Sorry friends, I got some Alzheimer symptom

I was using the formula to boot in UEFI by the kernel efi stub and it has worked well before I remade a fresh installation.
My expectations are that my booting sequence should go directly to the kernel except I need to do maintenance, in such case I choose the boot order list while the PC is booting, which includes the systemd-boot and its entries.

Finally solved

My mistake was that I wrote the wrong device number for the creation on the NVRAM.
Now is like this:

$ blkid |grep Lin
/dev/nvme1n1p2: LABEL="LinuxRoot" UUID="9d97b556-0573-4abc-a27c-a1fac6e447bc" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="e36b2b0e-7cf9-4bdd-9f78-0efa01530e08"
/dev/nvme1n1p3: LABEL="LinuxHome" UUID="77568eb3-09a6-4b23-9edd-5d80b849ce4b" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="d2fa632f-d176-4f13-ba1b-b9cab03620b4"
/dev/nvme1n1p1: LABEL_FATBOOT="LinuxBOOT" LABEL="LinuxBOOT" UUID="E92D-8A18" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="d4f6063a-1a75-442c-bda4-2953681950f6"

In facts the ESP is LinuxBOOT.
But I added a new SSD nvme and I assumed was the same as before.

# efibootmgr --create --disk /dev/nvme0n1 --part 1 --label "Arch Kernel" --loader /vmlinuz-linux --unicode 'root=LABEL=LinuxRoot rw initrd=\initramfs-linux.img  initrd=\intel-ucode.img'

Last edited by TheSaint (2025-03-19 07:46:29)

---

do it good first, it will be faster than do it twice the saint

dimich

Member

From: Kharkiv, Ukraine

Registered: 2009-11-03

Posts: 355

Re: [Solved] Booting wrong bootloader

I made a way to skip any bootloader but BIOS.
Actually this fails but I can't find the culprit, because I prefer that it start by the EFI stub.

Do you want to boot kernel directly from UEFI without bootloader?

File: └─/vmlinuz-linux

This is bare kernel binary, it doesn't contain initramfs. You have to create Unified kernel image.