Citeren Marco Calistri
I was basing my guessing on the first output (systemd-analyze blame ) where the bigger offenders appears to be the sda5 ( root / partition) and Modem-manager. As I wrote, I was not confident of this kind of analysis using systemd.
I'm almost certain, it is the HDD which is the culprit here.
Anyhow, look how we can be confused by ML users feedback which point the slowness of the boot to the splash boot whereas the issue is elsewhere!
See below.
If I would have followed straightly the suggestions passed by some of the users which provided their *"academic hints"*, I should have uninstalled Plymouth and disabled my splash boot uselessly :-/
You're comparing apples to oranges. Those people don't want fancy graphics, because the time to login is already in the order of ten seconds or so. They (like me) simply want to login and start work as fast as possible. Adding a second boot time there *is* relevant. On your system, it takes over a minute before the login prompt appears so I understand bootsplash may be relevant and you'll not notice this. But given the choice, over a minute waiting time with fancy graphics or less than ten seconds without, most people would probably choose the latter.
So now I would like to ask: why SuSEfirewall2_init.service, display-manager.service, NetworkManager.service, took so long time to be up and running at least on my system?
I don't know if there is a way to check this, but I highly suspect these services are waiting for disk-I/O. All caches are empty at boot time, so everything has to come from disk. This is where SSD drives with essentially zero seek times shine. Changing to SSD drives has been the single biggest performance improvement on my systems. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org