SteeMan

I should ask, what image are you working with?

It is in the fat32 partition on the sd card. The issue seems to be that that partition is created in such a way that windows can't see it, even though it is a windows formatted partition.

Please read this first:

moved to the correct forum

This is not an Armbian build. Please do not post information here that isn't about 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. Content related to their work shoud be discussed in their forums not here.

Do you have a non-windows machine to use? There may be an incompatibility with the partition type and windows.

If your emmc isn't working you won't be able to run the aml-s9xx-tvbox Armbian builds. Those builds use the original boxes uboot on emmc to boot from. So you need an intact working emmc with the original android uboot working.

FYI. Using armbian-config will limit you to compatible kernels for your current distribution.

You didn't answer the question from Werner above. What are you trying to do? meson (i.e. Amlogic cpus) and sunxi (i.e. Alwinner cpus) are completely different kernels designed for different CPU families from different CPU manufacturers. You can only use the kernel built for your CPU.

Replacing /boot is not the same. You also have to make sure that the contents of the kernel modules are present for the kernel you are loading (i.e. /lib/modules)

Moved post to proper forum

This board is not supported by Armbian. It is a Community Maintained board. Which means that the Armbian infrastructure is used to build automated untested builds and make them available for use. Thus that message.

The instructions don't say install, they say run. Running from SD card may/will change the boot environment on the mmc and prevent armbian from booting. If you have ever *run* another distribution on the box armbian may not run. You need to reinstall the original android firmware to reset things back to what armbian expects.

Read the part about having run *any* other distribution on your box before trying the armbian builds.

While normally we discourage references to ophub as they are a fork of Armbian but continue to use the Armbian name without permission for their fork. They also don't contribute back to Armbian nor do they participate in these forums, I think your post is helpful. It would really be nice if someone were to dig into this and submit a PR back to Armbian to bring the support into the base code that is maintained here.

Moved to the correct forum (community support). This is not a supported board. Adjusted the tag to reflect the correct board.

Change title to reflect the real question and moved to the appropriate forum

But the answer to your followup question is: config/sources/families/include/sunxi64_common.inc

Why did you title this thread Raspbian if this isn't about a rpi4 or rpi5 device? Maybe you need to explain a bit more about what you are trying to do. The Armbian builds for RPI devices pretty much use the standard raspbian sources. But the sunxi builds have like a hundred patches applied and that is a lot of work to port all those patches.

If you are pulling the armbian build framework from git and following the armbian build instructions, then.. The file you would want to change would be: ./config/sources/families/bcm2711.conf (adjust the appropriate section 'current' or 'edge' for the specific version you are looking to build) But note then you would also need to port the armbian patches for that kernel version, unless you are OK without having the armbian patches applied to your kernel. The armbian patches are located: ./patch/kernel/archive/bcm2711*

moved post to correct forum

The short answer is from your first post in this thread: These are mostly community supported boards. So it is up to volunteers in the community to add and test features, even ones like this that you consider basic. However, I think I would add the following comment. Based on another comment you made in the first post: That statement I think would have been correct probably 5 years ago. Today, not as much. I would venture to say that today with the latest generation of CPUs that most users are looking to SBCs as desktop replacement devices. So features like video acceleration, etc. are what we see the most requests for. So features like these basic lower level SPI/I2C etc get pushed down the priority list for those that are volunteering their time (unless they have that particular need themselves).

https://docs.armbian.com/Process_Contribute

@BladeCoder The official way to switch kernel versions is via armbian-config

It depends on which repository you are pointing to. But in general if you are pointing to the stable repository (apt.armbian.com) then you would see releases as they flow out to the stable channel. If you are pointing to the nightly rolling release repository (beta.armbian.com) then you get nightly rolling release builds. (look at what repository you are using in /etc/apt/sources.list.d/armbian.list) The version you are reporting for armbian-config is a nightly version (25.2.-trunk is a rolling release).