Now. the whole booting to login position coast 30 sec. I need reduce it to less than 10s(or 15s). Any reference, links, stuffs? Thanks at all !

First execute "systemd-analyze blame" command.

You will see how long the different services took time.

Some services, such as "NetworkManager-wait-online.service" maybe disabled to save time, depending of you needs...

 

yes, the most of the time spent in armbian services .... 

What the "armbian-hardware-monitor.service" and "armbian-ramlog.service" doing? No docs to say?

 

and, when I stop the network wait online service:

root@orangepizeroplus2:~# service NetworkManager-wait-online.service stop
Failed to stop NetworkManager-wait-online.service.service: Unit NetworkManager-wait-online.service.service not loaded.

 

the list:

4.286s armbian-hardware-monitor.service
1.399s dev-mmcblk2p1.device
1.342s armbian-ramlog.service
1.300s networking.service
1.109s console-setup.service
833ms NetworkManager-wait-online.service
523ms NetworkManager.service
325ms armbian-zram-config.service
320ms loadcpufreq.service
295ms systemd-logind.service
278ms systemd-journald.service
252ms systemd-udev-trigger.service
244ms sysstat.service
234ms zram-config.service
228ms ap6212-bluetooth.service
197ms alsa-restore.service
197ms ntp.service
195ms keyboard-setup.service
185ms apt-daily.service
133ms ssh.service
133ms apt-daily-upgrade.service
130ms user@0.service
128ms sys-kernel-debug.mount
128ms kmod-static-nodes.service
127ms systemd-udevd.service
123ms dev-hugepages.mount
121ms rsyslog.service
120ms fake-hwclock.service
113ms systemd-modules-load.service
101ms polkitd.service
95ms sysfsutils.service
90ms resolvconf.service
87ms wpa_supplicant.service
81ms dev-mqueue.mount
80ms systemd-user-sessions.service
80ms hddtemp.service
79ms systemd-remount-fs.service
74ms systemd-sysctl.service
73ms systemd-journal-flush.service
72ms cpufrequtils.service
70ms systemd-update-utmp.service
68ms armbian-hardware-optimize.service
58ms hostapd.service
57ms rc-local.service
56ms systemd-tmpfiles-setup.service
52ms sys-kernel-config.mount
51ms systemd-random-seed.service
48ms systemd-tmpfiles-setup-dev.service
33ms systemd-rfkill.service
20ms setvtrgb.service
20ms systemd-update-utmp-runlevel.service
18ms tmp.mount

 

5 hours ago, coollofty said:

4.286s armbian-hardware-monitor.service
1.342s armbian-ramlog.service

 

Since you claim you have to wait 30 seconds obviously these two services (collecting debug information and setting up efficient logging to RAM) are NOT the culprit, true?

 

You better provide output from

systemd-analyze critical-chain
armbianmonitor -u