compent

So what are the implications for this decision? Can we be optimistic that if RK3566/68 SOC's are to get mainline kernel support then the RK3588 will also get it? Or are we looking at another SOC that will essentially remain stuck in limbo because of a stalled manufacturer kernel development?

Thank you.

I decided to try the new Armbian 23.02 Jammy Gnome build and after booting with my SD card, the process gets to a point where it presents a prompt orangepi5 login: and whatever I attempt to enter returns as an incorrect login. I can't find any specific documentation which indicates the default login credentials for this build.

@acid If you pop across to the official Orange Pi forum, I have posted a topic that talks about this very issue, amongst others, so you can add your pennyworth. It's under the section for Orange Pi OS.

@martivo Thanks. I had not looked into it, thinking that the defaults would be enough but I now get that some modifications will be required.

martivo Whilst testing with every new trunk release I decided to try your Ansible roles but I came across a problem. When I run the ansible, ansible-playbook site.yml, I am prompted with BECOME password: and whatever I enter returns the following. [WARNING]: * Failed to parse /root/armbian-orange-pi-5-ansible/inventory.yml with auto plugin: We were unable to read either as JSON nor YAML, these are the errors we got from each: JSON: Expecting value: line 1 column 1 (char 0) Syntax Error while loading YAML. mapping values are not allowed in this context The error appears to be in '/root/armbian-orange- pi-5-ansible/inventory.yml': line 6, column 91, but may be elsewhere in the file depending on the exact syntax problem. The offending line appears to be: vars: normal_user: <non root user of your SBC that you created during armbian first boot, ex: martin> ^ here [WARNING]: * Failed to parse /root/armbian-orange-pi-5-ansible/inventory.yml with yaml plugin: We were unable to read either as JSON nor YAML, these are the errors we got from each: JSON: Expecting value: line 1 column 1 (char 0) Syntax Error while loading YAML. mapping values are not allowed in this context The error appears to be in '/root/armbian-orange- pi-5-ansible/inventory.yml': line 6, column 91, but may be elsewhere in the file depending on the exact syntax problem. The offending line appears to be: vars: normal_user: <non root user of your SBC that you created during armbian first boot, ex: martin> ^ here [WARNING]: * Failed to parse /root/armbian-orange-pi-5-ansible/inventory.yml with ini plugin: Invalid host pattern 'all:' supplied, ending in ':' is not allowed, this character is reserved to provide a port. [WARNING]: Unable to parse /root/armbian-orange-pi-5-ansible/inventory.yml as an inventory source [WARNING]: No inventory was parsed, only implicit localhost is available [WARNING]: provided hosts list is empty, only localhost is available. Note that the implicit localhost does not match 'all'

@martivo I tried the trunk release and the problems that I experienced are no longer there, so thanks for the tip. I happened to notice one thing though. I don't have an HDR TV and when I have tested HDR content on other platforms, whilst the quality on an SDR panel is distinctly average, there did seem to be a degree of tone mapping present to prevent it from being too washed out but with this, it is pretty much unwatchable. When I had tried the official release I did notice that HDR content was as I would have expected and with the options for manual tone mapping using Hable, AECS and Reinhart also added into the video controls. Only a minor thing but hopefully something to come in subsequent trunk releases.

Now that there is an official build for the Orange Pi 5, I decided to try this procedure with the Armbian_22.11.4_Orangepi5_jammy_legacy_5.10.110_gnome_desktop.img build. My observations are: 1. If Allow hardware acceleration with DRM prime is turned on, any 10 bit X265 video shows a black screen, even though playback is running. Turning it off will enable playback, but of course all rendering will be in software, whether 8 or 10 bit. 2. After enabling Allow hardware acceleration with DRM PRIME, the option "PRIME Render Method" to "Direct To Plane" is not shown. 3. At the login screen, there is no option to select “kodi” anywhere, just the user profile I initially created. So Kodi is run manually. 4. In Kodi, under Settings -> System -> Display, there is no option to change the resolution to 1920x1080p. The only option available is Monitor, for which there are 2 options, default or xwayland0. Things do run well though.

Fantastic. Thanks to all involved in the creation and support.