Werner

Upstream support for rk3588 is still wip.
For desktop usage I suggest to either try "edge" which may have the feature you want already merged in or try "vendor" kernel which is based on Rockchip BSP.

Multiple options:
- wait for upcoming 26.05 release which will most likely have an updated kernel package including a fix for this
- as suggested use nightly
- use the build framework to build an most up-to-date kernel package set by yourself (its very easy) which then can be installed via dpkg -i
 
However since "dirty frag" just showed up, there is more to fix anyway...
 
Edit: looks like fix for dirty frag hit upstream  earlier today

You posted in the wrong sub-forum.
Your topic is about the orangepizero2w which for once has nothing to do with orangepizero2 and for the other is unsupported by Armbian. Therefore the topic was moved (and the tag adjusted) to the unsupported/community supported section of the forums, also known as staging. Latter do not offer dedicated sub-forums for each individual board.

The upstream default seems to be "otg" to allow users in userspace to change the usb port behavior.
Try this and use armbian-add-overlay
 
/dts-v1/; /plugin/; / { fragment@0 { target = <&usb_host0_xhci>; __overlay__ { dr_mode = "host"; }; }; };  

moved to staging

There were changes merged fairly recently. Perhaps try this: https://github.com/armbian/build/pull/9600

Example for adding a new board with already existing board family:
https://github.com/armbian/build/pull/9456/changes

Yes, they seem to be missing in repo. 
As a quick fix I'd suggest to use the build framework to create yourself a set of deb files containing all necessary packages
code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } ./compile.sh BOARD=orangepi5 BRANCH=current kernel
code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } copy the packages from output/debs to your board and use dpkg to install them.

Hi, welcome.
 
Syncing forums and tags with supported boards is (still) a manual job and from time to time I either cannot keep up or miss things. Like in this case.
I'll fix this later and then move appropriately. Until then feel free to state your question in "Beginners" using the "other" tag.
 
Cheers

https://www.armbian.com/download/
https://github.com/armbian/os/releases
https://github.com/armbian/community/releases
 

You can create an extension including something like 
unset armbian_kernel_config__force_pa_va_48_bits_on_arm64  

would you mind sending a pr or even upstream this change?

Alright, found something. @Meestor_X please try this one: https://testing.armbian.de/Armbian-unofficial_26.02.0-trunk_Radxa-cubie-a5e_trixie_edge_6.18.2_minimal.img.xz

moved to feedback

Didn't warn ffmpeg from a guts feel years ago that they will issue a takedown if no action is taken? So I'm not surprised. Kind of.

https://github.com/armbian/build/pull/9094

Ricardo put some real effort into Rk3528 here :https://github.com/armbian/build/pull/9102 
 
Since the 2A/2F are using the same SoC this should actually help a lot.

Try installing qemu-user-static package  via apt

just noticed current kernel is broken. I assume because of upstream changes. looks like similar what I've fixed for meson64 6.18-rc7.
 
Got it, will send pr
 
Of course this does not explain why the image wasn't correctly assembled at all...
 
Looking good: https://paste.armbian.de/ohagifufem
 
ls -l|grep Odr -rw-rw-r-- 1 root root 142 Dec 2 05:14 Armbian-unofficial_26.02.0-trunk_Odroidc2_trixie_current_6.12.60_minimal.img.sha -rw-rw-r-- 1 root root 19751 Dec 2 05:14 Armbian-unofficial_26.02.0-trunk_Odroidc2_trixie_current_6.12.60_minimal.img.txt -rw-rw-r-- 1 root root 322026836 Dec 2 05:14 Armbian-unofficial_26.02.0-trunk_Odroidc2_trixie_current_6.12.60_minimal.img.x  

Hi,
 
my first step would be comparing the opp nodes in the device trees of both Armbian and any other distro that allows the faster speed. Perhaps the necessary node is just missing.

Seems missing in kernel config. Feel free to send a PR and enable the module.

none of these are Armbian images. We do not support 3rd party OS.

I think the easiest would be to get/build an image with mesa-vpu extension enabled. Unfortunately there is no automated way to do the stuff this extension does while building, in a live system.
 
In general there are two ways to get hw acceleration: panthor or proprietary mali blobs. Former is from my feels better for general desktop usage and latter for hw encoding/decoding. Both cannot co-exist, no idea why.
Latter needs vendor kernel branch.
 
This would give you a Noble Gnome desktop image with Panthor driver enabled:
./compile.sh BOARD=youyeetoo-r1-v3 BRANCH=vendor BUILD_DESKTOP=yes BUILD_MINIMAL=no DESKTOP_APPGROUPS_SELECTED='browsers desktop_tools internet multimedia' DESKTOP_ENVIRONMENT=gnome DESKTOP_ENVIRONMENT_CONFIG_NAME=config_base ENABLE_EXTENSIONS=mesa-vpu KERNEL_CONFIGURE=no RELEASE=noble Feel free to test: https://testing.armbian.de/Armbian-unofficial_25.11.0-trunk_Youyeetoo-r1-v3_noble_vendor_6.1.115_gnome_desktop.img.xz

moved to csc
 
 
https://docs.armbian.com/User-Guide_FAQ/#why-no-universal-image
 
tl;dr: You are using the wrong image. Get/build one for your board

Yes. This is an example of a rk3588 based board of mine:
 
overlay_prefix=rockchip-rk3588 overlays=panthor-gpu opp-oc-24ghz The overlay names come from /boot/dtb/*/
find an overlay matching your soc and needs and enable by putting its name to overlays=. Then reboot. Having a serial console to read uboot logs can show if it has been loaded properly or in case it did not why.