Igor

Just a small note here - I recently added Bianbu desktop (can be installed from armbian-config), where acceleration works on K1 based Musebook (legacy kernel). This should be possible to adopt to any other K1 board. Youtube video works fine in Chromium ...

For Ubuntu Resolute desktops you need to build from this branch: https://github.com/armbian/build/pull/9683 It is a matter of days when this will be merged. You can speed this process by reviewing the code. P.S. We lack 1-2 beefy arm64 servers or 30-40k $ and unknown $ for storage space as we would need to upgrade from free storage which is limited to 1000 artifacts in order to provide more build combinations. We are far away ...

You need to provide more informations. I wasn't able to repreoduce. I works here.

What you’re seeing is open-source maintenance in practice. It’s not centrally orchestrated. We only manage to do this for some key features while DVB support is present in some kernels, but it’s not guaranteed to be consistently enabled across all targets unless someone explicitly maintains this functionality. -> https://github.com/armbian/build/pulls

https://docs.armbian.com/User-Guide_Armbian-Config/System/#desktop Should be straighforward to enable desktop on top of CLI.

We have information on which mirrors are good and which bad. We just don't display it. Good are passed to the redirector.

Community images are tied to daily beta repo where it should always be a match kernel - headers. Just make sure you have a clean updated system then proceeding to header installation via armbian-config. And only if this doesn't work, report so we can look into.

Generic aarch64 or x86 image has all needed support for most comon virtual environments. On a side we provide cloud images, optimized to run inside KVM / QEMU virtualized environment - super lean kernel. https://armbian.com/boards/uefi-arm64 https://armbian.com/boards/uefi-x86 Look for cloud kernel images. Here it can only be a problem if host (Orangepi) supports qemu or not. I don't run it here but I think it must just work. There won't be any difference compared to standard Debian / Ubuntu. Armbian is more polished in general, comes with several important improvements. Securing support for virtual targets is relatively easy compared to any custom hardware. And this was done long time ago. We use Armbian UEFI and QCOW2 virtual images to drive our infrastructur and also automated testing, but of course we target KVM / Quemu not Virtualbox. Which anyway can run normal image. Our runners and cloud services mainly run Armbian Noble cloud. Our website (dual core x86 vps): www:/boot:% du -h vmlinuz-6.18.10-cloud-x86 15M vmlinuz-6.18.10-cloud-x86 + 17M for modules (normal image has 150-200M for modules, for things you never need in virtualized environment) Yep, that's the best path for this use case.

When SPI is erased, the board falls back to the bootloader on the SD card. If you want to run Armbian, or Linux in general, the bootloader often needs to be updated - in this case on SPI. This can be done with armbian-install. Android support is not verified and is outside the scope of Linux maintainers. It may continue to work, or it may break.

This likely means the I2S overlay doesn’t exist yet. Someone would need to implement it and add it upstream (or just here to Armbian build framework). You can try enabling it manually via the Device Tree editor: https://docs.armbian.com/User-Guide_Armbian-Config/System/#device-tree-editor No guarantees it will work — hardware descriptions are often incomplete or inaccurate, and that’s outside our control.

If someone is eager to add sway - we have a new cleaner way to add and maintain (unit tests, AI auto maintain) new desktop: https://docs.armbian.com/Developer-Guide_Desktops/

https://actions.armbian.com/?repo=armbian.github.io Here anyone can monitor ... but the real problem is capacity to fix problems. Not knowning them. We have too many problems on the to do list It is not O.K., but also not a critical problem. This script is making a cache for this package which is needed in critical operations. Where it can't fail. This is why this was made in 1st place. We can't rely on upstream infrastructure.

Gnome (wayland) desktop with kernel 6.18.y Probably this way? apt install mpv mpv --hwdec=auto test.mkv (+) Video --vid=1 (*) (hevc 1920x816 25.000fps) (+) Audio --aid=1 --alang=mul (*) (aac 2ch 48000Hz) AO: [alsa] 48000Hz stereo 2ch float VO: [gpu] 1920x816 yuv420p But something is still missing ... not hw accelerated. Sorry, not an expert here. I am happy when Chromium says it.

On vendor kernel you need to enable overlay https://github.com/armbian/build/blob/main/extensions/mesa-vpu.sh#L18-L28 mainline based gnome desktop + apt install kodi (just tested 4k/H264 video works without any problems)

Support for rotation is better in modern 6.18.y Linux. Fastest is to download image and try https://www.armbian.com/boards/roc-rk3399-pc But VPU acceleration in rotated screen might be a problem ... and you will need to generate Gnome desktop image to facilitate Wayland or no fun.