Quite long boot time compared to windows?

Ask Fedora
, , , , , , , ,
1

Hi I recentry installed fedora on this computer:

$ inxi -F
System:
  Host: davide-fedora Kernel: 6.10.6-200.fc40.x86_64 arch: x86_64 bits: 64
  Desktop: KDE Plasma v: 6.1.4 Distro: Fedora Linux 40 (KDE Plasma)
Machine:
  Type: Laptop System: ASUSTeK product: ASUS TUF Gaming F15 FX507ZV4_FX507ZV4
    v: 1.0 serial: <superuser required>
  Mobo: ASUSTeK model: FX507ZV4 v: 1.0 serial: <superuser required>
    UEFI: American Megatrends LLC. v: FX507ZV4.328 date: 04/15/2024
Battery:
  ID-1: BAT0 charge: 64.2 Wh (82.9%) condition: 77.4/90.0 Wh (86.0%)
    volts: 16.4 min: 15.9
CPU:
  Info: 14-core (6-mt/8-st) model: 12th Gen Intel Core i7-12700H bits: 64
    type: MST AMCP cache: L2: 11.5 MiB
  Speed (MHz): avg: 509 min/max: 400/4600:4700:3500 cores: 1: 400 2: 400
    3: 2593 4: 400 5: 400 6: 400 7: 400 8: 400 9: 400 10: 400 11: 400 12: 400
    13: 400 14: 400 15: 400 16: 400 17: 400 18: 400 19: 400 20: 400
Graphics:
  Device-1: Intel Alder Lake-P Integrated Graphics driver: i915 v: kernel
  Device-2: NVIDIA AD107M [GeForce RTX 4060 Max-Q / Mobile] driver: nvidia
    v: 560.35.03
  Device-3: Sonix USB2.0 HD UVC WebCam driver: uvcvideo type: USB
  Display: wayland server: X.org v: 1.20.14 with: Xwayland v: 24.1.2
    compositor: kwin_wayland driver: N/A resolution: 1536x864
  API: EGL v: 1.5 drivers: iris,nvidia,swrast
    platforms: gbm,wayland,x11,surfaceless,device
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: intel mesa v: 24.1.7
    renderer: Mesa Intel Graphics (ADL GT2)
  API: Vulkan v: 1.3.290 drivers: N/A surfaces: xcb,xlib,wayland
Audio:
  Device-1: Intel Alder Lake PCH-P High Definition Audio driver: snd_hda_intel
  Device-2: NVIDIA driver: snd_hda_intel
  API: ALSA v: k6.10.6-200.fc40.x86_64 status: kernel-api
  Server-1: PipeWire v: 1.0.7 status: active
Network:
  Device-1: Intel Alder Lake-P PCH CNVi WiFi driver: iwlwifi
  IF: wlo1 state: up mac: 8e:c0:26:70:47:63
  Device-2: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    driver: r8169
  IF: enp55s0 state: down mac: 08:bf:b8:c2:00:95
Bluetooth:
  Device-1: Intel AX201 Bluetooth driver: btusb type: USB
  Report: btmgmt ID: hci0 state: up address: 30:89:4A:D1:69:5A bt-v: 5.2
RAID:
  Hardware-1: Intel Volume Management Device NVMe RAID Controller driver: vmd
Drives:
  Local Storage: total: 1.38 TiB used: 809.35 GiB (57.5%)
  ID-1: /dev/nvme0n1 vendor: Micron model: 2400 MTFDKBA512QFM
    size: 476.94 GiB
  ID-2: /dev/nvme1n1 vendor: Samsung model: SSD 970 EVO Plus 1TB
    size: 931.51 GiB
