SteeMan

That is true that there are images that target server vs. desktop. But they share the same kernel. I find what you are working on an interesting idea. Good luck getting it working.

Ultimately, once you have this working, you should submit a PR and justify the inclusion of this feature with details on the pros and cons.

How much size does it add? Remember there are a wide variety of boards supported some with limited storage and ram.

@naceur abdelkader Your post has nothing to do with Armbian. Please find a more appropriate site to ask your question. This site is for Armbian linux.

Have you tried all of the gxm dtb files? Per the instructions (https://forum.armbian.com/topic/33676-installation-instructions-for-tv-boxes-with-amlogic-cpus)

In the world of TV boxes "identical looking" means nothing, as manufacturers build each batch with the lowest cost components available at the time. There are many cases where identical looking boxes even contain different cpus ( ie amlogic vs rockchip). My recommendation would be first to verify the markings on the boards (there is usually some sort of board identifying text on the board)to really see if they are the same under the hood.

You aren't using Armbian. The balbes150 builds were a fork of Armbian and know one here would know what sources they were built with. So this question is really off topic for Armbian.

Note that I believe Armbian will reset the max CPU frequency on boot. There is code in /usr/lib/armbian/armbian-hardware-optimization that uses the values defined in /etc/default/cpufrequtils to initialize the governor, min and max frequencies at boot time. So even though cpufrequtils is no longer an installed set of tools, Armbian is still doing some of the same work based on its old configuration files. So assuming this works as it used to, all you should need to do is set the max speed you want in /etc/default/cpufrequtils

There aren't any Armbian builds for 5.15 is what I said. And it would be a lot of work to make that happen. Why do you want 5.15? How do you know that would work, when 6.12 doesn't?

There are no Armbian builds that old, in fact Amlogic TV boxes weren't incorporated into Armbian until later Linux kernels. What you must have been using would most likely have been a fork of Armbian. What you are asking for isnt possible in the way you are asking. You essentially want Armbian ported to the 5.15 Linux kernels, which is a huge project. You would be better served but spending a month or so figuring out why current kernels don't work for you and fixing that.

Moved to proper forum

Moved to off-topic as this isn't Armbian related

What you now need to capture is the initial boot loader messages, what you are showing here look to me to be messages from a booted android linux kernel

I don't know what pins you are connecting to on the board as your video doesn't show that. But if I had to guess the three pads labeled gnd,rx,tx just above what you are connecting to is what you want to be connecting to.

poweroff doesn't work on any of my boxes either. Does reboot work correctly for you? It does on my boxes, and I usually issue a reboot and then time a power disconnect when the drives have spun down and before they restart.

Only a guess, but the first thing I would look at is how this is connected to your t box as it seems to not be connecting correctly. Maybe some pictures of your connection points?

Why are you expecting this to work?

Moved to amlogic TV ox forum

You would just burn your downloaded image file to any USB storage, just like you would to an SD card (i.e. plug the USB storage into another device and burn the image to the storage)

Please read the FAQ and installation instructions linked on the download page. https://www.armbian.com/amlogic-s9xx-tv-box/

You are not using Armbian. Ophub is a fork of Armbian. They do not contribute to Armbian development nor do they participate in these forums. You need to go to ophub to ask this question, as no one here can help you.

Moved to userspace forum

As long as you don't install Armbian to your emmc, you should be able to still boot android by removing the SD and/or usb drives. Once you install to emmc you will overwrite the android installation

If you want to understand what should be happening under a normal installation: Installing "multiboot" (i.e. pressing the hidden reset button while powering the device) runs the script aml_autoscript That script sets some uboot environment variables that are used by subsequent boots The boot process for these boxes is to use the original android uboot to intiialize the device and then hand off the boot process to the u-boot.ext from armbian. This is done in the script s905_autoscript (or emmc_autoscript). Which then essentially just runs (for emmc): if fatload mmc 1 0x1000000 u-boot.ext; then go 0x1000000; fi; (or "mmc 0" for SD card). The chainloaded u-boot then boots via the information in the extlinux/extlinux.conf file.

Current Armbian uses extlinux to load, not uboot scripts. I can't help you unless you are willing to follow my suggestions, which you seem to not want to do.