Manjaro KDE slow boot

Support
1

Hello everyone! :wave:

I recently did a clean install of Manjaro Linux (KDE Plasma) on my system:

  • CPU: AMD Ryzen 5 5600X
  • RAM: 32GB DDR4
  • Storage: NVMe SSD

While performance is smooth overall, I’ve noticed the full boot time averages 28 seconds. Given the hardware, I expected slightly faster startup times.

Could this be typical for KDE/Manjaro, or might there be room for optimization?
Thanks in advance
systemct-analyze blame

5.815s sys-devices-platform-serial8250-serial8250:0-serial8250:0.3-tty-ttyS3.device
5.815s dev-ttyS3.device
5.811s sys-devices-platform-serial8250-serial8250:0-serial8250:0.2-tty-ttyS2.device
5.811s dev-ttyS2.device
5.809s dev-ttyS0.device
5.809s sys-devices-platform-serial8250-serial8250:0-serial8250:0.0-tty-ttyS0.device
5.809s dev-ttyS1.device
5.809s sys-devices-platform-serial8250-serial8250:0-serial8250:0.1-tty-ttyS1.device
5.802s sys-module-fuse.device
5.801s sys-module-configfs.device
5.480s dev-disk-by\x2did-nvme\x2deui.00000000000000000026b7784b651ad5\x2dpart1.device
5.480s dev-disk-by\x2did-nvme\x2dKINGSTON_SNVS500G_50026B7784B651AD_1\x2dpart1.device
5.480s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart1.device
5.480s dev-disk-by\x2dpartlabel-Microsoft\x5cx20reserved\x5cx20partition.device
5.480s dev-disk-by\x2dpartuuid-4bc8ad19\x2dabbe\x2d4e4c\x2d94c4\x2d9c435119ccc2.device
5.480s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartlabel-Microsoft\x5cx20reserved\x5cx20partition.device
5.480s dev-disk-by\x2did-nvme\x2dKINGSTON_SNVS500G_50026B7784B651AD\x2dpart1.device
5.480s sys-devices-pci0000:00-0000:00:01.1-0000:01:00.0-nvme-nvme0-nvme0n1-nvme0n1p1.device
5.480s dev-disk-by\x2ddiskseq-1\x2dpart1.device
5.480s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-1.device
5.480s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-4bc8ad19\x2dabbe\x2d4e4c\x2d94c4\x2d9c435119ccc2.device
5.480s dev-nvme0n1p1.device
5.477s dev-disk-by\x2did-nvme\x2dKINGSTON_SNVS500G_50026B7784B651AD_1\x2dpart2.device
5.477s dev-disk-by\x2dlabel-Windows\x5cx2011.device
5.477s dev-disk-by\x2ddiskseq-1\x2dpart2.device
5.477s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart2.device
5.477s dev-nvme0n1p2.device
5.477s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-08a25448\x2d88b4\x2d47a8\x2da2f7\x2de53b24377458.device
5.477s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart-by\x2duuid-9A68899868897433.device
5.477s sys-devices-pci0000:00-0000:00:01.1-0000:01:00.0-nvme-nvme0-nvme0n1-nvme0n1p2.device
5.477s dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition.device
5.477s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition.device
5.477s dev-disk-by\x2did-nvme\x2deui.00000000000000000026b7784b651ad5\x2dpart2.device
5.477s dev-disk-by\x2did-nvme\x2dKINGSTON_SNVS500G_50026B7784B651AD\x2dpart2.device
5.477s dev-disk-by\x2duuid-9A68899868897433.device
5.477s dev-disk-by\x2dpartuuid-08a25448\x2d88b4\x2d47a8\x2da2f7\x2de53b24377458.device
5.477s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart-by\x2dlabel-Windows\x5cx2011.device
5.477s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-2.device
5.476s dev-disk-by\x2did-nvme\x2deui.00000000000000000026b7784b651ad5.device
5.476s dev-disk-by\x2did-nvme\x2dKINGSTON_SNVS500G_50026B7784B651AD_1.device
5.476s dev-nvme0n1.device
5.476s dev-disk-by\x2did-nvme\x2dKINGSTON_SNVS500G_50026B7784B651AD.device
5.476s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1.device
5.476s sys-devices-pci0000:00-0000:00:01.1-0000:01:00.0-nvme-nvme0-nvme0n1.device
5.476s dev-disk-by\x2ddiskseq-1.device
5.476s dev-nvme0n1p3.device
5.476s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-3.device
5.476s dev-disk-by\x2ddiskseq-1\x2dpart3.device
5.476s dev-disk-by\x2dpartuuid-f6b1f654\x2daca2\x2d452b\x2d8902\x2de14ae7a24ec7.device
5.476s dev-disk-by\x2did-nvme\x2dKINGSTON_SNVS500G_50026B7784B651AD\x2dpart3.device
5.476s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-f6b1f654\x2daca2\x2d452b\x2d8902\x2de14ae7a24ec7.device
5.476s dev-disk-by\x2duuid-88F2\x2dB948.device
5.476s dev-disk-by\x2did-nvme\x2deui.00000000000000000026b7784b651ad5\x2dpart3.device
5.476s dev-disk-by\x2did-nvme\x2dKINGSTON_SNVS500G_50026B7784B651AD_1\x2dpart3.device
5.476s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart-by\x2duuid-88F2\x2dB948.device
5.476s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart3.device
5.476s sys-devices-pci0000:00-0000:00:01.1-0000:01:00.0-nvme-nvme0-nvme0n1-nvme0n1p3.device
5.464s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-2.device
5.464s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-2c077cea\x2d003c\x2d4e92\x2db723\x2d7fdf953f5f89.device
5.464s sys-devices-pci0000:00-0000:00:01.2-0000:02:00.2-0000:03:04.0-0000:04:00.0-nvme-nvme1-nvme1n1-nvme1n1p2.device
5.464s dev-disk-by\x2did-nvme\x2deui.6479a7a400150745\x2dpart2.device
5.464s dev-disk-by\x2dpartlabel-root.device
5.464s dev-disk-by\x2did-nvme\x2dApacer_AS2280P4U_1TB_7EA8073818A400150745_1\x2dpart2.device
5.464s dev-disk-by\x2dpartuuid-2c077cea\x2d003c\x2d4e92\x2db723\x2d7fdf953f5f89.device
5.464s dev-disk-by\x2did-nvme\x2dApacer_AS2280P4U_1TB_7EA8073818A400150745\x2dpart2.device
5.464s dev-disk-by\x2ddiskseq-2\x2dpart2.device
5.464s dev-nvme1n1p2.device
5.464s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2duuid-05f82ddc\x2d3a04\x2d46c0\x2d98ab\x2dd97933c798a3.device
5.464s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartlabel-root.device
5.464s dev-disk-by\x2duuid-05f82ddc\x2d3a04\x2d46c0\x2d98ab\x2dd97933c798a3.device
5.464s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart2.device
5.457s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart1.device
5.457s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-8190e2aa\x2d88cb\x2d426d\x2daa2d\x2d287dbd23eeea.device
5.457s dev-nvme1n1p1.device
5.457s dev-disk-by\x2did-nvme\x2deui.6479a7a400150745\x2dpart1.device
5.457s dev-disk-by\x2duuid-D005\x2dF543.device
5.457s dev-disk-by\x2dpartuuid-8190e2aa\x2d88cb\x2d426d\x2daa2d\x2d287dbd23eeea.device
5.457s sys-devices-pci0000:00-0000:00:01.2-0000:02:00.2-0000:03:04.0-0000:04:00.0-nvme-nvme1-nvme1n1-nvme1n1p1.device
5.457s dev-disk-by\x2did-nvme\x2dApacer_AS2280P4U_1TB_7EA8073818A400150745\x2dpart1.device
5.457s dev-disk-by\x2ddiskseq-2\x2dpart1.device
5.457s dev-disk-by\x2did-nvme\x2dApacer_AS2280P4U_1TB_7EA8073818A400150745_1\x2dpart1.device
5.457s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-1.device
5.457s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2duuid-D005\x2dF543.device
5.456s sys-devices-pci0000:00-0000:00:01.2-0000:02:00.2-0000:03:04.0-0000:04:00.0-nvme-nvme1-nvme1n1.device
5.456s dev-disk-by\x2ddiskseq-2.device
5.456s dev-disk-by\x2did-nvme\x2dApacer_AS2280P4U_1TB_7EA8073818A400150745.device
5.456s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1.device
5.456s dev-nvme1n1.device
5.456s dev-disk-by\x2did-nvme\x2dApacer_AS2280P4U_1TB_7EA8073818A400150745_1.device
5.456s dev-disk-by\x2did-nvme\x2deui.6479a7a400150745.device
2.800s plymouth-quit-wait.service
2.800s plymouth-quit.service
 472ms initrd-switch-root.service
 292ms NetworkManager.service
 106ms systemd-journald.service
  79ms udisks2.service
  76ms systemd-fsck-root.service
  75ms user@1000.service
  74ms lvm2-monitor.service
  60ms upower.service
  60ms systemd-udev-trigger.service
  57ms plymouth-start.service
  57ms cups.service
  50ms modprobe@dm_mod.service
  50ms modprobe@loop.service
  50ms systemd-journal-flush.service
  48ms systemd-user-sessions.service
  43ms dev-hugepages.mount
  42ms dev-mqueue.mount
  42ms boot-efi.mount
  42ms sys-kernel-debug.mount
  42ms sys-kernel-tracing.mount
  41ms kmod-static-nodes.service
  41ms user-runtime-dir@1000.service
  34ms tmp.mount
  33ms ModemManager.service
  33ms systemd-tmpfiles-setup-dev-early.service
  33ms initrd-parse-etc.service
  31ms systemd-udevd.service
  30ms systemd-tmpfiles-setup.service
  25ms polkit.service
  21ms initrd-udevadm-cleanup-db.service
  19ms systemd-logind.service
  19ms power-profiles-daemon.service
  19ms systemd-timesyncd.service
  18ms systemd-hostnamed.service
  18ms plymouth-switch-root.service
  16ms systemd-modules-load.service
  15ms systemd-fsck@dev-disk-by\x2duuid-D005\x2dF543.service
  14ms plymouth-read-write.service
  12ms systemd-random-seed.service
  11ms systemd-userdbd.service
  10ms dbus-broker.service
   9ms systemd-tmpfiles-setup-dev.service
   6ms initrd-cleanup.service
   6ms systemd-udev-load-credentials.service
   5ms modprobe@drm.service
   5ms rtkit-daemon.service
   4ms systemd-update-utmp.service
   4ms systemd-vconsole-setup.service
   4ms systemd-remount-fs.service
   3ms systemd-sysctl.service
   3ms alsa-restore.service
   3ms modprobe@configfs.service
   3ms modprobe@fuse.service
   3ms sys-fs-fuse-connections.mount
   2ms sys-kernel-config.mount

