Werner

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

It is always handy to have a bunch of those when tinkering with SBCs. Thankfully the are rather cheap

I suggest to state this question to friendlyelec since you listed their images rather than Armbians. Armbian does not provide desktop images for this board afaik.

Not possible afaik

OMV heavily messes with the system settings and is known for causing all sorts of trouble and then users blame Armbian while the issues is OVM themselves in lots of cases. Anyways, for now I suggest to install plain Armbian in whatever flavour you like and make static ip work. Either try armbian-config or check https://www.google.com/search?q=how+to+set+static+ip+debian Once that works properly continue with OMV.

Tried building and install ffmpeg from source (with smb enabled)? Seems like mpv is depending on ffmpeg and its smb support.

I guess this information depends on using Debian's stock kernel with most likely will not even boot on your board.

This seems mostly a cosmetical issue. Since kernel upgrade seem to have worked properly there is nothing to worry about for now.

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.

looks like you are not using Armbian. Therefore support cannot be provided.

There should be. I suggest to start investigation here: https://github.com/armbian/build/blob/main/config/boards/nanopi-r4s.conf

Maybe because there is no HDMI output this has been stripped from the config? Did not investigate, just guessing

You have less uncompressed memory available then if this is a strain for you