boot time on image that ships on the Beaglebone AI

[jo...@pocketnc.com]

What image ships on the Beaglebone AI? It seems to boot much faster than any of the images I tried from here: https://elinux.org/Beagleboard:BeagleBoneBlack_Debian

[Robert Nelson]

On Fri, Apr 24, 2020 at 5:17 PM <jo...@pocketnc.com> wrote:
>
> What image ships on the Beaglebone AI? It seems to boot much faster than any of the images I tried from here: https://elinux.org/Beagleboard:BeagleBoneBlack_Debian

It was an earlier version of:

https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Debian_Stretch_LXQt_TIDL_Snapshot

If you have an un-flashed AI, it'll tell you on the login screen,
under /etc/dogtag what version it was.

Regards,


--
Robert Nelson
https://rcn-ee.com/

[John Allwine]

Thanks Robert!

This is what I found:

debian@beaglebone:~$ cat /etc/dogtag
BeagleBoard.org Debian Image 2019-08-03
debian@beaglebone:~$ uname -a
Linux beaglebone 4.14.108-ti-r113 #1 SMP PREEMPT Wed Jul 31 00:01:10 UTC 2019 armv7l GNU/Linux

debian@beaglebone:~$ systemd-analyze
Startup finished in 2.585s (kernel) + 14.250s (userspace) = 16.836s

debian@beaglebone:~$ systemd-analyze blame
         12.577s bb-bbai-tether.service
          9.343s generic-board-startup.service
          7.241s dev-mmcblk1p1.device
          1.406s systemd-rfkill.service
          1.158s loadcpufreq.service

...

