Boot Time Now 30 seconds
Forum rules
Do not post support questions here. Before you post read the forum rules. Topics in this forum are automatically closed 6 months after creation.
Do not post support questions here. Before you post read the forum rules. Topics in this forum are automatically closed 6 months after creation.
Boot Time Now 30 seconds
My boot times with 18.3 Cinnamon were consistently 55 seconds from pressing the power button to the desktop. Then when I installed the 19 beta it was a little longer to load. Now after loading 19 beta Cinnamon on yet another SSD: suddenly, the boot time is under 30 seconds.
I did not enable Fast Boot in the BIOS. And this is a Celeron CPU and no overclocking was done.
I did not enable Fast Boot in the BIOS. And this is a Celeron CPU and no overclocking was done.
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 1 time in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Re: Boot Time Now 30 seconds
Mod note:
This topic was moved because there's no support request in it.
This topic was moved because there's no support request in it.
If your issue is solved, kindly indicate that by editing the first post in the topic, and adding [SOLVED] to the title. Thanks!
Re: Boot Time Now 30 seconds
That is just 15 seconds from the BIOS splash screen to the desktop. Finally a reasonable boot time. Does any one else get these boot times? I will reload all my computers with Mint 19 Cinnamon beta to achieve these times but was looking for a little reassurance before proceeding.
Re: Boot Time Now 30 seconds
...Reassurance about what? Different systems have different processors and different hard drives:
without posting exact details of what your hardware is, and also what is going on during the boot sequence,
you will only get reports from random people quoting their equally random and 110% subjective experiences.
Boot time differences between 18 & 19 shouldn't be tremendously different "by default": maybe a few secs more or less.
Being a new base, chances are a few extra services will probably have been added (thereby *maybe* adding more time).
Being a new base (ie. 2 yrs newer systemd libraries), the boot procedure will most likely have been optimized (and possibly detracting from boot time).
Hope that clears it up.
Re: Boot Time Now 30 seconds
7-year old, low end eMachines 1831 (w/SSD):
Code: Select all
$ systemd-analyze
Startup finished in 3.486s (kernel) + 1.784s (userspace) = 5.271s
Please edit your original post title to include [SOLVED] if/when it is solved!
Your data and OS are backed up....right?
Your data and OS are backed up....right?
Re: Boot Time Now 30 seconds
I see that but how long does it actually take from the power button push till you see the desktop?Flemur wrote: ⤴Tue Jun 19, 2018 9:55 am 7-year old, low end eMachines 1831 (w/SSD):Code: Select all
$ systemd-analyze Startup finished in 3.486s (kernel) + 1.784s (userspace) = 5.271s
What is the text for me to see my boot time.
Last edited by Ozo on Tue Jun 19, 2018 10:08 am, edited 1 time in total.
Re: Boot Time Now 30 seconds
That is my point. I am getting 50% better boot times now which was totally unexpected.thx-1138 wrote: ⤴Tue Jun 19, 2018 9:23 am Boot time differences between 18 & 19 shouldn't be tremendously different "by default": maybe a few secs more or less.
Being a new base, chances are a few extra services will probably have been added (thereby *maybe* adding more time).
Being a new base (ie. 2 yrs newer systemd libraries), the boot procedure will most likely have been optimized (and possibly detracting from boot time).
Last edited by Moem on Tue Jun 19, 2018 10:14 am, edited 1 time in total.
Reason: Fixed a quote
Reason: Fixed a quote
Re: Boot Time Now 30 seconds
With respect, any answer you might get to this question, while informative, will be useless for comparison purposes. The time from pressing the power button the first "Linux action" is all your computer (how long for BIOS to start, how long for POST to complete, how long is the delay between the POST and the first "Linux Action" --- these are going to be different for each computer being discussed) ... and will be different from one computer to the next.
The time from Grub first loading until you get the login is, again, going to vary depending on the hardware involved so comparisons from one machine to the next are, again, might be informative but will, ultimately, be useless.
Re: Boot Time Now 30 seconds
A few seconds longer - I could cut that by disconnecting some of its many card-reading thingies that I never use.Ozo wrote: ⤴Tue Jun 19, 2018 10:03 amI see that but how long does it actually take from the power button push till you see the desktop?Code: Select all
$ systemd-analyze
That's the command, above ^^^What is the text for me to see my boot time.
Please edit your original post title to include [SOLVED] if/when it is solved!
Your data and OS are backed up....right?
Your data and OS are backed up....right?
Re: Boot Time Now 30 seconds
...Ozo, the general 'process' is:
In my system, with i5-6200 & 5400rpm:
Not all systems will display the above stuff necessary (ie. Flemur's for example doesn't show firmware & loader).
Loader i think it's grub and / or microcode, but i can't recall now - the rest are pretty self-explanatory.
If it takes ages until the "logo" pops-up, it might just be your BIOS firmware - in which case, it is what it is.
Misbehaving services, graphics' card driver (mis)configuration, improper fstab entries, huge logs and what not can cause a slow boot.
srq2625 pretty much covered the rest.
EDIT: Firmware & loader are only shown in (U)EFI-based installations.
systemd-analyze
systemd-analyze blame --no-pager
systemd-analyze critical-chain
In my system, with i5-6200 & 5400rpm:
Startup finished in 3.484s (firmware) + 4.416s (loader) + 4.432s (kernel) + 21.346s (userspace) = 33.680s
Not all systems will display the above stuff necessary (ie. Flemur's for example doesn't show firmware & loader).
Loader i think it's grub and / or microcode, but i can't recall now - the rest are pretty self-explanatory.
If it takes ages until the "logo" pops-up, it might just be your BIOS firmware - in which case, it is what it is.
Misbehaving services, graphics' card driver (mis)configuration, improper fstab entries, huge logs and what not can cause a slow boot.
srq2625 pretty much covered the rest.
EDIT: Firmware & loader are only shown in (U)EFI-based installations.
Re: Boot Time Now 30 seconds
Thanks.
Code: Select all
user@BadBott:~$ systemd-analyze
Startup finished in 5.561s (kernel) + 1.999s (userspace) = 7.560s
graphical.target reached after 1.966s in userspace
user@BadBott:~$ systemd-analyze blame --no-pager
18.991s configure-printer@usb-002-007.service
1.931s dev-sda1.device
785ms ubuntu-system-adjustments.service
759ms upower.service
606ms networkd-dispatcher.service
521ms accounts-daemon.service
511ms udisks2.service
492ms ModemManager.service
467ms NetworkManager.service
459ms plymouth-quit-wait.service
455ms lightdm.service
408ms grub-common.service
373ms speech-dispatcher.service
358ms keyboard-setup.service
354ms hddtemp.service
349ms thermald.service
311ms systemd-udev-trigger.service
298ms lm-sensors.service
277ms pppd-dns.service
276ms kerneloops.service
274ms swapfile.swap
268ms networking.service
262ms systemd-rfkill.service
259ms wpa_supplicant.service
227ms apparmor.service
220ms systemd-journald.service
212ms avahi-daemon.service
206ms gpu-manager.service
170ms rsyslog.service
157ms systemd-timesyncd.service
155ms systemd-resolved.service
121ms systemd-logind.service
103ms user@1000.service
98ms lvm2-monitor.service
92ms systemd-udevd.service
83ms systemd-modules-load.service
72ms polkit.service
58ms dns-clean.service
54ms systemd-sysctl.service
53ms packagekit.service
47ms systemd-remount-fs.service
46ms systemd-journal-flush.service
45ms dev-hugepages.mount
44ms blk-availability.service
44ms kmod-static-nodes.service
41ms ufw.service
41ms plymouth-start.service
39ms dev-mqueue.mount
38ms sys-kernel-debug.mount
37ms systemd-tmpfiles-setup.service
34ms sys-fs-fuse-connections.mount
31ms colord.service
29ms systemd-tmpfiles-setup-dev.service
25ms systemd-update-utmp-runlevel.service
23ms apport.service
21ms systemd-random-seed.service
17ms bluetooth.service
16ms systemd-tmpfiles-clean.service
15ms plymouth-read-write.service
15ms setvtrgb.service
13ms ureadahead-stop.service
13ms systemd-user-sessions.service
11ms sys-kernel-config.mount
10ms console-setup.service
10ms systemd-update-utmp.service
8ms rtkit-daemon.service
6ms openvpn.service
4ms motd-news.service
user@BadBott:~$ systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.
graphical.target @1.966s
└─multi-user.target @1.966s
└─getty.target @1.966s
└─getty@tty1.service @1.966s
└─system-getty.slice @1.963s
└─setvtrgb.service @1.946s +15ms
└─systemd-user-sessions.service @1.458s +13ms
└─network.target @1.456s
└─NetworkManager.service @988ms +467ms
└─dbus.service @918ms
└─basic.target @803ms
└─sockets.target @803ms
└─dbus.socket @803ms
└─sysinit.target @800ms
└─apparmor.service @572ms +227ms
└─local-fs.target @560ms
└─local-fs-pre.target @560ms
└─keyboard-setup.service @200ms +358ms
└─systemd-journald.socket @191ms
└─system.slice @190ms
lines 1-23