The 30.921s was the very last attempt. Both attempts were after disabling the NetworkManager-wait-online.service I didn’t do anything else apart from that.
May be able to get it lower if we don’t wait for the amdgpu driver to initialised… you’ll lose the splash screen and get bombarded with boot messages, but one can’t have it both ways.
Adjusting for the 30 seconds spent faffing about with the loader to remove the rhgb parameter didn’t really gain you a great deal - probably just as easy to leave it in place.
Removing the wait for the network to come up seems to be the main win point here.
Right, but let’s hope that the initrd duration stays at ~9s and not ~21s as seen
previously.
@walkingaround, if you reboot most often in Linux and not Windows, you can gain a lot by
suspending instead of powering off, but beware to follow the Rpmfusion Howto’s to setup
that for your nvidia card.
graphical.target reached after 6.018s in userspace.
At this point I’m not sure what to do. If I should leave it as it is and start suspending it more than powering off, or try to make your rhgb solution permanent.
Thanks a lot!! Thought it would be harder. I will think about it @computersavvy btw, is it also simple to revert it? Could you please tell me how it’s done just in case I need it in the future?
man grubby will tell you (in fact man some_command will usually give you the manual page for some_command describing the command and all of its parameters)
sudo grubby --update-kernel=ALL --args="rhgb"
That command already noted above (but with a typo).
It will assist you greatly if you learn to use the man pages as noted above.