Partition:
  ID-1: / size: 929.91 GiB used: 414.23 GiB (44.5%) fs: btrfs dev: /dev/dm-0
  ID-2: /boot size: 973.4 MiB used: 476.2 MiB (48.9%) fs: ext4
    dev: /dev/nvme1n1p2
  ID-3: /boot/efi size: 598.8 MiB used: 19 MiB (3.2%) fs: vfat
    dev: /dev/nvme1n1p1
  ID-4: /home size: 929.91 GiB used: 414.23 GiB (44.5%) fs: btrfs
    dev: /dev/dm-0
Swap:
  ID-1: swap-1 type: zram size: 8 GiB used: 131 MiB (1.6%) dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 43.0 C mobo: N/A
  Fan Speeds (rpm): cpu: 2500
Info:
  Memory: total: 16 GiB available: 15.24 GiB used: 4.93 GiB (32.4%)
  Processes: 432 Uptime: 11h 15m Shell: Bash inxi: 3.3.34

The drive is encrypted. Time to boot is approx. 25 seconds, which is actually quite lonhger than windows on this same machine (7 seconds). I was wondering if there was some optimization I could make.

 systemd-analyze 
Startup finished in 10.942s (firmware) + 1.131s (loader) + 1.551s (kernel) + 8.514s (initrd) + 3.108s (userspace) = 25.249s 
graphical.target reached after 3.097s in userspace.


$ 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 @3.097s
└─sddm.service @3.097s
  └─plymouth-quit.service @3.072s +23ms
    └─systemd-user-sessions.service @3.059s +6ms
      └─remote-fs.target @3.057s
        └─remote-fs-pre.target @3.057s
          └─nfs-client.target @3.056s
            └─gssproxy.service @3.003s +53ms
              └─network.target @2.999s
                └─wpa_supplicant.service @2.989s +9ms
                  └─basic.target @1.830s
                    └─dbus-broker.service @1.806s +21ms
                      └─dbus.socket @1.764s
                        └─sysinit.target @1.755s
                          └─systemd-resolved.service @1.710s +44ms
                            └─systemd-tmpfiles-setup.service @1.580s +102ms
                              └─local-fs.target @1.576s
                                └─boot-efi.mount @1.563s +11ms
                                  └─boot.mount @912ms +14ms
                                    └─systemd-fsck@dev-disk-by\x2duuid-9c312b86\x2da6c6\x2d4b7a\x2d8faf\x2d222fcc595926.service @846ms +33ms
                                      └─dev-disk-by\x2duuid-9c312b86\x2da6c6\x2d4b7a\x2d8faf\x2d222fcc595926.device @584542y 2w 2d 20h 1min 41.744s +8.616s