debian@beaglebone:~$ sudo /opt/scripts/tools/version.sh
[sudo] password for debian:
git:/opt/scripts/:[109f74fb87e6034ae1a8971a244064a8d5e090a5]
model:[BeagleBoard.org_BeagleBone_AI]
dogtag:[BeagleBoard.org Debian Image 2019-08-03]
kernel:[4.14.108-ti-r113]
nodejs:[v6.17.0]
pkg check: to individually upgrade run: [sudo apt install --only-upgrade <pkg>]
pkg:[bb-cape-overlays]:[4.4.20190801.0-0rcnee0~stretch+20190801]
pkg:[bb-wl18xx-firmware]:[1.20190227.1-0rcnee0~stretch+20190227]
pkg:[kmod]:[23-2rcnee1~stretch+20171005]
pkg:[librobotcontrol]:[1.0.4-git20190227.1-0rcnee0~stretch+20190327]
pkg:[firmware-ti-connectivity]:[20180825+dfsg-1rcnee1~stretch+20181217]
groups:[debian : debian adm kmem dialout cdrom floppy audio dip video plugdev users systemd-journal i2c bluetooth netdev gpio pwm eqep remoteproc admin spi tisdk weston-launch xenomai cloud9ide]
cmdline:[console=ttyS0,115200n8 root=/dev/mmcblk1p1 ro rootfstype=ext4 rootwait coherent_pool=1M net.ifnames=0 rng_core.default_quality=100 quiet]
dmesg | grep remote
[    2.968159] remoteproc remoteproc0: 4b234000.pru is available
[    2.969261] remoteproc remoteproc1: 4b238000.pru is available
[    2.995373] remoteproc remoteproc2: 4b2b4000.pru is available
[    3.000800] remoteproc remoteproc3: 4b2b8000.pru is available
[    7.529481] remoteproc remoteproc4: 58820000.ipu is available
[    7.582192] remoteproc remoteproc5: 55020000.ipu is available
[    7.597129] remoteproc remoteproc4: powering up 58820000.ipu
[    7.597150] remoteproc remoteproc4: Booting fw image dra7-ipu1-fw.xem4, size 6867360
[    7.631779] remoteproc remoteproc6: 40800000.dsp is available
[    7.637271] remoteproc remoteproc5: powering up 55020000.ipu
[    7.637297] remoteproc remoteproc5: Booting fw image dra7-ipu2-fw.xem4, size 3751356
[    7.638584] remoteproc remoteproc4: registered virtio0 (type 7)
[    7.638594] remoteproc remoteproc4: remote processor 58820000.ipu is now up
[    7.654881] remoteproc remoteproc7: 41000000.dsp is available
[    7.799217] Modules linked in: omap_remoteproc virtio_rpmsg_bus rpmsg_core usb_f_acm u_serial usb_f_ecm usb_f_mass_storage usb_f_rndis u_ether iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat libcomposite nf_conntrack iptable_mangle iptable_filter cmemk(O) uio_pdrv_genirq uio spidev pruss_soc_bus pru_rproc pruss pruss_intc ip_tables x_tables
[    7.800200] Modules linked in: omap_remoteproc virtio_rpmsg_bus rpmsg_core usb_f_acm u_serial usb_f_ecm usb_f_mass_storage usb_f_rndis u_ether iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat libcomposite nf_conntrack iptable_mangle iptable_filter cmemk(O) uio_pdrv_genirq uio spidev pruss_soc_bus pru_rproc pruss pruss_intc ip_tables x_tables
[    7.951028] remoteproc remoteproc6: powering up 40800000.dsp
[    7.951054] remoteproc remoteproc6: Booting fw image dra7-dsp1-fw.xe66, size 20998684
[    7.958543] remoteproc remoteproc7: powering up 41000000.dsp
[    7.958562] remoteproc remoteproc7: Booting fw image dra7-dsp2-fw.xe66, size 20998684
[    8.018185] remoteproc remoteproc5: registered virtio1 (type 7)
[    8.018199] remoteproc remoteproc5: remote processor 55020000.ipu is now up
[    8.061603] remoteproc remoteproc6: registered virtio2 (type 7)
[    8.061613] remoteproc remoteproc6: remote processor 40800000.dsp is now up
[    8.072743] remoteproc remoteproc7: registered virtio3 (type 7)
[    8.072754] remoteproc remoteproc7: remote processor 41000000.dsp is now up
dmesg | grep pru
[    2.946787] pruss 4b200000.pruss: creating PRU cores and other child platform devices
[    2.968159] remoteproc remoteproc0: 4b234000.pru is available
[    2.968233] pru-rproc 4b234000.pru: PRU rproc node /ocp/pruss_soc_bus@4b226004/pruss@0/pru@34000 probed successfully
[    2.969261] remoteproc remoteproc1: 4b238000.pru is available
[    2.969313] pru-rproc 4b238000.pru: PRU rproc node /ocp/pruss_soc_bus@4b226004/pruss@0/pru@38000 probed successfully
[    2.984426] pruss 4b280000.pruss: creating PRU cores and other child platform devices
[    2.995373] remoteproc remoteproc2: 4b2b4000.pru is available
[    2.995437] pru-rproc 4b2b4000.pru: PRU rproc node /ocp/pruss_soc_bus@4b2a6004/pruss@0/pru@34000 probed successfully
[    3.000800] remoteproc remoteproc3: 4b2b8000.pru is available
[    3.000845] pru-rproc 4b2b8000.pru: PRU rproc node /ocp/pruss_soc_bus@4b2a6004/pruss@0/pru@38000 probed successfully
[    7.799217] Modules linked in: omap_remoteproc virtio_rpmsg_bus rpmsg_core usb_f_acm u_serial usb_f_ecm usb_f_mass_storage usb_f_rndis u_ether iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat libcomposite nf_conntrack iptable_mangle iptable_filter cmemk(O) uio_pdrv_genirq uio spidev pruss_soc_bus pru_rproc pruss pruss_intc ip_tables x_tables
[    7.800200] Modules linked in: omap_remoteproc virtio_rpmsg_bus rpmsg_core usb_f_acm u_serial usb_f_ecm usb_f_mass_storage usb_f_rndis u_ether iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat libcomposite nf_conntrack iptable_mangle iptable_filter cmemk(O) uio_pdrv_genirq uio spidev pruss_soc_bus pru_rproc pruss pruss_intc ip_tables x_tables
dmesg | grep pinctrl-single
[    0.919687] pinctrl-single 4a003400.pinmux: 282 pins at pa fc003400 size 1128
dmesg | grep gpio-of-helper
lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
END

The latest image you linked takes much longer:

debian@beaglebone:~$ cat /etc/dogtag
BeagleBoard.org Debian LXQt TIDL Image 2020-04-01
debian@beaglebone:~$ uname -a
Linux beaglebone 4.14.108-ti-r131 #1stretch SMP PREEMPT Tue Mar 24 19:18:37 UTC 2020 armv7l GNU/Linux
debian@beaglebone:~$ systemd-analyze
Startup finished in 5.362s (kernel) + 1min 32.088s (userspace) = 1min 37.451s
debian@beaglebone:~$ systemd-analyze blame
    1min 28.320s generic-board-startup.service
         51.713s bb-bbai-tether.service
         43.695s dev-mmcblk1p1.device
         12.995s systemd-rfkill.service
          1.941s loadcpufreq.service

