Improving boot speed | Fedora 40 |

[sunby]

I am looking to improve or make any gains to the boot up speed.

Below is the output from systemd-analyze, but I am unclear what ones are I should look to try and focus on to improve the speeds. Appreciate any guidance on what ones to remove or take action to improve upon.

I have gathered potential ones but really unclear if it might be safe to do so and could really do with some guidance.

Thank you

SYSTEM INFO

systemd-analyze blame

6.459s plymouth-quit-wait.service
5.207s dev-ttyS24.device
5.207s sys-devices-platform-serial8250-serial8250:0-serial8250:0.24-tty-ttyS24.device
5.187s sys-module-fuse.device
5.168s dev-ttyS16.device
5.168s sys-devices-platform-serial8250-serial8250:0-serial8250:0.16-tty-ttyS16.device
5.162s dev-ttyS17.device
5.162s sys-devices-platform-serial8250-serial8250:0-serial8250:0.17-tty-ttyS17.device
5.160s sys-devices-platform-serial8250-serial8250:0-serial8250:0.11-tty-ttyS11.device
5.160s dev-ttyS11.device
5.158s sys-devices-platform-serial8250-serial8250:0-serial8250:0.3-tty-ttyS3.device
5.158s dev-ttyS3.device
5.153s dev-ttyS6.device
5.153s sys-devices-platform-serial8250-serial8250:0-serial8250:0.6-tty-ttyS6.device
5.152s dev-ttyS7.device
5.152s sys-devices-platform-serial8250-serial8250:0-serial8250:0.7-tty-ttyS7.device
5.146s dev-ttyS20.device
5.146s sys-devices-platform-serial8250-serial8250:0-serial8250:0.20-tty-ttyS20.device
5.141s dev-ttyS0.device
5.141s sys-devices-platform-serial8250-serial8250:0-serial8250:0.0-tty-ttyS0.device
5.139s dev-ttyS31.device
5.139s sys-devices-platform-serial8250-serial8250:0-serial8250:0.31-tty-ttyS31.device
5.139s sys-devices-platform-serial8250-serial8250:0-serial8250:0.30-tty-ttyS30.device
5.139s dev-ttyS30.device
5.135s sys-devices-platform-serial8250-serial8250:0-serial8250:0.27-tty-ttyS27.device
5.135s dev-ttyS27.device
5.135s dev-ttyS25.device
5.135s sys-devices-platform-serial8250-serial8250:0-serial8250:0.25-tty-ttyS25.device
5.126s dev-ttyS19.device
5.126s sys-devices-platform-serial8250-serial8250:0-serial8250:0.19-tty-ttyS19.device
5.126s dev-ttyS12.device
5.126s sys-devices-platform-serial8250-serial8250:0-serial8250:0.12-tty-ttyS12.device
5.124s sys-devices-platform-serial8250-serial8250:0-serial8250:0.10-tty-ttyS10.device
5.124s dev-ttyS10.device
5.121s sys-devices-platform-serial8250-serial8250:0-serial8250:0.26-tty-ttyS26.device
5.121s dev-ttyS26.device
5.119s dev-ttyS5.device
5.119s sys-devices-platform-serial8250-serial8250:0-serial8250:0.5-tty-ttyS5.device
5.119s dev-ttyS8.device
5.119s sys-devices-platform-serial8250-serial8250:0-serial8250:0.8-tty-ttyS8.device
5.115s sys-devices-platform-serial8250-serial8250:0-serial8250:0.22-tty-ttyS22.device
lines 1-41

systemd-analyze critical-chain

graphical.target @ 19.299s
└─multi-user.target @ 19.299s
└─plymouth-quit-wait.service @ 12.835s +6.459s
└─systemd-user-sessions.service @ 12.690s +90ms
└─remote-fs.target @ 12.663s
└─remote-fs-pre.target @ 8.867s
└─nfs-client.target @ 8.866s
└─gssproxy.service @ 8.744s +120ms
└─network.target @ 8.727s
└─wpa_supplicant.service @ 8.662s +62ms
└─basic.target @ 4.946s
└─dbus-broker.service @ 4.779s +159ms
└─dbus.socket @ 4.758s
└─sysinit.target @ 4.749s
└─systemd-vconsole-setup.service @ 6.157s +493ms
└─systemd-journald.socket
└─system.slice
└─-.slice

