H3 Reboot Issue

[Geoffrey F4FXL]

Hi All,

 

I have a couple of H3 based boards (Orange Pi Zero and FriendlyArm NanoPi Duo 2). With all of them I have the same issue:
command like "reboot" turn the board off instead of rebooting.

The workaround is to add following line in /boot/armbianEnv.txt
 

extraargs=reboot=warm

 

Running latest image on all of the boards.

 

 

Edited 2 hours ago by Geoffrey F4FXL
corrected /etc/armbianEnv.txt => /boot/armbianEnv.txt

[eselarm]

I think it must be  /boot/armbianEnv.txt

Besides that, I never had this issue with my 5 NanoPi-NEO boards, originally Armbian Buster, always in-place upgraded. Also 1 now tested with kernel 6.18, now issues.

So I think you maybe need to look at what U-Boot you use, what kernel is it and logs ( all via armbianmonitor -u )

[Geoffrey F4FXL]

Ooops, you are right I meant /boot/armbianEnv.txt, I edited the topic to correct.

The output of armbianmonitor -u can be found here:
https://paste.armbian.com/foyunagisu

What should I look for?

[eselarm]

I do not see something clearly wrong, but likely is is a newer U-Boot, maybe something wrong there; version in SD-card you can show with:

dd if=/dev/mmcblk0 count=32k status=none | strings | grep "U-Boot SPL"

 

[Geoffrey F4FXL]

Here is the output:
 

U-Boot SPL 2024.01_armbian-2024.01-S866c-P6b16-Ha5c2-V7d7d-Bbf55-R448a (Dec 22 2025 - 03:39:51 +0000)

 

Note that prior to this I tried to update uboot through armbian-install, it did not change anything to my reboot issue.

[eselarm]

OK, I have the following in my test NanoPi-NEO (using 6.18 kernel):

U-Boot SPL 2024.01-armbian-2024.01-S866c-P7738-Ha5c2-V2b78-Bb703-R448a (Mar 09 2025 - 03:54:42 +0000)

Same base, but it is older and anyway different hardware, although H3 SoC. I have no more ideas why you need that extra kernel cmdline statement. I think I have seen it as well for another board/SoC, but does not ring a bell.

 

[Geoffrey F4FXL]

The thing is that I need it on different boards .... Tried Armbian Trixie and Ubuntu based, same issue thus it might be uoot and/or kernel related.

Thanks for your help though.