...

debian@beaglebone:~$ sudo /opt/scripts/tools/version.sh
[sudo] password for debian:
git:/opt/scripts/:[62ea733f04b46cbcc4988eb0748bddac2301ede0]
model:[BeagleBoard.org_BeagleBone_AI]
dogtag:[BeagleBoard.org Debian LXQt TIDL Image 2020-04-01]
UBOOT: Booted Device-Tree:[am5729-beagleboneai.dts]
kernel:[4.14.108-ti-r131]
nodejs:[v6.17.0]
/boot/uEnv.txt Settings:
pkg check: to individually upgrade run: [sudo apt install --only-upgrade <pkg>]
pkg:[bb-cape-overlays]:[4.14.20200331.0-0rcnee0~stretch+20200331]
pkg:[bb-wl18xx-firmware]:[1.20200322.0-0rcnee0~stretch+20200322]
pkg:[kmod]:[23-2rcnee1~stretch+20171005]
pkg:[librobotcontrol]:[1.0.4-git20190227.1-0rcnee0~stretch+20190327]
pkg:[firmware-ti-connectivity]:[20190717-2rcnee1~stretch+20200305]
groups:[debian : debian adm kmem dialout cdrom floppy audio dip video plugdev users systemd-journal i2c bluetooth netdev gpio pwm eqep remoteproc admin spi iio docker tisdk weston-launch xenomai cloud9ide]
cmdline:[console=ttyS0,115200n8 root=/dev/mmcblk1p1 ro rootfstype=ext4 rootwait coherent_pool=1M net.ifnames=0 rng_core.default_quality=100 quiet]
dmesg | grep remote
[   39.886932] remoteproc remoteproc0: 58820000.ipu is available
[   39.900198] remoteproc remoteproc1: 55020000.ipu is available
[   39.964403] remoteproc remoteproc1: powering up 55020000.ipu
[   39.964460] remoteproc remoteproc1: Booting fw image dra7-ipu2-fw.xem4, size 3751356
[   39.974004] remoteproc remoteproc2: 40800000.dsp is available
[   39.986032] remoteproc remoteproc0: powering up 58820000.ipu
[   39.986080] remoteproc remoteproc0: Booting fw image dra7-ipu1-fw.xem4, size 7051536
[   40.030775] remoteproc remoteproc3: 41000000.dsp is available
[   40.247623] remoteproc remoteproc2: powering up 40800000.dsp
[   40.247672] remoteproc remoteproc2: Booting fw image dra7-dsp1-fw.xe66, size 21014532
[   40.364040] remoteproc remoteproc3: powering up 41000000.dsp
[   40.364088] remoteproc remoteproc3: Booting fw image dra7-dsp2-fw.xe66, size 21014532
[   40.474536] Modules linked in: omap_remoteproc virtio_rpmsg_bus rpmsg_core uio_pdrv_genirq uio usb_f_ecm usb_f_mass_storage usb_f_rndis u_ether libcomposite cmemk(O)
[   40.475802] Modules linked in: omap_remoteproc virtio_rpmsg_bus rpmsg_core uio_pdrv_genirq uio usb_f_ecm usb_f_mass_storage usb_f_rndis u_ether libcomposite cmemk(O)
[   40.531121] remoteproc remoteproc0: registered virtio0 (type 7)
[   40.531144] remoteproc remoteproc0: remote processor 58820000.ipu is now up
[   40.548826] remoteproc remoteproc1: registered virtio1 (type 7)
[   40.548856] remoteproc remoteproc1: remote processor 55020000.ipu is now up
[   40.598463] remoteproc remoteproc2: registered virtio2 (type 7)
[   40.598488] remoteproc remoteproc2: remote processor 40800000.dsp is now up
[   40.637304] remoteproc remoteproc3: registered virtio3 (type 7)
[   40.637330] remoteproc remoteproc3: remote processor 41000000.dsp is now up
[   64.771932] remoteproc remoteproc4: 4b234000.pru is available
[   64.794436] remoteproc remoteproc5: 4b238000.pru is available
[   64.798438] remoteproc remoteproc6: 4b2b4000.pru is available
[   64.804179] remoteproc remoteproc7: 4b2b8000.pru is available
dmesg | grep pru
[   58.849637] pruss_uio_shmem 4b200000.pruss_shmem: Allocating gdev
[   58.849665] pruss_uio_shmem 4b200000.pruss_shmem: Allocating info
[   58.849686] pruss_uio_shmem 4b200000.pruss_shmem: Requesting resource
[   58.849743] pruss_uio_shmem 4b200000.pruss_shmem: Mapping resource
[   58.849935] pruss_uio_shmem 4b200000.pruss_shmem: Registering with uio driver
[   58.855805] pruss_uio_shmem 4b200000.pruss_shmem: Saving platform data
[   58.856361] pruss_uio_shmem 4b280000.pruss_shmem: Allocating gdev
[   58.856383] pruss_uio_shmem 4b280000.pruss_shmem: Allocating info
[   58.856403] pruss_uio_shmem 4b280000.pruss_shmem: Requesting resource
[   58.856456] pruss_uio_shmem 4b280000.pruss_shmem: Mapping resource
[   58.856642] pruss_uio_shmem 4b280000.pruss_shmem: Registering with uio driver
[   58.869379] pruss_uio_shmem 4b280000.pruss_shmem: Saving platform data
[   63.891891] pruss 4b200000.pruss: creating PRU cores and other child platform devices
[   63.922775] pruss 4b280000.pruss: creating PRU cores and other child platform devices
[   64.771932] remoteproc remoteproc4: 4b234000.pru is available
[   64.772129] pru-rproc 4b234000.pru: PRU rproc node /ocp/pruss_soc_bus@4b226004/pruss@0/pru@34000 probed successfully
[   64.794436] remoteproc remoteproc5: 4b238000.pru is available
[   64.794612] pru-rproc 4b238000.pru: PRU rproc node /ocp/pruss_soc_bus@4b226004/pruss@0/pru@38000 probed successfully
[   64.798438] remoteproc remoteproc6: 4b2b4000.pru is available
[   64.798606] pru-rproc 4b2b4000.pru: PRU rproc node /ocp/pruss_soc_bus@4b2a6004/pruss@0/pru@34000 probed successfully
[   64.804179] remoteproc remoteproc7: 4b2b8000.pru is available
[   64.804362] pru-rproc 4b2b8000.pru: PRU rproc node /ocp/pruss_soc_bus@4b2a6004/pruss@0/pru@38000 probed successfully
dmesg | grep pinctrl-single
[    0.693155] pinctrl-single 4a003400.pinmux: 282 pins at pa fc003400 size 1128
dmesg | grep gpio-of-helper
lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
END