systemd-analyze blame --no-pager

6.459s plymouth-quit-wait.service
5.207s dev-ttyS24.device
5.207s sys-devices-platform-serial8250-serial8250:0-serial8250:0.24-tty-ttyS24.device
5.187s sys-module-fuse.device
5.168s dev-ttyS16.device
5.168s sys-devices-platform-serial8250-serial8250:0-serial8250:0.16-tty-ttyS16.device
5.162s dev-ttyS17.device
5.162s sys-devices-platform-serial8250-serial8250:0-serial8250:0.17-tty-ttyS17.device
5.160s sys-devices-platform-serial8250-serial8250:0-serial8250:0.11-tty-ttyS11.device
5.160s dev-ttyS11.device
5.158s sys-devices-platform-serial8250-serial8250:0-serial8250:0.3-tty-ttyS3.device
5.158s dev-ttyS3.device
5.153s dev-ttyS6.device
5.153s sys-devices-platform-serial8250-serial8250:0-serial8250:0.6-tty-ttyS6.device
5.152s dev-ttyS7.device
5.152s sys-devices-platform-serial8250-serial8250:0-serial8250:0.7-tty-ttyS7.device
5.146s dev-ttyS20.device
5.146s sys-devices-platform-serial8250-serial8250:0-serial8250:0.20-tty-ttyS20.device
5.141s dev-ttyS0.device
5.141s sys-devices-platform-serial8250-serial8250:0-serial8250:0.0-tty-ttyS0.device
5.139s dev-ttyS31.device
5.139s sys-devices-platform-serial8250-serial8250:0-serial8250:0.31-tty-ttyS31.device
5.139s sys-devices-platform-serial8250-serial8250:0-serial8250:0.30-tty-ttyS30.device
5.139s dev-ttyS30.device
5.135s sys-devices-platform-serial8250-serial8250:0-serial8250:0.27-tty-ttyS27.device
5.135s dev-ttyS27.device
5.135s dev-ttyS25.device
5.135s sys-devices-platform-serial8250-serial8250:0-serial8250:0.25-tty-ttyS25.device
5.126s dev-ttyS19.device
5.126s sys-devices-platform-serial8250-serial8250:0-serial8250:0.19-tty-ttyS19.device
5.126s dev-ttyS12.device
5.126s sys-devices-platform-serial8250-serial8250:0-serial8250:0.12-tty-ttyS12.device
5.124s sys-devices-platform-serial8250-serial8250:0-serial8250:0.10-tty-ttyS10.device
5.124s dev-ttyS10.device
5.121s sys-devices-platform-serial8250-serial8250:0-serial8250:0.26-tty-ttyS26.device
5.121s dev-ttyS26.device
5.119s dev-ttyS5.device
5.119s sys-devices-platform-serial8250-serial8250:0-serial8250:0.5-tty-ttyS5.device
5.119s dev-ttyS8.device
5.119s sys-devices-platform-serial8250-serial8250:0-serial8250:0.8-tty-ttyS8.device
5.115s sys-devices-platform-serial8250-serial8250:0-serial8250:0.22-tty-ttyS22.device
5.115s dev-ttyS22.device
5.114s sys-devices-platform-serial8250-serial8250:0-serial8250:0.13-tty-ttyS13.device
5.114s dev-ttyS13.device
5.113s dev-ttyS15.device
5.113s sys-devices-platform-serial8250-serial8250:0-serial8250:0.15-tty-ttyS15.device
5.112s dev-ttyS2.device
5.112s sys-devices-platform-serial8250-serial8250:0-serial8250:0.2-tty-ttyS2.device
5.109s dev-ttyS4.device
5.109s sys-devices-platform-serial8250-serial8250:0-serial8250:0.4-tty-ttyS4.device
5.108s sys-devices-platform-serial8250-serial8250:0-serial8250:0.29-tty-ttyS29.device
5.108s dev-ttyS29.device
5.107s sys-devices-platform-serial8250-serial8250:0-serial8250:0.18-tty-ttyS18.device
5.107s dev-ttyS18.device
5.104s dev-ttyS14.device
5.104s sys-devices-platform-serial8250-serial8250:0-serial8250:0.14-tty-ttyS14.device
5.103s dev-ttyS21.device
5.102s sys-devices-platform-serial8250-serial8250:0-serial8250:0.21-tty-ttyS21.device
5.101s dev-ttyS1.device
5.101s sys-devices-platform-serial8250-serial8250:0-serial8250:0.1-tty-ttyS1.device
5.101s sys-devices-platform-serial8250-serial8250:0-serial8250:0.23-tty-ttyS23.device
5.101s dev-ttyS23.device
5.095s sys-devices-platform-serial8250-serial8250:0-serial8250:0.28-tty-ttyS28.device
5.095s dev-ttyS28.device
5.095s dev-ttyS9.device
5.095s sys-devices-platform-serial8250-serial8250:0-serial8250:0.9-tty-ttyS9.device
4.921s sys-module-configfs.device
4.841s sys-devices-pci0000:00-0000:00:02.0-drm-card1-card1\x2deDP\x2d1-intel_backlight.device
4.789s dev-disk-by\x2ddiskseq-1\x2dpart5.device
4.789s dev-disk-by\x2dlabel-fedora_localhost\x2dlive.device
4.789s dev-disk-by\x2dpartuuid-e0b15beb\x2d249f\x2d4261\x2dbd98\x2d5057fe9d1d6f.device
4.789s dev-disk-by\x2dpath-pci\x2d0000:3a:00.0\x2dnvme\x2d1\x2dpart5.device
4.789s dev-disk-by\x2did-nvme\x2dPC401_NVMe_SK_hynix_256GB_MS8AN55961030AM0C_1\x2dpart5.device
4.789s dev-nvme0n1p5.device
4.789s dev-disk-by\x2did-nvme\x2deui.ace42e8175013db6\x2dpart5.device
4.789s sys-devices-pci0000:00-0000:00:1c.4-0000:3a:00.0-nvme-nvme0-nvme0n1-nvme0n1p5.device
4.789s dev-disk-by\x2did-nvme\x2dPC401_NVMe_SK_hynix_256GB_MS8AN55961030AM0C\x2dpart5.device
4.789s dev-disk-by\x2duuid-52538567\x2dfb7d\x2d4f5a\x2d9055\x2d3bd1faa3e3a6.device
4.733s sys-devices-pci0000:00-0000:00:1c.4-0000:3a:00.0-nvme-nvme0-nvme0n1-nvme0n1p2.device
4.733s dev-disk-by\x2did-nvme\x2deui.ace42e8175013db6\x2dpart2.device
4.733s dev-disk-by\x2ddiskseq-1\x2dpart2.device
4.733s dev-disk-by\x2did-nvme\x2dPC401_NVMe_SK_hynix_256GB_MS8AN55961030AM0C_1\x2dpart2.device
4.733s dev-disk-by\x2did-nvme\x2dPC401_NVMe_SK_hynix_256GB_MS8AN55961030AM0C\x2dpart2.device
4.733s dev-disk-by\x2duuid-2E6B\x2d03B4.device
4.733s dev-disk-by\x2dpartlabel-EFI\x5cx20System\x5cx20Partition.device
4.733s dev-disk-by\x2dpath-pci\x2d0000:3a:00.0\x2dnvme\x2d1\x2dpart2.device
4.733s dev-disk-by\x2dpartuuid-d83e23af\x2d3ab5\x2d416a\x2d93e6\x2df3e0f9f870dc.device
4.733s dev-nvme0n1p2.device
4.709s dev-disk-by\x2dpath-pci\x2d0000:3a:00.0\x2dnvme\x2d1\x2dpart3.device
4.709s dev-nvme0n1p3.device
4.709s dev-disk-by\x2did-nvme\x2dPC401_NVMe_SK_hynix_256GB_MS8AN55961030AM0C_1\x2dpart3.device
4.709s dev-disk-by\x2did-nvme\x2dPC401_NVMe_SK_hynix_256GB_MS8AN55961030AM0C\x2dpart3.device
4.709s dev-disk-by\x2dpartlabel-Microsoft\x5cx20reserved\x5cx20partition.device
4.709s dev-disk-by\x2did-nvme\x2deui.ace42e8175013db6\x2dpart3.device
4.709s dev-disk-by\x2dpartuuid-57fa2027\x2d8e83\x2d4984\x2db007\x2dda122fc5709d.device
4.709s sys-devices-pci0000:00-0000:00:1c.4-0000:3a:00.0-nvme-nvme0-nvme0n1-nvme0n1p3.device
4.709s dev-disk-by\x2ddiskseq-1\x2dpart3.device
4.706s dev-disk-by\x2did-nvme\x2dPC401_NVMe_SK_hynix_256GB_MS8AN55961030AM0C_1\x2dpart1.device
4.706s dev-disk-by\x2did-nvme\x2deui.ace42e8175013db6\x2dpart1.device
4.706s dev-disk-by\x2dpartuuid-2da5ce27\x2d9f91\x2d4877\x2da6c8\x2d122c9e65a98d.device
4.706s dev-disk-by\x2dlabel-Recovery.device
4.706s dev-disk-by\x2did-nvme\x2dPC401_NVMe_SK_hynix_256GB_MS8AN55961030AM0C\x2dpart1.device
4.706s dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition.device
4.706s dev-nvme0n1p1.device
4.706s dev-disk-by\x2dpath-pci\x2d0000:3a:00.0\x2dnvme\x2d1\x2dpart1.device
4.706s sys-devices-pci0000:00-0000:00:1c.4-0000:3a:00.0-nvme-nvme0-nvme0n1-nvme0n1p1.device
4.706s dev-disk-by\x2duuid-EA3A6A743A6A3E27.device
4.706s dev-disk-by\x2ddiskseq-1\x2dpart1.device
4.694s dev-disk-by\x2did-nvme\x2deui.ace42e8175013db6\x2dpart4.device
4.694s dev-disk-by\x2dpath-pci\x2d0000:3a:00.0\x2dnvme\x2d1\x2dpart4.device
4.694s dev-disk-by\x2duuid-00b8a168\x2d6d09\x2d4410\x2da289\x2d0d6d31236845.device
4.694s dev-disk-by\x2did-nvme\x2dPC401_NVMe_SK_hynix_256GB_MS8AN55961030AM0C_1\x2dpart4.device
4.694s dev-disk-by\x2dpartuuid-4adf24c2\x2dae8a\x2d401b\x2dbf13\x2df5066d844f46.device
4.694s dev-disk-by\x2ddiskseq-1\x2dpart4.device
4.694s dev-nvme0n1p4.device
4.694s sys-devices-pci0000:00-0000:00:1c.4-0000:3a:00.0-nvme-nvme0-nvme0n1-nvme0n1p4.device
4.694s dev-disk-by\x2did-nvme\x2dPC401_NVMe_SK_hynix_256GB_MS8AN55961030AM0C\x2dpart4.device
4.691s dev-disk-by\x2dpath-pci\x2d0000:3a:00.0\x2dnvme\x2d1.device
4.691s dev-disk-by\x2ddiskseq-1.device
4.691s sys-devices-pci0000:00-0000:00:1c.4-0000:3a:00.0-nvme-nvme0-nvme0n1.device
4.691s dev-disk-by\x2did-nvme\x2deui.ace42e8175013db6.device
4.691s dev-nvme0n1.device
4.691s dev-disk-by\x2did-nvme\x2dPC401_NVMe_SK_hynix_256GB_MS8AN55961030AM0C.device
4.691s dev-disk-by\x2did-nvme\x2dPC401_NVMe_SK_hynix_256GB_MS8AN55961030AM0C_1.device
4.005s NetworkManager-wait-online.service
3.179s fwupd.service
2.060s abrtd.service
1.517s dracut-initqueue.service
1.496s initrd-switch-root.service
1.438s systemd-journal-flush.service
1.273s firewalld.service
1.085s polkit.service
1.063s power-profiles-daemon.service
1.059s avahi-daemon.service
991ms mullvad-early-boot-blocking.service
990ms thermald.service
904ms udisks2.service
844ms systemd-udev-trigger.service
837ms accounts-daemon.service
768ms upower.service
737ms dracut-shutdown.service
684ms NetworkManager.service
619ms systemd-tmpfiles-setup-dev-early.service
562ms user @ 1000.service
556ms livesys.service
500ms iio-sensor-proxy.service
493ms systemd-vconsole-setup.service
475ms systemd-resolved.service
473ms systemd-oomd.service
446ms systemd-rfkill.service
417ms rtkit-daemon.service
414ms systemd-tmpfiles-setup.service
373ms var-lib-nfs-rpc_pipefs.mount
370ms systemd-logind.service
354ms ModemManager.service
353ms chronyd.service
311ms systemd-udevd.service
291ms passim.service
282ms systemd-zram-setup @ zram0.service
264ms switcheroo-control.service
259ms systemd-journald.service
242ms systemd-machined.service
242ms systemd-tmpfiles-setup-dev.service
230ms systemd-binfmt.service
214ms import-state.service
206ms virtqemud.service
177ms audit-rules.service
175ms sssd-kcm.service
173ms smartd.service
161ms boot-efi.mount
159ms dbus-broker.service
153ms modprobe @ loop.service
152ms systemd-update-utmp.service
145ms systemd-modules-load.service
142ms systemd-network-generator.service
141ms systemd-remount-fs.service
139ms systemd-boot-update.service
134ms systemd-userdbd.service
130ms systemd-backlight @ backlight:intel_backlight.service
129ms lvm2-monitor.service
129ms plymouth-start.service
126ms bluetooth.service
125ms modprobe @ drm.service
120ms dracut-cmdline.service
120ms gssproxy.service
111ms modprobe @ dm_mod.service
103ms systemd-fsck @ dev-disk-by\x2duuid-2E6B\x2d03B4.service
102ms colord.service
97ms plymouth-read-write.service
92ms gdm.service
90ms systemd-user-sessions.service
87ms livesys-late.service
83ms cups.service
79ms dev-zram0.swap
78ms systemd-sysctl.service
78ms plymouth-switch-root.service
77ms systemd-backlight @ leds:dell::kbd_backlight.service
77ms systemd-random-seed.service
71ms kmod-static-nodes.service
68ms dev-mqueue.mount
67ms sys-kernel-debug.mount
67ms dev-hugepages.mount
66ms rpc-statd-notify.service
65ms sys-kernel-tracing.mount
63ms proc-sys-fs-binfmt_misc.mount
62ms wpa_supplicant.service
60ms auditd.service
59ms systemd-fsck @ dev-disk-by\x2duuid-00b8a168\x2d6d09\x2d4410\x2da289\x2d0d6d31236845.service
54ms uresourced.service
54ms dracut-pre-pivot.service
50ms flatpak-system-helper.service
44ms user-runtime-dir @ 1000.service
40ms initrd-cleanup.service
38ms tmp.mount
34ms home.mount
33ms systemd-update-utmp-runlevel.service
30ms sys-fs-fuse-connections.mount
29ms tpm2-abrmd.service
22ms dracut-pre-udev.service
20ms boot.mount
17ms systemd-fsck-root.service
16ms systemd-sysusers.service
15ms initrd-parse-etc.service
10ms modprobe @ configfs.service
7ms initrd-udevadm-cleanup-db.service
1ms modprobe @ fuse.service