$ systemd-analyze blame
8.922s sys-module-fuse.device
8.879s sys-devices-LNXSYSTM:00-LNXSYBUS:00-MSFT0101:00-tpm-tpm0.device
8.879s dev-tpm0.device
8.856s sys-devices-platform-serial8250-serial8250:0-serial8250:0.0-tty-ttyS0.device
8.856s dev-ttyS0.device
8.855s dev-ttyS3.device
8.855s dev-ttyS2.device
8.855s sys-devices-platform-serial8250-serial8250:0-serial8250:0.3-tty-ttyS3.device
8.855s sys-devices-platform-serial8250-serial8250:0-serial8250:0.2-tty-ttyS2.device
8.855s dev-ttyS1.device
8.855s sys-devices-platform-serial8250-serial8250:0-serial8250:0.1-tty-ttyS1.device
8.847s sys-module-configfs.device
8.846s sys-devices-LNXSYSTM:00-LNXSYBUS:00-MSFT0101:00-tpmrm-tpmrm0.device
8.846s dev-tpmrm0.device
8.662s dev-disk-by\x2dpartlabel-EFI\x5cx20system\x5cx20partition.device
8.662s dev-disk-by\x2dpartuuid-5919e10a\x2d45fe\x2d4026\x2db1f3\x2d20c1cbd69084.device
8.662s sys-devices-pci0000:00-0000:00:0e.0-pci10000:e0-10000:e0:06.0-10000:e1:00.0-nvme-nvme0-nvme0n1-nvme0n1p1.device
8.662s dev-disk-by\x2did-nvme\x2dMicron_2400_MTFDKBA512QFM_22333CCB2AD7_1\x2dpart1.device
8.662s dev-disk-by\x2dpath-pci\x2d0000:00:0e.0\x2dpci\x2d10000:e1:00.0\x2dnvme\x2d1\x2dpart1.device
8.662s dev-disk-by\x2ddiskseq-2\x2dpart1.device
8.662s dev-disk-by\x2duuid-5A88\x2d0C56.device
8.662s dev-nvme0n1p1.device
8.662s dev-disk-by\x2did-nvme\x2deui.000000000000000100a075223ccb2ad7\x2dpart1.device
8.662s dev-disk-by\x2did-nvme\x2dMicron_2400_MTFDKBA512QFM_22333CCB2AD7\x2dpart1.device
8.660s dev-disk-by\x2ddiskseq-2\x2dpart2.device
8.660s dev-disk-by\x2did-nvme\x2dMicron_2400_MTFDKBA512QFM_22333CCB2AD7_1\x2dpart2.device
8.660s dev-disk-by\x2did-nvme\x2dMicron_2400_MTFDKBA512QFM_22333CCB2AD7\x2dpart2.device
8.660s dev-nvme0n1p2.device
8.660s dev-disk-by\x2dpartlabel-Microsoft\x5cx20reserved\x5cx20partition.device
8.660s dev-disk-by\x2dpartuuid-bfe18da3\x2da6c6\x2d455f\x2db505\x2d73bc611b104f.device
8.660s dev-disk-by\x2dpath-pci\x2d0000:00:0e.0\x2dpci\x2d10000:e1:00.0\x2dnvme\x2d1\x2dpart2.device
8.660s sys-devices-pci0000:00-0000:00:0e.0-pci10000:e0-10000:e0:06.0-10000:e1:00.0-nvme-nvme0-nvme0n1-nvme0n1p2.device
8.660s dev-disk-by\x2did-nvme\x2deui.000000000000000100a075223ccb2ad7\x2dpart2.device
8.645s dev-disk-by\x2duuid-9C62AEA062AE7EA0.device
8.645s dev-disk-by\x2ddiskseq-2\x2dpart4.device
8.645s dev-disk-by\x2dpartuuid-ba8692c2\x2ddc76\x2d476b\x2db3d6\x2d3d500571cd12.device
8.645s sys-devices-pci0000:00-0000:00:0e.0-pci10000:e0-10000:e0:06.0-10000:e1:00.0-nvme-nvme0-nvme0n1-nvme0n1p4.device
8.645s dev-disk-by\x2did-nvme\x2dMicron_2400_MTFDKBA512QFM_22333CCB2AD7\x2dpart4.device
8.645s dev-nvme0n1p4.device
8.645s dev-disk-by\x2did-nvme\x2deui.000000000000000100a075223ccb2ad7\x2dpart4.device
8.645s dev-disk-by\x2did-nvme\x2dMicron_2400_MTFDKBA512QFM_22333CCB2AD7_1\x2dpart4.device
8.645s dev-disk-by\x2dpath-pci\x2d0000:00:0e.0\x2dpci\x2d10000:e1:00.0\x2dnvme\x2d1\x2dpart4.device
8.644s dev-disk-by\x2ddiskseq-2\x2dpart3.device
8.644s dev-disk-by\x2dpath-pci\x2d0000:00:0e.0\x2dpci\x2d10000:e1:00.0\x2dnvme\x2d1\x2dpart3.device
8.644s dev-disk-by\x2dpartuuid-e3e73219\x2d1843\x2d481a\x2db8ef\x2de2e4f1d34293.device
8.644s dev-disk-by\x2did-nvme\x2deui.000000000000000100a075223ccb2ad7\x2dpart3.device
8.644s dev-disk-by\x2did-nvme\x2dMicron_2400_MTFDKBA512QFM_22333CCB2AD7_1\x2dpart3.device
8.644s dev-nvme0n1p3.device
8.644s sys-devices-pci0000:00-0000:00:0e.0-pci10000:e0-10000:e0:06.0-10000:e1:00.0-nvme-nvme0-nvme0n1-nvme0n1p3.device
8.644s dev-disk-by\x2duuid-3C208F34208EF3E4.device
8.644s dev-disk-by\x2did-nvme\x2dMicron_2400_MTFDKBA512QFM_22333CCB2AD7\x2dpart3.device
8.644s dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition.device
8.633s dev-disk-by\x2dpath-pci\x2d0000:00:0e.0\x2dpci\x2d10000:e2:00.0\x2dnvme\x2d1\x2dpart1.device
8.633s sys-devices-pci0000:00-0000:00:0e.0-pci10000:e0-10000:e0:06.2-10000:e2:00.0-nvme-nvme1-nvme1n1-nvme1n1p1.device
8.633s dev-disk-by\x2did-nvme\x2dSamsung_SSD_970_EVO_Plus_1TB_S4EWNX0W572243Y\x2dpart1.device
8.633s dev-disk-by\x2did-nvme\x2dSamsung_SSD_970_EVO_Plus_1TB_S4EWNX0W572243Y_1\x2dpart1.device
8.633s dev-disk-by\x2dpartuuid-dce1136b\x2de3d8\x2d493b\x2d9c6b\x2d0d888adafa78.device
8.633s dev-disk-by\x2ddiskseq-1\x2dpart1.device
8.633s dev-disk-by\x2dpartlabel-EFI\x5cx20System\x5cx20Partition.device
8.633s dev-disk-by\x2did-nvme\x2deui.0025385531b3dd0a\x2dpart1.device
8.633s dev-disk-by\x2duuid-7235\x2dCF69.device
8.633s dev-nvme1n1p1.device
8.622s dev-disk-by\x2ddiskseq-2.device
8.622s dev-disk-by\x2did-nvme\x2dMicron_2400_MTFDKBA512QFM_22333CCB2AD7.device
8.622s dev-disk-by\x2did-nvme\x2dMicron_2400_MTFDKBA512QFM_22333CCB2AD7_1.device
8.622s dev-disk-by\x2dpath-pci\x2d0000:00:0e.0\x2dpci\x2d10000:e1:00.0\x2dnvme\x2d1.device
8.622s dev-disk-by\x2did-nvme\x2deui.000000000000000100a075223ccb2ad7.device
8.622s dev-nvme0n1.device
8.622s sys-devices-pci0000:00-0000:00:0e.0-pci10000:e0-10000:e0:06.0-10000:e1:00.0-nvme-nvme0-nvme0n1.device
8.617s dev-disk-by\x2duuid-865495c0\x2d00d4\x2d4ee2\x2d86c0\x2d06cee3c3d47c.device
8.617s sys-devices-pci0000:00-0000:00:0e.0-pci10000:e0-10000:e0:06.2-10000:e2:00.0-nvme-nvme1-nvme1n1-nvme1n1p3.device
8.617s dev-disk-by\x2dpath-pci\x2d0000:00:0e.0\x2dpci\x2d10000:e2:00.0\x2dnvme\x2d1\x2dpart3.device
8.617s dev-nvme1n1p3.device
8.617s dev-disk-by\x2did-nvme\x2deui.0025385531b3dd0a\x2dpart3.device
8.617s dev-disk-by\x2did-nvme\x2dSamsung_SSD_970_EVO_Plus_1TB_S4EWNX0W572243Y_1\x2dpart3.device
8.617s dev-disk-by\x2did-nvme\x2dSamsung_SSD_970_EVO_Plus_1TB_S4EWNX0W572243Y\x2dpart3.device
8.617s dev-disk-by\x2ddiskseq-1\x2dpart3.device
8.617s dev-disk-by\x2dpartuuid-00e63a50\x2d30b0\x2d4bcd\x2d9443\x2de9efaf0ed0b0.device
8.616s dev-disk-by\x2did-nvme\x2dSamsung_SSD_970_EVO_Plus_1TB_S4EWNX0W572243Y\x2dpart2.device
8.616s dev-disk-by\x2dpartuuid-3457d6f9\x2d97d8\x2d449a\x2dba85\x2d93f627d2d560.device
8.616s dev-disk-by\x2dpath-pci\x2d0000:00:0e.0\x2dpci\x2d10000:e2:00.0\x2dnvme\x2d1\x2dpart2.device
8.616s dev-disk-by\x2ddiskseq-1\x2dpart2.device
8.616s sys-devices-pci0000:00-0000:00:0e.0-pci10000:e0-10000:e0:06.2-10000:e2:00.0-nvme-nvme1-nvme1n1-nvme1n1p2.device
8.616s dev-disk-by\x2did-nvme\x2dSamsung_SSD_970_EVO_Plus_1TB_S4EWNX0W572243Y_1\x2dpart2.device
8.616s dev-disk-by\x2did-nvme\x2deui.0025385531b3dd0a\x2dpart2.device
8.616s dev-disk-by\x2duuid-9c312b86\x2da6c6\x2d4b7a\x2d8faf\x2d222fcc595926.device
8.616s dev-nvme1n1p2.device
8.614s dev-disk-by\x2dpath-pci\x2d0000:00:0e.0\x2dpci\x2d10000:e2:00.0\x2dnvme\x2d1.device
8.614s dev-disk-by\x2did-nvme\x2dSamsung_SSD_970_EVO_Plus_1TB_S4EWNX0W572243Y_1.device
8.614s dev-disk-by\x2ddiskseq-1.device
8.614s sys-devices-pci0000:00-0000:00:0e.0-pci10000:e0-10000:e0:06.2-10000:e2:00.0-nvme-nvme1-nvme1n1.device
8.614s dev-disk-by\x2did-nvme\x2dSamsung_SSD_970_EVO_Plus_1TB_S4EWNX0W572243Y.device
8.614s dev-disk-by\x2did-nvme\x2deui.0025385531b3dd0a.device
8.614s dev-nvme1n1.device
7.697s dracut-initqueue.service
7.025s systemd-cryptsetup@luks\x2d865495c0\x2d00d4\x2d4ee2\x2d86c0\x2d06cee3c3d47c.service
2.124s plocate-updatedb.service
1.181s asusd.service
 652ms akmods.service
 648ms NetworkManager.service
 605ms initrd-switch-root.service
 316ms ModemManager.service
 269ms firewalld.service
 268ms upower.service
 248ms rsyslog.service
 242ms abrtd.service
 235ms udisks2.service
 201ms dnf-makecache.service
 176ms accounts-daemon.service
 174ms polkit.service
 174ms power-profiles-daemon.service
 155ms systemd-logind.service
 146ms bluetooth.service
 146ms chronyd.service
 123ms systemd-journal-flush.service
 114ms user@1000.service
 110ms switcheroo-control.service
 108ms rtkit-daemon.service
 102ms systemd-tmpfiles-setup.service
  94ms dracut-cmdline.service
  93ms lvm2-monitor.service
  87ms systemd-tmpfiles-setup-dev-early.service
  82ms systemd-udev-trigger.service
  77ms smb.service
  75ms dev-zram0.swap
  72ms systemd-journald.service
  67ms systemd-vconsole-setup.service
  55ms systemd-random-seed.service
  53ms gssproxy.service
  44ms sssd-kcm.service
  44ms avahi-daemon.service
  44ms systemd-tmpfiles-clean.service
  44ms systemd-resolved.service
  41ms dracut-pre-udev.service
  41ms var-lib-nfs-rpc_pipefs.mount
  38ms systemd-udevd.service
  37ms lm_sensors.service
  37ms systemd-fsck@dev-disk-by\x2duuid-7235\x2dCF69.service
  34ms smartd.service
  34ms packagekit.service
  33ms systemd-fsck@dev-disk-by\x2duuid-9c312b86\x2da6c6\x2d4b7a\x2d8faf\x2d222fcc595926.service
  33ms bolt.service
  31ms systemd-fsck-root.service
  30ms systemd-sysctl.service
  28ms plymouth-switch-root.service
  27ms dracut-shutdown.service
  24ms systemd-zram-setup@zram0.service
  24ms virtlxcd.service
  24ms virtqemud.service
  24ms plymouth-quit-wait.service
  23ms dracut-pre-pivot.service
  23ms systemd-homed.service
  23ms plymouth-quit.service
  22ms initrd-parse-etc.service
  21ms systemd-oomd.service
  21ms virtvboxd.service
  21ms dbus-broker.service
  21ms cups.service
  20ms dev-hugepages.mount
  19ms initrd-cleanup.service
  19ms systemd-machined.service
  18ms dev-mqueue.mount
  17ms plymouth-start.service
  17ms sys-kernel-tracing.mount
  17ms sys-kernel-debug.mount
  17ms systemd-tmpfiles-setup-dev.service
  17ms supergfxd.service
  16ms kmod-static-nodes.service
