sakittelsen

It loooks like the Panfrost gpu driver is made as a module in the kernel configuration, marked with an M and not *. If I want this module to be built into the kernel, can I change it from M to * to do this? When built as a module, how do I turn it on? Is it in armbian-config (under overlays) or some other place?

Thanks, found it. run this command to start building with an extension: ./compile.sh ENABLE_EXTENSIONS=mesa-vpu

How do I enable those extensions during the image build?

Yes, that sound right. Now I have to learn how to use backports or ppa ...

Does this include graphics, like gpu driver, mesa, opengl, vulkan and so on?

3000 EUR is a bit steep I'll use armbian+config for now.

I have problems with gpu drivers. Some builds have Panfrost drivers, and some har software rendering. Often, Ubuntu has Panfrost, but Bookworm has Software. Prebuilt images often have Panfrost, but if I build the same image myself, there is no gpu driver. Learning about overlays, and looks like I have to enable gpu drivers there. I want to use Debian and not Ubuntu, but Ubuntu seens to have better hardware support (audio/video drivers). Not sure if that is just something I "think"

Found the fix, run: sudo git config --system --add safe.directory '*' # For all users and all repositories

I normally like building server images because they are small and fast to compile. An then I can add the wanted desktop by "sudo apt install gnome" or other desktop later. But, sometimes I wonder if the desktop images have more features, like hardware drivers, than a server image with an added desktop afterwards. Can this be the case? Or does server images contain the same drivers and hardware support as a image built with a destop included?

After building many images, often there are combinations of kernel, sbc card and linux base that will just give an error, like this one: Getting sources from Git [ kernel:6.1 rk-6.1-rkr5.1 ] fatal: detected dubious ownership in repository at '/home/steven/build/cache/git-bare/shallow-kernel-6.1' To add an exception for this directory, call: git config --global --add safe.directory /home/steven/build/cache/git-bare/shallow-kernel-6.1 [💥] Error 128 occurred in main shell [ at /home/steven/build/lib/functions/logging/runners.sh:211 run_host_command_logged_raw() --> lib/functions/logging/runners.sh:211 run_host_command_logged() --> lib/functions/logging/runners.sh:193 fetch_from_repo() --> lib/functions/general/git.sh:129 kernel_prepare_git() --> lib/functions/compilation/kernel-git.sh:20 do_with_hooks() --> lib/functions/general/extensions.sh:567 do_with_logging_unless_user_terminal() --> lib/functions/logging/section-logging.sh:97 compile_kernel() --> lib/functions/compilation/kernel.sh:35 artifact_kernel_build_from_sources() --> lib/functions/artifacts/artifact-kernel.sh:240 artifact_build_from_sources() --> lib/functions/artifacts/artifacts-obtain.sh:34 obtain_complete_artifact() --> lib/functions/artifacts/artifacts-obtain.sh:280 build_artifact_for_image() --> lib/functions/artifacts/artifacts-obtain.sh:392 main_default_build_packages() --> lib/functions/main/build-packages.sh:102 full_build_packages_rootfs_and_image() --> lib/functions/main/default-build.sh:31 do_with_default_build() --> lib/functions/main/default-build.sh:42 cli_standard_build_run() --> lib/functions/cli/cli-build.sh:25 armbian_cli_run_command() --> lib/functions/cli/utils-cli.sh:136 cli_entrypoint() --> lib/functions/cli/entrypoint.sh:176 main() --> compile.sh:50 ] [💥] Cleaning up [ please wait for cleanups to finish ] Is there an easy fix for this, or does it mean that the combination of build options are not valid?

Since I'm not capable of writing any code, how much do i have to donate to get it added? :-)

I have noticed that when building images using the same kernel but selecting Ubuntu or Debian base (Bookworm vs Jammy), some hardware doesn't work on one of the images. Since the kernel is identical, why is not the hardware support the same? Is there a different build script for the two bases? Different userspace drivers? Just wondering..

During the installation process of Armbian you set admin password, make a new user, set time zone and system langue, BUT not the keyboard layout... Any reason this is not part of the default armbian install process? Keyboard layout should be the first option to set during boot.

I just tested the latest, 2025 May, built image with default/recommended options and there are some missing features. Here is what I have tested: LAN yes WiFi yes BT yes USB3 *partly, some devices are not detected at all, some will take a few minutes before detected* GPU Mali-G610 (Panfrost) HDMI audio *no* Fan control yes temp. sensor htop *no* Temp. sensor Gnome *no* Other: some cursor graphic glitches Armbian-unofficial_25.05.0-trunk_Rock-5c_noble_current_6.12.28_gnome_desktop.img Any ideas on how to get more features supported?