Potential solutions

Disable unnecessary services

sudo systemctl disable plymouth-quit-wait.service
sudo systemctl disable dev-ttyS24.device
sudo systemctl disable dev-ttyS16.device
sudo systemctl disable dev-ttyS17.device
sudo systemctl disable dev-ttyS11.device
sudo systemctl disable dev-ttyS3.device
sudo systemctl disable dev-ttyS6.device
sudo systemctl disable dev-ttyS7.device
sudo systemctl disable dev-ttyS20.device
sudo systemctl disable dev-ttyS0.device
sudo systemctl disable dev-ttyS31.device
sudo systemctl disable NetworkManager-wait-online.service
sudo systemctl disable gssproxy.service
sudo systemctl disable fwupd.service
sudo systemctl disable systemd-journal-flush.service

Optimize initramfs

sudo dracut --force

Disable unnecessary modules

sudo systemctl disable modprobe @ loop.service
sudo systemctl disable modprobe @ dm_mod.service
sudo systemctl disable modprobe @ drm.service

Blacklist serial8250 module

echo “blacklist serial8250” | sudo tee /etc/modprobe.d/blacklist.conf
sudo update-initramfs -u

[Espionage724]

Do you have a plain systemd-analyze for comparison?

---

I had this on Fedora 40 without doing much:

