sidro
December 26, 2015, 9:28pm
1
systemd-analyze
Startup finished in 1.524s (kernel) + 2.164s (initrd) + 43.195s (userspace) = 46
I use openSUSE 42.1 with MATE desktop.
sidro@linux-5u2z:~> uname -a
Linux linux-5u2z 4.1.13-5-default #1 SMP PREEMPT Thu Nov 26 16:35:17 UTC 2015 (49475c3) x86_64 x86_64 x86_64 GNU/Linux
CPU: Intel(R) Core™2 Duo CPU E8300 @ 2.83GHz
RAM: 4 GB DDR2
HDD: SAMSUNG HD502HJ
I_A
December 26, 2015, 9:32pm
2
I think it’s probably your network there are a few threads on the Install/Boot/Login Forum
For a more definitive picture, examine
systemd-analyze blame
systemd-analyze critical-chain
As I_A suggests, network-related services can often represent a significant component of the delays associated with booting.
deano_ferrari:
For a more definitive picture, examine
systemd-analyze blame
systemd-analyze critical-chain
As I_A suggests, network-related services can often represent a significant component of the delays associated with booting.
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 @37.838s
└─bumblebeed.service @37.838s
└─dkms.service @11.747s +26.090s
└─basic.target @10.366s
└─timers.target @10.364s
└─systemd-tmpfiles-clean.timer @10.364s
└─sysinit.target @10.364s
└─apparmor.service @9.772s +591ms
└─systemd-tmpfiles-setup.service @9.435s +335ms
└─local-fs.target @9.428s
└─var-lib-ntp-proc.mount @13.124s
└─local-fs-pre.target @3.874s
└─systemd-tmpfiles-setup-dev.service @2.887s +984ms
└─kmod-static-nodes.service @2.686s +200ms
└─systemd-journald.socket
└─-.slice
Should I worry about the dkms service?
sidro
December 27, 2015, 10:13am
5
sidro@home:~> systemd-analyze
Startup finished in 1.520s (kernel) + 2.158s (initrd) + 25.367s (userspace) = 29.046s
sidro@home:~> systemd-analyze blame
13.735s display-manager.service
13.124s NetworkManager.service
4.545s dev-sda1.device
1.688s accounts-daemon.service
1.267s postfix.service
1.045s systemd-fsck@dev-disk-by\x2duuid-a48cd85e\x2d63f6\x2d4545\x2d95
778ms sys-kernel-debug.mount
756ms mnt-hard2.mount
662ms systemd-update-utmp-runlevel.service
629ms systemd-modules-load.service
620ms dev-mqueue.mount
619ms dev-hugepages.mount
616ms systemd-tmpfiles-setup-dev.service
614ms systemd-tmpfiles-setup.service
610ms systemd-journald.service
599ms apparmor.service
585ms systemd-remount-fs.service
478ms var-tmp.mount
451ms home.mount
448ms systemd-fsck@dev-disk-by\x2duuid-203d4588\x2d984d\x2d4199\x2da5
441ms var-log.mount
428ms systemd-udev-trigger.service
425ms usr-local.mount
I change wicd with network manager and disable ntpd.
My system load faster, but…
I don’t know if I can drop time boot more.
Since you have bumblebee installed I assume that this is notebook so what processor and how much memory. You know the hardware as some effect here.