systemctl-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 @4.573s
└─sddm.service @4.573s
  └─plymouth-quit.service @1.772s +2.800s
    └─systemd-user-sessions.service @1.721s +48ms
      └─network.target @1.720s
        └─NetworkManager.service @1.428s +292ms
          └─basic.target @1.427s
            └─dbus-broker.service @1.416s +10ms
              └─dbus.socket @1.414s
                └─sysinit.target @1.412s
                  └─systemd-update-utmp.service @1.407s +4ms
                    └─systemd-tmpfiles-setup.service @1.376s +30ms
                      └─local-fs.target @1.374s
                        └─boot-efi.mount @1.331s +42ms
                          └─systemd-fsck@dev-disk-by\x2duuid-D005\x2dF543.service @494ms +15ms
                            └─dev-disk-by\x2duuid-D005\x2dF543.device

I can send other logs if needed

2

Welcome to the forum! :vulcan_salute:

I have 16 GiB of RAM and an SATA3-connected SSD. My system boots — from the grub menu to the sddm login screen — in about 11 seconds. So yes, I’d say there’s room for improvement.

The first thing I would recommend is to get rid of plymouth. I’ve explained the procedure in this post, although that was for doing it from a chroot environment, given that the OP could not boot from their installed system.

Secondly, there’s something strange going on with your serial ports — /dev/ttyS{0,1,2,3} are serial ports — and I have no idea what that is, because I am not seeing that on my own machine. So that warrants investigating as well.

