LinuxQuestions.org - Slow boot: long firmware and loader time.

- Linux Mint (https://www.linuxquestions.org/questions/linux-mint-84/)

- - Slow boot: long firmware and loader time. (https://www.linuxquestions.org/questions/linux-mint-84/slow-boot-long-firmware-and-loader-time-4175732169/)

Slow boot: long firmware and loader time.

Hello! I recently installed Linux Mint (21.2 Cinnamon) and encountered a problem that my PC is taking an unusually long time to boot.
Despite exploring various solutions, I haven't yet found anything that resolves the problem.
As a newcomer to Linux I'm still navigating in the system.

Code:

systemd-analyze

Startup finished in 19.648s (firmware) + 19.672s (loader) + 6.555s (kernel) + 5.592s (userspace) = 51.468s

Code:

systemd-analyze blame

3.170s NetworkManager-wait-online.service

1.549s systemd-udev-settle.service

1.533s ifupdown-pre.service

 352ms blueman-mechanism.service

 254ms dev-nvme0n1p2.device

 230ms networkd-dispatcher.service

 201ms accounts-daemon.service

 193ms udisks2.service

...

Code:

systemd-analyze critical-chain

The time when unit became active or started is printed after the "@" character.

The time the unit took to start is printed after the "+" character.



graphical.target @5.582s

└─multi-user.target @5.582s

  └─kerneloops.service @5.555s +26ms

    └─network-online.target @5.549s

      └─NetworkManager-wait-online.service @2.377s +3.170s

        └─NetworkManager.service @2.226s +148ms

          └─dbus.service @2.225s

            └─basic.target @2.218s

              └─sockets.target @2.218s

                └─uuidd.socket @2.218s

                  └─sysinit.target @2.216s

                    └─systemd-timesyncd.service @2.104s +112ms

                      └─systemd-tmpfiles-setup.service @2.092s +9ms

                        └─local-fs.target @2.088s

                          └─zfs-mount.service @2.081s +6ms

                            └─zfs-import.target @2.081s

Code:

cat /etc/fstab

# /etc/fstab: static file system information.

#

# Use 'blkid' to print the universally unique identifier for a

# device; this may be used with UUID= as a more robust way to name devices

# that works even if disks are added and removed. See fstab(5).

#

# <file system> <mount point>  <type>  <options>      <dump>  <pass>

# / was on /dev/nvme0n1p2 during installation

UUID=375820d8-3df9-4e7c-a918-63c731031e7b /              ext4    errors=remount-ro 0      1

# /boot/efi was on /dev/nvme0n1p1 during installation

UUID=FD0D-5F3B  /boot/efi      vfat    umask=0077      0      1

/swapfile                                none            swap    sw              0      0

I'm hopeful that this output provides some insight into the nature of the problem. Any assistance or guidance would be greatly appreciated!

Moderator Response

Moved: This thread is more suitable in <Linux Mint> and has been moved accordingly to help your thread/question get the exposure it deserves.

I hope LQgurus chime in, so I&others can learn.

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)

All good now? I am waiting for your response and till then I will visit https://www.linkedin.com/pulse/use-o...-landry-lqjre/ here because I want to know about the best research paper writing service and why shoud I use it. I am not that good at writing an essay assignment and that is why I need a help.