Slow Boot time SSD Manjaro KDe

Hi,

I installed Manjaro KDe today on a 2009 Dell Studio XPS 1640. I put in a new SSD so wanted to try a new OS and opted for Manjaro. I am liking the OS so far but boot times are almost 30 seconds. I calculated end user boot time using a stopwatch even though ‘systemd-analyze’ only shows 13 seconds. Also it takes around 4-5 seconds after entering my password to show me the desktop. I feel this is quite slow for an SSD. After reading some posts here, I can provide systemd-analyze and systemd-analyze blame data.

Would appreciate if anyone can guide me to solve this.

systemd-analyze
[viking@pradhyumna-studioxps1640 ~]$ systemd-analyze
Startup finished in 1.803s (kernel) + 5.751s (userspace) = 7.554s
graphical.target reached after 4.390s in userspace

systemd-analyze blame

[viking@pradhyumna-studioxps1640 ~]$ systemd-analyze blame
12.010s upower.service
2.217s lvm2-monitor.service
2.068s dev-sda1.device
2.059s systemd-random-seed.service
1.836s dev-loop2.device
1.767s dev-loop1.device
1.761s dev-loop3.device
1.757s NetworkManager-wait-online.service
1.745s dev-loop0.device
1.427s systemd-logind.service
1.412s apparmor.service
1.345s tlp.service
1.087s systemd-journald.service
953ms systemd-udevd.service
813ms snapd.service
461ms polkit.service
287ms avahi-daemon.service
282ms systemd-udev-trigger.service
267ms NetworkManager.service
197ms modprobe@drm.service
195ms var-lib-snapd-snap-chromium-1328.mount
191ms var-lib-snapd-snap-core18-1885.mount
190ms var-lib-snapd-snap-gtk\x2dcommon\x2dthemes-1506.mount
183ms var-lib-snapd-snap-snapd-9279.mount
171ms user@1000.service
162ms snapd.apparmor.service
161ms org.cups.cupsd.service
161ms systemd-journal-flush.service
151ms udisks2.service
145ms systemd-backlight@backlight:dell_backlight.service
117ms systemd-binfmt.service
105ms ModemManager.service
62ms dev-hugepages.mount
61ms linux-module-cleanup.service
61ms dev-mqueue.mount
60ms systemd-tmpfiles-setup-dev.service
58ms sys-kernel-debug.mount

Thanks.

What drive do you have? My computer boots up very fast on a Western Digital Green 240GB SSD.

To find your hardware you can run “inxi -F” in terminal

I have an A-Data SU650 120 GB SSD.

You could also check output of

systemd-analyze critical-chain

I feel that my system boots pretty fast with following result:

[xxx@xxx ~]$ systemd-analyze
Startup finished in 1.764s (kernel) + 8.879s (userspace) = 10.644s 
graphical.target reached after 2.745s in userspace

Also, after a fresh install the file system is still initializing and baloo file indexer could reduce the performance in the begin as well. I think your times are OK.

If you don’t use encrypted partitions you could disable and mask lvm2-monitor.service by:

systemctl disable --now lvm2-monitor.service
systemctl mask lvm2-monitor.service
1 Like

I have also a SSD and it takes also ~31sec. Starting at pushing the power button until displaying the XFCE Desktop (using a stopwatch).

systemd-analyze
Startup finished in 9.860s (firmware) + 1.673s (loader) + 1.931s (kernel) + 8.324s (userspace) = 21.789s 
graphical.target reached after 7.887s in userspace

When systemd says 13sec and you count 30sec, then i would say it is the KDE Desktop that takes time to start or the UEFI that needs time to initialize the hardware. “graphical.target reached” doesn’t mean KDE has been started, but it starts a DE at this point (after 13sec).

So XFCE started in ~2-3sec for me and was ready.

Make sure GRUB_TIMEOUT (set in /etc/default/grub) is not set unreasonably high and stalling every boot.

1 Like

Thanks. I would’ve thought it would be much lesser with a SSD though.

I have set it at 0. However don’t think it made much of a difference.

After editing /etc/default/grub it’s required to:

$ sudo update-grub

to apply the changes to the generated boot configuration.