2

If I remember correctly, the default behaviour in Windows when you click “Shut Down” is to just hibernate instead of a full shutdown.

1 Like
3

I have hibernation disabled on windows

4

That only changes timed hibernation. If the power button is assigned to “hibernate” then it will still hibernate.

1 Like
5

Is it 25 seconds real-world?

I get very similar times on systemd-analyze, but it doesn’t really take 20+ seconds real-world (albeit still a bit slower than Windows).

On my Dell Latitude 5591 laptop, firmware’s systemd-analyze time can be cut in-half (10s to 4-5s) if I boot with my laptop screen open (I use it docked to a screen/desktop set-up). No idea what that’s about.

initrd can be cut a good bit with Dracut tweaks to disable or change how it’s compressed. loader is largely GRUB’s timeout.

On openSUSE TW right now I have this without anything special (shorter GRUB timeout from 8s to 3s):

Startup finished in 5.413s (firmware) + 3.613s (loader) + 567ms (kernel) + 4.824s (initrd) + 4.277s (userspace) = 18.696s
6

I have completely and properly disabled hibernation.

What are those “dracut tweaks” you speak of? I can’t find anything online. Also, i boot without any secondary display on.

7

+1 for this.

My 2023 laptop with SSD claims that Fedora takes 44 seconds to boot:

