Reduce Boot time for Ubuntu 18.04 LTS Image

Hi,

we are using beaglebone black board with Installed Ubuntu 18.04 image on this board and kernel version is 4.14.108-ti-r104.
we installed LXDE GUI on this image. We want reduce boot time to show GUI within min time … Currently GUI start up time is 1 min approximate… so we want as early as possible …

please send us the procedure to reduce device boot up time …

Regards,
Dipak Shetye

Deepak,

Adding a GUI to a device such as the BB will have slow boot time versus a purely “server” configuration that does not . Check that the GRUB bootloader is not taking up time. Sometimes the GRUB boot loader takes up to 30 seconds. If that is not the case,you need to see what software packages you have installed on your Ubuntu image. Where did you get your Ubuntu image from?

The BB may not be the best application for you if you want faster than 1 minute boot time to the GUI.


We used [Debian 9.5 2018-10-07 4GB SD LXQT] from http://beagleboard.org/latest-images this site…how to check GRUB boot loader take so much time ?? and where we check which software installed on my system ?

any procedure to check which software get so much time take loading on system …

On Fri, 30 Aug 2019 12:24:07 +0530, Deepak Shetye
<deepak@evinsys.com> declaimed the following:

<http://debian.beagleboard.org/images/bone-debian-9.5-lxqt-armhf-2018-10-07-4gb.img.xz>
We used [Debian 9.5 2018-10-07 4GB SD LXQT
<http://debian.beagleboard.org/images/bone-debian-9.5-lxqt-armhf-2018-10-07-4gb.img.xz>]
from http://beagleboard.org/latest-images this site...how to check GRUB
boot loader take so much time ?? and where we check which software
installed on my system ?
  
  To my knowledge, Beagle Debian releases do not use GRUB -- just u-Boot

any procedure to check which software get so much time take loading on
system ...

  Before or after transition to Linux?

  [before and after] Connect a USB-Serial adapter to the debug header,
and use a time-stamping terminal program to capture the output of the boot
loaders.

  [after] Examine the output of "dmesg"

I show a 6-second delay in mounting the filesystem (SD card, I think this
is the IoT image as it only used a third of an 8GB card)

[ 2.654346] [drm] Cannot find any crtc or sizes
[ 8.598938] EXT4-fs (mmcblk0p1): mounted filesystem with ordered data
mode. Opts: (null)

9 seconds for

[ 12.715002] systemd-journald[507]: Received request to flush runtime
journal from PID 1
[ 21.720768] nf_conntrack version 0.5.0 (8192 buckets, 32768 max)

and it looks like a total of 37 seconds...

[ 37.566196] IPv6: ADDRCONF(NETDEV_CHANGE): usb0: link becomes ready
debian@beaglebone:~$

  The same information for a boot using eMMC (IOT image) gives 10 seconds
mounting the eMMC

[ 2.622296] [drm] Cannot find any crtc or sizes
[ 12.348867] EXT4-fs (mmcblk1p1): mounted filesystem with ordered data
mode. Opts: (null)

and 6 seconds at

[ 15.738640] systemd-journald[501]: Received request to flush runtime
journal from PID 1
[ 21.998761] nf_conntrack version 0.5.0 (8192 buckets, 32768 max)

Note that the "nf_conntrack" status is just about at the 22 second marker
in both cases, and the total came to

[ 26.464753] configfs-gadget gadget: high-speed config #1: c
[ 27.182908] IPv6: ADDRCONF(NETDEV_UP): usb1: link is not ready
debian@beaglebone:~$

about 27 seconds total.

systemd-analyze will help with that, google or read its man pages.

Like Jacob said, for faster boot choose an image with no gui. One of the iot or console images should do. Boot time around 30 seconds to multi-user.target.