SteeMan

Actually the forums are what you want to follow. The forums are the board issue logging system. Github issues are only for build system issues. If the r2s and r2s plus are boards you can help with (they are community maintained and don't have any Armbian staff support). You can fix issues on them and submit PRs to improve them.

@Thom Debian Buster (aka Debian 10) was EOL 2022-09-10 (and it ends its extended support life 2024-06-30). Armbian hasn't supported Buster with updates for a long time and recently set its status to EOL. You can ignore the error message, as there would be no updates to get from Armbian anyway. You need to move to a more current supported distribution.

@Caio Lima Viana If you post pictures of the front and back of your board, someone on here may be able to identify the uart connection points

@tj13You get details by hooking up a USB uart adapter and reading the serial console output of the boot process.

My suggestion since I assume you don't have an armbianmonitor output from before your upgrade, would be to use armbian-config and go back to a 6.1 kernel and see if it is the kernel that is causing the difference. If so then provide an armbianmonitor output with the old kernel and look at the memory info in the output to see where the difference is.

@lululombard I think this whole discussion needs to be moved to a new thread as this thread is about the Banana PI. Can you state what you are trying to accomplish? I can then move these posts to a new thread named according to what you are trying to do. It seems as if you are just trying to use 3d accelleration (which should be present for rk3399 out of the box on recent kernels). I think you may be following very old instructions that are no longer relevant. So again state what you are trying to accomplish with your RockPro64.

@lululombard So the historic images for the RockPro64 still exist in the archives. So I was going to suggest that you could extract the kernel from the images and manually apply the kernel. But in looking at the images, and your request above, it looks like the images contain the rockchip64 kernel and you are wanting to use the media kernel. I'm not sure why that is, as I'm not aware of the media kernel every being supported for this board. But you could take that strategy of finding an historic image for a board that supported the media kernel, and copy over the relevant files (/boot/dtb, /boot/Image, /boot/uinitrd and /lib/modules/<kernel>)

@lululombard There haven't been any updates coming from Armbian on buster for a while now. So just remove the repository or ignore the messages.

The Armbian repository has moved focal to EOL. That only means you will no longer receive any updates for the Armbian specific packages (like kernel, uboot, etc). Ubuntu still supports Focal for a couple more months so you will still receive any package updates that Ubuntu releases for userspace packages. But in a couple of months that will end as well. So you should be planning an upgrade to something more current as focal is now 4 years old.

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

@KanexMarcus I only have two suggestions: Try different SD cards (especially a lower capacity card if you are using a high capacity sd card. Try other dtb files. I don't have that box so can't help beyond generic suggestions.

How many times do I have to say, it isn't possible to do with Armbian builds. Armbian does not have a uboot for your TV Box. So there is no way for you to boot from something other than your emmc unless you have a uboot built for your box. And since Armbian doesn't produce such code, we can't help you here.

There is no current TV Box work being done to support s805 nor has there been for years.

https://docs.armbian.com/Developer-Guide_Welcome https://docs.armbian.com/Process_Contribute

There are no plans for Armbian to officially support this board. If community members step up to the task, there may a a community maintained version specific to that board. But currently people report success with the zero3 community maintained build working on the zero2w.

What build are/were you running? As I said multiple times now, what you want isn't possible with Armbian aml-s9xx-box builds. Those builds do not contain a u-boot that works to boot your TV Box. To accomplish what you want, you would need to port a u-boot to your specific TV Box hardware. Each TV box is different and needs a different u-boot. That is the reason the Armbian aml-s9xx-box build uses the TV Boxes native u-boot on emmc to start the boot process, so that one image can be used for multiple TV Boxes that use the s905x CPU.

What do you want to know about the s805?

Not possible. As I said the TV box builds use the EMMC uboot to start the boot process.

I'm guessing since you reposted in the TV box forum, that you have a TV box not an SBC. If thos is a TV box running an Armbian build then the answer is no. The Armbian TV box builds use the uboot from EMMC to start the boot process, no EMMC no boot. For other amlogic SBCs they use the uboot from the SD card, but not so with TV boxes.

Please don't double post

Armbian doesn't have a process to make regular releases to kernels in the stable channel.

It looks like that box uses the amlogic s802 cpu. That is the old 32bit cpu from amlogic. No work has been done with that cpu for years. The current builds only support the s905 64bit cpu family.

In looking at beta.armbian.com/content.html base-files appears to be missing from the bullseye, mantic and sid repositories. It is present in bookworm, jammy, noble and trixie.

Have you tried looking at this info?

13.03 image of what? That is how Armbian works. There is not option to change that behavior.