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?
Your second post?
I did it it was really helpful my system booted 40% faster!
I answered to you first post to! Its post 16.
1 Like
Sweet!! 
1 Like
In my case it wouldn’t be in MODULES=" it wouldn’t be right:
udevadm info --attribute-walk -n /dev/sda1 | grep 'DRIVERS=="[^"]' DRIVERS=="sd" DRIVERS=="ahci"
mkinitcpio -M ✔ ==> Modules autodetected acpi_cpufreq eeepc_wmi ext4 fjes i2c_piix4 jmb38x_ms jme joydev k10temp kvm_amd mac_hid mousedev pcc_cpufreq pcspkr peaq_wmi psmouse radeon rtl8188ee sdhci_pci serio_raw snd_hda_codec_hdmi snd_hda_codec_idt snd_hda_intel sp5100_tco sr_mod usbhid uvcvideo video wmi
With this result I suppose it would be right for me to:
ahci sr_mod ext4
Okay??
T+ = See you later