Also, you will probably be asked by other interlocutors for the specifics of your hardware, so please post the output of… :point_down:

inxi -Fxxz
3 Likes
3

Sure
inxi log

System:
  Kernel: 6.12.34-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 15.1.1
  Desktop: KDE Plasma v: 6.3.5 tk: Qt v: N/A wm: kwin_wayland dm: SDDM
    Distro: Manjaro base: Arch Linux
Machine:
  Type: Desktop Mobo: Gigabyte model: B550 AORUS ELITE V2
    serial: <superuser required> UEFI: American Megatrends LLC. v: F16h
    date: 12/25/2023
CPU:
  Info: 6-core model: AMD Ryzen 5 5600X bits: 64 type: MT MCP arch: Zen 3+
    rev: 2 cache: L1: 384 KiB L2: 3 MiB L3: 32 MiB
  Speed (MHz): avg: 3596 min/max: 550/4651 boost: enabled cores: 1: 3596
    2: 3596 3: 3596 4: 3596 5: 3596 6: 3596 7: 3596 8: 3596 9: 3596 10: 3596
    11: 3596 12: 3596 bogomips: 88665
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3
Graphics:
  Device-1: Advanced Micro Devices [AMD/ATI] Navi 23 [Radeon RX 6600/6600
    XT/6600M] vendor: Tul / PowerColor Red Devil driver: amdgpu v: kernel
    arch: RDNA-2 pcie: speed: 16 GT/s lanes: 16 ports: active: DP-1
    empty: DP-2, DP-3, HDMI-A-1, Writeback-1 bus-ID: 08:00.0
    chip-ID: 1002:73ff
  Display: wayland server: X.org v: 1.21.1.18 with: Xwayland v: 24.1.8
    compositor: kwin_wayland driver: X: loaded: amdgpu
    unloaded: modesetting,radeon alternate: fbdev,vesa dri: radeonsi
    gpu: amdgpu display-ID: 0
  Monitor-1: DP-1 model: LG (GoldStar) MP59G res: 1920x1080 hz: 75 dpi: 81
    diag: 690mm (27.2")
  API: EGL v: 1.5 platforms: device: 0 drv: radeonsi device: 1 drv: swrast
    gbm: drv: kms_swrast surfaceless: drv: radeonsi wayland: drv: radeonsi x11:
    drv: radeonsi
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 25.1.4-arch1.1
    glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 6600 XT (radeonsi
    navi23 LLVM 20.1.6 DRM 3.61 6.12.34-1-MANJARO) device-ID: 1002:73ff
    display-ID: :1.0
  API: Vulkan v: 1.4.313 surfaces: N/A device: 0 type: discrete-gpu
    driver: mesa radv device-ID: 1002:73ff
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor wl: wayland-info x11: xdpyinfo,xprop
Audio:
  Device-1: Advanced Micro Devices [AMD/ATI] Navi 21/23 HDMI/DP Audio
    driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s lanes: 16
    bus-ID: 08:00.1 chip-ID: 1002:ab28
  Device-2: Advanced Micro Devices [AMD] Starship/Matisse HD Audio
    vendor: Gigabyte driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s
    lanes: 16 bus-ID: 0a:00.4 chip-ID: 1022:1487
  API: ALSA v: k6.12.34-1-MANJARO status: kernel-api with: aoss
    type: oss-emulator
  Server-1: JACK v: 1.9.22 status: off
  Server-2: PipeWire v: 1.4.5 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
Network:
  Device-1: Realtek RTL8125 2.5GbE vendor: Gigabyte driver: r8169 v: kernel
    pcie: speed: 5 GT/s lanes: 1 port: f000 bus-ID: 05:00.0 chip-ID: 10ec:8125
  IF: eno1 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:
  Local Storage: total: 1.39 TiB used: 15.11 GiB (1.1%)
  ID-1: /dev/nvme0n1 vendor: Kingston model: SNVS500G size: 465.76 GiB
    speed: 31.6 Gb/s lanes: 4 serial: <filter> temp: 39.9 C
  ID-2: /dev/nvme1n1 vendor: Apacer model: AS2280P4U 1TB size: 953.87 GiB
    speed: 31.6 Gb/s lanes: 4 serial: <filter> temp: 48.9 C
Partition:
  ID-1: / size: 953.57 GiB used: 15.11 GiB (1.6%) fs: f2fs dev: /dev/nvme1n1p2
  ID-2: /boot/efi size: 299.4 MiB used: 320 KiB (0.1%) fs: vfat
    dev: /dev/nvme1n1p1
Swap:
  Alert: No swap data was found.
Sensors:
  System Temperatures: cpu: 51.2 C mobo: 39.0 C gpu: amdgpu temp: 50.0 C
    mem: 52.0 C
  Fan Speeds (rpm): N/A gpu: amdgpu fan: 0
Info:
  Memory: total: 32 GiB available: 31.25 GiB used: 3.78 GiB (12.1%)
  Processes: 328 Power: uptime: 1h 47m wakeups: 0 Init: systemd v: 257
    default: graphical
  Packages: pm: pacman pkgs: 1269 Compilers: clang: 20.1.6 gcc: 15.1.1
    Shell: Zsh v: 5.9 running-in: konsole inxi: 3.3.38

I removed plymouth and now the boot time is 25 seconds. -2 seconds :smile:
Should I send new logs?

1 Like
4

When I tested f2fs for root on NVMe - and f2fs is in some benchmarks superior to ext4 - even so I have found that f2fs under normal use becomes slow.

I can’t say if this is the cause of your issue…

It could be your partitions is not correctly aligned first and last sector. This can cause slow disk access even on SSD and NVMe.

f2fs is created for flash based devices so in theory it should be better then ext4.

My testing and always sent me back to ext4.

I am currently test driving xfs on one of my USB enclosures.

For comparison

 $ systemd-analyze
Startup finished in 28.499s (firmware) + 6.061s (loader) + 1.201s (kernel) + 2.617s (initrd) + 9.499s (userspace) = 47.879s 
graphical.target reached after 9.499s in userspace.

System (Plasma Settings → About this System)

Operating System: Manjaro Linux 
KDE Plasma Version: 6.4.2
KDE Frameworks Version: 6.15.0
Qt Version: 6.9.1
Kernel Version: 6.15.5-1-MANJARO (64-bit)
Graphics Platform: Wayland
Processors: 24 × AMD Ryzen Threadripper PRO 5945WX 12-Cores
Memory: 64 GiB of RAM (62,6 GiB usable)
Graphics Processor: AMD Radeon RX 7900 XTX
Manufacturer: LENOVO
Product Name: 30E000GMMT
System Version: ThinkStation P620

So - my workstation is using 50s to boot - I have no issues with that.

I remember how long time it took for a 80286 with 1MB ram and 40G SCSI disk took back in 1990.

5

This sort of hardware would be best used with btrfs :wink:

  • EFI-partition (vfat) ID2
  • swap partition ID2
  • partition with btrfs volume ID2
  • partition (on 2nd device ID1) added to the same btrfs volume
  • zstd kompression enabled (for speedup when reading)
  • eventually btrfs volume converted to btrfs-RAID

You find good Information about Btrfs in the wiki

6

Topic closed as abandoned by the OP.