freak

Yep...
 
edit /etc/default/nodm
 
Make sure these two lines are set correctly,,,

 
# Set NODM_ENABLED to something different than 'false' to enable nodm NODM_ENABLED=true # User to autologin for NODM_USER=your_user_name  

I have 85 tinkers running with armbian 5.41 xenial next 4.14.23.  Normally I run a script that apt upgrades them all but I run a small batch of them first as a test.  Today I ran apt update/upgrade on three of them and they are all bricked.  No output to the screen.  Can't ping them.  Any ideas?

I was just giving you an update my friend.  I will get your logs.

Appears to be fine now.  Thank you!!!

We dealt with this problem for quite a long time.  It started out on tinkeros which prompted us to try armbian... which didn't work any better.  I worked with an asus engineer who determined that the disconnects were because of network-manager scanning for a better connection.  While the problem is likely not network-manager itself and rather how the drivers handle it, there are a few work arounds.  Asus suggested setting the bssid which we tried and it did not help.  There is also a patched version of network-manager called network-manager-noscan which supposedly fixed this problem.  I never tried it.  We switched to wpa_supplicant and have 100% success staying connected.  We don't want the end users messing with the network-manager settings anyway which show up in the task manager by default.   Read the section in the link below titled "Regular network disconnects, latency and lost packets (WiFi)"
 
https://wiki.archlinux.org/index.php/NetworkManager

armbian-config -> system and security settings -> switch to alternative kernels

Yeah it works they're just not a sudoer like the auto created user is.