I hope this topic is in the right place and won't bother anyone.

I'm pretty new to the ARM world. In very first i would like to thanks all people and the communities who work hard on Armbian.

I successfully use a NanoPC T6 Plus / A NanoPi M6 and other forks on some TV Box with no major problems.

My curiosity pushed me to try using Armbian on a MinisForum MS-R1, so i bought one and tried to boot up the KDE or Gnome image on it.

In the two case, the installation is a fail at the step of launching the desktop environment, it's stuck here.

The uefi is up to date with the lastest version (cix_flash_all2_MGP1WSB_20260429.bin20260429).

Ubuntu Concept Cix P1 runs correctly - The proprietary Debian image runs very great but it's limited to the Cix 6.6.x kernel

I would like to know if anyone else has experienced the same issues with this board. I did search the forum and tried a few things (using different images) but I might have missed something.

Thanks in advance for your help.

./compile.sh BOARD=qemu-uefi-x86 BRANCH=current KERNEL_CONFIGURE=no ARCH=x86_64 BUILD_MINIMAL=yes BUILD_DESKTOP=no KERNEL_BTF=no RELEASE=jammy

Ao final do processo, recebo o seguinte erro. Alguém pode me ajudar?

Estava gerando corretamente e, de repente, parou.

 Ign:6 http://archive.ubuntu.com/ubuntu jammy-backports InRelease

[🔨] Erro:1 https://github.armbian.com/configng estável InRelease

