You are not logged in.
Pages: 1
I looked at the wiki, but I'm having a hard time determining what the actual cause of my times are, so I haven't started tweaking.
I'm not particularly concerned with my boot time as a few seconds means nothing to me. What I'm more curious about is the reason why something might be slower than it should be, in case that indicates potential issues somewhere else.
Hardware:
CPU: Ryzen 5 3600
GPU: 5700 XT
Mobo: B450
SSD: WD Black 500GB nVME
Misc details:
Using LVM encryption
Fastboot disabled
Secure boot disabled
CSM disabled
wu% systemd-analyze time
Startup finished in 15.063s (firmware) + 797ms (loader) + 12.585s (kernel) + 999ms (userspace) = 29.445s graphical.target reached after 960ms in userspace
wu% systemd-analyze blame
371ms lvm2-monitor.service
366ms dev-mapper-vg\x2droot.device
109ms lvm2-pvscan@254:0.service
95ms systemd-journal-flush.service
85ms boot.mount
83ms user@1000.service
58ms systemd-networkd.service
57ms polkit.service
57ms systemd-journald.service
56ms systemd-udev-trigger.service
51ms avahi-daemon.service
50ms systemd-modules-load.service
47ms bluetooth.service
42ms systemd-udevd.service
42ms systemd-binfmt.service
40ms geoclue.service
39ms cups.service
38ms systemd-timesyncd.service
30ms sys-kernel-debug.mount
29ms dev-mqueue.mount
29ms systemd-fsck@dev-disk-by\x2duuid-DFC5\x2d9337.service 29ms sys-kernel-tracing.mount
29ms systemd-logind.service
28ms tmp.mount
28ms dev-hugepages.mount
28ms kmod-static-nodes.service
26ms modprobe@configfs.service
26ms modprobe@drm.service
25ms modprobe@fuse.service
21ms systemd-rfkill.service
18ms systemd-remount-fs.service
14ms systemd-tmpfiles-setup.service
12ms sys-kernel-config.mount
11ms proc-sys-fs-binfmt_misc.mount
11ms sys-fs-fuse-connections.mount
10ms systemd-random-seed.service
9ms systemd-tmpfiles-setup-dev.service
8ms wpa_supplicant.service
6ms systemd-update-utmp.service
4ms user-runtime-dir@1000.service
3ms systemd-sysctl.service
2ms systemd-user-sessions.service
2ms rtkit-daemon.service
Anything standing out as concerning?
Offline
You can't really do anything about "firmware". You can experiment with settings in the UEFI/BIOS menus and see if something helps. There's usually a menu setting that promises a faster boot. On my system it doesn't improve the "firmware" boot time, it pretty much just disables the keyboard and makes it so I can't get into the UEFI/BIOS menus anymore without rebooting from the OS through "systemctl reboot --firmware-setup".
About your high "kernel" time:
If you replace the "udev" initramfs hook with the "systemd" hook in /etc/mkinitcpio.conf, you'll get that "kernel" number split into two numbers "kernel" and "initrd". You'll get full logs for what's happening at that early point in boot.
If you want to try change over to the "systemd" hook, make sure to look at the "mkinitcpio" ArchWiki article. There is a table somewhere in that article that compares "udev" and "systemd" setups. You have to switch other hooks over as well if you use them, for example "encrypt" to "sd-encrypt".
Offline
You can't really do anything about "firmware". You can experiment with settings in the UEFI/BIOS menus and see if something helps. There's usually a menu setting that promises a faster boot. On my system it doesn't improve the "firmware" boot time, it pretty much just disables the keyboard and makes it so I can't get into the UEFI/BIOS menus anymore without rebooting from the OS through "systemctl reboot --firmware-setup".
About your high "kernel" time:
If you replace the "udev" initramfs hook with the "systemd" hook in /etc/mkinitcpio.conf, you'll get that "kernel" number split into two numbers "kernel" and "initrd". You'll get full logs for what's happening at that early point in boot.
If you want to try change over to the "systemd" hook, make sure to look at the "mkinitcpio" ArchWiki article. There is a table somewhere in that article that compares "udev" and "systemd" setups. You have to switch other hooks over as well if you use them, for example "encrypt" to "sd-encrypt".
Ah, fair enough. If the firmware time isn't a result of a "problem" then I'll gladly live with it. Just making sure I haven't messed something up.
I'll look into switching to the systemd hook. Thanks for the recommendation and link to the wiki!
Offline
Pages: 1