8.498s plymouth-quit-wait.service 5.674s systemd-modules-load.service 1.063s dev-nvme0n1p5.device 719ms apparmor.service 575ms systemd-udev-trigger.service 536ms fwupd.service 510ms systemd-remount-fs.service 318ms modprobe@fuse.service 302ms ufw.service 281ms systemd-timesyncd.service 254ms lvm2-monitor.service 253ms modprobe@drm.service 247ms systemd-update-utmp.service 214ms systemd-tmpfiles-setup.service 203ms upower.service 190ms systemd-journal-flush.service 161ms systemd-tmpfiles-setup-dev.service 156ms systemd-backlight@leds:asus::kbd_backlight.service 152ms user@1000.service 138ms polkit.service 100ms systemd-vconsole-setup.service 90ms systemd-fsck@dev-disk-by\x2duuid-8055\x2d8EAF.service 77ms systemd-journald.service
Hi @milo_panda,
I’ve seen multiple times on the forum that pymouth can cause long boot times. So probably by removing it. Since I don’t use it, or for that matter care for it, I don’t know how. But I’m guessing reversing the installation process here:
https://wiki.archlinux.org/title/Plymouth#Installation
_Note Manjaro uses mkinitcpio.
1 Like