**** BEGIN LOGGING AT Wed Sep 16 19:21:26 2020 Sep 16 19:21:48 about 10 mm Sep 16 19:22:25 10 Minutes ? So, everytime I power it up, it will take 10 Minutes ? Sep 16 19:22:34 millimetres Sep 16 19:22:58 What do you mean by millimeter ? Sep 16 19:23:14 one thousandth of a metre Sep 16 19:23:53 a uSD card is ~10 mm in size Sep 16 19:24:13 your question doesn't have a simple answer Sep 16 19:24:41 the kernel should be running within seconds of power on Sep 16 19:24:45 Maybe you did not understand my question, I am asking how long (in minutes or seconds) it will take before the OS is up and running Sep 16 19:25:08 after that, the time it takes depends entirely on what your system has to do before it becomes "ready" Sep 16 19:25:53 that can be anything from a couple of seconds to several minutes Sep 16 19:27:24 the speed of the card will make a difference too Sep 16 19:27:29 some are much faster than others Sep 16 19:28:32 2 seconds, that is very fast. I am assuming I am not doing anything. Thanks. Sep 16 19:30:42 that would be for a small system doing only the bare minimum Sep 16 19:31:41 a fully featured system like debian will take much longer Sep 16 19:35:35 It looks like I can only flash the Debian on Pocket Beagle. In this case if you know how much longer please let me know. Sep 16 19:38:05 mar123: like mru said there's no simple answer to that... how long a system takes to boot depends very strongly on how much stuff (services and such) is being started at boot Sep 16 19:38:28 as well as whether initramfs is used, how big that initramfs is, how big the kernel is Sep 16 19:38:36 and of course the performance of the SD card Sep 16 19:39:10 I am assuming I am using the same image they provided with no modification. Sep 16 19:39:25 what is "the same image they provided" ? Sep 16 19:39:52 The debian image form beagleboard.org web site Sep 16 19:41:01 there are dozens and dozens of those. if you specifically mean the latest (2020-04-06) debian buster (10.3) IoT image then say so Sep 16 19:41:42 Yes, 10.3 Sep 16 19:44:58 of all the identifying information I listed that's the least relevant/informative bit :P anyway, I have that image booting from SD card (on a BBB but that should make no difference) in 1m15s, but I don't know if I've made any significant changes that might affect boot time, though I *think* this image is still fairly unmodified Sep 16 19:45:48 much lower boot time is without any doubt achievable if one invests a small amount of effort Sep 16 19:46:21 for example removing initramfs already reduced the boot time from 1m15s to 49s Sep 16 19:47:24 Thank you very much. This is very good info. Yes I will try to trim some stuff Sep 16 19:49:11 I've had beaglebones booting in 5.1 seconds from eMMC, so a 10-second boot time should definitely be achievable from sd card Sep 16 19:49:22 (but that requires considerable effort) Sep 16 19:55:14 disabling cape-universal further reduced it to 32.5s Sep 16 19:56:25 ok. Great. Sep 16 19:57:43 for comparison: Sep 16 19:59:10 iot image: https://liktaanjeneus.nl/boot-iot.svg Sep 16 19:59:23 initramfs and cape-universal disabled: https://liktaanjeneus.nl/boot-iot-noinitramfs-nouniversal.svg Sep 16 19:59:47 an old boot plot of a really stripped-down image (running from eMMC): https://liktaanjeneus.nl/boot.svg Sep 16 20:03:02 Very good information. Thank you. Sep 16 20:07:19 next thing I'd personally do is disable a bunch of unnecessary services and replace all the networking stuff (including generic-board-startup.service, which iirc doesn't really do anything of importance other than setting up the usb gadget) by systemd-networkd, systemd-resolved, and (if usb networking is desired, which will be the case on the pocketbeagle) g_ether Sep 16 20:07:57 however that might be beyond you (based on the sort of questions you've asked) Sep 16 20:32:20 hey zmatt, how is that chart understood? Sep 16 20:33:06 can you see what is being delayed by timeouts that can be minimized / vs what takes actuall processing Sep 16 20:34:59 is it just showing at what time the service got kicked off/ how long it was active and wether it continues running or exited? Sep 16 20:35:51 if so, why do some services overlap? is that threading that does that? **** BEGIN LOGGING AT Wed Sep 16 21:07:13 2020 **** BEGIN LOGGING AT Wed Sep 16 22:19:01 2020 **** BEGIN LOGGING AT Wed Sep 16 22:37:23 2020 **** BEGIN LOGGING AT Wed Sep 16 22:40:18 2020 **** BEGIN LOGGING AT Thu Sep 17 00:06:32 2020 Sep 17 00:50:55 still no luck https://drive.google.com/file/d/1CAGwZFIE9HtLBsA74qkX-IU-Dzvejn9M/view?usp=sharing **** BEGIN LOGGING AT Thu Sep 17 01:53:56 2020 **** BEGIN LOGGING AT Thu Sep 17 02:09:47 2020 **** BEGIN LOGGING AT Thu Sep 17 02:19:27 2020 **** BEGIN LOGGING AT Thu Sep 17 02:32:58 2020 **** ENDING LOGGING AT Thu Sep 17 02:59:57 2020