SteeMan

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/

https://forum.armbian.com/topic/16976-status-of-armbian-on-tv-boxes-please-read-first https://forum.armbian.com/topic/33676-installation-instructions-for-tv-boxes-with-amlogic-cpus

moved

You expect a lot for free. This is open source, please submit a PR for improvements. The level of your involvement is what makes open source work or not work. Anyone around here would agree our doc is poor.

Get involved and submit a PR to: https://github.com/armbian/build

You are using Orange Pi provided doc, but using Armbian and you expect the one to work with the other? Either use Armbian provided docs or use Orange Pi provided builds. Mixing the two is going to be a problem. I will advise that Orange Pi is not very well supported by Armbian due to the manufacturers unwillingness to work with Armbian.

Let's start with basic information. What build are you using? What manual are you following? Did you first try running from an SD card?

@ebin-dev Thanks for the explanation (i failed to notice that you were setting io_is_busy to a different value). I know that you are still working to stabilize this board. But at the end of this process, it should be possible to submit a PR to incorporate your settings into the base builds. Thus I'm looking for things that will make that difficult. I just added a comment to PR6507 stating that the way io_is_busy is now set doesn't allow it to be overridden if needed.

FYI. This is now included in armbian-hardware-optimization as of the 24.05 release of Armbian. which I no you are disabling. Why are you disabling armbian-hardware-optimization? What is it doing that is conflicting with your settings?

@cad 435 No you aren't really missing anything. In the stable channel, kernel .debs generally only get pushed out every three months when a new stable release is put out (24.05 will be out the end of this month for example). If you want to get regular updates of kernels you need to switch to the nightly builds repository in armbian-config. Right now there is no in between.

That board is no longer a valid armbian board. It is EOS status (end of support). So there is no Armbian support and no community support for that board.

If you are running the community build you should be able to use the standard Armbian way: armbian-config

I thought you might be interested in the following PRs: https://github.com/armbian/build/pull/6120 https://github.com/armbian/build/pull/6507 In Armbian 24.02 the default governor was changed to schedutil and recently it was changed back to ondemand. There is a lot of discussion about why in these two PRs.