SteeMan

I can't explain what you are seeing, as everything appears in order. The only thing I'm going to suggest as a long shot, is that you are getting pointed to a mirror that for some reason isn't up to date (which shouldn't be the case). Since I don't know where you are located in the world, you could try to update your armbian.list file to point explicitly to a different mirror (list is available here: https://github.com/armbian/mirror) When I look at the mirror I get resolved to, I see the 24.2.1 packages in the bullseye repository. I don't understand why apt isn't finding them for you.

There are many posts on similar topics in the forums. The usual work around is to force the resolution via a kernel boot parameter. Search the forums for other such discussions.

I don't have this board personally, so I can only make educated guesses. The two things that caught my eye were the text "Hit any" which I assume should say Hit any key (it seems like some of the output is garbled). Such a message often has a timeout associated with it so you have some time to use the keyboard. The other thing I noticed is that your build is using uboot 2022.01, where current code is using uboot 2024.01. So you might want to build a current version and see if the newer uboot has any difference in behavior.

They aren't officially supported, but there are many TV boxes that are Community Maintained and available on the Armbian download page. No need to remove the binaries, your warnings are good enough.

Armbian does not support upgrades from one userspace to another (i.e Focal to jammy in your case). The recommendation is to reinstall and reapply your changes. Upgrades can sometimes work, but they are not tested nor supported.

Please do not promote forks of Armbian on these forums. If you what to help Armbian, please submit PRs and contribute code that makes Armbian better. It doesn't help to have yet another fork of stuff out there that never gets contributed back. Your warning about using external builds applies equally well to external git sources. No one should trust this unless they inspect all the changes you have made from genuine Armbian. User be warned.

I can't explain what you are seeing. Are the contents of /etc/apt/sources.list.d/armbian.list correct? Have you tried to use armbian-config to upgrade the kernel?

It means the /boot folder. There should be two partitions on the SD card, one formated as a fat filesystem and the other as an ext2 filesystem.

Be more specific? What packages are you looking for and what is your use case? I.e. why do you need them? Because without some really compelling reason, you should be upgrading to something supported by both Armbian for the Armbian parts and Debian or Ubuntu for those parts.

No there is not. But there hasn't been anything new released by Armbian for focal for a very long time.

Yes armbian-config has a section on selecting kernel versions as well as freezing kernel updates.

Havnig siad the above, I have noticed on other devices running the Armbian builds, that there can be issues with higher capacity sd cards. There are a lot of low quality cheap SD cards out there. I would suggest either investing in a high quality SD card or a lower capacity sd card.

Since you are not using Armbian but a fork of Armbian you need to direct your questions to their support channels. The authors of that fork do not support Armbian, they do not contribute to its development, nor do they participate in these forums.

@Antonio Ramos But the TX3 is based on a completely different CPU (AMlogix s905x3) than the TX1 (alwinner h313). So yes there is some community support behind the s905x cpu based boxes. But not currently any behind alwinner based boxes.

@Antonio Ramos There is no one I am aware of working on TV box support on allwinner CPUs. TV boxes are community supported. That means people like you need to step in and do the work to make what you are requesting happen.

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

@chiefwigms As this board is in status community maintained, no Armbian resources are assigned to work on or support this board. Support/maintenance comes from the community. That means people like you submitting PRs to maintain/improve functionality. Without active community participation the board will langish and eventually be moved to end of support/end of life status.

@chiefwigms please submit a PR for this to get included into Armbian

@Adam Bresnay These forums are for Armbian. You would need to contact dietpi if you are not running Armbian. We can't help with dietpi issues.

@Adam Bresnay Run armbian-config and there is a submenu for selecting kernel versions.

@Sab44 please submit a PR with this change

Moved post to Libre Renegade forum

Do you have the boot log from the uart port? If so please post, if not I'd suggest you capture the boot console messages to see which step of the boot process is taking the time.

This board isn't a supported by Armbian. Moved to Community Supported/Unmaintained section of forums.

The contents of those packages are not isolated to /boot. For example the linux-image packages installes the kernel modules in /usr/lib/modules, and linux-u-boot puts binary information on the boot disk that isn't in the file system (it is on the raw disk). So it isn't as simple as copying a few files to /boot. But without knowing if this is a kernel issue or a uboot issue it is difficult to guess where to start.