Startup finished in 9.716s (firmware) + 1.638s (loader) + 992ms (kernel) + 6.840s (initrd) + 10.943s (userspace) = 30.132s

With a bit of tweaking (and slight cheating ) on the same computer with openSUSE Tumbleweed:

Startup finished in 4.491s (firmware) + 603ms (loader) + 452ms (kernel) + 3.874s (initrd) + 5.691s (userspace) = 15.112s

In my case (Dell Latitude 5591 UEFI, SK hynix P31 1TB):

• firmware is around 4s (open) or 10s (closed) depending on if I leave my laptop lid open while it’s connected to external stuff; it doesn’t feel like 10s real-time though so I’m not sure how that’s calculated; it was closed for Fedora and open for oS
• loader counts the GRUB timeout; on Fedora I kept it default but had no timer/0 on oS
• Not sure on kerneldifferences; I used the default one on both Fedora and oS
• initrd was a fun one; I kept defaults on Fedora but I did some dracut tweaks on oS (also fine on Fedora). I found that cat/no compression was fastest, but a few others were close too with half the filesize
• Not sure what userspace calculates

[sunby]

Thanks @Espionage724

here’s a clean output below of systemd-analyze

Startup finished in 8.745s (firmware) + 6.577s (loader) + 2.367s (kernel) + 3.653s (initrd) + 18.975s (userspace) = 40.319s graphical.target reached after 18.918s in userspace.

