Long BOOT Firmware POST time

Kamitachi · 2026-02-06 07:38:28

It's slightly over a month since I moved from Windows to Archlinux.

Since I'm on Arch I noticed that my PC takes way longer to boot, specifically, to boot the BIOS.

From what I remember, the only thing I changed when I moved was the secure boot. I've tried to change the fast boot on memory training, but it didn't change anything.

I ran systemd-analyze and systemd-analyze blame to know what was wrong, but I don't know what to do anymore.

systemd-analyze:

Startup finished in 47.076s (firmware) + 4.993s (loader) + 1.052s (kernel) + 4.001s (initrd) + 4.588s (userspace) = 1min 1.712s
graphical.target reached after 2.043s in userspace.

systemd-analyze blame
systemd-analyze plot
PC Specs

Last edited by Kamitachi (2026-02-07 00:55:50)

skunktrader · 2026-02-06 07:51:59

47+ seconds to init the firmware suggests some hardware problem. Does the kernel log contain any suspicious looking errors while enumerating hardware devices?

Kamitachi · 2026-02-06 08:11:33

sudo dmesg -l err,crit,alert, shows this:

[ 7.056973] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.XHCI.RHUB.HS14.BRDS.RIPM], AE_NOT_FOUND (20250807/psargs-332)
[ 7.056978] ACPI Error: Aborting method \_SB.PC00.XHCI.RHUB.HS14.BRDS due to previous error (AE_NOT_FOUND) (20250807/psparse-529)

The problem started happening when I switched to Linux. I don't know if I messed up with the installation, but when I had Windows, the boot time was low, I don't know how much, but low.

seth · 2026-02-06 09:07:30

tbc, it takes 45+ until the bootloader shows up?
But after it says "starting archlinux", "loading linux" or so it boots within 5s?

What is your bootloader?
Is the windows installation still there?
Does the UEFI (boot menu, typically F12 or so) think it's still there (stale entry efi entry)?

Kamitachi · 2026-02-06 09:26:09

Yeah, it takes that long to show the motherboard logo to enter the BIOS or continue.

No, the Windows installation is no longer there because I have my ssd in an LVM together

nvme0n1 259:0 0 1,8T 0 disk
├─nvme0n1p1 259:1 0 512M 0 part /boot
└─nvme0n1p2 259:2 0 1,8T 0 part
└─vg1-root 253:0 0 3,6T 0 lvm /
nvme1n1 259:3 0 1,8T 0 disk
└─nvme1n1p1 259:4 0 1,8T 0 part
└─vg1-root 253:0 0 3,6T 0 lvm /

And here I have my BIOS priority.
Boot priority

seth · 2026-02-06 09:38:52

takes that long to show the motherboard logo to enter the BIOS

Have you tried to reset the COMS/BIOS/UEFI?

ls -lR /boot

(I guess nvme0n1p1 is your ESP)

