9

I am using Ubuntu 18.04

I am confused with quiet splash adding nomodeset something like this..

What is the best option to boost the boot up time? My main aim is to reduce the boot time with in the given choices like quiet splash nomodeset or if 50 things to add, I am ready to do that if it can reduce the boot time.

i run the command
sudo journalctl --boot > boot.log it saved a copy in my home folder.

Here is the link https://paste.ubuntu.com/p/sSV9vhsyKh/

Output of systemd-analyze blame https://paste.ubuntu.com/p/Bd7wcbX5qF/

9
  • 1
    Please edit your question and add the output of systemd-analyze blame.
    – Jos
    Commented Jun 19, 2018 at 13:35
  • Add the results of the command yes. It will show what time each process cost when booting. If for instance it takes a bit of time for your wireless to appear it will show that and you could focus on something specific. Oh and quite, splash and nomodeset do NOT shorten boot time.
    – Rinzwind
    Commented Jun 19, 2018 at 14:03
  • Also, it's quiet, not quite.
    – Jos
    Commented Jun 19, 2018 at 14:05
  • 2
    The factors you want to know are in the output of systemd-analyze blame. That's why we ask for it.
    – user535733
    Commented Jun 19, 2018 at 14:38
  • 1
    If not using snaps, you can remove them also. askubuntu.com/questions/1039411/…
    – oldfred
    Commented Jun 19, 2018 at 18:57

1 Answer 1

9

Boot time is "controlled" by the speed at which the installed programs and services can load. So to speed it up:

  • Have a faster boot disk (using a faster SSD or similar - faster storage to load the programs from). You have this, so....
  • Probably DON'T need to worry about faster memory, though more of it and using preload could help with some programs particularly after boot. 6GB should be enough for now!
  • Removes unnecessary services (or dont install them in the first place)

The latter is the cheapest, and you already found one of the more ideal solutions in systemd-analyze (for newer linux systems). The blame option lists the services that take longest to complete (note, ones like plymouth, have to wait for other services to finish starting to complete, so removing them wont improve boot time by much).

Some services are important to the systems operation, so aren't ideal to remove (e.g. NetworkManager), but perhaps can be configured so no errors occur or it doesnt try and load stuff you may not use (e.g. lvm). If you post the top output of blame in your question we may be able to help with this!

Also, running systemd-analyze plot > file.svg will give you a visual overview of the boot time (as an image file.svg). Other methods are listed here (but surprisingly misses the plot option covered here).

The options you added are explained here. I'm not sure if I've heard of uses for them outside of dealing with weird video hardware, but any speed increase here is from skipping the splash screen. It might increase speed a bit but the output shows its starting up properly (i.e. I wouldn't bother except on a computer without a display in a fixed state).

3
  • @PRATAP have you changed anything (including those kernel options?). I'm guessing service(s) are failing to start, slowing it down. Can you append to the question a boot log (under systemd sudo journalctl --boot > boot.log (paste.ubuntu.com if necessary). If you boot it and leave if for a while, systemd-analyzemay work so you can add the outputs of blame or plot > systemd-plot.svg. Note in future a minimal install should be leaner on boots times so you dont have to experiment with removing things (removing some stuff may make it slower if it expects it to be there!)
    – Wilf
    Commented Jun 20, 2018 at 9:24
  • Hmm it shows i7-6550U on the boot log! (You can confirm this with lscpu or lshw). Do you have a discrete GPU? I guess after the 20-30 second mark you have logged in (automatically?) - you can probably remove whoopsie, spice-vdagent & xbrlapi.desktop (if you dont use the latter ones!) to speed up login.
    – Wilf
    Commented Jun 20, 2018 at 10:47
  • Also, messing with fsck and fastboot can marginally help unix.stackexchange.com/q/239709/52956 Setting a fixed IP on the network (and perhaps disabling autoconnecting to it if you dont need it straight away!). The cpu governer also appears to be on powersave BTW (unix.stackexchange.com/q/182696/52956). Further optimisation requires working out what is not causing it to finish booting properly (I cant guess at this time!), and getting systemd-analyze working :/ Does sudo systemctl --failed show anything?
    – Wilf
    Commented Jun 20, 2018 at 10:50

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .