Slow Boot Time Manjaro KDE

I am using Manjaro KDE Plasma on my HP Pavilion 15t cs200 laptop. It has Intel i7 8565U, Intel UHD 620 Graphics, and 1TB HDD.
The booting time is about 2 minutes. It is abnormal even for HDD. My GRUB timing is 2 seconds. About 1:30 minutes are spent on the black screen with the following text.

/dev/sda10: clean, 522270/15081472 files, 7445217/60296192 blocks

Manjaro is installed in sda10 as I have dual-booted my system with Windows 10 and Manjaro. Is there any fix to solve this slow booting process?


Hello :slightly_smiling_face:!
Do you have the package haveged (The Entropy Pool Harvesting Daemon) installed and is it’s service enabled? It sometimes is necessary to install & enable haveged to avoid slow boot times.
If not, you may want to run the command

sudo pacman -Syu haveged && sudo systemctl enable --now haveged

to install & enable haveged.

Additionally, in case the above does not work, the output of the command

env LANG=C inxi --admin --verbosity=7 --filter --no-host --width

would be helpful to diagnose your system further by providing some info about your system.

If you have any further questions, feel free to ask them.

I installed and enabled haveged. But, the booting time is still the same.

Here is the output of the command that you asked

[amartyasinha918@amartya-hp ~]$ env LANG=C inxi --admin --verbosity=7 --filter --no-host --width
Kernel: 5.10.34-1-MANJARO x86_64 bits: 64 compiler: gcc v: 10.2.0
parameters: BOOT_IMAGE=/boot/vmlinuz-5.10-x86_64
root=UUID=52cf9076-925a-43c1-afdf-1c9bea49a71b rw quiet apparmor=1
security=apparmor udev.log_priority=3
Desktop: KDE Plasma 5.21.4 tk: Qt 5.15.2 info: latte-dock wm: kwin_x11 vt: 1
dm: SDDM Distro: Manjaro Linux base: Arch Linux
Type: Laptop System: HP product: HP Pavilion Laptop 15t-cs200
v: Type1ProductConfigId serial: Chassis: type: 10 serial:
Mobo: HP model: 84C0 v: 15.32 serial: UEFI: Insyde v: F.23
date: 12/25/2020
ID-1: BAT0 charge: 11.1 Wh (33.2%) condition: 33.4/33.4 Wh (100.0%)
volts: 12.1 min: 11.6 model: HP Primary type: Li-ion serial: N/A
status: Charging
RAM: total: 15.53 GiB used: 1.43 GiB (9.2%)
RAM Report: permissions: Unable to run dmidecode. Root privileges required.
Info: Quad Core model: Intel Core i7-8565U bits: 64 type: MT MCP
arch: Kaby Lake note: check family: 6 model-id: 8E (142) stepping: C (12)
microcode: DE cache: L2: 8 MiB bogomips: 31999
Speed: 700 MHz min/max: 400/4600 MHz Core speeds (MHz): 1: 700 2: 700 3: 700
4: 700 5: 700 6: 700 7: 700 8: 700
Flags: 3dnowprefetch abm acpi adx aes aperfmperf apic arat arch_capabilities
arch_perfmon art avx avx2 bmi1 bmi2 bts clflush clflushopt cmov constant_tsc
cpuid cpuid_fault cx16 cx8 de ds_cpl dtes64 dtherm dts epb ept ept_ad erms
est f16c flexpriority flush_l1d fma fpu fsgsbase fxsr ht hwp hwp_act_window
hwp_epp hwp_notify ibpb ibrs ibrs_enhanced ida intel_pt invpcid
invpcid_single lahf_lm lm mca mce md_clear mmx monitor movbe mpx msr mtrr
nonstop_tsc nopl nx pae pat pbe pcid pclmulqdq pdcm pdpe1gb pebs pge pln pni
popcnt pse pse36 pts rdrand rdseed rdtscp rep_good sdbg sep smap smep ss
ssbd sse sse2 sse4_1 sse4_2 ssse3 stibp syscall tm tm2 tpr_shadow tsc
tsc_adjust tsc_deadline_timer vme vmx vnmi vpid x2apic xgetbv1 xsave xsavec
xsaveopt xsaves xtopology xtpr
Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: spec_store_bypass
mitigation: Speculative Store Bypass disabled via prctl and seccomp
Type: spectre_v1
mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Enhanced IBRS, IBPB: conditional, RSB filling
Type: srbds mitigation: TSX disabled
Type: tsx_async_abort status: Not affected
Device-1: Intel UHD Graphics 620 vendor: Hewlett-Packard driver: i915
v: kernel bus-ID: 00:02.0 chip-ID: 8086:3ea0 class-ID: 0300
Device-2: Quanta HP Wide Vision HD Camera type: USB driver: uvcvideo
bus-ID: 1-3:2 chip-ID: 0408:5300 class-ID: 0e02 serial:
Display: x11 server: X.Org 1.20.11 compositor: kwin_x11 driver:
loaded: intel unloaded: modesetting alternate: fbdev,vesa display-ID: :0
screens: 1
Screen-1: 0 s-res: 1366x768 s-dpi: 96 s-size: 361x203mm (14.2x8.0")
s-diag: 414mm (16.3")
Monitor-1: eDP1 res: 1366x768 hz: 60 dpi: 102 size: 340x190mm (13.4x7.5")
diag: 389mm (15.3")
OpenGL: renderer: Mesa Intel UHD Graphics 620 (WHL GT2) v: 4.6 Mesa 21.0.3
direct render: Yes
Device-1: Intel Cannon Point-LP High Definition Audio
vendor: Hewlett-Packard driver: snd_hda_intel v: kernel
alternate: snd_soc_skl,snd_sof_pci bus-ID: 00:1f.3 chip-ID: 8086:9dc8
class-ID: 0403
Sound Server-1: ALSA v: k5.10.34-1-MANJARO running: yes
Sound Server-2: JACK v: 0.125.0 running: no
Sound Server-3: PulseAudio v: 14.2 running: yes
Sound Server-4: PipeWire v: 0.3.26 running: no
Device-1: Intel Cannon Point-LP CNVi [Wireless-AC] driver: iwlwifi v: kernel
port: 4000 bus-ID: 00:14.3 chip-ID: 8086:9df0 class-ID: 0280
IF: wlo1 state: up mac:
IP v4: type: dynamic noprefixroute scope: global
IP v6: type: dynamic noprefixroute scope: global
IP v6: type: noprefixroute scope: link
Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: Hewlett-Packard driver: r8169 v: kernel port: 3000 bus-ID: 02:00.0
chip-ID: 10ec:8168 class-ID: 0200
IF: eno1 state: down mac:
Device-1: Intel Bluetooth 9460/9560 Jefferson Peak (JfP) type: USB
driver: btusb v: 0.8 bus-ID: 1-10:4 chip-ID: 8087:0aaa class-ID: e001
Report: rfkill ID: hci0 rfk-id: 1 state: down bt-service: enabled,running
rfk-block: hardware: no software: yes address: see --recommends
Message: No logical block device data found.
Hardware-1: Intel 82801 Mobile SATA Controller [RAID mode] driver: ahci
v: 3.0 port: 4060 bus-ID: 00:17.0 chip-ID: 8086.282a rev: 30 class-ID: 0104
Local Storage: total: 931.51 GiB used: 380.08 GiB (40.8%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Toshiba model: MQ04ABF100
size: 931.51 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
rotation: 5400 rpm serial: rev: 4C
Message: No optical or floppy data found.
ID-1: / raw-size: 230.01 GiB size: 225.34 GiB (97.97%)
used: 23.87 GiB (10.6%) fs: ext4 dev: /dev/sda10 maj-min: 8:10 label: N/A
uuid: 52cf9076-925a-43c1-afdf-1c9bea49a71b
ID-2: /boot/efi raw-size: 260 MiB size: 256 MiB (98.46%)
used: 82.5 MiB (32.2%) fs: vfat dev: /dev/sda1 maj-min: 8:1 label: SYSTEM
uuid: 6A39-883B
ID-3: /run/media/amartyasinha918/Amartya Sinha raw-size: 100.05 GiB
size: 100.05 GiB (100.00%) used: 21.71 GiB (21.7%) fs: ntfs dev: /dev/sda5
maj-min: 8:5 label: Amartya Sinha uuid: 01D70F2C427E2560
ID-4: /run/media/amartyasinha918/Education raw-size: 30.36 GiB
size: 30.36 GiB (100.00%) used: 631.6 MiB (2.0%) fs: ntfs dev: /dev/sda6
maj-min: 8:6 label: Education uuid: 01D70F2C4E9BCCD0
ID-5: /run/media/amartyasinha918/VMware raw-size: 19.68 GiB
size: 19.68 GiB (100.00%) used: 17.91 GiB (91.0%) fs: ntfs dev: /dev/sda7
maj-min: 8:7 label: VMware uuid: 6EB08B4EB08B1BA9
ID-6: /run/media/amartyasinha918/Videos raw-size: 150.05 GiB
size: 150.05 GiB (100.00%) used: 82 GiB (54.7%) fs: ntfs dev: /dev/sda4
maj-min: 8:4 label: Videos uuid: 01D70F2A4CD1CD20
ID-7: /run/media/amartyasinha918/Windows raw-size: 400.08 GiB
size: 400.08 GiB (100.00%) used: 233.97 GiB (58.5%) fs: ntfs dev: /dev/sda3
maj-min: 8:3 label: Windows uuid: 01D70F253E41B860
Alert: No swap data was found.
ID-1: /dev/sda2 maj-min: 8:2 size: 16 MiB fs:
label: N/A uuid: N/A
ID-2: /dev/sda8 maj-min: 8:8 size: 917 MiB fs: ntfs label: N/A
uuid: 01D71588BB16AD00
ID-3: /dev/sda9 maj-min: 8:9 size: 8 MiB fs: ntfs label: N/A
uuid: B03A12E23A12A57E
Hub-1: 1-0:1 info: Full speed (or root) Hub ports: 12 rev: 2.0
speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900
Device-1: 1-3:2 info: Quanta HP Wide Vision HD Camera type: Video
driver: uvcvideo interfaces: 2 rev: 2.0 speed: 480 Mb/s power: 500mA
chip-ID: 0408:5300 class-ID: 0e02 serial:
Device-2: 1-8:3 info: G2Touch Multi-Touch by G2TSP type: Mouse,HID
driver: hid-generic,hid-multitouch,usbhid interfaces: 2 rev: 2.0
speed: 12 Mb/s power: 100mA chip-ID: 2a94:5009 class-ID: 0300
Device-3: 1-10:4 info: Intel Bluetooth 9460/9560 Jefferson Peak (JfP)
type: Bluetooth driver: btusb interfaces: 2 rev: 2.0 speed: 12 Mb/s
power: 100mA chip-ID: 8087:0aaa class-ID: e001
Hub-2: 2-0:1 info: Full speed (or root) Hub ports: 6 rev: 3.1 speed: 10 Gb/s
chip-ID: 1d6b:0003 class-ID: 0900
System Temperatures: cpu: 48.0 C mobo: N/A
Fan Speeds (RPM): N/A
Processes: 239 Uptime: 3m wakeups: 1 Init: systemd v: 247 tool: systemctl
Compilers: gcc: 10.2.0 Packages: 1400 pacman: 1387 lib: 389 flatpak: 0
snap: 13 Shell: Bash v: 5.1.4 running-in: konsole inxi: 3.3.04

I hope that the output I have provided will help you in diagnosing the issue. :slightly_smiling_face:

Can you reboot your PC and right after booting execute this command:

systemd-analyze blame

and post here the output?

1 Like

Here is the output just after reboot

[amartyasinha918@amartya-hp ~]$ systemd-analyze blame
14.135s systemd-journal-flush.service
9.001s snapd.service
8.935s lvm2-monitor.service
7.706s dev-sda10.device
4.925s polkit.service
3.356s cups.service
3.257s systemd-fsck@dev-disk-by\x2duuid-6A39\x2d883B.service
2.075s var-lib-snapd-snap-spotify-46.mount
2.066s tlp.service
2.017s var-lib-snapd-snap-gtk\x2dcommon\x2dthemes-1515.mount
1.951s systemd-udevd.service
1.918s NetworkManager.service
1.890s apparmor.service
1.809s var-lib-snapd-snap-snapd-11588.mount
1.591s var-lib-snapd-snap-teams-4.mount
1.567s var-lib-snapd-snap-qt513-20.mount
1.550s user@1000.service
1.504s var-lib-snapd-snap-core18-1997.mount
1.467s avahi-daemon.service
1.466s bluetooth.service
1.458s systemd-logind.service
1.414s systemd-random-seed.service
1.394s var-lib-snapd-snap-python38-22.mount
1.279s var-lib-snapd-snap-code-62.mount
1.127s var-lib-snapd-snap-ksuperkey-1.mount
1.108s systemd-modules-load.service
1.051s systemd-rfkill.service
1.049s var-lib-snapd-snap-gnome\x2d3\x2d28\x2d1804-145.mount
962ms var-lib-snapd-snap-core-10958.mount
927ms snapd.apparmor.service
918ms var-lib-snapd-snap-walc-19.mount
872ms systemd-backlight@backlight:intel_backlight.service
828ms systemd-tmpfiles-setup-dev.service
812ms dev-loop4.device
806ms ModemManager.service
731ms udisks2.service
725ms wpa_supplicant.service
573ms dev-loop8.device
570ms upower.service
530ms dev-loop1.device
522ms dev-loop2.device
509ms systemd-udev-trigger.service
476ms dev-loop10.device
470ms modprobe@drm.service
469ms modprobe@fuse.service
429ms systemd-tmpfiles-setup.service
422ms dev-loop9.device
409ms dev-loop0.device
393ms dev-loop6.device
389ms dev-loop3.device
302ms dev-loop11.device
264ms dev-loop7.device
244ms systemd-journald.service
206ms boot-efi.mount
161ms systemd-remount-fs.service
140ms systemd-timesyncd.service
139ms systemd-binfmt.service
135ms systemd-sysctl.service
126ms dev-loop5.device
94ms systemd-update-utmp.service
61ms dev-hugepages.mount
59ms dev-mqueue.mount
58ms sys-kernel-debug.mount
57ms sys-kernel-tracing.mount
41ms linux-module-cleanup.service
34ms systemd-user-sessions.service
25ms modprobe@configfs.service
23ms kmod-static-nodes.service
21ms tmp.mount
20ms rtkit-daemon.service
7ms user-runtime-dir@1000.service
4ms sys-kernel-config.mount
2ms sys-fs-fuse-connections.mount
1ms snapd.socket
1ms proc-sys-fs-binfmt_misc.mount
lines 51-75/75 (END)

Please check out the output of systemd-analyze blame after reboot

can you post

journalctl --disk-usage
1 Like

@Ernest1337 Here’s the output

[amartyasinha918@amartya-hp ~]$ journalctl --disk-usage
Archived and active journals take up 504.0M in the file system.

Couple of questions:

  • Do you use snaps on your system?
  • Do you rely on any log files on your system? (are you using them?)

Also, post the output of:

journalctl --verify

I use snap to install various software that is not available on the official repository.
I don’t rely on log files. I just used journalctl --vacuum-time=2weeks to clear log files.

[amartyasinha918@amartya-hp ~]$ journalctl --verify
PASS: /var/log/journal/ce687bbc784f4a0186f6f71477ce2546/system.journal
PASS: /var/log/journal/ce687bbc784f4a0186f6f71477ce2546/user-1000.journal

Great! What’s the output of systemd-analyze blame now? (after reboot)

wait, I’m rebooting my system

Asked and answered multiple times. Please use the forum search tool for “slow boot time”

@Ernest1337 output after reboot

[amartyasinha918@amartya-hp ~]$ systemd-analyze blame
9.485s lvm2-monitor.service
8.771s snapd.service
7.591s dev-sda10.device
3.885s systemd-journal-flush.service
3.551s cups.service
3.382s polkit.service
3.261s ldconfig.service
2.494s var-lib-snapd-snap-snapd-11588.mount
2.492s NetworkManager.service
2.397s var-lib-snapd-snap-teams-4.mount
2.327s var-lib-snapd-snap-core-10958.mount
2.228s var-lib-snapd-snap-gnome\x2d3\x2d28\x2d1804-145.mount
2.090s apparmor.service
2.069s tlp.service
2.024s bluetooth.service
2.024s avahi-daemon.service
1.858s systemd-logind.service
1.765s systemd-udevd.service
1.621s var-lib-snapd-snap-python38-22.mount
1.605s var-lib-snapd-snap-qt513-20.mount
1.567s var-lib-snapd-snap-walc-19.mount
1.457s user@1000.service
1.377s var-lib-snapd-snap-gtk\x2dcommon\x2dthemes-1515.mount
1.332s systemd-tmpfiles-setup.service
1.299s ModemManager.service
1.298s dev-loop3.device
1.293s var-lib-snapd-snap-code-62.mount
1.252s var-lib-snapd-snap-core18-1997.mount
1.204s var-lib-snapd-snap-ksuperkey-1.mount
1.180s var-lib-snapd-snap-spotify-46.mount
1.164s systemd-journal-catalog-update.service
1.141s dev-loop1.device
1.089s dev-loop4.device
1.070s systemd-sysusers.service
1.025s snapd.apparmor.service
1.008s systemd-modules-load.service
854ms modprobe@drm.service
743ms systemd-backlight@backlight:intel_backlight.service
722ms udisks2.service
708ms dev-hugepages.mount
705ms dev-mqueue.mount
703ms sys-kernel-debug.mount
701ms sys-kernel-tracing.mount
697ms systemd-binfmt.service
631ms dev-loop0.device
618ms dev-loop8.device
616ms dev-loop7.device
593ms tmp.mount
589ms kmod-static-nodes.service
587ms upower.service
585ms modprobe@configfs.service
582ms modprobe@fuse.service
579ms dev-loop6.device
572ms dev-loop5.device
474ms systemd-timesyncd.service
467ms wpa_supplicant.service
443ms systemd-fsck@dev-disk-by\x2duuid-6A39\x2d883B.service
430ms sys-fs-fuse-connections.mount
421ms proc-sys-fs-binfmt_misc.mount
418ms sys-kernel-config.mount
389ms systemd-random-seed.service
362ms dev-loop11.device
362ms dev-loop10.device
353ms systemd-udev-trigger.service
304ms systemd-sysctl.service
286ms dev-loop9.device
255ms systemd-update-utmp.service
246ms boot-efi.mount
226ms dev-loop2.device
200ms systemd-rfkill.service
161ms linux-module-cleanup.service
133ms systemd-journald.service
132ms systemd-tmpfiles-setup-dev.service
126ms rtkit-daemon.service
66ms systemd-remount-fs.service
18ms systemd-user-sessions.service
18ms user-runtime-dir@1000.service
6ms systemd-update-done.service
1ms snapd.socket
lines 55-79/79 (END)

So the biggest thing is gone, that’s good.
Can you post output of:


The next thing is lvm2-monitor.service which I’m pretty sure can be masked.


[amartyasinha918@amartya-hp ~]$ systemd-analyze
Startup finished in 3.519s (firmware) + 3.585s (loader) + 4.985s (kernel) + 32.550s (userspace) = 44.640s reached after 30.477s in userspace

This is the output of systemd-analyze
userspace is taking most time

Try doing:

sudo systemctl mask lvm2-monitor.service

rebooting and checking systemd-analyze


[amartyasinha918@amartya-hp ~]$ systemd-analyze
Startup finished in 3.539s (firmware) + 2.844s (loader) + 4.969s (kernel) + 32.556s (userspace) = 43.910s reached after 32.144s in userspace