SteeMan

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.

Technically the user space you are using is Debian Stretch. Armbian provides the boot environment and linux kernel, the user space comes from either Debian or Ubuntu (depending on the version you choose to install). From the Debian release page: : "Debian 9.13 was released July 18th, 2020. Debian 9.0 was initially released on June 17th, 2017. The release included many major changes, described in our press release and the Release Notes. Debian 9 (stretch) has been superseded by Debian 10 (buster). Security updates have been discontinued as of July 6th, 2020." So Debian stretch stopped being supported over three years ago. Armbian generally follows similar time lines to the underlying support of the Debian or Ubuntu user spaces. The message you are getting is because Armbian recently cleaned up the support status of these older releases. So even though no updates have been created for the Armbian parts for likely years, you didn't have any message that you weren't getting any updates until the recent change. The reality is that you need to upgrade your system. You haven't received any security updates for years.

@fever_wits I just want to point out if you don't already know, the board you have isn't supported by Armbian. It is community maintained. That means there is no one specifically that has responsibility for the board. It is up to people who read these forums to respond if they have an interest. So don't expect any specific response in any specific time frame. Having said that, this is the correct place to post questions, observations, and hopefully solutions to issues with your board. Armbian provides community builds as a service but doesn't have the resources to test or in anyway to support them. So fixes/changes happen only as community members contribute them via PRs to armbian. If no one contributes, over time the quality of a board degrades and when it stops building it then gets removed from armbian all together.

The script that displays that info is: /etc/update-motd.d/10-armbian-header

This is certainly possible. The level of difficulty depends on exactly what you mean by 'using a different kernel'. Start with https://docs.armbian.com/Developer-Guide_Welcome The basic Armbian kernel build process is to start with a kernel git tree, apply a bunch of patches that are missing from said tree (usually patches that haven't yet made it to mainline), combine with a kernel specific config file and build the resulting kernel. So depending on what the differences are between your 'different kernel' and what Armbian builds, you could insert your different kernel into any/all of those areas (i.e. you could add the missing patches that other kernel has, you could fix/change the kernel config to add/removed features, or you could use an entirely different git kernel source tree, or a combination of these three). The key would be to figure out what is different between the Armbian and other kernel that is relevant for your board. Ideally this could be done as a PR to Armbian to add better support for that board into Armbian.