Werner

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

I don't know. Neither do I have such a device nor I am a developer. I can give generic advice only. Overall you can try any kernel from this list. Not sure that exactly you mean by this question. However here are two ansers that might be right: - You cannot "upgrade" from a Ubuntu-based userspace to a Debian-based one since they are incompatible. - Any userspace (Bookworm, Bullseye, Jammy...) for a board are shipped with the very same kernel package. So hardware-supporting-wise does this not make any difference.

Armbian does not support this device. This topic is also not about zero3 but the original zero which has exactly zero (lol) in common with the zero3.

fixed

Tried current kernel? Edge can break anytime...

The topics there are related to Armbian as well. People want to boot Armbian on their board but fail due to either PSU or sdcard issues which are sorted out there. If anyone for example reports a boot issue for Raspi OS related to sd or PSU it will be moved to off-topic or at least told that this is the wrong place for the question.

If the question is not about armbian it is off-topic automatically.

I don't know. Never tested userspace upgrade.

Maybe rename Beginner to Beginner / General?

httpredir has been deprecated for years. https://wiki.debian.org/DebianGeoMirror "bullseys"

https://docs.armbian.com/User-Guide_Getting-Started/#how-to-upgrade-distribution-like-focal-to-jammy-or-bullseye-to-bookworm

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

Armbian is designed to run natively. So no easy way to achieve what you are looking for.

Only building from main is supported.

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

Not really. You should keep in mind that mainline support for the RK3588 is under heavy development so issues are to be expected.

I did not test but I'd do something like this: create fs on the new sd like it is on the current one copy everything via rsync or similar that keeps symlinks, permissions and such of all files. Adjust code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } rootdev=UUID= in code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } /boot/armbianEnv.txt to match the UUID of the new sdcard. ??? Profit

Strongly agreeing to Nico and silencer. Do not buy any tvbox but consider getting a properly supported SBC. Don't feed this market.

Usually installing DE should be available via armbian-config. However since this tool is kind of neglected due to major rewrite is WIP this might not work. Anyway you can try to use userspace tutorials available here or start from scratch with pre-configured Armbian desktop image.

Maybe armbian-install does not get that you messed with mtd0 beforehand. When I attached my nvme and used armbian-install everything worked flawless including mtd writing. Since I assume it came empty from factory I'd suggest to zero it as well and retry using armbian-install. That is the old name of now armbian-install. It is just a symlink but keep in mind using the old command is considered deprecated and might be removed entirely in future. I assume you are aware but just in case not you will have trouble with hw acceleration in this configuration. For now only Jammy Gnome offers - with the PPAs mentioned on download page in place - this. Are you using an SSD or an actual NVMe? AFAIK you need some dtbo to support SSDs while real NVMes work OOB.

1. If nobody takes the task to build the necessary packages for Debian this will not get solved anytime soon. 2. Yes because the ppas are made for Jammy 3. Perhaps but don't know.

moved to userspace

Well both problems can sort of be summarized under the fact - which you already guessed - that Armbian doesn't have sufficient funding (we actually never had unfortunately) to provide all these features properly. Software development actually costs lots of money which the majority is payed from our own pockets. So we have to make best out of it which is best effort support. If things are missing everyone is invited to join by sending a PR to fix things simply or pay for their development. A board being maintained means that there is a dedicated person attached to it which has access to the hardware and can do tests. However they are not necessarily developers so they cannot fix but observe.

Armbian does not provide any images for this board. They are from a 3rd party. Complain where you got them from.

Looks like Debian stock kernel which obviously won't work with this board. Try installing wireguard with "--no-install-recommends" switch