SteeMan

What are the contents of your /etc/apt/sources.list.d/armbian.list file?

This board is not supported by Armbian. It has no maintainer. It is Community Maintained, which means that the Armbian infrastructure is used to produce automated but untested builds weekly. Moved topic to the Community Maintained sub forum.

Armbian doesn't regularly release updated kernels to the stable channel, except once every three months with new releases. If you switch to the nightly/beta channel in Armbian-config you should be able to access more current kernels at anytime.

Minimal really means minimal. So it doesn't come installed with even basic things like Armbian-config. The minimal install is an 'expert' type build, use only if you know what you are doing and are willing to install a lot of basic things to get your system working the way you want. The standard server builds are likely what you are looking for.

That confirms most likely that the problem was more recently introduced. If you have the time to do some testing to maybe narrow down where it might have stopped working that would be useful information for the community. So could you rest the current s905x-s912 uboot bin in your working setup to see if it was a uboot change that is the problem? And then could you install newer kernels through Armbian-config to pinpoint which kernel breaks things?

@M782 It depends on what you mean by official. Armbian does not support TV Boxes. There are a handful of people out there that tries to provide some support using the armbian infrastructure as a Community Maintained image. https://forum.armbian.com/topic/16976-status-of-armbian-on-tv-boxes-please-read-first https://www.armbian.com/amlogic-s9xx-tv-box If you want to stick with what you have installed then do a web search on 'ophub'

@rafman Since these are Armbian forums, please don't post links to other distributions in here.

Board is not a supported Armbian SBC, moved to the Community Maintained forum section and reset the board tag to reflect the correct board.

@ivanstein Why not just submit a PR to Armbian for Armbian to include the changes you need? That seems like less work for you in the long term.

Edited subject to include board name

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

My recent experience is that current kernels are very picky about the type/quality of the SD card. So try different SD cards. That has solved the issue for me when I have run into this issue recently.

@lucksufe Where did you get a dtb for your box? The reason I ask is if you are using an android dtb it won't work with mainline linux.

You can use any method that will recognize an ext4 linux file system. Windows does not by default. But if you installed WSL then I think you can, but I don't use windows.

@lucksufe Are you using Armbian or ophub images? If the later then you need to ask your build question in the ophub pages as they are an unrelated fork of Armbian. Given what you have said above, you are following instructions for Amlogic TV boxes which have nothing to do with your rockchip based box. Do not follow those instructions. Why are you expecting the panther-x2 image to work on your box? Each box is different and generally needs an image specific to that hardware. If you are using an Armbian image, then @maka stated you should be able to write the image to an SD card, put that card into a linux machine, edit the files you are talking about and then move that SD card to your box and boot.

@Igor But from my understanding that statement (audio not working) is correct for the current release images (24.5.x) but no longer true for the nightly's and the forth coming 24.8 images.

Go to the community images download page to find the weekly built images.

Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.

That is the latest stable build, not the latest release. Go to the very bottom of the downloads page for the nightly/rolling releases for the latest.

@ioncube I think you mean legacy 5.10 (not 5.1). The code to build legacy 5.10 is still there (https://github.com/armbian/build/blob/b8dbe607e59a9eb23c70f129b60e2df2b08cdb01/config/sources/families/rk35xx.conf#L19-L27) But as igor commented above: So it is unmaintained and may no longer build. To use the legacy branch you need to specify it on the command line: BRANCH=legacy

Moved post to Raspberry Pi sub forum and added the Rpi5 tag.

Moved post to Community Maintained Alwinner

Moved post to the Kahdas Vim1s forum

Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.

Have you tried the standard (not minimal) image? Where the other environments also minimal images that worked? Specific versions of images would be helpful info.