Werner

Could this be a power supply issue?
 
Unfortunately, there is no official maintainer for your board.  None of the core devs will be able to verify your issue.

Um...no? Where did you get that info?
Using armbian-config is totally optional. Everything this tool does can also be done manually.

I usually check here every couple of days: https://patchwork.kernel.org/project/linux-rockchip/list/
Yes, they will be included in edge kernel and in a year or two when the next LTS kernel hits they'll be included in current as well.

I usually check here every couple of days: https://patchwork.kernel.org/project/linux-rockchip/list/
Yes, they will be included in edge kernel and in a year or two when the next LTS kernel hits they'll be included in current as well.

vendor kernel has rknpu enabled by default.
edge will receive initial support for it (called Rocket then) with 6.17 iirc.

There are two ways to achieve hw acceleration: backported panthor or mali blobs.
Depending on your usecase latter might be necessary. You may find this interesting: https://jellyfin.org/docs/general/post-install/transcoding/hardware-acceleration/rockchip/#configure-on-linux-host
Don't forget to disable panthor overlay in /boot/armbianEnv.txt if you decide to go this route.

Revert to 6.15. The 6.16 package is useful for A523 only atm.
 
Don't use bleeding edge and complain about things breaking the same time.
To answer on your level: Either help fixing things or fuck off and move along.

Depending on your location this might not be anything that can be fixed on Armbian side. If this happens on any mirror, the issue is either your setup or ISP blocking access.

data corruption can always happen when there is a power outage. Could be by chance that one device suffered while the other didn't.
Best way to prevent is as guessed a small PSU which ideally tells the device 'there is an outtage, please shut down before I run out of battery".
 
Having OS or data or microSD, eMMC or NVMe does not make a difference since the OS decides when and how often data is written. NVMe are even more fragile since they often come with an internal cache themselves that is emptied onto the actual flash asynchronously. 
Disabling write caches may lower chances for data corruption but for once can decrease performance a lot and for the other significantly decreases the lifetime of microSD cards.

These things can happen, yes. Sometimes old vendor-style uboot cannot process a modern mainline kernel and vice versa. Glad to hear it worked well this time.

Ah, I misunderstood. I thought does not appear at all anymore but the question was about manual call.
Has been answered properly already.

Vendor kernel 6.1.y with mesa-vpu extension https://github.com/armbian/os/blob/main/userpatches/targets-extensions.map#L58 (with patched Chromium) is the only way to come close to what you want.
 
Only this:

Install code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } qemu-user-static package and retry

This should have been addressed: https://github.com/armbian/linux-rockchip/pull/373
May take a while until an updated kernel is available via apt. You can always build a up-to-date package by yourself using the build framework.

https://docs.armbian.com/User-Guide_Autoconfig/

I cannot verify your claim that Ubuntu "reverted" to Gnome v44.  Noble has v44 indeed.  v46 is not anywhere in a Ubuntu release so my guess is you shot yourself in the foot with some random PPA or whatever repo out there.
 
https://launchpad.net/ubuntu/+source/meta-gnome3
 
There is no shortage of boards out in the wild, nobody would think that.  What there is, is a shortage of people willing to fund development, be it users or companies.  Big shout out to those who do and to our volunteer devs, thank you!

No, Armbian has not become a total nightmare.  But your posting all over the place, in several threads here and even Ubuntu ustream trackers with a bunch of unsubstantiated and obviously nonsensical claims IS absolutely a nightmare.  PLEASE STOP!

You make bogus claims faster than anybody can look into them.  What made you think this was related to postgres?  What makes you think Ubuntu downgraded their Gnome in Noble?  Slow down, take a deep breath and stop being all over the place.

No, this board isn't supported. However anyone from the community can step up and add support for it.
Found an attempt on Github:https://github.com/juanesf/build/pull/1 

This is not an Armbian image. We do not support 3rd party images.

Detailed/full uart logs would probably be helpful

Maybe this helps? https://forum.armbian.com/topic/29427-shrink-backup-a-tool-for-backing-up-sbcs/

Maybe this helps? https://forum.armbian.com/topic/29427-shrink-backup-a-tool-for-backing-up-sbcs/

Yes, DB9 won't work.
But if, as eselarm mentions, a proper chip is on board already a simple usb-a to usb-c or c-to-c cable should do.
Check dmesg when connection to see what pops up.

If nvme is correctly recognized code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } armbian-install should do.

symptom:
> apt update ... Err:8 https://github.armbian.com/configng stable InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 93D6889F9F0E78D5 ... W: Failed to fetch https://github.armbian.com/configng/dists/stable/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 93D6889F9F0E78D5 observed in Armbian image for Orange pi zero 3 Armbian_community_25.8.0-trunk.90_Orangepizero3_bookworm_current_6.12.30_minimal.img build date May 28, 2025
 
fix:
- run this as root
> su - ^ login as root > wget -O - https://apt.armbian.com/armbian.key | gpg --dearmor -o /usr/share/keyrings/armbian.gpg  
you should find a file /usr/share/keyrings/armbian.gpg about 2 KB in size
 
repeat apt update etc should have resolved the error