Did you muck around w/ https://wiki.archlinux.org/title/Unifie … efibootmgr ?
What does the list of boot entries look like (don't flail around w/ efibootmgr or bcfg otherwise!)

Kamitachi · 2026-02-06 10:07:01

ls -lR /boot

efibootmgr

BootCurrent: 0001
Timeout: 0 seconds
BootOrder: 0001
Boot0001* UEFI OS HD(1,GPT,38358050-1949-4b4a-aa71-4c36be695465,0x800,0x100000)/\EFI\BOOT\BOOTX64.EFI0000424f

As much as I remember, I didn't touch efibootmgr much, I just installed Arch and started configuring the enviroment

seth · 2026-02-06 13:30:49

So there's only BOOTX64.EFI and despite the grub installation apparently no /boot/EFI/GRUB/grubx64.efi

I just installed Arch and

How exactly did you go about installing grub?
https://wiki.archlinux.org/title/GRUB#Installation

Kamitachi · 2026-02-06 21:00:40

I have a BOOTX64.EFI inside /boot/EFI/BOOT and the folder x86_64-efi inside

This is the complete tree of /boot

seth · 2026-02-06 21:03:59

Yeah, that's the default fallback EFI entry.

seth wrote:

How exactly did you go about installing grub?

Kamitachi · 2026-02-06 21:27:31

Probably I did install it this way, I don't remember quite well, it's been more than a month since I've installed Arch.

grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=GRUB --removable

I remember the --removable because I had to move the BOOTX64.EFI to where it's now with that name.

This is my HOOKS

HOOKS=(base systemd autodetect microcode modconf kms keyboard keymap sd-vconsole block lvm2 filesystems fsck)

seth · 2026-02-06 22:05:50

I remember the --removable

I had to move the BOOTX64.EFI to where it's now

https://wiki.archlinux.org/title/GRUB#D … _boot_path
If you had used --removable you'd not have to move around files.
Fwwi, --efi-directory is supposed to be the directory where you mounted the ESP, ie. in doubt /boot, not /boot/efi

Using --removable/moving the efi to BOOTX64.EFI was strictly necessary itfp?
Or maybe only consequence of the bogus --efi-directory parameter?

Do you have optical drives attached to the system?
Are they being accessed during the pause?

This is my HOOKS

The initramfs is irrelevant here, it loads later.

Kamitachi · 2026-02-06 22:30:04

Yeah, it was necessary. I don't know why, but it was because of the LVM. Arch was unable to boot until I did that.

seth · 2026-02-06 23:25:37

I don't know why, but it was because of the LVM.

You either know it was because of the LVM (what's highly unlikely) or you don't know why at all.
Not both.
You could try to re-install grub and make sure to use the proper ESP path and see whether
1. you get a grub entry in efibootmgr
2. This has any impact on the firmware loading time

Also seth wrote:

Do you have optical drives attached to the system? [(because of the screenshow)]
Are they being accessed during the pause?

Last edited by seth (2026-02-06 23:25:50)

Kamitachi · 2026-02-07 00:30:42

seth wrote:

Do you have optical drives attached to the system? [(because of the screenshow)]
Are they being accessed during the pause?

No, I don't have optical drives.

I tried reinstalling grub but nothing changed
This is what I did:

sudo mount /dev/nvme0n1p1 /boot/efi
sudo grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=GRUB
sudo grub-mkconfig -o /boot/grub/grub.cfg

Now, my sudo efibootmgr looks like this:

BootCurrent: 0001
Timeout: 2 seconds
BootOrder: 0001,0000
Boot0000* GRUB HD(1,GPT,38358050-1949-4b4a-aa71-4c36be695465,0x800,0x100000)/\EFI\GRUB\grubx64.efi
Boot0001* UEFI OS HD(1,GPT,38358050-1949-4b4a-aa71-4c36be695465,0x800,0x100000)/\EFI\BOOT\BOOTX64.EFI0000424f

In the BIOS, I had to change UEFI Hard Disk Drive BBS Priorities to use GRUB instead of UEFI OS, but nothing changed; it still takes ~45s for Firmware POST

Last edited by Kamitachi (2026-02-07 00:45:52)

seth · 2026-02-07 15:11:53

So you don't actually require the --removable flag or the BOOTX64.EFI entry - what if you remove that?
(Have some bootable USB key ready in case this goes wrong)

It's however not likely that this is the cause for the delay at all and the latter will more likely hinge on other changes you made to the UEFI
Did you disable any other "fast boot" features that would skip self-checks?

Kamitachi · 2026-02-07 16:04:17

I disabled the fast boot feature from the motherboard, but that was a while ago, much before I even thought to switch to Linux.
The description of that feature in the motherboard says that it's only to support the fast boot feature in Windows. And that was disabled too when I had Windows.
Anyway, I tried to activate the motherboard's Fast Boot to see if the boot was better, but nothing changed.

seth · 2026-02-07 16:08:53

Can you boot w/o delay when attaching a bootable USB key (and in doubt change the boot order)?

If not, reset/update/re-install the firmware - whatever is going on there is not related to the OS and increasingly unlikely to the bootloader/EFI either.

Scimmia · 2026-02-07 16:11:46

Any hardware/peripherals changes? The firmware time includes setting up hardware and a problem there can cause this. It wouldn't be a bad idea to unplug anything you can and see if it changes.

Last edited by Scimmia (2026-02-07 16:12:00)

Kamitachi · 2026-02-07 16:25:14

seth wrote:

Can you boot w/o delay when attaching a bootable USB key (and in doubt change the boot order)?
If not, reset/update/re-install the firmware - whatever is going on there is not related to the OS and increasingly unlikely to the bootloader/EFI either.

Even thinking that it wasn't related, yesterday I updated the firmware, and it's still the same.

Scimmia wrote:

Any hardware/peripherals changes? The firmware time includes setting up hardware and a problem there can cause this. It wouldn't be a bad idea to unplug anything you can and see if it changes.

Nothing, I just changed from Windows to Linux, nothing else. What I always have connected to my pc is a keyboard, a mouse, a proprietary Bluetooth USB stick for my headphones, a Valve Index, ethernet, and my monitor. I had all this when I was on Windows

tekstryder · 2026-02-07 16:29:51

30-40s is about how long it takes my UEFI to initialize before bootloader if I make ANY changes to DRAM clocks/latency and forget to disable memory training.

Any chance you messed with memory settings? Double check your training profile.

seth · 2026-02-07 16:32:55

seth wrote:

Can you boot w/o delay when attaching a bootable USB key (and in doubt change the boot order)?

What I always have connected to my pc

Remove what's not strictly necessary (everything but keyboard/monitor) and replace the keyboard if you can.
Something might have broken coincidentally.

Kamitachi · 2026-02-07 16:38:57

tekstryder wrote:

30-40s is about how long it takes my UEFI to initialize before bootloader if I make ANY changes to DRAM clocks/latency and forget to disable memory training.
Any chance you messed with memory settings? Double check your training profile.

No, I have not changed any memory settings. Because of this issue, I have tried to disable memory training, but the issue persisted.

seth wrote:

Remove what's not strictly necessary (everything but keyboard/monitor) and replace the keyboard if you can.
Something might have broken coincidentally.

Honestly, I don't think it's anything like this. The day I made the change, my pc was fine, I booted Windows, downloaded the Arch iso and wnet though all the installation.
That morning, my PC booted as fast as expected, but when I rebooted after installing Arch is when I started getting this absurd firmware POST time.
And I have no problem using any of those devices in Linux.

Last edited by Kamitachi (2026-02-07 16:39:51)

seth · 2026-02-07 16:47:49

Honestly, I don't think it's anything like this.

Honestly, knowing is better than believing.

Also seth now a couple of times wrote:

Can you boot w/o delay when attaching a bootable USB key (and in doubt change the boot order)?

tekstryder · 2026-02-07 17:18:28

Oh, I missed upthread... you reinstalled the bootloader, but it's still trying the wrong entry (0001) first.

Set grub to load first:

sudo efibootmgr -o 0000,0001

Arch Linux

#1 2026-02-06 07:38:28

Long BOOT Firmware POST time

#2 2026-02-06 07:51:59

Re: Long BOOT Firmware POST time

#3 2026-02-06 08:11:33

Re: Long BOOT Firmware POST time

#4 2026-02-06 09:07:30

Re: Long BOOT Firmware POST time

#5 2026-02-06 09:26:09

Re: Long BOOT Firmware POST time

#6 2026-02-06 09:38:52

Re: Long BOOT Firmware POST time

#7 2026-02-06 10:07:01

Re: Long BOOT Firmware POST time

#8 2026-02-06 13:30:49

Re: Long BOOT Firmware POST time

#9 2026-02-06 21:00:40

Re: Long BOOT Firmware POST time

#10 2026-02-06 21:03:59

Re: Long BOOT Firmware POST time

#11 2026-02-06 21:27:31

Re: Long BOOT Firmware POST time

#12 2026-02-06 22:05:50

Re: Long BOOT Firmware POST time

#13 2026-02-06 22:30:04

Re: Long BOOT Firmware POST time

#14 2026-02-06 23:25:37

Re: Long BOOT Firmware POST time

#15 2026-02-07 00:30:42

Re: Long BOOT Firmware POST time

#16 2026-02-07 15:11:53

Re: Long BOOT Firmware POST time

#17 2026-02-07 16:04:17

Re: Long BOOT Firmware POST time

#18 2026-02-07 16:08:53

Re: Long BOOT Firmware POST time

#19 2026-02-07 16:11:46

Re: Long BOOT Firmware POST time

#20 2026-02-07 16:25:14

Re: Long BOOT Firmware POST time

#21 2026-02-07 16:29:51

Re: Long BOOT Firmware POST time

#22 2026-02-07 16:32:55

Re: Long BOOT Firmware POST time

#23 2026-02-07 16:38:57

Re: Long BOOT Firmware POST time

#24 2026-02-07 16:47:49

Re: Long BOOT Firmware POST time

#25 2026-02-07 17:18:28

Re: Long BOOT Firmware POST time

Board footer