Linux Lite Forums
General => Suggestions and Feedback => Topic started by: uthappam on June 11, 2018, 08:53:51 AM
-
It appears that slow booting has been a problem with Linux Lite for some years. I downloaded and installed LL 4.0 last night and was about to discard it when a search turned up these steps:
sudo leafpad /etc/default/grub
replace GRUB_CMDLINE_LINUX_DEFAULT=”quiet splash” with GRUB_CMDLINE_LINUX_DEFAULT=”quiet splash profile”
sudo update-grub2
sudo leafpad /etc/init.d/rc
find this line : CONCURRENCY=none or CONCURRENCY=makefile
replace with : CONCURRENCY=shell
sudo apt purge virtualbox*
sudo systemctl stop vboxadd.service
sudo systemctl stop vboxadd-service.service
sudo systemctl disable vboxadd.service
sudo systemctl disable vboxadd-service.service
untick the vbox client in the menu, settings, session and startup, application auto-start setting.
I do not think that software so recently released should require a user to do such things, specially as LL is said to have been designed for first time Linux users.
-
Uthappam
Interesting post.
Will your instructions - up to (but not including) sudo apt purge virtualbox* - work in LL 3.8?
Thanks
Mart
-
concurrency=shell is not a valid entry. won't break anything but acts the same as concurrency=none.
TC
-
Mart, I cannot answer your question. This is my first use of Linux Lite. Virtualbox is in the repositories but was not installed. I have no idea why it was put in -- or was permitted to sneak in.
-
Mart, I cannot answer your question. This is my first use of Linux Lite. Virtualbox is in the repositories but was not installed. I have no idea why it was put in -- or was permitted to sneak in.
Let me enlighten you on the reason. https://www.linuxliteos.com/forums/release-announcements/linux-lite-4-0-final-released/
-
I have just found a great blog-post on speeding-up a slow boot here: https://www.dedoimedo.com/computers/ubuntu-beaver-slow-boot.html
Before:
systemd-analyze
Startup finished in 9.259s (kernel) + 50.555s (userspace) = 59.815s
graphical.target reached after 50.545s in userspace
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 @50.545s
└─multi-user.target @50.545s
└─smbd.service @43.502s +7.043s
└─nmbd.service @26.375s +17.124s
└─network-online.target @26.374s
└─NetworkManager-wait-online.service @21.157s +5.216s
└─NetworkManager.service @16.400s +4.751s
└─dbus.service @15.213s
└─basic.target @14.954s
└─paths.target @14.954s
└─acpid.path @14.954s
└─sysinit.target @14.867s
└─apparmor.service @12.237s +2.599s
└─local-fs.target @12.181s
└─run-user-1000-gvfs.mount @39.479s
└─run-user-1000.mount @35.576s
└─swap.target @9.917s
└─dev-disk-by\x2duuid-420eef95\x2d688c\x2d40bd\x2dab12\x2d8662342ff8de.swap @8.521s +1.395s
└─dev-disk-by\x2duuid-420eef95\x2d688c\x2d40bd\x2dab12\x2d8662342ff8de.device @8.520s
After analyzing the log files as explained in the post I linked to above I noticed that the main slow-down was caused by NetworkManager waiting for IPv6 to activate. As I hadn't enabled any support for it on my network, I just disabled it in "NetworkManager -> Edit Connections -> IPv6 Settings: Ignore".
This shaved off another 20 seconds from the boot process:
systemd-analyze
Startup finished in 9.235s (kernel) + 30.131s (userspace) = 39.366s
graphical.target reached after 30.124s in userspace
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 @30.124s
└─multi-user.target @30.124s
└─smbd.service @29.666s +457ms
└─nmbd.service @24.134s +5.530s
└─network-online.target @24.132s
└─NetworkManager-wait-online.service @20.163s +3.969s
└─NetworkManager.service @16.606s +3.553s
└─dbus.service @16.388s
└─basic.target @16.336s
└─sockets.target @16.336s
└─avahi-daemon.socket @16.336s
└─sysinit.target @16.305s
└─systemd-timesyncd.service @16.097s +207ms
└─systemd-tmpfiles-setup.service @15.994s +101ms
└─systemd-journal-flush.service @3.718s +12.274s
└─systemd-remount-fs.service @2.633s +1.084s
└─systemd-journald.socket @2.602s
└─system.slice @2.602s
└─-.slice @2.244s
8)
-
I registered on this site just to thank you for this post. Thank you so much for this help!
-
Hello,
Very interesting !
Using a SSD, my PC boots in less than 20 seconds.
(http://i.imgur.com/FC3xuyY.png)