Werner

Need to sync tags and boards at some point again...or hopefully this will work automatically at some point.
 
Anyway, try https://github.com/armbian/build/pull/9796 

orangepi zero3 and 3w have, besides the confusing name, nothing in common.
There is no support for any Allwinner A733 device in the framework yet. Best chance is to get in touch with Nick A since he tries to bring up support for raxda a7a, a7z, a7whateever devices which also use this SoC.

If this is really the case, then this must be an upstream issue since Armbian does not touch this file AFAIK.
 
Picked a random userspace from armhf (since you did not state which you are using)
 
~/build/cache/rootfs/bin# file su su: setuid ELF 32-bit LSB pie executable, ARM, EABI5 version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux-armhf.so.3, BuildID[sha1]=b24ceef58082e181650b17e52819559be2d3a97b, for GNU/Linux 3.2.0, stripped  

Known issue on multiple older 64 bit Allwinner socs
Try these: https://fi.mirror.armbian.de/incoming/igorpecovnik/pine64/archive/

Hi,
It depends on what you want to do with your device. You should check this sheet if the features you depend on are actually available in mainline linux: https://gitlab.collabora.com/hardware-enablement/rockchip-3588/notes-for-rockchip-3588/-/blob/main/mainline-status.md
 
Also take note that you may run into trouble booting when switching kernels. The reason is that vendor kernel images may (I don't know for this particular board) also come with (from guts feel from the stoneage) 2017 vendor uboot which may have issues booting an up to date mainline kernel. Fixing can be a bit of a pain if you don't have a second arm64 device which you could plug your microsd (via usb adapter for example) into, chroot into and fix this.

We're in the middle of the May release, so new packages should eventually hit repo in a few days/weeks.

Hi,
 
this board isn't supported, hence no images available.

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