You are not logged in.
Pages: 1
[hydn@ArchLinux ~]$ systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.
graphical.target @1.253s
└─multi-user.target @1.253s
└─NetworkManager.service @502ms +750ms
└─basic.target @502ms
└─timers.target @502ms
└─systemd-tmpfiles-clean.timer @502ms
└─sysinit.target @501ms
└─systemd-backlight@backlight:intel_backlight.service @1.206s +3ms
└─system-systemd\x2dbacklight.slice @1.205s
└─system.slice @94ms
└─-.slice @93msNetworkManager and intel_backlight.service show in red.
Easy to resolve?
Linux Performance Blog: https://linuxblog.io/
Offline
Use a different network manager...
Offline
...slow? it's a couple of seconds. How often do you reboot? once a day? week? month?
I don't understand why there is such an obsession with boot speed (and at the same time, system stability).
My: [ GitHub | AUR Packages ]
Offline
Check how how big is your journal https://wiki.archlinux.org/index.php/Sy … _over_time
Offline
Pages: 1