SteeMan

You would want to add: BUILD_MINIMAL=yes (the default is the non-minimal server build)

The instructions on above (under DIY) should be clearer to explain that. When I looked at this earlier, I was guessing that is what the instructions assumed you needed to do (download that referenced file). Edited the above instructions to clarify.

What you are describing sounds like standard gnome desktop behavior. I don't think all desktops have that same default behavior. You said above you installed xfce desktop not gnome.

Moved to the proper sub forum for a non supported device The OPi5 Pro is not a supported board. It is currently wip - work in process status. Therefore it has no support forum and should be talked about here under staging/community maintained.

These forums are for Armbian not for the discussion of other distributions. It would be more appropriate to post this in a forum dedicated to MiniArch.

You have the 24.5.1 version of kernel headers, but... of the kernel. Thus your headers and kernel don't match. I doubt you will find a 6.6.36 version of the headers, so either down grade your kernel to the version that matches your headers, or use the Armbian build framework to build your own .deb files of both the kernel and headers together so you have a matching version.

Moved post the the appropriate forum.

I deleted your other post as it is just a duplicate of this. Please take the time to research. There is a topic in the fourms for your type of box. That is where your should be posting, and before you post you should read what has already been posted to see if others have already run into what you are seeing. Don't waste other peoples time until you have used the resources available to you.

I'd recommend you post in the master thread for the rk3318 TV boxes in this sub forum.

TV boxes are not supported by Armbian. They are automated builds that are untested. These are 'Community Maintained' which means there is no official maintainer but anyone in the community can submit fixes/changes. The forums are the method of discussing issues.

This is Community Maintained software (not supported by Armbian). So please submit a PR if you would like to see changes. My experience is that ophub just ships a lot of binary code from unknown origins (the dtb is a binary file, you would need to track down the source file (.dts) to submit here as we don't include binary files from unknown origins but build things from source). Also note that the dtb file doesn't need to be inside the /boot/dtb/amlogic directory. To avoid your issue just put it in /boot (and adjust the extlinux.conf accordingly).

So have you tried a current build? Instead of an update from an older build? There is a thread in this forum for this type of box that you should review and likely post questions there.

Note that Armbian doesn't support TV boxes. That.means all Armbian does is provide automated builds with no testing which are created weekly. These boxes are 'Community Maintained' which means support is up to members of the community i.e users like you.

Moved to the correct forum

Note that there are no "official" images for this board. Armbian doesn't support this board. This board is "Community Maintained". Which means that someone at some time had it working and submitted it to the armbian build framework and it gets built weekly automatically. No support or testing is done by Armbian on this. As long as it builds without error it can exist as a Community Maintained board. But note that most community maintained boards have no one actively working with them. Looking at the forum activity on this board, it doesn't seem like much in the last 9 months or so.

That isn't how the armbian build system works. Armbian is basically the u-boot and linux kernel (which are built from sources in the framework) plus an ubuntu/debian userspace. The build process builds the u-boot and kernel packages and then installs them along with the user space packages from ubuntu or debian based on what distribution you are using. There isn't a reason to build other things as they are just installed from repositories. So what you probably want to do is build your custom .deb in your own environment and then install it through the armbian build.

User space upgrades are not supported nor tested. However I've upgraded recently a number of boxes from Focal to Jammy. So generally they do work. You are just using the standard Ubuntu upgrade mechanisms to do this (i.e do-release-upgrade). But note that Ubuntu doesn't support the upgrade from Jammy to Noble yet itself. That support comes with 24.04.1 to be released this summer. I'm waiting for that to do my own upgrades to Noble.

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

How armbian-release is created and maintained is outside my area of knowledge. @Igor Is it as simple as copying armbian-image-release to armbian-release to replace the missing file?

armbian-config is a shell script so it is fairly easy to debug and modify with echo statements to print out what is going on. There is currently no log produced. So if you have decent shell scripting skills debugging shouldn't be too hard.

By default the community builds point to the 'beta' channel, otherwise known as 'nightly' or rolling releases, which have updates constantly. If you want something more stable, use armbian-config to switch to the stable channel, and then you should only get updates quarterly.

None of the builds you are dealing with are Armbian builds. They are all armbian forks and are really not appropriate for discussing in the Armbian forums as it leads to confusion on what is and isn't Armbian. So if you do continue this discussion here, please make it clear that you are talking about non-armbian builds.

@threpwood Since I'm the current maintainer of the Armbian amlogic TV Box builds I may be biased in my response. I will first state the official Armbian position which is that TV Boxes are crap and not supported. (This is often the case and you may find that you purchase something really cheap and it doesn't work with Armbian at all - this can be for any number of reasons, from TV boxes generally have the cheapest components, often two 'identical' boxes will have completely different components, etc). But, to address your original question, between the aml s905x3 and rk3566 I would recommend that you go with s905x3. That CPU is now many years old, which means its support within mainline linux is pretty mature. Whereas the rk3566 is relatively new and the mainline linux support is still being worked on. Also, while armbian has community builds for the older amlogic cpus and the older rockchip cpus (aml-s9xx-box, rk32xx-box, rk3318-box) there is only one community build for the h96-tvbox-3566 which is currently being worked on - other rk3566 boxes will be very hit or miss (but there is active work on getting more supported (search the forums for information). Now having said that, you need to be willing to deal with the limitations of the amlogic tv box builds (https://forum.armbian.com/topic/16976-status-of-armbian-on-tv-boxes-please-read-first), which I suspect you are based on the fact that you already appear to be using the armbian amlogic builds for an older box, but I mention here for completeness for others who may stumble across this post. Finally in my basic performance tests the s905x3 show that it is almost twice as fast as the older s905x. But neither is what I would call fast, but for general server type services, they do a fine job. I have an s905x2 box that hosts a few production websites and it is fine for that purpose.

Have you tried to use armbian-config to change the settings?

First off you aren't following the TV box install instructions. You don't use armbian-install with the aml-s9xx-box builds as it will brick your box. But regardless, even if you were following the correct instructions there is a note there: Note: It is not possible to install into emmc on boxes with the s905 cpu The way that the emmc is laid out on the s905 makes it impossible to intall Armbian to the emmc on that cpu. The later varients (s905x, etc) don't have that issue. So you are stuck running off of SD storage.