Hey, thanks for posting results! I’ve just checked and I’m able to boot in 24 seconds from uSD. Something is not right with my eMMC installation then. I’d like to investigate further because the box requires couple of tweaks to make it fully working (remote, VFD, wake up) so I’d much rather fix the existing installation than start over.
Edit: Okay I think I found a culprit: iptables.service takes 16 seconds to start on boot
$ systemd-analyze critical-chain
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.
kodi.target @19.801s
└─kodi-aml-hdmimonitor.service @19.799s
└─kodi.service @19.081s +711ms
└─smp-affinity.service @18.963s +113ms
└─graphical.target @18.957s
└─multi-user.target @18.201s
└─avahi-daemon.service @18.200s
└─network.target @18.193s
└─iptables.service @1.869s +16.247s
└─basic.target @1.757s
└─sockets.target @1.757s
└─lircd.socket @1.757s
└─sysinit.target @1.755s
└─systemd-udevd.service @1.716s +38ms
└─add-entropy.service @626ms +259ms
└─systemd-tmpfiles-setup.service @595ms +25ms
└─systemd-journal-flush.service @558ms +33ms
└─systemd-journald.service @422ms +133ms
└─machine-id.service @362ms +56ms
└─systemd-journald.socket @132ms
└─system.slice @125ms
└─-.slice @125ms
Interesting. Because starting/stopping this service over SSH after boot is instantaneous.
Edit 2: Full debug info is here http://ix.io/2yGa