You are not logged in.
Pages: 1
I'm trying to reduce the boot up time of my system as much as possible. I've been reading about it here: https://wiki.archlinux.org/index.php/Im … ot_process
For my system, the slowest part is the firmware (for those new to this, run systemd-analyze).
Startup finished in 25.530s (firmware) + 1.496s (loader) + 1.060s (kernel) + 2.099s (userspace) = 30.186s
graphical.target reached after 1.386s in userspace
What exactly is the firmware phase of the boot up, and how does one go about reducing this time?
Update: I did find this, but I'm open to other ideas: https://bbs.archlinux.org/viewtopic.php?id=181188
Last edited by BelowZero (2018-06-29 13:59:19)
Offline
It is the amount of time the firmware reported as taking before the loader started https://github.com/systemd/systemd/blob … amps.c#L22
Offline
Would be good to know your setup and how you configured the bootloader/UEFI. 25s spent without even calling the kernel seems a lot to me.
Offline
Would be good to know your setup and how you configured the bootloader/UEFI. 25s spent without even calling the kernel seems a lot to me.
This. What type of drive are you booting from, and what boot loader are you using?
I get about what you are getting with systemd boot. However, when I boot directly from efistub I get this:
systemd-analyze
Startup finished in 1.943s (kernel) + 1.381s (userspace) = 3.325s
graphical.target reached after 1.380s in userspace
I do boot from an SSD drive. Interestingly, I do not notice a 20 second difference in the time to GUI between systemd boot, and efistub boot. There is a bit of difference, but not nearly the amount shown
by systemd-analyze, which is nearly 20 seconds.
Last edited by cirrus9 (2018-07-01 02:24:09)
Offline
I'm using an SSD, and GRUB. I hadn't considered trying another boot loader. Isn't the "loader" mentioned in these results the boot loader? I may swap that out next and see if there is any improvement. I was able to go into the Dell BIOS and turn off a few items (which are not necessary for my configuration), and that cut a few seconds off my time. This is the latest set of results:
Startup finished in 20.500s (firmware) + 1.454s (loader) + 1.015s (kernel) + 1.759s (userspace) = 24.730s
graphical.target reached after 1.402s in userspace
Offline
I reduced it from 10s to 2s by doing following:
1. Enable fastboot in BIOS.
2. https://wiki.archlinux.org/index.php/GR … workaround
It worked only if both are done.
Offline
Pages: 1