dano

My Rock64 using Armbian_21.02.3_Rock64_buster_current_5.10.21.img.xz works fine. It didn't used to. I had the same shutdown, autorestart problem. Last year, my problem first occurred with the Armbian_20.08.1_Rock64_buster_current_5.8.6.img.xz version when I upgraded to the 5.9.14 kernel. I used the armbian-config program to back out the kernel to the 5.9.11 version and the poweroff then worked. One thing that I noticed when I restored the kernel is that my hardware ethernet address xx:xx:xx:xx:xx:xx changed. I had OMV5 installed and had to run omv-firstaid to fix the ethernet definition. My Rock64 with Armbian has worked ever since. I don't know why the address changed or why it is now working. So, I now decided to install the current Armbian_21.02.3_Rock64_buster_current_5.10.21.img.xz on a new SD card. Everything works just fine. Using 'sudo poweroff', it shuts down immediately without restarting. I also installed OMV5 and the shutdown from OMV works also. Could that restoring of the kernel and some process changing the hardware ethernet address have fixed it ?

Well, thinks have improved. I installed the latest Armbian Debian Jessie Server release and after applying all of the updates, I ended up with a more stable system. I did still have some startup issues, so I found that changing the disp_mode parm from 720p60 to 480p or 480i in /boot/armbianEnv.txt fixes my startup issues. I left the default setting for dhcp in /etc/networking/interfaces. I also have another system running Armbian Ubuntu Server with Mate installed. This was also having startup issues without a static IP set. Now, after the recent updates which I applied today, this system works with dhcp and the disp_mode parm of 720p60 or 1080p60. These are running on a Pine64+ 2Gb.

I am currently running ARMBIAN 5.25 stable Ubuntu 16.04.2 LTS 3.10.104-pine64 (server) and also had this problem after I applied updates unless I had a monitor attached. To resolve the startup issue, I changed from dynamic dhcp to static. Starts up every time now.