The initial responses to your question suggested using systemd-analyze and/or dmesg in a Konsole.
Do yourself a favor and find out what part(s) of the kernel and user space bootup is taking the most time. Open a Konsole and issue:
dmesg | less
The "|" command pipes the output of dmesg into the "less" command, which allows you to scroll the output up or down. Now, examine the timeline on the left and look for large jumps in time between two successive listings. The second of those two is the one taking the time. There may be more than one gap in the listing. Those will tell you what is happening. Copy and paste the gap pairs (not the whole listing) in your next post.
Do yourself a favor and find out what part(s) of the kernel and user space bootup is taking the most time. Open a Konsole and issue:
dmesg | less
The "|" command pipes the output of dmesg into the "less" command, which allows you to scroll the output up or down. Now, examine the timeline on the left and look for large jumps in time between two successive listings. The second of those two is the one taking the time. There may be more than one gap in the listing. Those will tell you what is happening. Copy and paste the gap pairs (not the whole listing) in your next post.
Comment