On Thu, Sep 22, 2016 at 05:35:48PM +0800, Umarzuki Mochlis wrote:
2016-09-22 17:16 GMT+08:00 Floris <jkflo...@dds.nl>:

$ systemd-analyze blame
to find out which services are slow to start


it seemed that most services less than 5 seconds to start

Another avenue, then, might be "systemd-analyze critical-chain". That will give you a tree of what the slowest dependencies of graphical.target are. Slow units will get two times: one preceded by "@" tells you how long into the boot the unit became active and the one preceded by "+" tells you how long the unit took to start.

dmesg output shows some error regarding firmware-linux-nonfree but
other desktop with same model also does not have it installed and did
not have this problem

dmesg pastebin:

For more information, please reread.

Attachment: signature.asc
Description: PGP signature

Reply via email to