[Robert Nelson]

On Fri, Apr 24, 2020 at 6:07 PM John Allwine <jo...@pocketnc.com> wrote:
>
> Thanks Robert!
>
> This is what I found:
> debian@beaglebone:~$ cat /etc/dogtag
> BeagleBoard.org Debian Image 2019-08-03

> The latest image you linked takes much longer:
>
> debian@beaglebone:~$ cat /etc/dogtag
> BeagleBoard.org Debian LXQt TIDL Image 2020-04-01
> debian@beaglebone:~$ uname -a
> Linux beaglebone 4.14.108-ti-r131 #1stretch SMP PREEMPT Tue Mar 24 19:18:37 UTC 2020 armv7l GNU/Linux
> debian@beaglebone:~$ systemd-analyze
> Startup finished in 5.362s (kernel) + 1min 32.088s (userspace) = 1min 37.451s
> debian@beaglebone:~$ systemd-analyze blame
> 1min 28.320s generic-board-startup.service
> 51.713s bb-bbai-tether.service
> 43.695s dev-mmcblk1p1.device
> 12.995s systemd-rfkill.service
> 1.941s loadcpufreq.service

umm.. reboot it and try again.. the full 1 Minute looks wrong, smells
like first bootup... if it's still 1 minute on the 2nd boot, i'll
flash an ai and double check.

anywho.. the 2019-08-03 image is here, about half way down..

https://beagleboard.org/latest-images

[John Allwine]

That is on the second boot.

> On Apr 24, 2020, at 6:06 PM, Robert Nelson <robert...@gmail.com> wrote:
>

[Bernard Fischer]

My BBAI takes a minute and a half to boot as well.  The times look similar to what John Allwine posted.  