Startup finished in 25.412s (firmware)
 + 5.996s (loader) 
 + 1.038s (kernel) 
 + 3.093s (initrd) 
 + 9.039s (userspace) 
 = 44.579s

While in reality GDM is on screen waiting for input in less than 10 seconds, measured from the grub menu.

@fottl make sure you are comparing real-world timings before trying all sorts of low-level tweaks to your system.

8

This is one example: Moving GPU drivers out of the initramfs - Hans' hacking log — LiveJournal

If you deviate from a standard installation, however, it “voids the warranty” so to speak as to how stable the system will be going forward. It might not cause any problems at all, or what problems it does create might be trivial to workaround for an advanced Linux user, but you will want to consider carefully the trade-offs of “optimizing” your system like that versus having a more standard install that is less likely to error out when running various programs in the future.

9

This is what I do to strip the initramfs to only include essentials specific to the machine, and have initramfs uncompressed (the 3 stuff at the end disable logging/noise; I know it works :stuck_out_tongue: ):

sudo -e '/etc/dracut.conf.d/99-custom.conf' && sudo dracut --force --regenerate-all

compress="cat"
do_strip="yes"
aggressive_strip="yes"
hostonly="yes"
hostonly_mode="strict"
fileloglvl="0"
sysloglvl="0"
stdloglvl="0"
2 Likes
10

