Werner

no

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

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

As long as you do not redistribute an image with built-in ZFS no. https://docs.kernel.org/admin-guide/tainted-kernels.html

Whole documentation is needs updates. Like all the build switches (kernel, kernel-config, uboot,...) are missing...

RK3588 support in mainline is still very basic/experimental.

Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed. Try installing armbian-firmware-full via apt

Player left the game. Case closed.

for legacy: https://forum.armbian.com/topic/25590-problems-installing-zfs-dkms-config_modules-not-enabled/?do=findComment&comment=179556

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

https://openzfs.github.io/openzfs-docs/Developer Resources/Building ZFS.html [ 424.596656] zfs: module license taints kernel. [ 425.491531] ZFS: Loaded module v2.2.99-311_gd9cb42da9, ZFS pool version 5000, ZFS filesystem version 5 tested on OPi5 with kernel 6.7.1 Getting it working on legacy 5.10.y rk Android-hackedtogether kernel is a bot tougher. https://github.com/radxa/kernel/issues/54 Spoiler: patching method does not work anymore, at least not for me . Tested with 5.10.160...

Try installing from scratch: https://openzfs.github.io/openzfs-docs/Getting Started/index.html

So this is more or less a feature request. Therefore moved.

Tried this? https://developer.toradex.com/software/linux-resources/linux-features/real-time-clock-rtc-linux/#change-default-rtc

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.