This problem actually does not only occur in Manjaro but in all Linux distributions, but now using Manjaro, previously I used Windows and it booted fast, btw I used SSD NVME, then I moved to Linux and the boot was still fast, then I moved to 4 distros other then the problem occurred, after that I still moved to the distro and ignored the problem, when the power button was pressed and displayed the Lenovo logo it could take up to 10 seconds, even though before this problem occurred, a few seconds after pressing the power button the Lenovo logo immediately appeared
sorry if my english is bad
Provide more information, with your current description others can only read from glass sphere.
Welcome to Manjaro!
To allow all of us helpful gurus on this forum TO HELP YOU, we need some basic information about your system. This probably means you described the symptoms of your problem, but now we need some more information to know where the origin of your issue is exactly.
Someone probably linked you to this tutorial, so if you’re reading this in response to a question, please click the green link above this text to bring you to the full and unabridged text of the tutorial…
If you post the output of
It will list you boot process/what is taking time
9.110s systemd-tmpfiles-clean.service >
1.450s systemd-random-seed.service >
1.369s lvm2-monitor.service >
1.223s dev-nvme0n1p2.device >
1.076s apparmor.service >
738ms tlp.service >
498ms snapd.service >
306ms systemd-udev-trigger.service >
288ms systemd-journald.service >
277ms systemd-udevd.service >
213ms firstname.lastname@example.org >
203ms polkit.service >
194ms upower.service >
188ms systemd-logind.service >
159ms systemd-modules-load.service >
120ms email@example.com >
115ms avahi-daemon.service >
105ms NetworkManager.service >
97ms systemd-journal-flush.service >
87ms systemd-binfmt.service >
67ms firstname.lastname@example.org >
66ms systemd-fsck-root.service >
66ms ModemManager.service >
66ms dev-hugepages.mount >
65ms dev-mqueue.mount >
64ms kmod-static-nodes.service >
64ms udisks2.service >
64ms sys-kernel-debug.mount >
62ms sys-kernel-tracing.mount >
60ms cups.service >
59ms email@example.com >
51ms linux-module-cleanup.service >
41ms systemd-tmpfiles-setup.service >
37ms boot-efi.mount >
37ms systemd-fsck@dev-disk-by\x2duuid-C675\x2d7DF7.service >
31ms systemd-tmpfiles-setup-dev.service >
30ms sys-fs-fuse-connections.mount >
29ms systemd-remount-fs.service >
25ms sys-kernel-config.mount >
This must be a local issue - my system boots in no time - of course the boottime is depending on services loaded - e.g. requiring a network can slow things down when you are on wireless.
I use a multitude of systems various brands and configurations only commonality is Manjaro. None of them are noticable slow.
Unless you are actually using flatpak, snap - whatever I highly recommend disabling those and the related apparmor services.
hi, I have similar problem: NVME drive, systemd-analyze blame points to dev-nvme0n1p2; device name from blame report is constant across multiple boots, while UUID changes, sometimes it is swap partition, then home partition or even efi partition; delay introduced is ~ 15 seconds, which does not feel right.
sudo systemd-analyze blame
any hint where to look?