SteeMan

@Nandhu Thanks for the info. I need to take my box apart to compare. But I am heading out for a week of vacation, so I might not get to that until I get back in early April.

I just downloaded the same image and it is fine. How are you burning the image to your sd card? Since the image is compressed not all burning tools can handle compressed images.

I don't have this box, I can only point you to the latest builds: https://forum.armbian.com/topic/17106-installation-instructions-for-tv-boxes-with-amlogic-cpus https://forum.armbian.com/topic/16976-status-of-armbian-on-tv-boxes-please-read-first

Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed. At a minimum what build have you installed?

@tnt Two things I'll note. Unless you are only testing, you should use the stable builds (not the unstable development community builds) located here: https://redirect.armbian.com/aml-s9xx-box/archive/ Second, in moving to the new armbian build framework post 23.02 release, there is an incompatible change in how the kernel .deb package is installed. After this change there no longer is a /boot/uImage file created. So the /boot/extlinux/extlinux.conf file will need to be changed if you upgrade to a later built kernel changing from uImage to Image. I don't know if this might be what you are running into, or some other instability in the development/unstable tree.

@joula You are not using Armbian. The location you are downloading from is a fork of armbian. They use the Armbian name without permission. We can't help you in these forums because we don't know what code you are using, you need to direct your questions to the location you downloaded your code from. Those developers do not participate in these forums, nor support armbian development.

Can you include pictures of the top and bottom of your box and then open the case and take pictures of the top and bottom of the board (with good enough resolution to see the markings on the board as well as on the chips). My boxes work fine, so I want to see if your box as different hardware. TV box manufacturers often make hardware changes but still call it by the same name.

What exact builds are you downloading and from where? The file names you mention above don't correspond to builds I am familiar with.

I no longer experience this problem on any of the boxes I own in recent kernels (i.e. kernels 6.x). So I can't troubleshoot.

Your first post says you are using the p281 dtb (which is what I use), but the screen shots show you are using the tx3-mini dtb. You need to fix your extlinux.conf

I have two x96 mini's and don't have any issues. Could you screen capture the boot process before it starts loading the kernel? Also pictures of your board would be helpful to compare to mine.

Yes through a patch just like you modified u-boot with the config patch jock provided you. You should create a patch that makes the changes to u-boot that you want.

Try a build that isn't over two years old:

@ArmeBian Google play is an android feature. Armbian is linux not android. You are asking your question in the wrong place. You should either be asking in an android forum somewhere, or ask the manufacturer for their plans to support the hardware you purchased with updates.

Moved post to correct forum.

@vitor Have you paid for support? Armbian is composed of volunteers who donate their time. If no volunteer desires to work on any particular board/feature/bug, no one is getting paid to be told to add such board/feature/bug. This is open source so anyone can go in and make changes/fixes/improvements and then hopefully submit them back for others to benefit from. First and foremost Armbian provides a place (forums, frameworks, source code) for anyone to join the volunteer community and help support the wide variety of boards that are out there.

This is good to know. I'm only starting to upgrade to Win11, so I haven't run into this yet. But I can pass this advice on to others.

It would be helpful to include which options in armbian-install you are running to create the problem

@samaritan You do understand that the Odroid C1 board is listed as EOS (End of support). No one is working to maintain that board anymore and thus over time more and more will cease to work on that board.

@samaritan This is an Armbian forum, not a dietpi forum. Please direct your posts elsewhere for dietpi issues.

@wyim Have you read: It may or may not work. For example the installs for coreelec and armbian are incompatible.

That file is located in the armbian build system at: packages/bsp/common/etc/X11/xorg.conf.d/01-armbian-defaults.conf running a ./compile.sh will rebuild the deb's

Either use armbian-config to switch to nightly (unstable) builds, or build images yourself via the build framework. But either way in doing so you would be switching from a stable build to unstable/under development builds. Also at this moment do to significant changes in build framework introduced after the release of 23.02, no nightly builds are being produced as issues are being sorted out.

https://docs.armbian.com/Developer-Guide_User-Configurations/#user-provided-patches