Can you start these services later? If you cannot just sleep, or hibinate to save power, and have to cold boot quickly. I would hope for something like:
Initially load the kernel loader load the kernel (load root file-system service) (load IPC or network service) load the turnkey application Then as Needed load device and file-system services For a screen based turnkey app, you can only display a splash screen for a few seconds, before the user thinks it is broken, a bit longer for an animated splash screen. Imagine a car radio, something has happen immediately after power on (speaker click or LED indicator or screen backlight), then less than half a second "Tuning..." before music appears. On Monday, 24 May 2021 at 16:42:08 UTC+1 RobertCNelson wrote: > On Sun, May 23, 2021 at 9:19 PM Karishma Jaiswal > <karry....@gmail.com> wrote: > > > > @Dennis L Bieber Really thanks for your detailed explanation about the > each services. > > I also updated ubuntu from 16 to 18 and done some modification in the > services. now my board's logs are as below > > My system should be working as station mode but may be future, we will > add AP mode also. > > I will also remove nginx services. > > > > > > ubuntu@beaglebone:~$ systemd-analyze blame > > 51.048s dev-mmcblk1p1.device > > 28.951s generic-board-startup.service > > 6.550s led-status.service > > 6.133s systemd-hwdb-update.service > > 4.805s grub-common.service > > 4.611s loadcpufreq.service > > 3.244s nginx.service > > 3.053s systemd-udev-trigger.service > > 2.971s avahi-daemon.service > > 2.099s ssh.service > > 1.958s archive_log.service > > 1.839s keyboard-setup.service > > 1.548s rsyslog.service > > 1.512s connman.service > > 1.438s systemd-user-sessions.service > > 1.404s wpa_supplicant.service > > 1.315s ofono.service > > 1.291s systemd-logind.service > > 1.275s cpufrequtils.service > > 1.253s tacread-keymap.service > > 887ms systemd-timesyncd.service > > 786ms us...@0.service > > 685ms systemd-journald.service > > 508ms kmod-static-nodes.service > > 498ms dev-mqueue.mount > > 487ms fake-hwclock.service > > 469ms sys-kernel-config.mount > > 459ms systemd-fsck-root.service > > 422ms systemd-tmpfiles-setup-dev.service > > 406ms systemd-modules-load.service > > 401ms systemd-sysctl.service > > 390ms systemd-tmpfiles-setup.service > > 387ms setvtrgb.service > > 350ms nvda.service > > 341ms sys-fs-fuse-connections.mount > > > > > > Also want to know that in ubuntu 18, why below two task taking so much > time and how we can reduce it further to achieve the over all boot time as > 30 sec. Any suggestion will help me. > > > > 51.048s dev-mmcblk1p1.device > > 28.951s generic-board-startup.service > > as long as you don't use usb-serial, usb-flash, or usb-networking on > the "OTG" USB port, you can nuke generic-board-startup.service > > Regards, > > -- > Robert Nelson > https://rcn-ee.com/ > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/f25766a9-4032-4466-a3b5-e42a5df485d5n%40googlegroups.com.
