SteeMan

Does it boot properly if you pull the power? Reboot not working correctly is a common issue on these boxes where you don't have a dtb file that is an exact match for your hardware.

The repository exist again, but is empty as focal is EOS (End of Support status) for Armbian

After releasing the button, then remove the power and plug the power back in. What happens then? Also what dtbs have you tried?

If you are getting the android recovery you are holding the reset button too long. Have you ever installed and/or run any other OS on this box other than the preinstalled android?

Those are not what you have installed on that SD card.

The directory listing you show has files from 2020. But this download page doesn't have anything that old. You are not using builds that are current.

If you look at the log you will see that a patch is failing to apply. If you look at the error, you will see that the failure is for: drivers/usb/typec/tcpm/tcmp.c and if you look at kernel.org you will see that that file change earlier today as part of changes for 6.6.31 which was released today. So you can either contribute a fix for the patch, wait until someone else does that, or pin your build to the previous kernel version.

Based on this, you are not using Armbian. You are using a fork of Armbian. The maintainers of this fork use the Armbian name without permission. They do not participate in Armbian development, nor do they participate in these forums. Either use Armbian (Armbian com), or get support for what you are using from where you downloaded it from.

You should not put a custom dtb in this location. When you upgrade the kernel it will delete this directory and replace it with the contents of the new kernel 's dtbs. And then your box will fail to boot at the dtb file referenced in your extlinix.conf file will be missing. To answer your original question don't expect wifi to work on any TV box running amlogic build. I have about 6 different boxes and wifi doesn't work on any of them. This is mentioned in the FAQ: https://forum.armbian.com/topic/16976-status-of-armbian-on-tv-boxes-please-read-first It would be easier to buy a USB dongle for wifi if you need it.

What build of Armbian are you running?

In general you are going to need to find or fix a dtb file to correspond to the hardware you are running.

https://forum.armbian.com/topic/29202-orange-pi-zero-3 @madeofstown If you care there was a discussion the last week on this topic in the above thread (the 2w and 3 are similar).

The issue is the 1.5gb memory. That particular memory configuration isn't currently working. Look back in the threads for the 2w and 3 and you can see a lot of discussion on this topic.

If you are using an ophub kernel you are not using Armbian. These forums are for Armbian ophub is a fork of Armbian. They use the Armbian name without permission. They do not contribute to Armbian development nor do they participate in these forums. You need to direct your question to their forums/support channels.

I'd be interested in understanding better what is going on to enable the toothpick to switch boot order. So by default it seems that the boot order looks for u-boot on emmc first (as it doesn't boot from an SD card with a valid u-boot when inserted). But something happens with the pressing of the button that causes the boot order to change from emmc first to SD first. And that change seems to be persistent from your description. That would imply that some state information (boot order) is being stored somewhere as sometimes it boots emmc first and other times it boots SD card first. Where and how does this process work?

That looks like a fork of Armbian. These forums for Armbian builds not forks of Armbian builds. Generally we would recommend you direct questions based on forks of Armbian to those working on those forks.

What build are you using? Where are you placing you custom dtb? What entry do you have in your extlinux.conf file for the dtb?

I was reacting to this comment. No Armbian devs are going to look at this issue because it is reported on an unsupported board. I was just explaining how the various support models work. While it may or may not be a generic issue, the fact is that it is reported on an unsupported board. With very limited resources the volunteer devs can't look into most things that are reported. Thus I was encouraging you to contribute your time to submit a fix. You did provide a workaround, but indicate here that you are looking for an underlying fix. I'm just here saying that unless someone in the community steps up that isn't likely to happen.

Your board isn't supported by Armbian. It is Community Maintained. You are the community, PRs are welcome with fixes.

That isn't the full name of the build. Please provide the full name of the image file or the output of armbianmonitor -u

Let's start with what build of Armbian do you have installed?

@Charlie Romer Thanks for the explaination. And thanks for the help. But since you aren't running Armbian, this won't help your DietPi situation. Often users come here to get help with DietPi thinking that because it is forked from Armbian that we can help them, but we can't.

That is not an Armbian build. If that is what you have installed it isn't relevant to discussions here.

@Charlie Romer This site is for Armbian issues not DietPi issues. You need to direct your question to DietPi forums as we can't help you here.

https://forum.armbian.com/topic/16976-status-of-armbian-on-tv-boxes-please-read-first/