[🔨Erro do sistema ao resolver 'github.armbian.com:https' - getaddrinfo (16: Dispositivo ou recurso ocupado)

[🔨] Erro:2 https://apt.armbian.com jammy InRelease

[🔨Erro do sistema ao resolver 'apt.armbian.com:https' - getaddrinfo (16: Dispositivo ou recurso ocupado)

[🔨] Err:3 http://archive.ubuntu.com/ubuntu jammy InRelease

[🔨Erro de sistema ao resolver 'archive.ubuntu.com:http' - getaddrinfo (16: Dispositivo ou recurso ocupado)

[🔨] Erro:4 http://archive.ubuntu.com/ubuntu jammy-security InRelease

[🔨Erro de sistema ao resolver 'archive.ubuntu.com:http' - getaddrinfo (16: Dispositivo ou recurso ocupado)

[🔨] Erro:5 http://archive.ubuntu.com/ubuntu jammy-updates InRelease

[🔨Erro de sistema ao resolver 'archive.ubuntu.com:http' - getaddrinfo (16: Dispositivo ou recurso ocupado)

[🔨] Erro:6 http://archive.ubuntu.com/ubuntu jammy-backports InRelease

[🔨Erro de sistema ao resolver 'archive.ubuntu.com:http' - getaddrinfo (16: Dispositivo ou recurso ocupado)

[🔨Lendo listas de pacotes...

[🔨] W: Falha ao buscar https://github.armbian.com/configng/dists/stable/InRelease Erro de sistema ao resolver 'github.armbian.com:https' - getaddrinfo (16: Dispositivo ou recurso ocupado)

[🔨] W: Falha ao buscar https://apt.armbian.com/dists/jammy/InRelease Erro de sistema ao resolver 'apt.armbian.com:https' - getaddrinfo (16: Dispositivo ou recurso ocupado)

[🔨] W: Falha ao buscar http://archive.ubuntu.com/ubuntu/dists/jammy/InRelease Erro de sistema ao resolver 'archive.ubuntu.com:http' - getaddrinfo (16: Dispositivo ou recurso ocupado)

[🔨] W: Falha ao buscar http://archive.ubuntu.com/ubuntu/dists/jammy-security/InRelease Erro de sistema ao resolver 'archive.ubuntu.com:http' - getaddrinfo (16: Dispositivo ou recurso ocupado)

[🔨] W: Falha ao buscar http://archive.ubuntu.com/ubuntu/dists/jammy-updates/InRelease Erro de sistema ao resolver 'archive.ubuntu.com:http' - getaddrinfo (16: Dispositivo ou recurso ocupado)

[🔨]   W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/jammy-backports/InRelease System error resolving 'archive.ubuntu.com:http' - getaddrinfo (16: Device or resource busy)

[🔨]   W: Some index files failed to download. They have been ignored, or old ones used instead.

[🚸] WARNING: SDCARD /var/lib/apt/lists dir is not empty [ before 'apt-get --no-install-recommends install armbian-config' :: /home/adm64/buldx86-64/.tmp/rootfs-ad6535a3-5649-47eb-bfe2-25cd24623192/var/lib/apt/lists (21 files) ]

[🔨]   /home/adm64/buldx86-64/.tmp/rootfs-ad6535a3-5649-47eb-bfe2-25cd24623192/var/lib/apt/lists:

[🔨]   total 182M

[🔨]   drwxr-xr-x 5 root            root  120 Apr  6 15:49 ..

[🔨]   drwxrwxr-x 4 root            root  500 Apr  6 15:25 .

[🔨]   drwx------ 2 systemd-network root   40 Apr  6 15:25 partial

[🔨]   -rw-r----- 1 root            root    0 Apr  6 15:24 lock

[🔨]   drwxr-xr-x 2 systemd-network root   40 Apr  6 15:24 auxfiles

[🔨]   -rw-r--r-- 1 root            root 125K Apr  6 12:23 archive.ubuntu.com_ubuntu_dists_jammy-backports_InRelease

[🔨]   -rw-r--r-- 1 root            root 126K Apr  6 12:22 archive.ubuntu.com_ubuntu_dists_jammy-updates_InRelease

[🔨]   -rw-r--r-- 1 root            root 126K Apr  6 12:19 archive.ubuntu.com_ubuntu_dists_jammy-security_InRelease

[🔨]   -rw-r--r-- 1 root            root  19M Apr  3 18:09 archive.ubuntu.com_ubuntu_dists_jammy-updates_main_binary-amd64_Packages

[🔨]   -rw-r--r-- 1 root            root 6.9M Apr  3 18:09 archive.ubuntu.com_ubuntu_dists_jammy-updates_universe_binary-amd64_Packages

[🔨]   -rw-r--r-- 1 root            root  17M Apr  2 19:01 archive.ubuntu.com_ubuntu_dists_jammy-security_main_binary-amd64_Packages

[🔨]   -rw-r--r-- 1 root            root 5.9M Apr  2 19:01 archive.ubuntu.com_ubuntu_dists_jammy-security_universe_binary-amd64_Packages

[🔨]   -rw-r--r-- 1 root            root  33M Apr  1 00:36 archive.ubuntu.com_ubuntu_dists_jammy-updates_restricted_binary-amd64_Packages

[🔨]   -rw-r--r-- 1 root            root 5.4K Mar 30 03:55 github.armbian.com_configng_dists_stable_InRelease

[🔨]   -rw-r--r-- 1 root            root  623 Mar 30 03:55 github.armbian.com_configng_dists_stable_main_binary-amd64_Packages

[🔨]   -rw-r--r-- 1 root            root  31M Mar 25 09:42 archive.ubuntu.com_ubuntu_dists_jammy-security_restricted_binary-amd64_Packages

[🔨]   -rw-r--r-- 1 root            root 440K Mar 15 04:56 archive.ubuntu.com_ubuntu_dists_jammy-backports_main_binary-amd64_Packages

[🔨]   -rw-r--r-- 1 root            root 143K Mar 15 04:56 archive.ubuntu.com_ubuntu_dists_jammy-backports_universe_binary-amd64_Packages

[🔨]   -rw-r--r-- 1 root            root 277K Jan 28 17:31 archive.ubuntu.com_ubuntu_dists_jammy-security_multiverse_binary-amd64_Packages

[🔨]   -rw-r--r-- 1 root            root 308K Jan 26 14:47 archive.ubuntu.com_ubuntu_dists_jammy-updates_multiverse_binary-amd64_Packages

[🔨]   -rw-r--r-- 1 root            root 264K Apr 21  2022 archive.ubuntu.com_ubuntu_dists_jammy_InRelease

[🔨]   -rw-r--r-- 1 root            root  62M Apr 21  2022 archive.ubuntu.com_ubuntu_dists_jammy_universe_binary-amd64_Packages

[🔨]   -rw-r--r-- 1 root            root 897K Apr 20  2022 archive.ubuntu.com_ubuntu_dists_jammy_multiverse_binary-amd64_Packages

[🔨]   -rw-r--r-- 1 root            root 6.5M Apr 18  2022 archive.ubuntu.com_ubuntu_dists_jammy_main_binary-amd64_Packages

[🔨]   -rw-r--r-- 1 root            root 895K Apr 13  2022 archive.ubuntu.com_ubuntu_dists_jammy_restricted_binary-amd64_Packages

[🔨]  

[🔨]   /home/adm64/buldx86-64/.tmp/rootfs-ad6535a3-5649-47eb-bfe2-25cd24623192/var/lib/apt/lists/partial:

[🔨]   total 0

[🔨]   drwx------ 2 systemd-network root  40 Apr  6 15:25 .

[🔨]   drwxrwxr-x 4 root            root 500 Apr  6 15:25 ..

[🔨]  

[🔨]   /home/adm64/buldx86-64/.tmp/rootfs-ad6535a3-5649-47eb-bfe2-25cd24623192/var/lib/apt/lists/auxfiles:

[🔨]   total 0

[🔨]   drwxrwxr-x 4 root            root 500 Apr  6 15:25 ..

[🔨]   drwxr-xr-x 2 systemd-network root  40 Apr  6 15:24 .

[🔨]   E: Failed to fetch http://archive.ubuntu.com/ubuntu/pool/main/n/newt/libnewt0.52_0.52.21-5ubuntu2_amd64.deb System error resolving 'archive.ubuntu.com:http' - getaddrinfo (16: Device or resource busy)

[🔨]   E: Failed to fetch http://archive.ubuntu.com/ubuntu/pool/main/n/newt/whiptail_0.52.21-5ubuntu2_amd64.deb System error resolving 'archive.ubuntu.com:http' - getaddrinfo (16: Device or resource busy)

[🔨]   E: Failed to fetch http://archive.ubuntu.com/ubuntu/pool/main/p/pv/pv_1.6.6-1build2_amd64.deb System error resolving 'archive.ubuntu.com:http' - getaddrinfo (16: Device or resource busy)

[🔨]   E: Failed to fetch https://github.armbian.com/configng/pool/main/a/armbian-config/armbian-config_26.2.0-trunk.655.0330.065342_all.deb System error resolving 'github.armbian.com:https' - getaddrinfo (16: Device or resource busy)

[🔨]   E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?

[💥] Error 1 occurred in main shell [ at /home/adm64/buldx86-64/lib/functions/logging/runners.sh:15

   chroot_sdcard_apt_get_install() --> lib/functions/logging/runners.sh:15

   post_armbian_repo_customize_image__install_armbian-config() --> extensions/armbian-config.sh:17

   post_armbian_repo_customize_image() --> <extension_magic>:167

          call_extension_method() --> lib/functions/general/extensions.sh:57

   run_hooks_post_armbian_repo_customize_image() --> lib/functions/rootfs/customize.sh:60

                do_with_logging() --> lib/functions/logging/section-logging.sh:81

         build_rootfs_and_image() --> lib/functions/main/rootfs-image.sh:59

   full_build_packages_rootfs_and_image() --> lib/functions/main/default-build.sh:36

          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

 ]

[💥] Limpeza [aguarde a conclusão da limpeza]

[🌿] Desmontando recursivamente [ SDCARD - aguarde ]

[🌿] Desmontando recursivamente [ MOUNT - aguarde ]

[🌿] Arquivo de log ANSI criado; inspecione-o executando: [ less -RS output/logs/log-build-ad6535a3-5649-47eb-bfe2-25cd24623192.log.ans ]

[🌱Compartilhar o log manualmente: [use um dos comandos abaixo (ou adicione SHARE_LOG=yes na próxima vez!)]

[🌿] Compartilhe o log manualmente: [ curl --data-binary @output/logs/log-build-ad6535a3-5649-47eb-bfe2-25cd24623192.log.ans https://paste.armbian.com/log ]

[🌿] Compartilhe o log manualmente: [ curl --data-binary @output/logs/log-build-ad6535a3-5649-47eb-bfe2-25cd24623192.log.ans https://paste.armbian.de/log ]

[🌿] Compartilhe o log manualmente: [ curl --data-binary @output/logs/log-build-ad6535a3-5649-47eb-bfe2-25cd24623192.log.ans https://paste.next.armbian.com/log ]

[🌿] Compartilhe o log manualmente: [ curl --data-binary @output/logs/log-build-ad6535a3-5649-47eb-bfe2-25cd24623192.log.ans https://pa

https://drive.google.com/file/d/1gkEzVoY5QkNcWq3MOKYUSc8nkFYg91p-/view?usp=sharing

Video of what I see

https://drive.google.com/file/d/17yhnIjzkiYkkVohFrLf7MKDtYyb0xfOL/view?usp=sharing

I have upgraded an existing x86 Armbian system with kernel 6.6.63 and zfs 2.3.2 to the suggested kernel 6.12.32-current-x86, but I cannot get the zfs kernel module loaded after the latest updates to Armbian 25.5.1 noble. I also tried on other kernels, only the old 6.6.63 seems to work.

Normally when you select a different kernel in the armbian-config menu, it should automatically compile the zfs modules if it is activated. It just skips it. But you can of course compile it with the provided DKMS system:

Quote

 

dkms build -m zfs -v 2.3.2 -k 6.12.32-current-x86

 

 

 

the build just finishes fine, without any error, also the install, but when you try to load the module:

Quote

modprobe zfs

it responds with:

Quote

 

modprobe: ERROR: could not insert 'zfs': Exec format error

 

 

 

dmesg:

Quote

[Mon Jun 16 12:40:38 2025] module spl: .gnu.linkonce.this_module section size must match the kernel's built struct module size at run time

I have zfs 2.3.2 on kernel 6.12.32-current-bcm2711 running just fine on a Raspberry Pi 4, so I tested what would happen if I just build a small kernel driver module:

root@armbian:/usr/src/dummydriver# cat dummydriver.c
 

Quote

 

#include <linux/module.h>
#include <linux/version.h>
#include <linux/kernel.h>

static int __init driver_init(void)
{
    printk(KERN_INFO "Goodbye World!");

    return 0;
}

static void __exit driver_exit(void)
{
    printk(KERN_INFO "Hello World!");
}

module_init(driver_init);
module_exit(driver_exit);

MODULE_LICENSE("GPL");
MODULE_AUTHOR("dude");
MODULE_DESCRIPTION("driver");

 

 

 

root@armbian:/usr/src/dummydriver# cat Makefile
 

Quote

 

obj-m = dummydriver.o
KVERSION = $(shell uname -r)
all:
    make -C /lib/modules/$(KVERSION)/build M=$(shell pwd) modules

clean:
    make -C /lib/modules/$(KVERSION)/build M=$(shell pwd) clean

 

So when I run this on the  Raspberry Pi 4, I can load the module and unload

Quote

 

insmod dummydriver.ko

rmmod dummydriver

 

But when I run this on the x86 machine I get the same error:

Quote

root@armbian:/usr/src/dummydriver# insmod dummydriver.ko 
insmod: ERROR: could not insert module dummydriver.ko: Invalid module format
root@armbinan:/usr/src/dummydriver# [Mon Jun 16 12:13:21 2025] module dummydriver: .gnu.linkonce.this_module section size must match the kernel's built struct module size at run time

root@armbian:/usr/src/dummydriver# modinfo dummydriver.ko
 

Quote

 

filename:       /usr/src/dummydriver/dummydriver.ko
description:    driver
author:         dude
license:        GPL
srcversion:     4510E7795B8BE551B44A0E5
depends:        
name:           dummydriver
retpoline:      Y
vermagic:       6.12.32-current-x86 SMP preempt mod_unload modversions 
 

 

 

 

root@armbian:/usr/src/dummydriver# gcc --version
 

Quote

 

gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0
Copyright (C) 2023 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
 

 

 

 

I also tried gcc 11.4.0

Here is my armbianmonitor -u:

https://paste.armbian.com/orepumazam

Any help welcome!

Philippe

Has anyone managed to get our fave OS booting on this device. ? Wyse 3040 (N10D)

I've created UEFI boot media, with both Rufus and Etcher, but it dosne't see it as bootable.

To prove settings are ok on the device, it boots the deb bookworm usb image I made. 
Unfortunatly, Deb won't install as this device only has 8GB of flash... hence why I returned again to Armbain

Many thanks

MarkA

i try to install the current IOT/minmal image on the intern ssd on a old thinclient.

USB-Drive will ident as sda and the ssd as sdb.

if i use on armbian-config the install script for install, he create two partitions (sdb1 &2 / efi & linux) but it only boot with usb drive. 

On the usb drive i has a BIOS boot partition, must i swaphis somehow to the ssd drive?

https://github.com/albertogviana/YT6801

https://github.com/dante1613/Motorcomm-YT6801

https://forums.linuxmint.com/viewtopic.php?t=438301

https://deb.tuxedocomputers.com/ubuntu/pool/main/t/tuxedo-yt6801/

and run the gamut for two days straight without much luck.

First the linux headers were not installed, so I installed them through armbian-config, only to find out they were still not available because potentially the headers are for 6.12.41 are not available?

https://mirror.twds.com.tw/armbian-apt/pool/main/l/linux-headers-current-x86/ (I don't see them listed here, I do see a 6.12.32 and a 6.12.44)

Then I rolled back the Kernel to 6.12.32 and tried to install the headers again them through armbian-config, only to find out they were still not available?!?!? So I installed them by downloading the *.deb directly and manually installed them.

Now I can get the latest tuxedo driver (tuxedo-yt6801_1.0.30tux4_all.deb) to build and install, but the module will not load.

journalctl | grep "yt6801" shows

.gnu.linkonce.this_module section size must match the kernel's built struct module size at run time

here is the output from the install:

root@Armbian:~# sudo dpkg -i tuxedo-yt6801_1.0.30tux4_all.deb
(Reading database ... 79866 files and directories currently installed.)
Preparing to unpack tuxedo-yt6801_1.0.30tux4_all.deb ...
Module tuxedo-yt6801-1.0.30tux4 for kernel 6.12.32-current-x86 (x86_64).
Before uninstall, this module version was ACTIVE on this kernel.

yt6801.ko:
 - Uninstallation
   - Deleting from: /lib/modules/6.12.32-current-x86/updates/dkms/
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.
depmod.........
Deleting module tuxedo-yt6801-1.0.30tux4 completely from the DKMS tree.
(Re)load module if possible
Unpacking tuxedo-yt6801 (1.0.30tux4) over (1.0.30tux4) ...
Setting up tuxedo-yt6801 (1.0.30tux4) ...
Loading new tuxedo-yt6801-1.0.30tux4 DKMS files...
Building for 6.12.32-current-x86
Building initial module for 6.12.32-current-x86
Done.

yt6801.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/6.12.32-current-x86/updates/dkms/
depmod...
(Re)load module if possible
Warning: Could not load module yt6801.

Any clues on what I might be missing? I'm not a hardcore Linux pro by any means, but I'm not a novice either. Any help would be much appreciated.

- improved support in GRUB (armbian wallpaper) & HiDPI GRUB support

- all preinstalled applications are normal apt packages

- current 5.15.y kernel, Jammy userland (5.19.y has some strange issues)

- snapd is not installed (user can install it)

- HiDPI support (automated adjustments on big screen resolutions)

- NVIDIA graphics acceleration with proprietary driver (x86 only)

- Intel graphics acceleration also works out of the box

- preinstalled Google Chrome (x86 only)

- preinstalled Microsoft Visual Studio Code (x86 only)

- ZFS 2.1.5 ready (apt install zfsutils-linux zfs-dkms)

- face unlock works perfectly fine on this laptop

- installation to SSD drive to dual boot with Windows 10/11 is supported Armbian classical way by transferring actual live image to the prepared partition via nand-sata-install. All you need to do is prepare spare space on your drive, Windows 10/11 or Linux, UEFI support (most if not all hardware for past 10 years has it).

I have tweaked images (XFCE, Gnome, Cinnamon) a bit to my personal needs, but making changes is welcome.

Nice to have: disk encryption within nand-sata-install, small bug fixing, additional DEs. Currently we have CLI, XFCE, Gnome and Cinnamon. Others are too buggy.

https://www.armbian.com/uefi-x86/

https://www.armbian.com/uefi-arm64/

Please report where it works and how (well)!

See the attached screenshot:

Disabling the secure boot isn't an option, because every time I turn it off and then turn it on the next morning, the BIOS settings are being reset, then the secure boot is enabled once again (I believe it is intentional, because the CMOS battery only keeps the clock & date).

Moreover, I want to use it as a headless computer, so no keyboard will be attached.

Is this fixable or Armbian isn't compatible with secure boot?

Thanks in advance.

Then I've tried /etc/default/grub adding the parameters to GRUB_CMDLINE_LINUX_DEFAULT= and then doing update-grub, but it is also ignored.

Where should I put the kernel parameters?

I have installed

Armbian 24.2.4 Jammy Kde-neon Kernel: 6.6.21, Size: 1.9GB, Release date: Mar 12, 2024

on a mini pc J4125 Celeron based.

What I noticed that is during initial boot, when finds the timezone and asks to accept or select a diff one, i tried 2 times. I selected accept and then took minuted to complete and enter the desktop

First time I killed it and second clean i waited.:-)

I checked in armbian-config the locales and noticed that ALL options were checked. Which makes sense why I waited so long

If this a know bug or needs to be fixed?

Just wanted to bring to your attention.
Rest work smooth and fast!

Tx for your work

I tested on the

/etc/default/grub

and

 /etc/default/grub.d/98-armbian.cfg

Is there another config file Im missing that ignores above, especially later?
Tried also with custom override config at boot.

Any advise is welcome

Thanks.

Context

I build my own custom Arabian image on arm 32bit (prod), and experimenting running the following armbian image configuration on Qemu with console/serial only support for  uefi-x86 and uefi-arm64 boards to speed up development/test.

Quote

BOARD="refi-x86"

...

BUILD_DESKTOP="no"

BUILD_MINIMAL="yes"

CONSOLE_AUTOLOGIN="no"

REVISION="23.11.2"

 

Problem

I stumble upon something odd: both "uefi-*" boards are configured to only run GRUB in gfxterm mode ONLY.

BOARD: uefi-86        -> BOARDFAMILY="uefi-x86".        -> UEFI_GRUB_TERMINAL="gfxterm" [0]

BOARD: uefi-arm64 -> BOARDFAMILY="uefi-arm64".  -> UEFI_GRUB_TERMINAL="gfxterm" [1]

[0] https://github.com/armbian/build/blob/2afd8fe9bb8aca33a2a3913e931fc43c43c8e309/config/sources/families/uefi-x86.conf#L11

[1] https://github.com/armbian/build/blob/2afd8fe9bb8aca33a2a3913e931fc43c43c8e309/config/sources/families/uefi-arm64.conf#L10

Image built from these boards should be runnable as CLI image (no gui) or Desktop image (gui).

However, when running with  

qemu -nographic ...

 these image can't boot up to a working shell and produce an error: "GRUB: gfxterm is not supported"

Proposed change
I would like to submit a patch to change UEFI_GRUB_TERMINAL to "gfxterm vga_text console serial" to cover a large set of virtualised hardware configurations.

1. Is this something you guys are interested in ?

2. Does this fix need more than the proposed change to achieve the desired objective ?

Thanks

Is anybody able to install and install Armbian bookworm on Proxmox (OVMF uefi, Q35)? I tried multiple times but proxmox doesn't recognize the UEFI partition and I can only boot from the USB... 

Debian boots fine tho.

I wanna test Armbian x86 on virtual machine.

Is possible to convert its img file to some format (vdi or vmdk) and boot on Virtualbox?

I made a attempt but it wont boot..

VBoxManage.exe convertfromraw --format VDI armbian.img ambian.vdi

Thx a lot

not sure where to post this, intended for @rpardini

I have an x13s running here with dual boot to win11 and ubuntu 23.04 lunar, the armbian work was a great help to get it to work. Not quite finished setting it up tbqh. However, if you're on a fast boot device like the local NVMe drive, the remoteproc firmwares qcadsp8280.mbn and qccdsp8280.mbn fail to load and won't get retried later, the GPU firmwares a660_sqe.fw and a660_gmu.bin may fail but get loaded later. That is a little unfortunate, since PMIC GLINK (among other things) is running on one of these. My Windows Dev Kit 2023 (same SoC) doesn't balk this way, both boot the same Ubuntu image (more or less). Analysis has shown that I have a firmware hook for initramfs on the wdk2023 which provides the firmware images in the initrd.img file. This is the version I hacked up for the x13s, which appears to load the desired firmwares as intended:

#!/bin/sh

set -e

PREREQ=""

prereqs()
{
        echo "$PREREQ"
}

case \\$1 in
# get pre-requisites
prereqs)
        prereqs
        exit 0
        ;;
esac

. /usr/share/initramfs-tools/hook-functions

# Define a list of firmware files to be included
FIRMWARE_FILES="\
qcom/sc8280xp/LENOVO/21BX/qcadsp8280.mbn \
qcom/sc8280xp/LENOVO/21BX/qccdsp8280.mbn \
qcom/sc8280xp/LENOVO/21BX/qcdxkmsuc8280.mbn \
qcom/sc8280xp/LENOVO/21BX/qcvss8280.mbn \
qcom/sc8280xp/LENOVO/21BX/qcslpi8280.mbn \
qcom/a660_sqe.fw \
qcom/a660_gmu.bin"

# Copy each firmware file to initramfs
for file in $FIRMWARE_FILES; do
    dir=$(dirname "$file")
    mkdir -p "${DESTDIR}/lib/firmware/${dir}"
    cp "/lib/firmware/${file}" "${DESTDIR}/lib/firmware/${dir}/"
done

It needs to be copied into /etc/initramfs-tools/hooks/ and be set as executable. initramfs -u -k all includes the files into the initrd images.

with best regards

Jens

x13s-firmware

I am planning to run a MariaDB instance for a scientific database.  My past test use was using Armbian on an 8 GB Raspberry pi 4B, with MariaDB, and it worked very well, until the SD card failed.

Any thoughts or points of caution before attempting this would be appreciated.  I have generally had a very positive experience with Armbian so far.

UEFI can be way how to boot it maybe

i am new user of armbian and i really like it. so i am experimenting with it a little. yesterday i successfully installed armbian on one of my old laptops in the lab (Armbian Bullseye with XFCE desktop with kernel 5.15.y released on feb 27, 2023), so currently it boots from internal hard drive. today i wanted to try another image, so i wanted to do the same thing:

1. boot from USB key

2. download the new image on USB key

3. run

xzcat armbian.img.xz | dd of=/dev/sda status=progress

4. reboot laptop (to new system)

but the step 1 failed - instead of booting the system from USB key (yes - i selected the USB key on laptop start), system started from the laptop's hard drive.

i think, this is not expected behavior. or am i missing something and it is really a feature? 🙂

anyway - thanks for the project. it gives my old laptops new life

mirek

I use the Image "Armbian_22.08.5_Uefi-x86_bullseye_current_5.15.73"

The /tmp/switch_kernel.log says the following

linux-image-current-x86=22.08.6 linux-dtb-current-x86=22.08.6

Thx in advance