Booting Manjaro is a very long process, 40 seconds in average. I have a dell Latitude E7250 laptop and I use the 5.4 kernel and sddm.
How can I make manjaro boot faster?
I have KDE stable as manjaro edition.
systemd-analyze says this:
firmware: 24.25 s
loader: 10.46 s
kernel: 1.477 s
userspace:4.456 s
All: 40.645
Welcome to the forum! 
Can you post the output ofā¦ 
systemd-analyze blame
Click on the </> button in the toolbar of the post editor and then paste the output in between the two lines of three backticks (```).
1 Like
First:
Thanks to your answer with a friendly welcome and a guide to post Terminal outputs.
Second:
1.155s systemd-logind.service
970ms systemd-backlight@backlight:intel_backlight.service
968ms lvm2-monitor.service
931ms snapd.service
880ms dev-sda1.device
757ms apparmor.service
411ms upower.service
405ms systemd-udevd.service
377ms systemd-journald.service
368ms polkit.service
298ms tlp.service
213ms ldconfig.service
188ms ModemManager.service
169ms NetworkManager.service
160ms avahi-daemon.service
112ms systemd-udev-trigger.service
101ms user@1000.service
86ms modprobe@drm.service
79ms udisks2.service
77ms systemd-tmpfiles-setup.service
52ms systemd-journal-flush.service
46ms linux-module-cleanup.service
45ms systemd-modules-load.service
45ms systemd-backlight@leds:dell::kbd_backlight.service
43ms systemd-rfkill.service
40ms systemd-sysusers.service
39ms systemd-binfmt.service
31ms snapd.apparmor.service
29ms dev-disk-by\x2duuid-87cad71e\x2deb87\x2d45f8\x2da372\x2d5bbc90009018.swap
29ms systemd-journal-catalog-update.service
26ms pamac-daemon.service
26ms NetworkManager-wait-online.service
18ms org.cups.cupsd.service
18ms systemd-tmpfiles-setup-dev.service
17ms systemd-remount-fs.service
17ms systemd-sysctl.service
17ms dev-hugepages.mount
17ms systemd-update-utmp.service
16ms dev-mqueue.mount
16ms wpa_supplicant.service
15ms sys-kernel-debug.mount
14ms user-runtime-dir@1000.service
14ms sys-kernel-tracing.mount
14ms rtkit-daemon.service
13ms kmod-static-nodes.service
9ms systemd-user-sessions.service
9ms systemd-update-done.service
6ms sys-kernel-config.mount
4ms proc-sys-fs-binfmt_misc.mount
3ms tmp.mount
2ms sys-fs-fuse-connections.mount
1ms snapd.socket ```
1 Like
As long as you have no encrypted partition you could stop/disable/mask
by
systemctl disable --now lvm2-monitor.service
systemctl mask lvm2-monitor.service
If you need 24s for your firmware itās worth to check your firmware settings (thatās your part) and to have us a look into your system more in detail, please post
inxi -Fazy
sudo parted -l
sudo efibootmgr -v
1 Like
I changed the boot form UEFI to legacy (i dont know what this means; in boot process iām a noob) and it takes also ~ 40s too boot, but the weird thing is, that
Startup finished in 1.430s (kernel) + 9.057s (userspace) = 10.488s
graphical.target reached after 2.712s in userspace
where are the 30s? Was my laptop travelling in time?
inxi -Fazy
sudo parted -l
sudo efibootmgr -v
outputs
[qawsedrftgzh@manjaro ~]$ inxi -Fazy
System:
Kernel: 5.8.11-1-MANJARO x86_64 bits: 64 compiler: N/A
parameters: BOOT_IMAGE=/boot/vmlinuz-5.8-x86_64
root=UUID=e2cf8e12-f244-4871-89db-001fe53f8b18 rw quiet apparmor=1
security=apparmor resume=UUID=87cad71e-eb87-45f8-a372-5bbc90009018
udev.log_priority=3
Desktop: KDE Plasma 5.19.5 tk: Qt 5.15.1 info: latte-dock wm: kwin_x11
dm: SDDM Distro: Manjaro Linux
Machine:
Type: Laptop System: Dell product: Latitude E7250 v: N/A serial: <filter>
Chassis: type: 9 serial: <filter>
Mobo: Dell model: 0TVD2T v: A01 serial: <filter> UEFI [Legacy]: Dell v: A21
date: 05/16/2019
Battery:
ID-1: BAT0 charge: 39.9 Wh condition: 40.3/45.1 Wh (89%) volts: 8.7/7.4
model: SMP DELL KWFFN33 type: Li-ion serial: <filter> status: Charging
CPU:
Topology: Dual Core model: Intel Core i7-5600U bits: 64 type: MT MCP
arch: Broadwell family: 6 model-id: 3D (61) stepping: 4 microcode: 2F
L2 cache: 4096 KiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
bogomips: 20760
Speed: 798 MHz min/max: 500/3200 MHz Core speeds (MHz): 1: 1708 2: 1561
3: 1204 4: 1915
Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf
mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
Type: mds mitigation: Clear CPU buffers; SMT vulnerable
Type: meltdown mitigation: PTI
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: Full generic retpoline, IBPB: conditional,
IBRS_FW, STIBP: conditional, RSB filling
Type: srbds mitigation: Microcode
Type: tsx_async_abort mitigation: Clear CPU buffers; SMT vulnerable
Graphics:
Device-1: Intel HD Graphics 5500 vendor: Dell driver: i915 v: kernel
bus ID: 00:02.0 chip ID: 8086:1616
Device-2: Microdia type: USB driver: uvcvideo bus ID: 1-1.6:4
chip ID: 0c45:6709
Display: x11 server:``` X.org ```1.20.9 compositor: kwin_x11 driver: 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: 124 size: 280x160mm (11.0x6.3")
diag: 322mm (12.7")
OpenGL: renderer: Mesa Intel HD Graphics 5500 (BDW GT2) v: 4.6 Mesa 20.1.8
direct render: Yes
Audio:
Device-1: Intel Broadwell-U Audio vendor: Dell driver: snd_hda_intel
v: kernel bus ID: 00:03.0 chip ID: 8086:160c
Device-2: Intel Wildcat Point-LP High Definition Audio vendor: Dell
driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:9ca0
Sound Server: ALSA v: k5.8.11-1-MANJARO
Network:
Device-1: Intel Ethernet I218-LM vendor: Dell driver: e1000e v: 3.2.6-k
port: f080 bus ID: 00:19.0 chip ID: 8086:15a2
IF: eno1 state: down mac: <filter>
Device-2: Intel Wireless 7265 driver: iwlwifi v: kernel port: f040
bus ID: 02:00.0 chip ID: 8086:095a
IF: wlp2s0 state: up mac: <filter>
Device-3: Dell Dell Wireless 5809e Gobiā¢ 4G LTE Mobile Broadband Card
type: USB driver: cdc_mbim bus ID: 2-8:3 chip ID: 413c:81b1
IF: wwp0s20u8c2i12 state: down mac: <filter>
Drives:
Local Storage: total: 238.47 GiB used: 9.79 GiB (4.1%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda vendor: SK Hynix model: SC210 mSATA 256GB size: 238.47 GiB
block size: physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter>
rev: 1L00 scheme: MBR
RAID:
Hardware-1: Intel 82801 Mobile SATA Controller [RAID mode] driver: ahci
v: 3.0 port: f060 bus ID: 00:1f.2 chip ID: 8086.282a rev: 03
Partition:
ID-1: / raw size: 229.67 GiB size: 225.06 GiB (97.99%) used: 9.79 GiB (4.4%)
fs: ext4 dev: /dev/sda1
Swap:
Kernel: swappiness: 60 (default) cache pressure: 100 (default)
ID-1: swap-1 type: partition size: 8.80 GiB used: 0 KiB (0.0%) priority: -2
dev: /dev/sda2
Sensors:
System Temperatures: cpu: 50.0 C mobo: 42.0 C sodimm: 42.0 C
Fan Speeds (RPM): cpu: 0
Info:
Processes: 160 Uptime: 7m Memory: 7.65 GiB used: 991.2 MiB (12.7%)
Init: systemd v: 246 Compilers: gcc: 10.2.0 Packages: pacman: 1228 lib: 351
flatpak: 0 Shell: Bash v: 5.0.18 running in: konsole inxi: 3.1.05
[qawsedrftgzh@manjaro ~]$ sudo parted -l
[Than typed I the rootpassword]
Modell: ATA SK hynix SC210 m (scsi)
Festplatte /dev/sda: 256GB
SektorgrƶĆe (logisch/physisch): 512B/512B
Partitionstabelle: msdos
Disk-Flags:
Nummer Anfang Ende GrƶĆe Typ Dateisystem Flags
1 1049kB 247GB 247GB primary ext4 boot
2 247GB 256GB 9449MB primary linux-swap(v1)
[qawsedrftgzh@manjaro ~]$ sudo efibootmgr -v
EFI variables are not supported on this system.
It happened to me few weeks ago with KDE, system booted fine but KDE start itself was taking ages. Isnāt it a KDE related (bug?) more than kernel/fs/network etc.?
P.S. Solved by dropping KDE version entirely and now happy with Gnome/Wayland
Ok I could try this but i measured the time to the sddm login screen and the terminal output too, and I am great KDE fan, but thanks for your answer
Hello,
Before you jump through hoops and change from the DE you want to use. Please do a search on this forum for issues regarding slow startup times and KDE, you will find a answer that will resolve the issue. Also please read both the wikiās Manjaro and Arch. Get a better understanding of the desktop you want to use.
Taking a blanket statement as reinstall and use a perticular desktop is not resolving the issue, but it can be a complete waste of time. Linux is the OS that allows you to learn. Your computer is your computer, the better you understand it, the quicker issues can be resolved.
4 Likes
Yes, was rather joking, KDE is a very nice DE. But only wanted mention that experienced some troubles of that kind as well. Stick to KDE, both KDE and Gnome are beautiful and very polished piece of software.
This is firmware ā¦ has nothing to do with DE.
This is odd. What do you mean exactly? Is the system installed as EFI or not ?
This is not odd at all, is it?
My system:
Startup finished in 23.758s (firmware) + 1.910s (loader) + 1.464s (kernel) + 1.948s (userspace) = 29.082s
graphical.target reached after 1.948s in userspace
after 5 seconds Iām logged into Gnome but another 18 seconds waiting for the USB network dongle to become available via network-manager (mt76 module I assume).
Depends on your setup.
In your case you have a similar firmware time.
For example, OPs āALLā from systemd-analyze is only 10 seconds slower than yours.
Partially from the loader ā¦ but again thats system-dependent.
(such as ā¦ is a splashscreen enabled? is there a fancy theme? etc)
OP is complaining about their ~40sec boot ā¦ the majority of which is from the firmware.
In my case (on KDE) both the firmware and the loader are significantly lower.
My last boot happened to be abnormally slow ā¦ but looks like this:
Startup finished in 3.253s (firmware) + 5.446s (loader) + 3.743s (kernel) + 2.595s (userspace) = 15.039s
graphical.target reached after 2.509s in userspace
Howdy!
Could you please provide me the output of udevadm info --attribute-walk -n /dev/sda1 | grep 'DRIVERS=="[^"]' , please?
Oh, and the output of mkinitcpio -M!
Simple ad-hoc step of disabling USB Device Legacy Support in BIOS cuts ~5 seconds on my machine from the firmware value.
EDIT. Note that the whole time before hitting GRUB or whatever (tried pressing F8 on my machine to select the boot device and then waited) prolongs the firmware component of the systemd-report appropriately.
Startup finished in 42.008s (firmware) + 1.524s (loader) + 1.405s (kernel) + 1.777s (userspace) = 46.715s
graphical.target reached after 1.777s in userspace
Your system was already booting in legacy mode before. All youāve done by that switch is disable UEFI support.
If your system was really booting in UEFI mode before, then you would have had an EFI system partition on your drive, and you donāt have one. UEFI boot needs an EFI system partition of about 512 MiB in size, formatted with a vfat (FAT32) filesytstem, and with the boot and esp flags set.
1 Like
the first Command:
DRIVERS=="sd"
DRIVERS=="ahci"
the second:
==> Modules autodetected
ac
acpi_cpufreq
aesni_intel
at24
atkbd
battery
btusb
cdc_mbim
coretemp
crc32c_intel
crc32_pclmul
crct10dif_pclmul
dcdbas
dell_laptop
dell_rbtn
dell_smbios
dell_smm_hwmon
dell_wmi
dell_wmi_descriptor
e1000e
ehci_pci
evdev
ext4
fjes
ghash_clmulni_intel
i2c_i801
i8042
i915
input_leds
int3400_thermal
int3402_thermal
int3403_thermal
intel_cstate
intel_powerclamp
intel_rapl_common
intel_rapl_msr
intel_spi_platform
intel_uncore
iTCO_wdt
iwlwifi
joydev
kvm_intel
lpc_ich
mac_hid
mei_hdcp
mei_me
mei_wdt
mousedev
parport_pc
pcc_cpufreq
pcspkr
processor_thermal_device
psmouse
qcserial
rapl
sdhci_pci
sd_mod
serio_raw
snd_hda_codec_hdmi
snd_hda_codec_realtek
snd_hda_intel
uvcvideo
wmi
wmi_bmof
x86_pkg_temp_thermal
xhci_pci
Sweet!
Now its time to sudo nano /etc/mkinitcpio.conf !
Then find the line starting by MODULES=" , and remove everything between the quotation marks and add ahci sd_mod ext4 in between of the quotation mark.
Then find the line starting with BINARIES=" and clear everything (or add fsck fsck.ext4 if you want to check the disk quickly at startup)
Now find the line starting with HOOKS=" and remove everything except base .
After that go completely to the bottom, and add COMPRESSION="cat"
Ctrl+S to save, Ctrl+X to leave.
You may then execute sudo mkinitcpio -P , sudo update-grub and reboot!
It should be 10% faster (results may vary)!
2 Likes
Ok I reinstalled Manjaro with a EFI partition.
Now its booting in 30seconds but many other people says that they have 7seconds bootyime dependents it to the kernel?
You should ask those people to provide their output of systemd-analyze to compare with yours 
Because āboot timeā can mean many different things.
- Time it takes from a completely powered-off system upto the point you have your GUI open and ready for usage.
- Time it takes your Machine to load the kernel and start executing the ramdisk aka
initrd.img. - etc etcā¦
I would not be worried in your case because you are already booting super fast
May you execute the commands I provided, please?