BB Blue is pretty pokey as well, but not as bad, I don't think (I'll have to double check).

On Fri, Apr 24, 2020 at 7:58 PM John Allwine <jo...@pocketnc.com> wrote:

That is on the second boot.

> On Apr 24, 2020, at 6:06 PM, Robert Nelson <robert...@gmail.com> wrote:
>

--
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...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/80442C38-F5F6-4383-8A1A-24D116F7ED49%40pocketnc.com.

--

Take care,
Ben Fischer

[John Allwine]

Still taking about a minute and a half. Any ideas what happened since August last year?

debian@beaglebone:~$ systemd-analyze
Startup finished in 3.901s (kernel) + 1min 30.548s (userspace) = 1min 34.449s
debian@beaglebone:~$ systemd-analyze blame
    1min 28.412s generic-board-startup.service
         46.345s bb-bbai-tether.service
         42.818s dev-mmcblk1p1.device
         14.048s systemd-rfkill.service
           927ms loadcpufreq.service
           861ms systemd-udev-trigger.service

[Robert Nelson]

On Mon, Apr 27, 2020 at 8:48 AM John Allwine <jo...@pocketnc.com> wrote:
>
> Still taking about a minute and a half. Any ideas what happened since August last year?
>
> debian@beaglebone:~$ systemd-analyze
> Startup finished in 3.901s (kernel) + 1min 30.548s (userspace) = 1min 34.449s
> debian@beaglebone:~$ systemd-analyze blame
> 1min 28.412s generic-board-startup.service
> 46.345s bb-bbai-tether.service
> 42.818s dev-mmcblk1p1.device
> 14.048s systemd-rfkill.service
> 927ms loadcpufreq.service
> 861ms systemd-udev-trigger.service

Quick comparison, between teh kernel from last august and today:

debian@beaglebone:~$ uname -r ; systemd-analyze
4.14.108-ti-r132
Startup finished in 6.013s (kernel) + 1min 30.734s (userspace) = 1min 36.747s

debian@beaglebone:~$ uname -r ; systemd-analyze
4.14.108-ti-r113
Startup finished in 4.517s (kernel) + 1min 30.544s (userspace) = 1min 35.062s

So that isn't it..

[Robert Nelson]

It's taking 40+ seconds for the brcmfmac driver to load:

Apr 27 14:50:27 beaglebone bb-bbai-tether[1610]: bbai:tether waiting
for /sys/class/net/wlan0
Apr 27 14:50:32 beaglebone bb-bbai-tether[1610]: bbai:tether waiting
for /sys/class/net/wlan0
Apr 27 14:50:37 beaglebone bb-bbai-tether[1610]: bbai:tether waiting
for /sys/class/net/wlan0
Apr 27 14:50:42 beaglebone bb-bbai-tether[1610]: bbai:tether waiting
for /sys/class/net/wlan0
Apr 27 14:50:48 beaglebone bb-bbai-tether[1610]: bbai:tether waiting
for /sys/class/net/wlan0
Apr 27 14:50:52 beaglebone bb-bbai-tether[1610]: bbai:tether waiting
for /sys/class/net/wlan0
Apr 27 14:50:57 beaglebone bb-bbai-tether[1610]: bbai:tether waiting
for /sys/class/net/wlan0
Apr 27 14:51:02 beaglebone bb-bbai-tether[1610]: bbai:tether waiting
for /sys/class/net/wlan0
Apr 27 14:51:07 beaglebone bb-bbai-tether[1610]: bbai:wlan0:Power Management:off
Apr 27 14:51:07 beaglebone bb-bbai-tether[1610]: bbai:tether [iw phy
phy0 interface add SoftAp0 type __ap]
Apr 27 14:51:07 beaglebone bb-bbai-tether[1610]: bbai:tether [phy0 created]
Apr 27 14:51:07 beaglebone bb-bbai-tether[1610]: bbai:tether [ip link
set dev SoftAp0 down]
Apr 27 14:51:07 beaglebone bb-bbai-tether[1610]: bbai:tether [ip link
set dev SoftAp0 address 28:EC:9A:4C:63:D8]
Apr 27 14:51:07 beaglebone bb-bbai-tether[1610]: bbai:tether [ip link
set dev SoftAp0 up]
Apr 27 14:51:08 beaglebone bb-bbai-tether[1610]: bbai:tether [ip addr
add 192.168.8.1/24 broadcast 192.168.8.255 dev SoftAp0]
Apr 27 14:51:08 beaglebone bb-bbai-tether[1610]: bbai:tether [iptables
-w -t nat -A POSTROUTING -o wlan0 -j MASQUERADE]
Apr 27 14:51:08 beaglebone bb-bbai-tether[1610]: bbai:tether [iptables
-w -A FORWARD -i wlan0 -o SoftAp0 -m state --state RELATED,ESTABLISHE
D -j ACCEPT]
Apr 27 14:51:08 beaglebone bb-bbai-tether[1610]: bbai:tether [iptables
-w -A FORWARD -i SoftAp0 -o wlan0 -j ACCEPT]
Apr 27 14:51:10 beaglebone bb-bbai-tether[1610]: Configuration file:
/tmp/hostapd-bbai.conf
Apr 27 14:51:10 beaglebone bb-bbai-tether[1610]: SoftAp0: Could not
connect to kernel driver
Apr 27 14:51:10 beaglebone bb-bbai-tether[1610]: Using interface
SoftAp0 with hwaddr 28:ec:9a:4c:63:d8 and ssid "BeagleBone-63D8"
Apr 27 14:51:11 beaglebone bb-bbai-tether[1610]: SoftAp0: interface
state UNINITIALIZED->ENABLED
Apr 27 14:51:11 beaglebone bb-bbai-tether[1610]: SoftAp0: AP-ENABLED

