Werner

Check this. Also full logs are missing.

Then you are using a fork of Armbian which we don't support here. Ask at the place where you got the image from.

Hi, its just a warning. Check the files mentioned and remove duplicate lines.

I don't think so. You can check in /boot/armbianEnv.txt if there is panthor overlay enabled. If so, disable it so you can use the proprietary mali blobs.

Only possible with starting over with a fresh image written to sd. Armbian does not come with some sort of overlayfs.

unsupported host os for build environment. Grant the user access to Docker or use a Noble host.

split into new topic. Use one of the curl commands mentioned in your logs go upload full logs to a paste server. These will contain more information to debug this.

I don't know where these shortcuts link to, but I assume they both link to the same executable script which is the next generation version. I am not aware that any current Armbian image still ships the old version. So at the bottom-line there is no difference.

The correct way to modify a kernel with patches is to use - ./compile kernel-patch BOARD=... BRANCH=... - review your patches and if you are satisfied move them to patch/ or the equivalent directory under userpatches/ - ./compile.sh kernel BOARD=... BRANCH=...

moved You are using the wrong kernel branch. You need vendor 6.1.y kernel. This is also mentioned in the official documentation of Jellyfin.

I assume the armbian-config shortcut is a left-over from the old version of this tool: https://github.com/armbian/config It has been replaced with https://github.com/armbian/configng

Loading a kernel module has nothing to do with enabling a device tree overlay.

https://zuckerbude.org/armbian-using-kernel-config/ https://www.google.com/search?q=google+how+to+load+linux+kernel+modules

https://docs.armbian.com/Developer-Guide_Build-Switches/ Look for ENABLE_EXTENSIONS

Here is an sample implementation of both: https://forum.armbian.com/topic/51915-server-vs-desktop-images/#findComment-218346

You can see here what the most important one does: https://github.com/armbian/build/blob/main/extensions/mesa-vpu.sh

Hm sounds like it all boils down to mesa. Ubuntu Noble has kisak ppa to provide a more current version while Debian can pull more recent mesa packages from backports. mesa-vpu extension should deal with that.

https://forum.armbian.com/subscriptions/ Being a Gold Partner would be a good start. Software development is expensive and unfortunately getting 10 bucks here and there are simply not enough to make a living from for anyone.

Desktop images have some standard adjustments, like other wallpaper or certain extensions enabled. Driver, or kernel-wise, they are, depending on things mentioned earlier, identical to server images. You can check the build framework on Github for all the code.

https://docs.armbian.com/User-Guide_FAQ/#why-is-there-no-image-for-board-with-bookwormjammynobletrixie-and-minimalclignomekdexfce-with-vendorlegacycurrentedge-kernel

moved

Probably because nobody implemented this yet. Feel free to do so and send a PR.

moved

Use edge or vendor for more features. current will stick to 6.12 LTS kernel which will receive fixes only.

Using screen is sufficient. No settings besides baud rate (115200 for any Allwinner) need adjustments. As mentioned above make sure your serial device is correct. If you are unsure, simply - unplug - run sudo dmesg -ew - plug in and check output in the terminal with the command above. Also make sure wiring is correct. Ground to ground and rx/tx crossed.