SteeMan

There are hundreds of different TV boxes. No one likely has tried on those specific boxes. So I would say try from an SD card first to see if the box works at all, and note the warning in the install instructions that installing to emmc has risks (on any amlogic TV box).

No I don't. If they are not here https://armbian.tnahosting.net/archive/aml-s9xx-box/archive then they are no longer stored by Armbian. Have you tried a current build?

https://forum.armbian.com/topic/16976-status-of-armbian-on-tv-boxes-please-read-first Note the comments in the above link that these boxes are not suitable for use as a desktop replacement. https://forum.armbian.com/topic/33676-installation-instructions-for-tv-boxes-with-amlogic-cpus Note the comment in the install instructions that if you have installed any other build, you will not be able to use the armbian builds without an android firmware restore.

Can you run: apt list --installed| grep armbian apt list --installed| grep linux

So yes the emmc isn't detected (there is no mmcblk1). Are you sure you have emmc on the box? (I have for example some TX3 boxes that have old style nand instead of emmc and mainline linux doesn't support nand. TV Box manufacturers will cut costs in anyway possible and nand is cheaper than emmc) You would need open the box and inspect what physical chips are installed. Since I don't have your box, there is little I can do to debug this. Have you looked at the full log of the boot process to look for any indication of issues reported during the boot? (You would need to find the debug serial console pins on the mother board and hook up a usb serial reader to capture the boot messages) (some of this information goes to HDMI, but some gets output before HDMI is initialized).

That isn't a message produced by the install-aml.sh script. What does lsblk output?

@Ian Coelho How about some basic information first. What build are you running? What dtb are you using? What dtbs have you tried? How are you attempting to install to emmc?

Not right at all. Every SBC that has different hardware configuration requires a different dtb file that describes the hardware to the Linux kernel. So every SBC needs it's own build ( sometimes dtb overlays can be used to shortcut this). And similar issues can exist at the uboot level too.

So this dtb is not part of the image? Where are you placing the custom dtb? Do not put it in the dtb directory as that entire directory is removed and replaced on a kernel update. Put it in /boot or a custom subdirectory and adjust the extlinux file accordingly.

Also, what dtb are you using and what uboot.bin file?

What kernel version are you successfully running with? What version is apt trying to upgrade to? Are you running from SD card? Is this a new install of 24.11.0-trunk that you are then immediately trying to apt upgrade?

As Igor says, I'm assuming you have a separate /boot partition that is FAT separate from your / root partition. In that case, this would be a normal 'warning' message for a system that has a FAT /boot partition. All of my devices fall in that category (with a FAT /boot partition) and I see this message for every update.

@shubkin Here are my recommendations, fist try to get plain Armbian to run on your box. (https://www.armbian.com/amlogic-s9xx-tv-box/) Then if that works, follow the DIY instructions on the first post to make your own build with the framework installed (ENABLE_EXTENSIONS="ha) and then try running that build. My personal Home Assistant server is running on a TX3-Mini box which is Amlogic S905w, but I just run the standard HA docker build as that server setup predates this Armbian extension. So it certainly is possibly to run HA on a box like you have (given all the caviates mentioned in the Read First post Igor Link to above)

Moved to userspace sub forum. Removed incorrect tag.

That unallocated space was your boot loader.

You are confusing what is Armbian and what is upstream Ubuntu. The release upgrade comes from the Ubuntu repositories not Armbian. Armbian is only providing a few packages (important ones like the linux kernel) and everything else comes directly from upstream repositories. Ubuntu Noble didn't support release upgrades until the .1 release came out in the last few days.

I want to clarify this statement. Armbian does not support this box. This is a Community Maintained box, which means it uses the Armbian infrastructure to produce automated weekly builds. The effort to maintain and support this box comes from the community not from Armbian resources. (https://docs.armbian.com/User-Guide_Board-Support-Rules)

I want to clarify this statement. Armbian does not support this box. This is a Community Maintained box, which means it uses the Armbian infrastructure to produce automated weekly builds. The effort to maintain and support this box comes from the community not from Armbian resources. (https://docs.armbian.com/User-Guide_Board-Support-Rules)

The default is 'root' and '1234'

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'