The booting of Fedora 32 Beta is very slow. The procedure of the last line always takes about 40 s to complete. What’s the problem?
I’m using a Huawei matebook x pro.
1 Like
Hi,
Try to edit:
/lib/systemd/system/NetworkManager-wait-online.service
search for the line:
ExecStart=/usr/bin/nm-online -s -q --timeout=30
and try to change --timeout= value to a smaller one. I had it set to 30s by default but service started after 10 seconds.
I reduced it to 2 seconds and I didn’t notice any negative impact on the system. Maybe somebody else knows if it could have a negative impact on e.g. installing updates during system startup.
2 Likes
Thank you. I reinstalled the system and the booting speed is acceptable.
I just want say I am experiencing the same on fedora 32 beta, really slow startup on an ssd. I will try what roypen suggested. If it’s still slow, I’ll reinstall too.
1 Like
I recreated the installation media and reinstalled a couple of times. I still have a much slower boot than fedora 31. I created a bug report if anyone else wants to chime in.
4 Likes
A recent update of the system made the booting slow again. I tried as roypen suggested and the booting speed is good now.
and try to change --timeout= value to a smaller one. I had it set to 30s by default but service started
after 10 seconds.I reduced it to 2 seconds and I didn’t notice any negative impact on the system.
That’s not best. NetworkManager-wait-online.service exists to delay network-online.target until network is up.
In the best case, you have nothing depend on network-online.target. In that case, nothing gets delayed. If something requires network-online.target for good reasons, then it’s not right to just bypass the mechanism and set a unrealistical low timeout.
Also, NetworkManager-wait-online.target always a few seconds if you boot with ethernet cable unplugged, because NetworkManager waits whether the driver will still detect the cable. That can sometimes take several seconds, and NetworkManager doesn’t know in advance (see carrier-wait-timeout in NetworkManager.conf(5) manual). Beyond that, if NetworkManager takes significantly longer to complete NetworkManager-wait-online.service, you should investigate why that is, and solve the problem. It usually is a misconfiguration.
Finally, NetworkManager-wait-online.service is some simple implementation, not very configurable. If you have special requirements, you can disable the service and replace it by your own implementation that is ordered Before=network-online.target. But again: best is that you don’t have anything waiting for network-online.target in the first place.
1 Like
I just want to say/repeat that the output of “systemd-analyze blame” can help in finding the cause of slow boot.
2 Likes
Just a general note for anyone using Fedora 32:
Please note that Fedora 32 has not yet been released and is not meant to be used as a daily use distro.
If anyone is using it already, please keep this in mind: it has bugs, and you are expected to debug these where possible and file bugs so that they can be fixed before the release. Ideally, discussion related to Fedora 32 should be held with the Fedora QA team on one of their channels:
https://fedoraproject.org/wiki/QA
That is also where you will get the most up to date information on the bugs/updates and general state of Fedora 32.
Edit: we’re not saying don’t use it, but please keep in mind the significance of “beta” 
2 Likes