Hi, I had some free time so I timed the startup with a stopwatch and the real time was actually 34 seconds, while systemd-analyze reported 24 seconds. I followed the guide to remove graphic drivers out of initramfs and I managed to gain a 4 seconds (real time) improvement.

Since there doesn’t seem much else to do, I will just accept this since the OS as a whole is performing really well and I can finally rest having found a good distro to use.

1 Like
11

I also find your boot time sort of slow, my i7 Intel gen 7 Thinkpad boots much faster (no tweaks), but I wouldn’t bother and tweak it all the way until it breaks. How often do you even reboot…?
I reboot once a week, so 20 sec more don’t matter to me.

1 Like
12

From someone a little extreme, in the hunt for boot/reboot seconds, here is what i have found so far.

These tweaks is not for everyone, if you are not comfortable doing the things below, please dont…

Bios:
Disabled cpu virtualization in bios, as i dont use virtual machines, gained as far as i remember about 4 seconds in total boot time.
*Edit 8/9-24- Have to correct the statement above, turning virtualization off do not save time, the time i found was from uninstalling KVM (Kernel-based Virtual Machine).

Fedora:
Disabled obvious services i do not need/want, then searched information about what different services do, and have along the way disabled more, so that i now disable 20 services, and have not had any issues on F39 or F40. Its a good idea to keep a log of the services you disable, so you are able to turn them back on if you find issues.

