search

blue-systems / netrunner-core-releases

Core releases based on Debian stable
0 stars 0 forks source link

C1: before C1 boots, there is a 30-45 seconds wait state that does nothing, even though the device starts blinking #36

Open star-buck opened 5 years ago

star-buck commented 5 years ago

1701 img for C1 booted immediately.

llelectronics commented 5 years ago

On first glance it does not seem to be the libnss-systemd issue we hit before once as that package shouldn't be installed. For some reason my debug output is not working (its detecting the usb serial debug but I don't get any output). Maybe systemd-analyze blame might tell us what is keeping it waiting.

star-buck commented 5 years ago

i think it happens before systemd is even involved... more like when initilaizing the bios takes too long or the sdcard doesnt respond right away.

llelectronics commented 5 years ago

Found out that systemd-analyze blame cannot run as "bootup did not finish". The culprits for this are the apt-daily and apt-daily-upgrade services. After 14 Minutes I get a systemd-analyze output. I think we should disable both of those services as all they do is run apt update and apt upgrade if defined for unattended security updates in the background.

For the record I am not saying that those are the ones delaying your start. But an observation I made during the debugging of this problem. And of course disabling those services has consequences even if they are a bit minor to the overall boot time aswell.

edit: Removing exim4 packages makes bootup time even faster. Exim4 is not used anyway on those zeroboxes and can be removed safely.