SteeMan

There are no instructions to do this because it isn't supported and it is really, really, really hard because there are many, many, many dependencies across many different repositories all changing over time. While you may be able to get something to work in some cases, you have to deal with tracking down build errors and figure out what changed and what to roll that source back to.

From the screenshot you included I can determine the following: 1) This is a repurposed TV Box type device since it is running the rk3318-box build. (Note Armbian does not support TV Boxes, these are all community supported) 2) You are running a build from May of 2022 (over three years old) 3) As it says: No end-user support: built from trunk (which means this isn't any sort of official armbian build) For support you really need to go to the company that you bought this from

You would also need to rollback all the patches that armbian applies to the point in time that Armbian built with that particular kernel version. And likely all the outside repositories that Armbian pulls in that have source code for the various drivers and other code that is also built into the kernel.

moved to the Pine A64 forum.

The rk322x is a 32bit CPU, so it can't run 64bit code

Generally debugging is done through the UART connector: https://debug.armbian.de/

I would first suggest that you read this post: That may give you lots of reasons why you shouldn't depending on what your goals are. Installing armbian on a TV Box depends on the TV Box. Each CPU has differing levels of support (from none to fairly well supported in mainline linux). And then given there are hundreds of different TV Boxes, each will have different sets of working/non-working features depending on a variety of factors. As far as supporting a USB audio device, it shouldn't be any different than support for the device on any other linux platform/distribution. On Armbian you may need to install the linux-firmware-full package to get the driver support as by default Armbian ships with a slimed down set of firmware support.

This would be very very hard. Would likely take years and would likely never achieve full functionality. If you have access to the source code for the firmware that comes on the device you would have a chance.

Armbian doesn't support TV Boxes. Read the following to understand the status of Armbian and TV Boxes:

Since this issue is well over a year old, I'm not sure where you stand with this. Are you still looking to get a fix? If so, answering all of the questions asked would be helpful. When you say "broke again" what do you mean by broke? Apparently the box is running and you can update it as you continue to update it per the message above saying you have upgraded to 6.12.32. Have you tried a fresh image installed on a new SD card to see if that works (vs. your upgraded system)?

Technically a DTS is specific to a kernel version. As changes happen to the kernel apis, those need to be reflected in the DTS's. So they DTB and kernel image are always built and shipped together. Now in practice changes that impact the DTS aren't common, so you can usually use DTS's accross kernel versions. However in this case, I'm assuming that when you refer to 6.1 that is a vendor kernel, and 6.10 or greater would be mainline kernel. Now these are two very different code bases. A vendor kernel is whatever the board/cpu vendor hacked together to get a kernel running on their hardware. Often these are more android kernel based. When features finally get rolled into mainline, their implementation is often completely different. Thus one can't share a DTS between a vendor kernel and a mainline kernel. But often you can use the vendor DTS to gather information about what needs to be implemented in the mainline DTS.

What build of armbian are you using? Please provide the exact steps you are having problems with, your description of the problem is not clear.

Moved to Community supported forum as this isn't a standard support board.

Yes exactly

@KrzyPacu The Amlogic TV Box builds use extlinux.conf. So you should add your overlay info in that file (/boot/extlinux/extlinux.conf). I believe the syntax for extlinux is: OVERLAYS /dtb/amlogic/overlay/... (I'd recommend placing it just below the FDT line) (Note: I've never tried to load an overlay through extlinux, but have been intending to try it some day. Let us know how it goes)