What are your tips for faster boots? My system seems to hang a bit at POST until it boots into Mint. Right after post I’ll get a blinking cursor for about a full minute until it boots in. All ssd, so I know it’s something I must have done wrong. It’s also a 14 year old processor (amd fx be 8 core, rx580), but win### booted faster on it.
Off the top of my head I cannot remember the specifics, but there are several options during boot that you can make optional, for instance don’t wait until there’s an internet connection.
I am going to guess its getting the network up and going. You should be able to hit escape on the screen and see where the boot is in its process. Getting the networking going during boot is something a lot of linux installs will do as most enterprise/devs (tbh the biggest part of their audience) have network attached storage. I have never looked into getting it just to move on past it (it will still start the process for getting networking online, it just shouldnt pause) I know that some fedora installs I have had in the past did this.
But boot it again and hit escape and get more info and if it something else post again here maybe we can help better.
If you post a boot log perhaps it’ll help determine what fat can be trimmed
Are you positive you mean during POST? Like when you see your motherboard details and such?
It varies wildly from board to board, but if you don’t already know what you’re flipping around in there, I wouldn’t mess with it. You can try disabling certain tests like memory or components checks if everything seems fine operationally.
Mint uses systemd, so just use it; systemd-analyze / systemd-analyze blame.
You can also visualize it;
$ systemd-analyze plot > boot_analysis.svg
$ xviewer boot_analysis.svg
This is the second time I hear about systemd-analyze, which is funny because the first time was earlier today in that Brodie Robertson video about that pewdiepie video…
Anyway, I checked it out and the only thing I noticed was that cups took a whole second, which wouldn’t matter, except that I hardly have a printer to print with anyway, so I disabled it. (could also just remove cups I guess)
I feel like the issue is pretty prevalent in the community as systemd not being incredibly popular with the fogies (myself included). Systemd is expanding at an exponential rate and the documentation is difficult to sift through for niche things like this.
But yes, it does exist and works relatively well.
This is so cool. I don’t know how yall know all this stuff but thanks for sharing ! My startup is 1 min 21 seconds. I know it should be more like 20 seconds
I think that’s really an oversimplification–it really all depends. Systems won’t boot in under 20 seconds under all circumstances, and just because your system takes a while to boot doesn’t necessarily indicate there’s an issue.
But either way, systemd-analize blame will help you track down some possible issues and hopefully correct them.
Another thing you can try if you’re running Gnome, is to edit the application.desktop file in your system application launch folder and add a startup delay X-GNOME-Autostart-Delay=60 to some non-critical applications that you still want to run at startup. This will ensure that not everything tries to star at once, but you still get all your helpful apps to run at startup.
Considering that from my own experience systemd tends to increment boot times by a factor of about 20x due to insisting about things like raising a wifi interface that won’t ever connect because you’re later on supposed to plug in the wifi password (no save to store), which is an outright historic systemd problem, I wonder: is systemd-anamyze blame at least honest enough to recognize the fault is in its own design, or will it always blame it on something else in the system?
I couldn’t tell you. Personally I avoid systemd. My daily driver is Alpine Linux. lol
Alpine? How does it do? I’ve heard it’s pretty good for containers but at the same time some reasonable complaints for end-user workflows such as “it doesn’t even have locales”.