appreciate any pointers. thank you

[Espionage724]

firmware might be shortened by enabling Fast Boot in UEFI settings (others report issues; I didn’t notice any on a Dell 5591)

loader is probably 5 seconds of Fedora’s GRUB timeout but I’m not sure if it’s actually calculated when it’s not shown on boot (usually auto-shows on improper restarts)

If there’s any black screens at the boot animation, or between it and going to the log-in screen, that could possibly be sped-up by adding the kernel option i915.fastboot=1 but I think that might be default on all Intel GPUs (iirc I didn’t see that option with modinfo -p i915 on F40)

If you have CPU virtualization enabled in UEFI settings, disable both settings for it (unless you use VMs); if Intel’s IOMMU is on, it’s slower on bare-hardware than just DMA’ing(?)/communicating with devices directly; Dell has it enabled by-default on my 5591, and iirc Fedora’s default IOMMU policy is to run everything through it (not Passthrough).

991ms mullvad-early-boot-blocking.service

If that’s a VPN app, I’d remove it and only handle it with OpenVPN configs through NetworkManager or WireGuard.

4.005s NetworkManager-wait-online.service

If you use wifi, I’d go to NetworkManager and disable the main AP for all users; I think that’ll stop network from trying to be reached at the log-in screen and theoretically should also stop any hold-ups from waiting for network.

