Hi everyone, I apologise in advance for any mistakes, but I have recently installed Manjaro and being the first time for me on Linux, I am trying to learn.
My problem right now is the boot which is very slow, I’ll leave you the result here.
systemd-analyze
Startup finished in 25.920s (firmware) + 6.917s (loader) + 2.973s (kernel) + 37.025s (userspace) = 1min 12.836s
graphical.target reached after 37.025s in userspace.
How can I improve it?
I premise that I have 16gb of ram and an Intel® Core™ i5-4460 processor and AMD Radeon™ R9 380 Series gpu, I also wanted to ask if anyone has any tricks to speed up Manjaro in general.
Thanks in advance.
I could be wrong, but I believe that Plymouth doesn’t actually affect boot speeds, it’s just misleading because it waits for everything else to be done?
Thank you very much for the fast feedback, btw I have done it but my boot seems quite the same as before, I navigated around the forum but I was nor able to find any solutions…
What’s going on with your BIOS, it takes almost 30 seconds before it starts loading GRUB.
GRUB itself takes 5+ seconds to then load your kernel. Reduce the timeout to 1 second in its configuration file /etc/default/grub (and issue a sudo update-grub command then) so it doesn’t wait that you validate the kernel or that the timeout is reached.
SystemD critical chain would be also good to have.
Sorry for the bad command. I’ll leave you the new output:
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.
graphical.target @40.073s
└─multi-user.target @40.073s
└─plymouth-quit-wait.service @16.887s +23.185s
└─systemd-user-sessions.service @16.751s +115ms
└─nss-user-lookup.target @17.626s
Set to 1, reboot and this is the output of systemd-analyze critical-chain
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.
graphical.target @43.468s
└─multi-user.target @43.468s
└─plymouth-quit-wait.service @17.882s +25.585s
└─systemd-user-sessions.service @17.789s +65ms
└─nss-user-lookup.target @19.194s
Do you use many snap programs? dev-loopX.device could be indicating this, and i seem to remember that disabling snap fixed someone else’s long boot time.
If you want to try something else, maybe just disable plymouth. It should not have an effect, but some have said it worked for them, maybe bug or maybe something else.
“I don’t know what to do… My boot is really slow…” Mine is slow too, but I turn it on in the morning, then go make coffee and assorted morning chores. May not be what you want to hear, but it works. “A watched pot never boils”
