Start Endeavour OS

Hello to all of you,

I allow myself to come to you, having tried EndeavourOS with “virtual box” for a few months, the start was more than fast.
Having installed it in hard, I find myself with a start of more than 15s.
For info, on other environment, I am on 7 to 8 seconds.

                 ./sssso-                -------------------- 
                 `:osssssss+-              OS: EndeavourOS Linux x86_64 
               `:+sssssssssso/.            Host: B660 GAMING X DDR4 
             `-/ossssssssssssso/.          Kernel: 5.15.60-1-lts 
           `-/+sssssssssssssssso+:`        Uptime: 12 mins 
         `-:/+sssssssssssssssssso+/.       Packages: 1124 (pacman) 
       `.://osssssssssssssssssssso++-      Shell: bash 5.1.16 
      .://+ssssssssssssssssssssssso++:     Resolution: 1920x1200, 1920x1200 
    .:///ossssssssssssssssssssssssso++:    DE: Plasma 5.25.4 
  `:////ssssssssssssssssssssssssssso+++.   WM: KWin 
`-////+ssssssssssssssssssssssssssso++++-   Theme: [Plasma], Breeze [GTK2/3] 
 `..-+oosssssssssssssssssssssssso+++++/`   Icons: [Plasma], breeze [GTK2/3] 
   ./++++++++++++++++++++++++++++++/:.     Terminal: konsole 
  `:::::::::::::::::::::::::------``       CPU: 12th Gen Intel i7-12700K (20) @ 5.000GHz 
                                           GPU: NVIDIA Quadro P620 
                                           GPU: Intel AlderLake-S GT1 
                                           Memory: 2423MiB / 31877MiB 

Here is the output of systemd-analyze

Startup finished in 8.840s (firmware) + 2.421s (loader) + 4.712s (kernel) + 1.505s (userspace) = 17.479s reached after 1.499s in userspace.

Here is the output of systemd-analyze blame

37.732s fstrim.service
  373ms systemd-modules-load.service
  337ms lvm2-monitor.service
  231ms dev-nvme0n1p3.device
  147ms firewalld.service
  118ms systemd-fsck@dev-disk-by\x2duuid-e73b91f6\x2d9269\x2d4ba4\x2da17f\x2d28ce710e8b3e.service
  106ms user@1000.service
   67ms ldconfig.service
   58ms systemd-logind.service
   49ms home-data.mount
   43ms systemd-udev-trigger.service
   42ms udisks2.service
   33ms upower.service
   30ms power-profiles-daemon.service
   27ms systemd-udevd.service
   27ms systemd-journal-flush.service
   21ms systemd-fsck@dev-disk-by\x2duuid-da9dc19f\x2d7630\x2d42b5\x2db8a5\x2d20cc4ae61256.service
   20ms systemd-fsck@dev-disk-by\x2duuid-96B7\x2d93E5.service
   18ms avahi-daemon.service
   18ms cups.service
   17ms dbus.service
   17ms systemd-journald.service
   16ms systemd-tmpfiles-setup.service
   16ms NetworkManager.service
   15ms systemd-timesyncd.service
   12ms boot-efi.mount
   10ms systemd-tmpfiles-setup-dev.service
    9ms user-runtime-dir@1000.service
    8ms systemd-sysusers.service
    8ms polkit.service
    7ms home.mount
    5ms systemd-journal-catalog-update.service
    5ms modprobe@fuse.service
    4ms dev-hugepages.mount
    4ms dev-mqueue.mount
    4ms sys-kernel-debug.mount
    3ms sys-kernel-tracing.mount
    3ms kmod-static-nodes.service
    3ms systemd-user-sessions.service
    3ms modprobe@configfs.service
    3ms systemd-random-seed.service
    3ms systemd-update-utmp.service
    2ms dev-nvme0n1p2.swap
    2ms systemd-sysctl.service
    2ms rtkit-daemon.service
    2ms systemd-remount-fs.service
    2ms alsa-restore.service
    1ms systemd-update-done.service
    1ms modprobe@drm.service
  824us sys-kernel-config.mount
  751us tmp.mount
  622us sys-fs-fuse-connections.mount

Modèle : WD Blue SN570 500GB (nvme)
Disque /dev/nvme0n1 : 500GB
Taille des secteurs (logiques/physiques) : 512B/512B
Table de partitions : gpt
Drapeaux de disque :

Numéro Début Fin Taille Système de fichiers Nom Drapeaux
1 1049kB 514MB 513MB fat32 démarrage, esp
2 514MB 4514MB 4000MB linux-swap(v1) swap
3 4514MB 36,0GB 31,5GB ext4 root
6 36,0GB 500GB 464GB ext4 home

let me know if i can add anymore info.
thank you for your feedback:)

So there is a 7-8 second difference. Seems fair:

Real hardware initialization can take longer than virtual hardware initialization, which is nearly instant. You can try enabling fast boot on your UEFI or booting with less devices connected to decrease firmware initialization time.

thank you for your return
I’m watching this :slight_smile: