PDA

View Full Version : Kubuntu, long time to startup



zalle1
April 18th, 2019, 12:44 PM
Hi guys,

I'm working on an old Dell Latitude D630 laptot, with 4GB RAM and an SSD, I installed 18.04 Kubuntu, it's all good, except the start up process, which takes a long time (around 4-5minutes). Shutdown also takes at least 1 minute.

XUBUNTU starts up in under 10 seconds, but I can't get the graphics card to work, so I went with Kubuntu.

I tried "systemd-analyze" and I get:

Startup finished in 1min 7.687s (kernel) + 50.834s (userspace) = 1min 58.522s
graphical.target reached after 21.780s in userspace

I also get these errors when starting up:

( 71.081675) leds dell::kbd_backlight: Setting an LED’s brightness failed (-5)
( 80.608217) (drm:drm_atomic helper_wait_for_flip_done (drm_kms_helper)) *ERROR* (CRTC:41:pipe B) flip_done timed out
( 90.848216) (drm:drm_atomic helper_wait_for_dependencies (drm_kms_helper)) *ERROR* (CRTC:41:pipe B) flip_done timed out
( 101.088237) (drm:drm_atomic helper_wait_for_dependencies (drm_kms_helper)) *ERROR* (CONNECTOR:52:SVIDEO-1) flip_done timed out


Any ideas of how I can make it faster?

VMC
April 18th, 2019, 03:44 PM
From terminal type:

systemd-analyze blame --no-pager

Report back with results.

zalle1
April 18th, 2019, 06:44 PM
20.029s plymouth-quit.service
6.419s NetworkManager-wait-online.service
3.441s dev-sdb5.device
1.460s mpd.service
1.135s networkd-dispatcher.service
809ms udisks2.service
683ms winbind.service
587ms ModemManager.service
480ms accounts-daemon.service
472ms systemd-rfkill.service
397ms NetworkManager.service
360ms keyboard-setup.service
358ms systemd-journald.service
349ms snapd.service
342ms wpa_supplicant.service
323ms apparmor.service
291ms apport.service
291ms avahi-daemon.service
286ms systemd-udev-trigger.service
281ms upower.service
274ms rsyslog.service
251ms systemd-logind.service
239ms preload.service
227ms systemd-journal-flush.service
224ms thermald.service
192ms snapd.seeded.service
186ms swapfile.swap
163ms grub-common.service
161ms pppd-dns.service
150ms systemd-resolved.service
146ms systemd-timesyncd.service
137ms gpu-manager.service
126ms systemd-udevd.service
125ms systemd-modules-load.service
117ms polkit.service
81ms user@1000.service
68ms packagekit.service
64ms systemd-backlight@backlight:dell_backlight.service
59ms ufw.service
58ms systemd-remount-fs.service
57ms sys-kernel-debug.mount
56ms systemd-sysctl.service
55ms dev-hugepages.mount
55ms dev-mqueue.mount
54ms kmod-static-nodes.service
48ms systemd-tmpfiles-setup.service
46ms systemd-tmpfiles-setup-dev.service
40ms plymouth-start.service
35ms systemd-tmpfiles-clean.service
31ms setvtrgb.service
29ms sys-kernel-config.mount
28ms sys-fs-fuse-connections.mount
24ms systemd-user-sessions.service
19ms console-setup.service
18ms kerneloops.service
17ms plymouth-read-write.service
17ms systemd-update-utmp.service
17ms systemd-random-seed.service
15ms ureadahead-stop.service
13ms systemd-update-utmp-runlevel.service
10ms systemd-backlight@backlight:intel_backlight.service
6ms rtkit-daemon.service
6ms systemd-backlight@leds:dell::kbd_backlight.service
6ms snapd.socket
5ms sddm.service

VMC
April 18th, 2019, 07:50 PM
Please put your info between code-tags:
info

zalle1
April 19th, 2019, 10:49 AM
20.214s plymouth-quit.service
6.491s NetworkManager-wait-online.service
4.915s apt-daily-upgrade.service
3.965s dev-sda5.device
1.233s apparmor.service
1.220s systemd-udevd.service
1.118s systemd-journal-flush.service
1.024s plymouth-read-write.service
1.004s console-setup.service
992ms mpd.service
982ms networkd-dispatcher.service
830ms udisks2.service
747ms systemd-rfkill.service
481ms ModemManager.service
465ms NetworkManager.service
396ms systemd-journald.service
390ms systemd-backlight@backlight:dell_backlight.service
379ms keyboard-setup.service
362ms systemd-udev-trigger.service
338ms accounts-daemon.service
313ms winbind.service
306ms snapd.service
285ms preload.service
276ms wpa_supplicant.service
269ms upower.service
225ms thermald.service
199ms snapd.seeded.service
197ms grub-common.service
174ms apport.service
170ms avahi-daemon.service
148ms swapfile.swap
143ms systemd-timesyncd.service
135ms systemd-resolved.service
117ms gpu-manager.service
105ms systemd-modules-load.service
95ms rsyslog.service
77ms systemd-sysctl.service
77ms user@1000.service
74ms kmod-static-nodes.service
74ms polkit.service
72ms pppd-dns.service
71ms systemd-remount-fs.service
71ms dev-mqueue.mount
69ms dev-hugepages.mount
66ms packagekit.service
66ms ufw.service
62ms sys-kernel-debug.mount
53ms sys-kernel-config.mount
52ms sys-fs-fuse-connections.mount
47ms systemd-logind.service
46ms systemd-tmpfiles-setup-dev.service
39ms systemd-tmpfiles-setup.service
32ms systemd-random-seed.service
31ms plymouth-start.service
22ms systemd-user-sessions.service
20ms kerneloops.service
20ms setvtrgb.service
16ms ureadahead-stop.service
13ms systemd-update-utmp-runlevel.service
11ms systemd-update-utmp.service
8ms snapd.socket
7ms systemd-backlight@leds:dell::kbd_backlight.service
7ms rtkit-daemon.service
7ms sddm.service
6ms systemd-backlight@backlight:intel_backlight.service

VMC
April 19th, 2019, 05:36 PM
There's no indication as to the long bootup. What services?

systemctl list-unit-files --state=enabled --no-pager
Also, the output of pstree:

pstree

zalle1
April 19th, 2019, 09:01 PM
UNIT FILE STATE
acpid.path enabled
apport-autoreport.path enabled
cups.path enabled
accounts-daemon.service enabled
anacron.service enabled
apparmor.service enabled
autovt@.service enabled
avahi-daemon.service enabled
bluetooth.service enabled
console-setup.service enabled
cron.service enabled
cups-browsed.service enabled
cups.service enabled
dbus-fi.w1.wpa_supplicant1.service enabled
dbus-org.bluez.service enabled
dbus-org.freedesktop.Avahi.service enabled
dbus-org.freedesktop.ModemManager1.service enabled
dbus-org.freedesktop.nm-dispatcher.service enabled
dbus-org.freedesktop.resolve1.service enabled
dbus-org.freedesktop.thermald.service enabled
getty@.service enabled
gpu-manager.service enabled
irqbalance.service enabled
kerneloops.service enabled
keyboard-setup.service enabled
ModemManager.service enabled
mpd.service enabled
network-manager.service enabled
networkd-dispatcher.service enabled
NetworkManager-dispatcher.service enabled
NetworkManager-wait-online.service enabled
NetworkManager.service enabled
ondemand.service enabled
pppd-dns.service enabled
rsync.service enabled
rsyslog.service enabled
setvtrgb.service enabled
snapd.autoimport.service enabled
snapd.core-fixup.service enabled
snapd.seeded.service enabled
snapd.service enabled
snapd.system-shutdown.service enabled
spice-vdagent.service enabled
spice-vdagentd.service enabled
syslog.service enabled
systemd-resolved.service enabled
systemd-timesyncd.service enabled
thermald.service enabled
udisks2.service enabled
ufw.service enabled
unattended-upgrades.service enabled
ureadahead.service enabled
whoopsie.service enabled
winbind.service enabled
wpa_supplicant.service enabled
acpid.socket enabled
apport-forward.socket enabled
avahi-daemon.socket enabled
cups.socket enabled
mpd.socket enabled
snapd.socket enabled
uuidd.socket enabled
remote-fs.target enabled
anacron.timer enabled
apt-daily-upgrade.timer enabled
apt-daily.timer enabled
fstrim.timer enabled
motd-news.timer enabled
snapd.snap-repair.timer enabled

69 unit files listed.

zalle1
April 19th, 2019, 09:02 PM
systemd─┬─ModemManager───2*[{ModemManager}]
├─NetworkManager─┬─dhclient
│ └─2*[{NetworkManager}]
├─accounts-daemon───2*[{accounts-daemon}]
├─acpid
├─at-spi-bus-laun─┬─dbus-daemon
│ └─3*[{at-spi-bus-laun}]
├─at-spi2-registr───2*[{at-spi2-registr}]
├─avahi-daemon───avahi-daemon
├─baloo_file───{baloo_file}
├─cron
├─cups-browsed───2*[{cups-browsed}]
├─cupsd
├─2*[dbus-daemon]
├─dbus-launch
├─dconf-service───2*[{dconf-*********]
├─gconfd-2
├─irqbalance───{irqbalance}
├─kactivitymanage───6*[{kactivitymanage}]
├─kdeconnectd───3*[{kdeconnectd}]
├─kdeinit5─┬─file.so
│ ├─firefox─┬─Web Content───17*[{Web Content}]
│ │ ├─Web Content───15*[{Web Content}]
│ │ ├─WebExtensions───16*[{WebExtensions}]
│ │ └─51*[{firefox}]
│ ├─kaccess───2*[{kaccess}]
│ ├─kded5───7*[{kded5}]
│ ├─klauncher───2*[{klauncher}]
│ └─ksmserver─┬─kwin_x11───6*[{kwin_x11}]
│ └─2*[{ksmserver}]
├─2*[kerneloops]
├─kglobalaccel5───2*[{kglobalaccel5}]
├─krunner───4*[{krunner}]
├─kscreen_backend───2*[{kscreen_backend}]
├─kuiserver5───2*[{kuiserver5}]
├─kwalletd5───3*[{kwalletd5}]
├─mount.ntfs
├─mpd───4*[{mpd}]
├─networkd-dispat───{networkd-dispat}
├─obexd
├─org_kde_powerde───4*[{org_kde_powerde}]
├─packagekitd───2*[{packagekitd}]
├─plasmashell─┬─konsole─┬─bash───pstree
│ │ └─3*[{konsole}]
│ ├─ksysguardd
│ └─9*[{plasmashell}]
├─polkit-kde-auth───4*[{polkit-kde-auth}]
├─polkitd───2*[{polkitd}]
├─preload
├─pulseaudio─┬─gconf-helper
│ └─2*[{pulseaudio}]
├─rsyslogd───3*[{rsyslogd}]
├─rtkit-daemon───2*[{rtkit-daemon}]
├─sddm─┬─Xorg───3*[{Xorg}]
│ ├─sddm-helper───startkde─┬─kwrapper5
│ │ └─ssh-agent
│ └─{sddm}
├─start_kdeinit
├─systemd───(sd-pam)
├─systemd-journal
├─systemd-logind
├─systemd-resolve
├─systemd-timesyn───{systemd-timesyn}
├─systemd-udevd
├─udisksd───4*[{udisksd}]
├─unattended-upgr───{unattended-upgr}
├─update-apt-xapi───{update-apt-xapi}
├─upowerd───2*[{upowerd}]
├─whoopsie───2*[{whoopsie}]
├─winbindd───winbindd
├─wpa_supplicant
└─xembedsniproxy───2*[{xembedsniproxy}]

VMC
April 20th, 2019, 01:14 AM
I'm unsure about SSD drives. Maybe trim or something else, I don't have a SSD. Regarding long shutdown, and can try this and see if it helps.

sudo sed -i 's/\#DefaultTimeoutStartSec=90s/DefaultTimeoutStartSec=10s/' /etc/systemd/system.conf

sudo sed -i 's/\#DefaultTimeoutStopSec=90s/DefaultTimeoutStopSec=10s/' /etc/systemd/system.conf

zalle1
April 20th, 2019, 12:19 PM
Hi, thanks for your answer, it seems slightly faster... But still very slow.

It takes around one minute to show the Kubuntu logo, another minute to show the 4 lines of errors I mentioned above, at around 2m45s I can see and move the cursor, one minute later (3m45s) I log-in.

VMC
April 20th, 2019, 03:17 PM
On that second error, look here:
https://askubuntu.com/questions/893817/boot-very-slow-because-of-drm-kms-helper-errors