Uninstalled plymouth and removed rhgb quiet in /etc/default/grub, as i prefer to visually follow the boot process.

Dont remember the total time i saved on boot/reboot (was using F37 or F38 at the time), but in my book it is quite a lot, and absolutely worth it, but it depends on what services you need, if you need virtualisation, or prefer to boot with plymouth enabled.

Other than these tweaks i have hidden the grub menu (menu_auto_hide=1): https://discussion.fedoraproject.org/t/make-grub-hidden-again/98688 - for reboot speedup and convenience.

Last thing i want to mention is systemctl soft-reboot, which i have been using for over 6 months now, and the reboot speed is brilliant. I use it if i have updates without a new kernel (use terminal for system updates), and have yet to find any issues using it. Made a keyboard shortcut and a terminal alias command, to be able to use it quickly.

Made a setup-script so that these changes is easily applied (disabling services, remove plymouth, hide grub menu and more), if i want to re-install Fedora.

1 Like
13

Out of curiosity i tested my statement above on a fully updated F40 spin, and to provide something more concrete.

Using an external usb nvme drive, this is what i found.

No Tweaks - All services with plymouth installed

Cold boot: 27.569s
Reboot: 27.560s

Tweaks - Disabled services - no plymouth

Cold boot: 22.910s
Reboot: 22.387s

Internal nvme drive (same hardware - disabled services - no plymouth)
Cold boot: 17.117s
Reboot: 13.041s (time is gained from the fast boot bios setting)

Corrected the false statement in my post above, about disabling virtualization in bios.
“turning virtualization off do not save time, the time i found was from uninstalling KVM (Kernel-based Virtual Machine).”

14

Thank you for the writeup. I indeed disabled plymouth and noticed another small improvement in boot time. I will maybe look into disabling some services, but I think I have a pretty acceptable boot time as is. Unfortunately, I can’t disable HyperV/KVM since I use a VM from time to time to run adobe and office.

Thank you all for the contributions. I am fine with a ~30s boot time since the OS itself works great and has no issues except for some wird stanby bugs which don’t bother me too much.

15

I’m wondering why this is taking so long. It seems excessive.

16

Maybe it has something to do with the drive being encrypted? Maybe it’s just the time it takes for me to type in the password.

17

Yes, that’s what it is.