Welcome to LQ! Sorry no guru answered. This seems to be a general Linux topic.
I
guess you're saying: 51sec is a
lot longer than e.g. M$Win taking 10sec (IDK how)
Maybe you can somehow configure [efi?] firmware (again, IDK; hopefully some LQ'er does), so it takes the typical few seconds.
I think the 'loader' is grub
The 'blame' is init=systemd (probably 'userspace'), all
after 'kernel' (so not relevant I'd
guess).
Here's some ideas for more info: inxi -Fza; efiboomgr -v; egrep -v '^#|^$' /etc/default/grub; journalctl -o short-monotonic -b | nc termbin.com 9999 #
post url
In 1 (Googled) case,
fixing efi BootOrder fixed it. The inxi will tell us
all about your PC. The journal is like dmesg; you might see n-second gaps but IDK what they indicate; without the |nc, you can
see hilites & issues in color. (You can put () around the cmds
before the | pipe nc, to get it all in 1 URL)
Customizing the kernel .config so it doesn't need (grub=loader) initrd/ramdisk would be a
huge, expert project, for max optimization.
More, added later... (At least post just your efibootmgr -v)
Quote:
The “firmware” part of the systemd-analyze report shows the time spent initialising EFI, i.e. the time elapsed between the instant you switched the power on (or the system rebooted) and the instant your boot loader started running. If you want to decrease that you’ll need to investigate your motherboard’s setup options.
|
https://systemd.io/BOOT_LOADER_INTERFACE/
So, the firmware time is UEFI finding your disk, I guess! (see [&
Google] efibootmgr BootOrder above)