[TJF]

Am Montag, 27. April 2020 03:16:09 UTC+2 schrieb Bernard Fischer:

My BBAI takes a minute and a half to boot as well.  The times look similar to what John Allwine posted.  

BB Blue is pretty pokey as well, but not as bad, I don't think (I'll have to double check).

You must be in error! Take a BBB! The webside says: "Boot Linux in under 10 seconds ...":

http://beagleboard.org/black

[Robert Nelson]

No, that was 10 years ago... Now we are running so much random
application on bootup, and every kernel module enabled...

[John Allwine]

How can I disable that driver?

[Robert Nelson]

On Mon, Apr 27, 2020 at 12:46 PM John Allwine <jo...@pocketnc.com> wrote:
>
> How can I disable that driver?

The driver is: brcmfmac

That was just an outlier, i moved it to be force loaded on startup
via: /etc/modules-load.d/modules.conf

Which removed the 40second delay, but something else was still slowing
things down. So it didn't change anything.

Anywho, i stopped for today, as day job was getting busy..

[John Allwine]

Thanks for looking into it, Robert!

[John Allwine]

I'm pretty much shooting in the dark here, but could this have anything to do with it? I don't see a /dev/ttyGS0

debian@beaglebone:/etc$ systemctl status serial...@ttyGS0.service
● serial...@ttyGS0.service - Serial Getty on ttyGS0
   Loaded: loaded (/lib/systemd/system/serial-getty@.service; enabled; vendor preset: enabled)
   Active: inactive (dead)
     Docs: man:agetty(8)
           man:systemd-getty-generator(8)
           http://0pointer.de/blog/projects/serial-console.html

Apr 27 18:16:17 beaglebone systemd[1]: Dependency failed for Serial Getty on ttyGS0.
Apr 27 18:16:17 beaglebone systemd[1]: serial...@ttyGS0.service: Job serial...@ttyGS0.service/start failed with result 'dependency'.

[Robert Nelson]

On Mon, Apr 27, 2020 at 1:48 PM John Allwine <jo...@pocketnc.com> wrote:
>
> I'm pretty much shooting in the dark here, but could this have anything to do with it? I don't see a /dev/ttyGS0
>
> debian@beaglebone:/etc$ systemctl status serial...@ttyGS0.service
> ● serial...@ttyGS0.service - Serial Getty on ttyGS0
> Loaded: loaded (/lib/systemd/system/serial-getty@.service; enabled; vendor preset: enabled)
> Active: inactive (dead)
> Docs: man:agetty(8)
> man:systemd-getty-generator(8)
> http://0pointer.de/blog/projects/serial-console.html
>
> Apr 27 18:16:17 beaglebone systemd[1]: Dependency failed for Serial Getty on ttyGS0.
> Apr 27 18:16:17 beaglebone systemd[1]: serial...@ttyGS0.service: Job serial...@ttyGS0.service/start failed with result 'dependency'.

I tried just removing that today, no change..

https://github.com/RobertCNelson/boot-scripts/commits/master