[sunby]

cheers pal - fastboot is enabled in BIOS settings, I find the VPN app easier to use, but I will try and learn the Wireguard settings to see if I can make any gains from that.

Re. loader and the kernel
this is the current setup

GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR=“$(sed ‘s, release .*$,g’ /etc/system-release)”
GRUB_DEFAULT=saved
GRUB_DISABLE_SUBMENU=true
GRUB_TERMINAL_OUTPUT=“console”
GRUB_CMDLINE_LINUX=“rhgb quiet”
GRUB_DISABLE_RECOVERY=“true”
GRUB_ENABLE_BLSCFG=true

I am not sure if I add a line in there with i915.fastboot=1 or somewhere else?

I do have a Boxxee Ubuntu setup but I use that rarely, I dont suppose that plays a part.

I have also disabled AP for all users.

AFTER

Startup finished in 22.810s (firmware) + 10.657s (loader) + 2.844s (kernel) + 3.039s (initrd) + 13.934s (userspace) = 53.285s graphical.target reached after 13.884s in userspace.

Somehow, ive managed to make it slower…

[boredsquirrel]

No keep the VPN app if you care about privacy.

This is an early boot blocker for a reason.

How can I configure a killswitch for OpenVPN using firewalld?

There are some guides available online on how to do this, but they don’t really offer what I need. Also, they seem very complicated and I wonder if there’s not an easier solution. Basically, I want to block all incoming and all outgoing traffic except outgoing VPN traffic on the tun0 interface. The only traffic allowed outside of tun0 should be the initial connection to the VPN server (to be more specific, the ip address of the VPN server should be whitelisted so I can establish the VPN conne…

[sunby]

cheers…

I’ve not done much else but noticed after a few reboots, that the speed has gone back to what it was more or less…

Startup finished in 8.872s (firmware) + 8.068s (loader) + 2.329s (kernel) + 3.778s (initrd) + 18.258s (userspace) = 41.307s graphical.target reached after 18.194s in userspace.

I’ve also taken an output of systemd-analyze plot not sure if that is helpful on anything else to try, below

[computersavvy (Jeff V)]

Half of that 40 second total is in firmware and loader and kernel. Don’t know how that could be reliably reduced much.

The plot is totally unreadable due to size. Please post the actual .svg file instead of the image.

Mine spends 23+ seconds with firmware and loader before it begins o load the kernel and then finishes loading in an additional 17 seconds or 40.6 seconds total.

[sunby]

cheers @computersavvy - I wasn’t able to share the .SVG to the post, as there is prompt which gives a

Sorry, the file you are trying to upload is not authorised (authorised extensions: jpg, jpeg, png, gif, webp).

I have uploaded the .SVG here Filen

[josevillani]

I reckon Fedora has always been extremely slow to boot. Comparison with a similar computer on the same lan, identical SDDs:

Debian 12:
$ systemd-analyze
Startup finished in 13.023s (kernel) + 15.468s (userspace) = 28.492s

Fedora 40:
$ systemd-analyze
Startup finished in 1.524s (kernel) + 36.695s (initrd) + 12.996s (userspace) = 51.216s

[Espionage724]

@josevillani

I reckon Fedora has always been extremely slow to boot.

I don’t know about extremely in my case, but Fedora has consistently booted a little slower than openSUSE TW and Ubuntu for me for years. I just figure it’s SELinux being loaded or some other security stuff the other distros don’t have

[computersavvy (Jeff V)]

@josevillani

Debian 12:
$ systemd-analyze
Startup finished in 13.023s (kernel) + 15.468s (userspace) = 28.492s

Fedora 40:
$ systemd-analyze
Startup finished in 1.524s (kernel) + 36.695s (initrd) + 12.996s (userspace) = 51.216s

I wonder why your results are not showing the full output on fedora.?
Your listing here is missing the firmware and loader bits which are part of the total shown with mine. This on my desktop host.

$ systemd-analyze
Startup finished in 16.036s (firmware) + 7.257s (loader) + 3.542s (kernel) + 1.512s (initrd) + 12.265s (userspace) = 40.615s 
graphical.target reached after 12.237s in userspace.

and this on my f40 VM (which does not show either the firmware or loader items)

$ systemd-analyze
Startup finished in 1.073s (kernel) + 1.514s (initrd) + 6.221s (userspace) = 8.809s 
graphical.target reached after 6.173s in userspace.

[josevillani]

I wonder why your results are not showing the full output on fedora.?

I couldn’t tell Maybe because I use MBR instead of EFI, or I use LUKS encryption. That’s just the way it shows and I’ve not been able to reproduce your output. Sorry, I tried.

[josevillani]

I just figure it’s SELinux being loaded or some other security stuff the other distros don’t have

I completely disabled SELinux quite a while ago after I had serious/critical issues with btrfs, snapshots and rsync.

[hamrheadcorvette (hammerhead corvette)]

@computersavvy

Half of that 40 second total is in firmware and loader and kernel.

systemd-boot

@josevillani

I completely disabled SELinux

Questionable . . .

[josevillani]

Questionable . . .

Maybe. I’ve been leaving without it since Debian 3 and I’m still very well.

[hamrheadcorvette (hammerhead corvette)]

@josevillani

since Debian 3

When was the last time you updated? I know Debian updates are slow but. . .

[josevillani]

Haha, a few weeks ago. Currently Debian 12.5

[sunby]

I get the feeling that fedora boot up is generally slow vs other distros - but there may be some marginally gains to be made but with some trade off…