Werner

You should be up-to-date regarding "current" branch. Since "edge" kernels are not available through this you can try building and installing those packages by yourself. https://docs.armbian.com/Developer-Guide_Build-Preparation/ Anyway also an option is to try an older one, like 5.15.y and see if the issue disappears....

Possible certainly. If it works is unknown https://docs.armbian.com/Developer-Guide_Build-Preparation/

"legacy" is a term that thas been established years ago when there wasn't much confusion about it. However things have changed and now it is, depending on board family, either an old-LTS just for historical purpose or a vendor kernel which may or may not significantly outdated but working. Anyway there are discussion about renaming that into "vendor" or something, however the impact would be huge if not done carefully. If anyone steps up doing, testing and maintaining this, why not? We won't simply due to lack of human resources.

Check /etc/default/armbian-zram-whatever file. Don't remember the exact name

Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.

https://www.armbian.com/download/?device_support=Standard support Zero 2W is not supported. If however anyone steps up and provides a PR with necessary adjustments and wants to participate as maintainer this can change.

As mentioned. No end-user support. Please retry with stable image from here: https://www.armbian.com/orange-pi-4-lts/

Interesting that no header package is generated. However we cannot debug this issue since you are using a 3rd party fork of Armbian.

It is quite common that boards actually like slight overvoltage. This is last but not least to compensate for voltage drop across connectors, wiring and the PCB itself. As an example the official PSU for Orange Pi 5 boards, while being marked as 5vdc output, in reality output around 5.3 volts. Also cellphone chargers are not recommended since they are not designed to handle variable but constant charging loads. Also voltage very likely drops well below 5 volts under load.

mainline support has still long way to go until completion. Current state is more or less to be considered experimental. For its current state it works suprisingly well.

That will need mainline kernel since drivers for it have been merged into 6.5 but legacy is 5.10.y However mainline support for RK3588 is still experimental. The decision if you prefer using the most recent WiFi or everything else mostly functional is up to you. There is nothing we can do further.

As @Spooky stated this should work OOB. Install armbian-firmware-full via apt. Both Armbian and their own OS' kernel base are very close.

User has been temporary suspended for repeated violation of our terms.

moved to userspace Buster is EOL

If this is an issue at kernel level my best guess is that both Armbian and Spooky's image sharing this issue since kernel bases are very close. However you how it often is in life: There is only one way to find out

What does dmesg show when connecting the device on both the rpi and the zero?

moved

You are not using Armbian. Ask where you got the OS from you are actually using.

Maybe. The next step would be to bump to rkr7.1 which is 5.10.198 I think and then sometimes after 6.1 might be an option.

Enable OC overlay via armbian-config

Armbian does not support this board. The images you may have found in the web are not ours. Complain where you got them from. Our own Zero3 support is WIP: https://github.com/armbian/build/blob/main/config/boards/orangepizero3.wip

Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.

Hi, try here: https://docs.armbian.com/Developer-Guide_Adding-Board-Family/

We can only afford to support the most recent version which is 23.11. Check https://www.armbian.com/rockpi4/ If there is none with Bullseye (old-stable btw.) userspace you can build your own image: https://github.com/armbian/build/ OMV heavily messes with the system and is known to cause all sorts of trouble.

Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed. Outdated. Does plain Armbian work as expected.