Can someone help me keep updating linux kernel without breaking zfs-dkms?

I attach the output of `apt` just in case:

```sh

$ sudo apt install linux-image-current-meson64
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
linux-image-current-meson64 is already the newest version (26.8.3).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
2 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] 
Setting up zfs-dkms (2.4.4-1arter97~ubuntu24.04.1) ...
Removing old zfs-2.4.4 DKMS files...
Deleting module zfs-2.4.4 completely from the DKMS tree.
Loading new zfs-2.4.4 DKMS files...
It is likely that 6.18.34-current-meson64 belongs to a chroot's host
Building for 6.18.44-current-meson64
Building initial module for 6.18.44-current-meson64
configure: error: 
                *** This kernel does not include the required loadable module
                *** support!
                ***
                *** To build OpenZFS as a loadable Linux kernel module
                *** enable loadable module support by setting
                *** `CONFIG_MODULES=y` in the kernel configuration and run
                *** `make modules_prepare` in the Linux source tree.
                ***
                *** If you don't intend to enable loadable kernel module
                *** support, please compile OpenZFS as a Linux kernel built-in.
                ***
                *** Prepare the Linux source tree by running `make prepare`,
                *** use the OpenZFS `--enable-linux-builtin` configure option,
                *** copy the OpenZFS sources into the Linux source tree using
                *** `./copy-builtin <linux source directory>`,
                *** set `CONFIG_ZFS=y` in the kernel configuration and compile
                *** kernel as usual.
                        
Error! Bad return status for module build on kernel: 6.18.44-current-meson64 (aarch64)
Consult /var/lib/dkms/zfs/2.4.4/build/make.log for more information.
dpkg: error processing package zfs-dkms (--configure):
 installed zfs-dkms package post-installation script subprocess returned error exit status 10
Setting up linux-image-current-meson64 (26.8.3) ...
Armbian 'linux-image-current-meson64' for '6.18.44-current-meson64': 'postinst' starting.
 * dkms: running auto installation service for kernel 6.18.44-current-meson64
The kernel is be built without module signing facility, modules won't be signed

Running the pre_build script:
checking for gawk... gawk
checking metadata... META file

checking build system type... aarch64-unknown-linux-gnu
checking host system type... aarch64-unknown-linux-gnu
checking target system type... aarch64-unknown-linux-gnu
checking whether to enable maintainer-specific portions of Makefiles... no
checking whether make supports nested variables... yes
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a race-free mkdir -p... /usr/bin/mkdir -p
checking whether make sets $(MAKE)... yes
checking how to create a pax tar archive... gnutar
checking how to print strings... printf
checking whether make supports the include directive... yes (GNU style)
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether the compiler supports GNU C... yes
checking whether gcc accepts -g... yes
checking for gcc option to enable C11 features... none needed
checking whether gcc understands -c and -o together... yes
checking dependency style of gcc... none
checking for a sed that does not truncate output... /usr/bin/sed
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for fgrep... /usr/bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking how to convert aarch64-unknown-linux-gnu file names to aarch64-unknown-linux-gnu format... func_convert_file_noop
checking how to convert aarch64-unknown-linux-gnu file names to toolchain format... func_convert_file_noop
checking for /usr/bin/ld option to reload object files... -r
checking for file... file
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for ar... ar
checking for archiver @FILE support... @
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for sysroot... no
checking for a working dd... /usr/bin/dd
checking how to truncate binary pipes... /usr/bin/dd bs=4096 count=1
checking for mt... mt
checking if mt is a manifest tool... no
checking for stdio.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for strings.h... yes
checking for sys/stat.h... yes
checking for sys/types.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate

checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking for gcc... (cached) gcc
checking whether the compiler supports GNU C... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to enable C11 features... (cached) none needed
checking whether gcc understands -c and -o together... (cached) yes
checking dependency style of gcc... (cached) none
checking whether ln -s works... yes
checking for pkg-config... no
checking dependency style of gcc... none
checking whether to build with code coverage support... no
checking how to create a pax tar archive... (cached) gnutar
checking zfs author... OpenZFS
checking zfs license... CDDL
checking whether NLS is requested... yes
checking for msgfmt... no
checking for gmsgfmt... :
checking for xgettext... no
checking for msgmerge... no
checking for ld... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for shared library run path origin... done
checking 32-bit host C ABI... no
checking for the common suffixes of directories in the library search path... lib,lib
checking zfs config... kernel
checking the number of available CPUs... 4
checking whether gcc supports -Wno-clobbered... yes
checking whether gcc supports -Winfinite-recursion... yes
checking whether gcc supports -Winfinite-recursion... yes
checking whether gcc supports -Wno-atomic-alignment... yes
checking whether gcc supports -Wimplicit-fallthrough... yes
checking whether gcc supports -Wframe-larger-than=<size>... yes
checking whether gcc supports -Wno-format-truncation... yes
checking whether gcc supports -Wno-format-zero-length... yes
checking whether gcc supports -Wno-format-zero-length... yes
checking whether gcc supports -Wformat-overflow... yes
checking whether gcc supports -fno-omit-frame-pointer... yes
checking whether gcc supports -fno-ipa-sra... yes
checking whether gcc supports -fno-ipa-sra... yes
checking whether to build with -fsanitize=address support... no
checking whether to build with -fsanitize=undefined support... no
checking whether assembler supports .cfi_negate_ra_state... yes
checking for system type (linux-gnu)... Linux
checking for conflicting environment variables... done
checking for python3... python3
checking for python version... 3.12
checking for python platform... linux
checking for GNU default python prefix... ${prefix}
checking for GNU default python exec_prefix... ${exec_prefix}
checking for python script directory (pythondir)... ${PYTHON_PREFIX}/lib/python3.12/site-packages
checking for python extension module directory (pyexecdir)... ${PYTHON_EXEC_PREFIX}/lib/python3.12/site-packages
configure: Disabling pyzfs for kernel/srpm config
checking whether to enable pyzfs: ... no
checking for sed --in-place... --in-place
checking for cppcheck... no
checking for shellcheck... no
checking for checkbashisms... no
checking for parallel... no
checking kernel source and build directories... done

checking kernel source directory... /lib/modules/6.18.44-current-meson64/build
checking kernel build directory... /lib/modules/6.18.44-current-meson64/build
checking kernel source version... 6.18.44-current-meson64
checking for kernel config option compatibility... done
checking whether CONFIG_MODULES is defined... no
configure: error: 
                *** This kernel does not include the required loadable module
                *** support!
                ***
                *** To build OpenZFS as a loadable Linux kernel module
                *** enable loadable module support by setting
                *** `CONFIG_MODULES=y` in the kernel configuration and run
                *** `make modules_prepare` in the Linux source tree.
                ***
                *** If you don't intend to enable loadable kernel module
                *** support, please compile OpenZFS as a Linux kernel built-in.
                ***
                *** Prepare the Linux source tree by running `make prepare`,
                *** use the OpenZFS `--enable-linux-builtin` configure option,
                *** copy the OpenZFS sources into the Linux source tree using
                *** `./copy-builtin <linux source directory>`,
                *** set `CONFIG_ZFS=y` in the kernel configuration and compile
                *** kernel as usual.
                        

Building module:
Cleaning build area...(bad exit status: 2)
make -j4 KERNELRELEASE=6.18.44-current-meson64...(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.18.44-current-meson64 (aarch64)
Consult /var/lib/dkms/zfs/2.4.4/build/make.log for more information.
dkms autoinstall on 6.18.44-current-meson64/aarch64 failed for zfs(10)
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
 * dkms: autoinstall for kernel 6.18.44-current-meson64                                                                                                 [fail] 
run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
update-initramfs: Generating /boot/initrd.img-6.18.44-current-meson64
update-initramfs: Armbian: Converting to u-boot format: /boot/uInitrd-6.18.44-current-meson64
Image Name:   uInitrd
Created:      Thu Sep  3 20:09:09 2026
Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
Data Size:    29057340 Bytes = 28376.31 KiB = 27.71 MiB
Load Address: 00000000
Entry Point:  00000000
update-initramfs: Armbian: Symlinking /boot/uInitrd-6.18.44-current-meson64 to /boot/uInitrd
'/boot/uInitrd' -> 'uInitrd-6.18.44-current-meson64'
update-initramfs: Armbian: done.
dpkg: error processing package linux-image-current-meson64 (--configure):
 installed linux-image-current-meson64 package post-installation script subprocess returned error exit status 11
Processing triggers for initramfs-tools (0.142ubuntu25.8) ...
update-initramfs: Generating /boot/initrd.img-6.18.44-current-meson64
update-initramfs: Armbian: Converting to u-boot format: /boot/uInitrd-6.18.44-current-meson64
Image Name:   uInitrd
Created:      Thu Sep  3 20:09:40 2026
Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
Data Size:    29056210 Bytes = 28375.21 KiB = 27.71 MiB
Load Address: 00000000
Entry Point:  00000000
update-initramfs: Armbian: Symlinking /boot/uInitrd-6.18.44-current-meson64 to /boot/uInitrd
'/boot/uInitrd' -> 'uInitrd-6.18.44-current-meson64'
update-initramfs: Armbian: done.
Errors were encountered while processing:
 zfs-dkms
 linux-image-current-meson64
E: Sub-process /usr/bin/dpkg returned an error code (1)

```

Best Regards,

Gunwoo Gim

With freshly installed armbian (commit id: d9fb61be0) I created a new uboot config file:

./compile.sh uboot-config BOARD=orangepizeroplus BRANCH=current SHARE_LOG=yes

This creates the file: ./output/defconfig-uboot-orangepizeroplus-current

But the command:

./compile.sh uboot BOARD=orangepizeroplus BRANCH=current SHARE_LOG=yes

does not compile uboot, it just touches ./output/debs/linux-u-boot-orangepizeroplus-current_26.11.0-trunk_arm64__2026.07-*.deb file.

Do I miss something?

Do I have to copy the file ./output/defconfig-uboot-orangepizeroplus-current to a place in ./userpatches?

Thanks in advance,

Hackbeere

log-uboot-config-f8ff6bc1-9053-44de-932f-fc933aa65f54.log log-uboot-289bad48-a6fa-43df-9b92-ac809bac3c2d.log

earlier I booted up the board (Radxa Dragon Q8B) when it prompted to reboot & update and I allowed it. The update took uncharacteristically long. The OS is running off an SD card. There is no SSD or eMMC installed.

Turns out it wiped the install clean. There was about 20 GB of free space prior to the update, now there's 46 GB.

For some reason the user itself and the wifi login are still there, but everything in the home directory is gone. Installed applications and the driver for the wireless card are gone. Chrome add-ons are still there, but reset. The Downloads folder now has Armbian_26.8.1_Radxa-dragon-q8b_resolute_vendor_7.0.11_gnome_desktop.img.xz, which wasn't there before.

I didn't lose anything important, just 60 hrs of savegames and a godot project I don't really care about.

Could I stupidly have triggered this somehow? I've been running Armbian on three other boards and nothing like this happened on those. So if it's not my fault this might be a Q8B-specific problem.

Thanks for any input

Kind regards

Edit1: Just noticed there's now another update requiring restart. Weird.

Edit2: Alright, this one was pain free. I'm a bit paranoid now :,-)

I flashed EDK2 to SPI and  I am able to enter the UEFI menu and change things, but it seems that u-boot takes over the boot process to actually boot the kernel.

I also built a custom resolute image using the command below which I flashed to SDCard:
 

Quote

./compile.sh BOARD=rock-5-itx RELEASE=resolute BUILD_DESKTOP=no BUILD_MINIMAL=yes EXT=uefi-edk2-rk3588 UEFI_EDK2_BOARD_ID=rock-5-itx  CLEAN_LEVEL=make

Then I added a Grub entry for the SDCard image with this custom build but when I boot it it shows that u-boot is being used not UEFI. 

Quote

[Sep23 19:43] Booting Linux on physical CPU 0x0000000000 [0x412fd050]
[  +0.000000] Linux version 7.1.13-edge-rockchip64 (build@armbian) (aarch64-linux-gnu-gcc (Ubuntu 13.3.0-6ubuntu2~24.04.1) 13.3.0, GNU ld (GNU Binutils for Ubuntu) 2.42) #4 SMP PREEMPT Wed Sep  2 12:32:39 UTC 2026
[  +0.000000] KASLR enabled
[  +0.000000] Machine model: Radxa ROCK 5 ITX
[  +0.000000] efi: EFI v2.11 by Das U-Boot

The default Grub boot is from emmc with an EFI FAT32, /boot EXT4, and / F2FS which is  armbian trixie, and it works well - but  with u-boot so I am trying to test how booting via pure UEFI will work so I can migrate to a pure UEFI setup on EMMC as the default - but the custom image is not  preventing u-boot from taking over the boot sequence. I am not sure  I need to flash something to emmc first to prevent u-boot because u-boot takes over before grub and then the custom image starts to boot. 

Q: What do I need to do to switch to a pure UEFI boot sequence?

I am trying to determine whether this is expected behavior or a bug/ordering issue in Armbian's armbian-ramlog.

My /etc/systemd/journald.conf contains:

Storage=persistent

SystemMaxUse=20M

Persistent journal storage is available:

/var/log/journal -> /var/log.hdd/journal

and /var/log.hdd is mounted read-write.

However, after every reboot, systemd-journald initially writes to /run/log/journal.

I verified this directly:

sudo ls -l /proc/$(pidof systemd-journald)/fd | grep journal

Immediately after boot I get:

33 -> /run/log/journal/d1d6e2a49fd24499b90cb6d5198cb70e/system.journal

So journald is actually holding the runtime journal open.

The system has armbian-ramlog enabled. Its unit contains:

Before=rsyslog.service sysinit.target syslog.target RequiresMountsFor=/var/log /var/log.hdd

Interestingly, running this manually:

sudo journalctl --flush

immediately switches journald to persistent storage.

Afterwards:

sudo ls -l /proc/$(pidof systemd-journald)/fd | grep journal

shows:

33 -> /var/log.hdd/journal/d1d6e2a49fd24499b90cb6d5198cb70e/system.journal 34 -> /var/log.hdd/journal/d1d6e2a49fd24499b90cb6d5198cb70e/user-1000.journal

So the persistent filesystem is definitely accessible and writable.

This makes me wonder:

Is armbian-ramlog causing systemd-journald to remain on /run/log/journal after boot, or is this simply an ordering issue involving systemd-journal-flush.service?

In other words, should armbian-ramlog allow/trigger the journal flush automatically once /var/log.hdd is mounted?

Any insight from the Armbian side would be appreciated.

They will boot up to a text console where I can configure Wifi, root password, intitial user name, and locale. After that, they state that they are starting the desktop  or running some script and continue no further. That I see uniform and reliable failure across the images and the devices make me think that I may be doing something wrong. But I cannot find some step documented somewhere that I am missing. 

I am using a power supply that is also branded Orange Pi capable of up to 100 watts on both units. I am able to run other OS images on both units, but not Armbian. Is there some trick or additional step that is required for these to successfully boot up? 

Images tried on the Zero 3:

• Armbian 26.11.0 XFCE
• Armbian 26.11.0 Minimal

Images tried on the 6 plus:

• Armbian 26.8.3 Minimal
• Armbian 26.8.3 GNOME
• Armbian 26.8.3 KDE

I urgently need help, as I am on the verge of throwing my Khadas out the window.
I bought a used Khadas Vim3L HTPC Kit (S905D3) and want to use it for Navidrome and Audiobookshelf.
The FLAC files are located on an external 2.5" WD Elements hard drive, first I intended to format this hard drive to ext4 and set it up in the setup process but it doesnt work and the first thing now is to setup the system,i will add the hd later.

Currently, the Vim boots into CoreELEC (which appears to be installed on the internal storage of the vim).
Im a total noob and thats my first vim / Board.
 

I just can't seem to get it to work; no matter what I do, it always boots into CoreELEC.

I have flashed the recommended Debian 13 (Trixie) → Minimal / CLI image (Armbian_25.11.1_Khadas-vim3l_trixie_current_6.12.58_minimal.oowow.img.xz) using balenaEtcher—onto two different SD cards as well as a USB stick, and I am attempting to boot from them.
I have tried various key combinations, but nothing works.
 

For example, when I attempt the method suggested by ChatGPT:

Recovery Button Method

Unplug the power supply

Insert the SD card

Hold down the FUNCTION button

Briefly press RESET

Continue holding the FUNCTION button for another 2–3 seconds
 

I briefly see the Khadas logo, and then it reboots; this process then gets stuck in a loop.

I tried using three different power adapters and usb-c cables, thinking that might be the issue... but it was always the same result. I tried a different SD card and various USB sticks and different formats always the same outcome. As a test, I even selected a different image just to see if it would progress any further, but again, I just saw the Khadas logo followed by a boot loop. As soon as I remove the SD card or USB stick, it boots back into CoreELEC from the internal storage.
 

Now I’ve read on another site that I shouldn't use BalenaEtcher, but instead format the SD card/USB stick to FAT32 and place the image in the root directory. I did exactly that and tested it on both the USB 3.0 and 2.0 ports and with the SD because it boots before usb ?!?.

Then: disconnect the power supply.

Insert the USB stick.

Connect HDMI + keyboard.

Hold down the FUNCTION button.

Plug in the power supply.

Immediately press RESET briefly.

Continue holding FUNCTION for another 3–5 seconds.

And once again, I only see the Khadas logo for a sec and am stuck in a boot loop.
 

Could someone please give me a direct link or the name of the correct image, and tell me the right key combination I need to press or let me know what I'm doing wrong?
A step by step guide for an idiot would be great and sorry if the question is stupid, i watched youtube videos, read in the forum etc. but i dont get it, i need really your help.

Thank you

I had previously downloaded the Armbian_community_26.11.0-trunk.52_Orangepi5-max_resolute_edge_7.2.6_gnome_desktop.img file and flashed it to an SD card, when it came up it ran a provisioning script allowing me to add my timezone, user definition, etc.

Shouldn't this execute on all images the same way? Is there some way to manually execute it if it doesn't kick off automatically?? I flashed this SD card twice with this image and it was the same both times, I think the image is broken...

tayolepuqi.txt

Here you go — two solid solderless picks:
 

1. Adafruit MOSFET Driver #5648 (the clean reference — genuine logic-level AO3406, flyback diode already onboard, jumper-friendly header, ~$4):

https://www.adafruit.com/product/5648

Also stocked via resellers (Mouser/DigiKey/Pimoroni) if you search "Adafruit 5648."
 

2. Generic 3.3 V-trigger dual-MOSFET board (cheapest, everywhere, screw terminals — fully solderless; just add a flyback diode across the fan since these usually omit it):

https://www.amazon.com/ANMBEST-Trigger-Adjustment-Electronic-Control/dp/B08TW9RB49
 

If that exact listing has rotated (Amazon ASINs come and go), search "DC 5V-36V MOSFET trigger switch module 3.3V" — you want one whose description explicitly says 3.3 V trigger and, ideally, names the FET (AO3400 / IRLZ44N).
 

For the fan itself, either module handles it with room to spare — a 5 V 40 mm fan pulls well under 0.2 A, and these are rated for amps.

 

Verified straight from your local Armbian build tree — yes. The linux-rockchip64-edge.config (the branch .217 runs) ships all three of the relevant symbols:
 

CONFIG_THERMAL_EMULATION=y ← yes, emul_temp works CONFIG_THERMAL_GOV_BANG_BANG=y ← bonus: the ideal on/off governor is available CONFIG_SENSORS_GPIO_FAN=m ← the fan driver (module)

(current also has THERMAL_EMULATION=y, so any edge/current board is covered.)
 

Answer for Pi Claude: Go ahead and use the emul_temp method in Phase A —
 

Compile-verified — exit 0, pull-none pinctrl and all (rockchip,pins = <1 RK_PA4 GPIO &pcfg_pull_none>, trips 75000/10000, active). So the overlay in this post is a real, building artifact, not a sketch.
 

And ha — a real cooking show it is: you're watching me taste-test the sauce (compile it) before it goes to the pass. Here's the plated dish. 👨‍🍳
 

CPU Cooling: Automatic Fan Control on RK3588 (Orange Pi 5 / 5B) — Armbian / Debian 13

If your Orange Pi 5/5B fan runs flat-out all the time (or not at all), here's how to let the kernel run it — silent at idle, full blast under load — with no daemon and no script. One cheap switch module plus a small device-tree overlay.
 

1) The hardware — a switch module + your fan
 

You can't drive a fan motor straight off a GPIO pin. A GPIO is a ~few-milliamp logic output; a fan pulls 100–150 mA and would damage the pin. So the GPIO signals a tiny logic-level MOSFET module that switches the fan's 5 V. Two solderless picks:

Generic "3.3 V trigger" MOSFET module — screw terminals, ~$1–2, everywhere. Easiest. The listing must say 3.3 V trigger and ideally names the FET (AO3400 / IRLZ44N). These usually omit the flyback diode, so add a 1N5819/1N4001 across the fan.

Adafruit #5648 ($4) — cleanest; guaranteed logic-level with the flyback diode onboard. Add its JST-PH 3-pin→female-socket cable ($1.25) for a solderless header tap.

2) Wiring (low-side switch)
 

Fan + → 5V (header pin 2 or 4) Fan − → module output GPIO → module signal / trigger input GND → module GND (common ground is essential) Flyback diode across the fan if your module lacks one (band → +5V side)
 

3) The overlay — this is what makes it automatic
 

Save as rk3588-gpio-fan.dts. It turns the fan on at 75 °C, off at 65 °C on the big-core sensors (which heat first), safely below the 85 °C throttle. The pull-none pinctrl matches how mainline wires fan GPIOs:

/dts-v1/; /plugin/; #include <dt-bindings/gpio/gpio.h> #include <dt-bindings/pinctrl/rockchip.h> #include <dt-bindings/thermal/thermal.h> / { fan: gpio-fan { compatible = "gpio-fan"; pinctrl-names = "default"; pinctrl-0 = <&fan_en>; gpios = <&gpio1 RK_PA4 GPIO_ACTIVE_HIGH>; /* set to YOUR pin (both here and below) */ gpio-fan,speed-map = <0 0>, <5000 1>; #cooling-cells = <2>; }; }; &pinctrl { fan { fan_en: fan-en { rockchip,pins = <1 RK_PA4 RK_FUNC_GPIO &pcfg_pull_none>; }; }; }; &bigcore0_thermal { polling-delay = <2000>; trips { fan0: fan0 { temperature = <75000>; hysteresis = <10000>; type = "active"; }; }; cooling-maps { m { trip = <&fan0>; cooling-device = <&fan THERMAL_NO_LIMIT THERMAL_NO_LIMIT>; }; }; }; &bigcore2_thermal { polling-delay = <2000>; trips { fan2: fan2 { temperature = <75000>; hysteresis = <10000>; type = "active"; }; }; cooling-maps { m { trip = <&fan2>; cooling-device = <&fan THERMAL_NO_LIMIT THERMAL_NO_LIMIT>; }; }; };

Change both RK_PA4 references to the header pin you actually wired to (GPIO1_A4 is just the example — group A = 0, B = 1, C = 2, D = 3, so GPIO1_D6 = RK_PD6).
 

4) Install & verify
 

sudo armbian-add-overlay rk3588-gpio-fan.dts sudo reboot # fan registered as a cooling device? (driver is a module; load it if the grep is empty) grep -l gpio-fan /sys/class/thermal/cooling_device*/type || sudo modprobe gpio-fan # watch it react under load: watch -n1 'cat /sys/class/thermal/cooling_device*/cur_state' stress-ng --cpu 8 --timeout 120s

cur_state flips to 1 as the die crosses 75 °C and back to 0 below 65 °C.

Set-points: 75 on / 65 off (10 °C hysteresis) keeps a 10 °C guard below the 85 °C throttle, so the chip never has to slow down. Thanks to Boardcon (EM3588) for the field-proven numbers from real 24/7 industrial enclosures.

Tested on: Orange Pi 5B — Armbian <edge ver> — kernel <uname -r>

(This will ship built-in on the new distro — but it works on stock Armbian today.)
 

No sandbagging

defcom5-rockchip

I have a Raspberry 5 that I have armbian 13 minimal cli installed on a sd card, I have other means if it makes a difference. I have an ssd connected to a radxa penta sata hat that i have successfully installed with editing the config file, also have an ssd installed and shows. First time around i used the imager to install an exact copy of the os on the ssd which also meant exact copies of labels and uuid's, which i learned the hard way is not so good, got it to boot on the ssd but not update properly. Now I tried "sudo armbian -install" and i got the result below. I'm been informed right the raspberry 5 does not support grub nor board uboot. Instead of another goose chase with AI i'm hoping to guidance how to properly install it. I want to be able to update the os on the ssd, that is my next milestone...

 

zack@rpi5b:~$ cat /etc/os-release

PRETTY_NAME="Armbian 26.8.1 trixie"

NAME="Debian GNU/Linux"

VERSION_ID="13"

VERSION="13 (trixie)"

VERSION_CODENAME=trixie

DEBIAN_VERSION_FULL=13.6

ID=debian

HOME_URL="https://www.armbian.com"

SUPPORT_URL="https://forum.armbian.com"

BUG_REPORT_URL="https://www.armbian.com/bugs"

ARMBIAN_PRETTY_NAME="Armbian 26.8.1 trixie"

zack@rpi5b:~$ uname -r

6.18.42-current-bcm2711

zack@rpi5b:~$ lspci

0001:00:00.0 PCI bridge: Broadcom Inc. and subsidiaries BCM2712 PCIe Bridge (rev 30)

0001:01:00.0 SATA controller: JMicron Technology Corp. JMB58x AHCI SATA controller

0002:00:00.0 PCI bridge: Broadcom Inc. and subsidiaries BCM2712 PCIe Bridge (rev 30)

0002:01:00.0 Ethernet controller: Raspberry Pi Ltd RP1 PCIe 2.0 South Bridge

zack@rpi5b:~$ lsblk -o NAME,FSTYPE,LABEL,PARTUUID,SIZE,MOUNTPOINTS

NAME        FSTYPE LABEL      PARTUUID                               SIZE MOUNTPOINTS

sda                                                                111.8G

└─sda1      exfat  boot                                            111.8G

mmcblk0                                                              7.3G

├─mmcblk0p1 vfat   RPICFG     3f631019-01                            512M /boot/firmware

└─mmcblk0p2 ext4   armbi_root 3f631019-02                            6.6G /var/log.hdd

                                                                          /

zram0       swap                                                     3.9G [SWAP]

zram1       ext4   log2ram                                            50M /var/log

zram2                                                                  0B

zack@rpi5b:~$

I'm new to this game,being mostly a (French) software dev doing backend Node.js.

Recently I bought a 21.5" Android kiosk display from Beelta, the T2100AA, to build a custom kiosk for my company. The Android build is bloated, so I wanted something cleaner.

I started looking into porting Armbian to this display. Inside there's an SBC identified as a Shimeta AIoT-3568A. There's no Linux support for this board, and the manufacturer wasn't willing to provide any documentation.

I started digging with Claude and worked through most of the blockers in under a day. Here's what I found — and possibly a path forward for other Shimeta-based boards too (more on that below).

Hardware

• SoC: Rockchip RK3568 (quad Cortex-A55, Mali-G52, unused 0.8 TOPS NPU)
• Based on the reference rockchip,rk3568-evb1-ddr4-v10 design; the stock firmware actually bundles several board variants (EVB1/3568HV/3568S/3568ST/3568WP) selected at boot via androidboot.dtb_idx
• DDR4, DDR init confirmed working with the stock rk3568_ddr_1560MHz idbloader (MiniLoaderAll.bin)
• PMIC: RK809 (i2c 0x20) with integrated audio codec
• 21.5" Full HD (1920×1080) touch panel — this is an all-in-one panel/SBC unit, not a bare dev board

Analysis method
Full generic Android firmware image extracted (RKFW→RKAF) plus a live dump (via adb root) from a unit actually running in production, giving both /sys/firmware/fdt and the real boot/dtbo/vbmeta partitions to cross-check against.

Display pipeline — the core blocker

• RK3568 DSI0 → GM8775C (DSI-to-dual-channel-LVDS bridge, "CORPRO") → dual-LVDS → 21.5" FHD panel
• RK3568 has no native dual-channel LVDS output (needed above ~1440×900), hence the GM8775C bridge chip on the PCB. It's configured purely through generic DSI commands from the RK3568 (no separate I2C control) — the full init sequence has been extracted from the vendor DTB (panel-init-sequence). Timing is confirmed stable at 1920×1080@60 (148.5 MHz pixel clock).

Everything else is straightforward / mainline-ready

• Backlight: standard pwm-backlight, PWM + GPIO enable, nothing to write
• Touch: pure USB, ILITEK controller, standard HID multitouch — zero driver work
• Ethernet: dual GMAC with RTL8211F PHY, mature mainline support
• WiFi/BT: AW-NM43438 (Broadcom/AmpaK BCM43438/AP6212 rebrand) — just needs the correct firmware/nvram blobs pulled from the vendor partition, brcmfmac/hci_bcm handle the rest
• Power button, headset jack, IR receiver: all standard or non-blocking

Getting a working base

• The Odroid M1 mainline image worked out of the box for HDMI, USB, etc., but had no LVDS output and no networking. With Claude's help, I:
• Overwrote the Odroid idbloader with the one from the stock Android install
• Built a DTB for the AIoT-3568A to get networking working, which let me switch to SSH over Ethernet for much faster iteration
• Wrote (well, Claude wrote...) the MIPI-DSI-to-LVDS bridge driver for the Corpro GM8775C, plus the LVDS panel config — resulting in a fully working panel with backlight

Reboot issue and solution

Board freezes completely and power-cycles (not a clean reboot, not a kernel panic) roughly 10 minutes after power-on, regardless of load, distro, or kernel config. Confirmed independently by another user on the same board family in the youyeetoo forum back in 2023 — including a report that it happens even while stuck in U-Boot, before Linux ever runs.

What we ruled out (with evidence, on Armbian mainline kernel 6.18)

• SoC-internal software watchdog (dw_wdt): disabled, masked, or actively fed via ftrace-confirmed kicks right up to the crash — innocent either way
• Thermal: never critical (43–58 °C)
• CPU/RAM/storage stress in isolation (stress-ng): all pass
• Two different SD cards, freshly reformatted: same symptom
• systemd timers (fstrim/tmpfiles/hwclock): masked, no effect
• Main DC input power, scoped on a Rigol DP832: no anomalous current draw correlated with the crash
• Ethernet fully unplugged, WiFi/BT unloaded: no effect
• PMIC (RK809) regulator config: confirmed exact match against the live vendor DTB, node by node
• ext4 commit interval: tested multiple values, inconclusive

Decisive test:

powered on, then issued a software reboot at ~5 min uptime. The board still crashed at ~10 min from the original power-on, not restarted from the software reboot. This proves the timer is driven by something external to Linux, tied to physical power, not the OS.

Root cause: undocumented external supervisor MCU

These boards carry a secondary microcontroller separate from the RK3568/RK3588/RK3399 main SoC — an STM8S00K3, shown in the vendor device tree as:

dts
mcuinf@62 {
   compatible = "smdtmcu,STM8S00K3"; status = "okay"; reg = <0x62>;
};

Sitting on an I2C bus (i2c5 @ 0x62 on the 3568A), invisible to any mainline Linux driver. ShiMeta's own product documentation confirms its purpose: "Watchdog Timer Configuration: To ensure 24/7 autonomous uptime, the MCU runs a hardware watchdog. If the main Android system freezes, the MCU automatically forces a hard reset to recover the device."

Reverse-engineered by tracing I2C traffic (ftrace events/i2c) on the stock Android vendor image, where a kernel thread literally named mcu proc (kthread, PPID 2 — not killable from userspace) talks to the MCU continuously:

I2C transactionFrequencyPurpose

None of this exists in mainline Linux, so on any custom OS (Armbian, or any non-vendor image) the MCU eventually decides the AP never booted / has hung, and fires the hardware reset it's designed to perform.

What actually fixes it:

• Write reg 0x51 = 0x33, read back via 0xD1 → 0x33 (once, ~25s after power-on (triggered by vendor binary /system/bin/mcu_tool notify_power_on)  : Tells the MCU "AP booted successfully" — disarms the initial boot-timeout
• Write 0x80, read 1 byte (every 3.04s, continuous) : Status poll (0x00 = nominal, 0xAA = observed once feeding stops)
• Write [0x33, 0xAB] (2 bytes) (every 11.15s, continuous) : Periodic heartbeat/feed from the AP

This script fixes sends the correct frames:

# one-shot, early in boot
i2cset -y 5 0x62 0x51 0x33

# then, forever, two independent loops:
while true; do i2cget -y 5 0x62 0x80 >/dev/null; sleep 3; done &
while true; do i2cset -y 5 0x62 0x33 0xAB >/dev/null; sleep 10; done &

Thomas.

# ramlog OFF
sudo systemctl stop armbian-ramlog
sudo sed -i 's/^ENABLED=.*/ENABLED=false/' /etc/default/armbian-ramlog
sudo systemctl restart rsyslog
sudo journalctl --flush

# ramlog ON
sudo sed -i 's/^ENABLED=.*/ENABLED=true/' /etc/default/armbian-ramlog
sudo systemctl start armbian-ramlog
sudo systemctl restart rsyslog

The vendor OMX component reports the proprietary colour format 0x7f000002 through a malformed port-format enumeration, so gst-omx can't build a negotiation map. You can chase that a long way. Don't.

libOmxVdec.so is a wrapper over libvdecoder.so, and that lower library is what actually owns the decode surfaces. VideoPicture.nBufFd is a genuine dma_buf fd per frame, and the matching headers already ship in /usr/include on the stock image. Import it with drmPrimeFDToHandle, scan it out on a DRM plane, done — the broken layer isn't on the path at all.

Same board, same clip:

CPUthreads

omxh264dec ! videoconvert ! ximagesink174% (+16.5% X)10

zero-copy DRM~8%1

cedarzcdec ! kmssink (GStreamer element)12–13%4

No kernel patches, no custom modules, no SDK build. There's a GStreamer element so existing pipelines work unchanged:

gst-launch-1.0 filesrc location=clip.mp4 ! qtdemux ! h264parse ! cedarzcdec ! kmssink

Code, plus a writeup of the undocumented API traps that cost me the most time (GetVeOpsS takes an argument and has no prototype; use CdcMemOpen not CdcMemSetup; modetest -p hides the fence properties unless you set the atomic client cap):

https://github.com/skamagedon/a733-zero-copy

Tested on A733/sun60iw2, Bullseye, kernel 5.15.147, H.264 only. The same libcedarc family ships on A133/H616/H618/T527 and this likely transfers, but I haven't tested those — VideoPicture's layout is guarded by VE_SUPPORT_DECODER_LBC_MODE, so check your own vbasetype.h.

board: firefly rk3399-pc pro ( yeah I know it’s old, but so am I!)

os: armbian Debian trixie

kernel: 6.18.35

Bear with me, last time I touched Linux, lilo and xfree86 were things…

I installed the community supported rk3399-firefly as I didn’t find a better match for the pro. Most of the hardware worked with the major exception of the audio. No problem, the rk3399-roc-plus.dts had the correct audio for the board all I needed to do was switch the audio portion into the rk3399-firefly.dts  (though other aspects including just booting stopped me from directly switching to the plus dts). I mistakenly cloned and compiled from the mainline (I put the ‘no!’ In noob). It of course didnt work. Next I cloned and compiled (without changing anything) from the armbian repository. Again it would not boot.

So here is the embarrassing question. Where is the repository that contains the dts files that are actually used to build the dtb files in the active images? My last try was github.com/armbian/rockchip.git .

Im pretty sure I’m cloning, compiling and switching the dtb correctly, just can’t find the right source material!

Again, thank you in advance.

-J

After install the AP is shown in the login screen:

WiFi AP:      SSID: (BPi), channel 7 (2442 MHz), width: 20 MHz, center1: 2442 MHz

When I try to connect from my mobile phone it either says "connecting without Internet".

The output in syslog is then:

026-07-06T12:35:02.645970+02:00 bananapipro hostapd: wlan0: STA 22:50:7b:ac:e3:2e IEEE 802.11: associated
2026-07-06T12:35:02.690671+02:00 bananapipro hostapd: wlan0: STA 22:50:7b:ac:e3:2e RADIUS: starting accounting session 500A81EDD1715454
2026-07-06T12:35:02.691497+02:00 bananapipro hostapd: wlan0: STA 22:50:7b:ac:e3:2e WPA: pairwise key handshake completed (RSN)

Ort otherwise the phone just says "cannot connect".

My netplan file is as follows:

network:
  version: 2
  renderer: networkd
  ethernets:
    end0:
      dhcp4: false
      dhcp6: false
      macaddress: "02:cd:08:83:3c:f3"
    wlan0:
      dhcp4: false
      dhcp6: false
  bridges:
    br0:
      addresses:
      - "192.168.178.29/24"
      nameservers:
        addresses:
        - 9.9.9.9
        - 1.1.1.1
      interfaces:
      - wlan0
      - end0
      routes:
      - metric: 200
        to: default
        via: "192.168.178.1"

The hostapd.conf is:

interface=wlan0
driver=nl80211
ssid=BPi
hw_mode=g
channel=7
wmm_enabled=0
macaddr_acl=0
auth_algs=1
ignore_broadcast_ssid=0
wpa=2
wpa_passphrase=secret
wpa_key_mgmt=WPA-PSK
wpa_pairwise=TKIP
rsn_pairwise=CCMP

ctrl_interface=/var/run/hostapd
ctrl_interface_group=0

ieee80211n=1
ht_capab=[DSSS_CK-40][HT20+]

preamble=1

bridge=br0

The output of network list is:

root@bananapipro:/etc/hostapd# networkctl list
IDX LINK  TYPE     OPERATIONAL SETUP     
  1 lo    loopback carrier     unmanaged
  2 end0  ether    enslaved    configured
  3 br0   bridge   routable    configured
  4 wlan0 wlan     enslaved    failed   

Does anybody have an idea where to look further for a solution? As I have an AP running on my other BananaPiPro (Bookworm CLI / Networkmanager, manual config, not bridged) it cannot be a complete HW limitation, I think.

First post here.

I'm fairly new with Armbian.  I have a LibreComputer Le Potato that I want to use for Home Assistant.  To avoid all the hassle of setting up Home Assistant with docker, I used the Armbian imager to install the Armbian 26.2.1 Home Assistant on an SD card.

Once the SD card was flashed, I put it into the Le Potato board.  The board starts up fine, asks for the root password, creates a new user and so on.

Later on, the Preparing Home Assistant Supervised window appears.  However, after the first round to 100% I get a "RTNETLINK answers: Invalid argument" on the screen.  The preparation goes on and on, moving the progress bar over and over to 100%.  But the installation seems to never stop. 

See the image attached for the error I get.

Anyone any idea?

Best,

--Geert

a total beginner tia

I did a bit of an unorthodox installation, I wanted to install on an nvme drive, and instead of using a microSD and then copying the system with armbian-install, since I didn't have a working microsd available I did a "manual" installation, I flashed rkspi_loader.img into the SPI taken from the armbian image and then flashed the armbian img directly to the nvme drive with an usb adapter from my PC.

All is good and working fine, but I'm wondering if I'm missing any settings that gets applied during the armbian-install process (are there any?) that are specific for nvme.

And regarding Zram, ram2log and other optimizations that armbian uses for SDs, how should I configure them?

My setup is a Radxa Rock 5B with 8GB of RAM with a Samsung 970 evo plus, should I disable zram and create a swapfile? Any other setting to look out for?

I think my hdparm -t speed is a bit low, around 1300 MB/s.

Thanks in advance

I would get a red power light, but none of the others.

I was finally able to boot `Armbian_25.8.1_Orangepi5-plus_noble_vendor_6.1.115_gnome_desktop` after grabbing it from archive.armbian.com, but I'm wondering what the problem may have been? I'd like to get onto the latest Armbian but of course don't want to start having boot issues all over again.

Edit: Looks like I may have run into this known issue: https://github.com/armbian/build/issues/9897

It appears there's a fixed image available for now while the issue gets resolved properly: https://github.com/jeffcrouse/orangepi5plus-armbian-image

FYI, there might be an issue with old, slow hardware. Yesterday I installed the minimal Ubuntu 26.04 current 6.18.24 downloaded from https://armbian.com/boards/bananapi on my old Banana Pi on an similar old 8GB SD by sandisk.

It runs normaly, but cannot set up the end0 during booting.

Doing an "ip link set end0 up" manually on cli afterwards immediately activated end0, so my solution was using an script to do this command after booting. The AI aiding me thinks it's just the slow hardware causing a timeout when it should set up the interface during booting.

Just wanted to let you know.

Apparently the Link Star H68K is hardware equivalent to the Hinlink H68K.

I'm trying to install one of the community supported Armbian images (Debian Trixie, Ubuntu 26.04)  for the Hinlink onto a Link Star H68K, using the RKDevTool from the Seeed Studio wiki. And failing.

The only image that loads into RKDevTool is the Lubuntu 20.04 from the Seeed Studio wiki. It's just a tad out of date.

Any pointers on getting a more up-to-date OS installed would be most welcome. AFAIK my device is OG, not V2.

I've also tried booting from TF card, but the device refuses to boot at all with a TF card inserted. Some Googling suggests that a current TF card is too fast for the device and causes boot failure. Card spec is Class 10 / UHS-1. I've sourced some Sandisk Class 4 cards and currently awaiting delivery, to see if that solves the boot issue and gives me a path to transfer the OS from TF to EMMC.

Any thoughts/advice most welcome.

I just installed Armbian on my OrangePi 5, but I can't get it to recognize the NVMe drive. I've tried the official OrangePi Ubuntu distro, and it detects the NVMe without any issues. However, when using Armbian, it simply doesn't show up.

I'm not sure what to do at this point. I would really like to use Armbian, but it seems unable to detect the NVMe on this particular device. Interestingly, I have another OrangePi 5 Pro where I installed Armbian, and it recognizes the NVMe and works perfectly fine — but not on the standard OrangePi 5.

Does anyone know how to fix this issue, or can you recommend a good alternative?

Quote

root@orangepi5:~# lsblk
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
mtdblock0    31:0    0    16M  0 disk
mmcblk0     179:0    0 238.8G  0 disk
└─mmcblk0p1 179:1    0 236.3G  0 part /var/log.hdd
                                      /
zram0       252:0    0   7.8G  0 disk [SWAP]
zram1       252:1    0    50M  0 disk /var/log
zram2       252:2    0     0B  0 disk
 

Thank you in advance.

I really like it on my desktop, 

so now I want to use Guix system as the OS for my Orange Pi 5 Pro as well.  

The problem is, the Arm distro for Guix System is only available for Generic EFI 

and I didn't have the money to buy a Orange Pi 6 Plus.  

But I figure, why not install Armbian on SD card and have it boot Guix System on the SSD?

Is that possible and if so, how would I achieve that?  

So far I've been able to 'dd' the guix system install ISO onto the SSD.  

It seems to have an iso9660 filesystem.  

I was about to create a swapfile and then the above command happened.  

Where can I find swapon?

I tried the Trixie-current-minimal at first, but that didn't want to start for whatever reason.  

Should I try installing an Ubuntu one?  

I'm clueless.  

[edit]

I managed to get Trixie-current-minimal working. Same issue.  

Anyway, always interested in crypto throughput, and ARM64 crypto extensions have always put up some good results. So, a little weird when I saw that AES XTS performance seems decent, but CBC seems awful?

user@odroidm2:~$ /sbin/cryptsetup benchmark
        aes-cbc        128b       178.5 MiB/s       162.7 MiB/s
        aes-cbc        256b       135.0 MiB/s       211.3 MiB/s
        aes-xts        256b      1399.5 MiB/s      1407.2 MiB/s
        aes-xts        512b      1186.7 MiB/s      1198.7 MiB/s

Checking /proc/crypto seems to indicate that rk_crypto2 is being used, so on a whim, I tried doing this:

user@odroidm2:~$ sudo rmmod rk_crypto2
[sudo] password for user: 
user@odroidm2:~$ /sbin/cryptsetup benchmark
        aes-cbc        128b       880.4 MiB/s      1722.3 MiB/s
        aes-cbc        256b       755.8 MiB/s      1247.9 MiB/s
        aes-xts        256b      1225.2 MiB/s      1422.5 MiB/s
        aes-xts        512b      1088.9 MiB/s      1123.7 MiB/s

Huh.

XTS speed is about the same, but CBC is an order of magnitude faster? Might not even be worth using it?

Anyway, before I go digging, just curious if anyone's seen this or can reproduce on a Rockchip other than an RK3588S2?

Logs from Armbian 26.2.1 (noble/current) -> https://paste.armbian.com/mudojesajo

First time poster, so immediately confused with the tags. tag was required but could not find one for Radxa Rock 4se. 

I want to get the raspberry pi camera working in ubuntu on my rock 4se. I tested with the image radxa provides and the hardware works. Then i switched to the community ubuntu image and it seems i need an overlay to tell the linux device tree that the rpi camera is there. Can anybody help me with this?

Thanks!

The same addresses work perfectly on Rocky Linux; any thoughts on what I might be overlooking?

I decided to format the card and put my own image of Armbian on the card using the Armbian imager. when installed the card would no longer boot. lights on board but black screen no HDMI output.

I tried several different SD cards and different images all with the same result (A1 Sandisk cards)

Eventually I tried a hail mary and put an Armbian image on a really old USB thumb stick and it immediately booted and worked just fine.

I tried putting the OrangePi os on one of my SD cards for kicks and it gets HDMI output but is just stuck on the OrangePi splash screen

When I insert the SD card while running on the USB thumb drive image I can view the partitions and see that the OS image is correctly installed on the SD. 

I can't figure out where I'm going wrong, am I having a bootloader compatability issue with armbian?

Thanks for armbian on Banana PI, it is really wonderful compared to official releases.

I installed the image "Armbian_community_26.2.0-trunk.904_Bananapim2ultra_trixie_current_6.18.29_minimal.img.xz" on my Banana PI M2 Berry (there is no image for this type), and all is working wonderfully well ... except rebooting or shutting down the Banana PI.

When typing reboot, all services stop but the screen blocks on

systemd-shutdown[1]: Rebooting.

and it never reboots.

It does the same for shutdown, stuck on same kind of message.

Could you help me please ?

Regards

I would like to install Armbian with Virtualbox, so that I can run Home Assistant (HA) in a VM environment (Intel chip .vdi) - yes, no container.

Would chose this image  "Armbian 25.11.1 Minimal / IOT 6.1 kernel" (rolling release)

Installing Virtualbox with:

sudo apt install virtualbox

Is this possible?

Best wishes, Greg

Links:

https://www.home-assistant.io/installation/linux/

https://wiki.debian.org/VirtualBox

https://www.armbian.com/orange-pi-5-plus/

I had to run:

```sh

 sudo apt install linux-image-current-meson64=25.8.1 linux-headers-current-meson64=25.8.1 linux-dtb-current-meson64=25.8.1 && sudo dpkg-reconfigure zfs-dkms

```

I couldn't look in to the problem, because I was busy doing something else when I was just upgrading every package on the system.

I had to prioritize quickly fixing it before another user arrives so I just reverted the suspicious packages (the three I mentioned in the title)

I can't look into the problem now either because the computer is not being used by me alone..

1. There are no linux-tools packages build -- which is fair enough, I'm probably in a minority. Some parts of the tools directories are culled during a cleaning process for the headers, I can see that

2. I am happy to copy over the kernel source and build on the device, but this is a patched vendor kernel. Can I just rsync across `cache/sources/linux-kernel-worktree`? Is that the patched kernel source tree?

3. There are some old allusions in the forums to using armbian-config to get sources -- I'm guessing that's long deprecated

4. Would it be appropriate at some point to create a .deb for the actual kernel sources, just in case -- or even, ideally, the linux-tools packages themselves?

I am very happy to invest effort into helping make this happen, but I am starting from cold into this fairly complex build infrastructure, so any help or pointers I'd be extremely grateful.

I have Banana Pi BPI-M2-Ultra v1.1 board with A40i chip

I download img from armbian "Armbian_community_25.2.0-trunk.86_Bananapim2ultra_noble_current_6.6.62_xfce_desktop.img.xz" and write it on microSD(HC) 32Gb A1 10 class with balena etcher.

Then plug it in a board and turn on.

Here is uart debug output

11:14:41.598 ->
11:14:42.396 -> U-Boot SPL 2024.01-armbian-2024.01-S866c-Pb2fe-H0429-V0f9a-Bda0a-R448a (Nov 17 2024 - 03:22:36 +0000)
11:14:42.429 -> DRAM: 2048 MiB
11:14:42.429 -> Trying to boot from MMC1
11:14:42.728 -> ns16550_serial serial@1c28000: pinctrl_select_state_full: uclass_get_device_by_phandle_id: err=-19
11:14:42.728 -> 
11:14:42.728 -> 
11:14:42.728 -> U-Boot 2024.01-armbian-2024.01-S866c-Pb2fe-H0429-V0f9a-Bda0a-R448a (Nov 17 2024 - 03:22:36 +0000) Allwinner Technology
11:14:42.761 -> 
11:14:42.761 -> CPU:   Allwinner R40 (SUN8I 1701)
11:14:42.761 -> Model: Banana Pi BPI-M2-Ultra
11:14:42.761 -> DRAM:  2 GiB
11:14:42.795 -> sunxi-pinctrl pinctrl@1c20800: pinctrl_select_state_full: pinctrl_config_one: err=-38
11:14:42.795 -> Core:  66 devices, 23 uclasses, devicetree: separate
11:14:42.828 -> WDT:   Not starting watchdog@1c20c90
11:14:42.828 -> MMC:   gpio_sunxi pinctrl@1c20800: pinctrl_select_state_full: pinctrl_config_one: err=-38
11:14:42.828 -> mmc@1c0f000: 0, mmc@1c10000: 2, mmc@1c11000: 1
11:14:42.861 -> Loading Environment from FAT... Unable to use mmc 0:1...
11:14:42.861 -> In:    serial@1c28000
11:14:42.894 -> Out:   serial@1c28000
11:14:42.894 -> Err:   serial@1c28000
11:14:42.927 -> Net:   eth0: ethernet@1c50000
11:14:42.927 -> starting USB...
11:14:42.927 -> Bus usb@1c19000: Port not available.
11:14:42.961 -> Bus usb@1c19400: Port not available.
11:14:42.961 -> Bus usb@1c1c000: Port not available.
11:14:42.961 -> Bus usb@1c1c400: Port not available.
11:14:42.994 -> Autoboot in 1 seconds, press <Space> to stop
11:14:43.991 -> switch to partitions #0, OK
11:14:44.024 -> mmc0 is current device
11:14:44.024 -> Scanning mmc 0:1...
11:14:44.024 -> Found U-Boot script /boot/boot.scr
11:14:44.024 -> 5442 bytes read in 3 ms (1.7 MiB/s)
11:14:44.024 -> ## Executing script at 43100000
11:14:44.057 -> U-boot loaded from SD
11:14:44.057 -> 154 bytes read in 3 ms (49.8 KiB/s)
11:14:44.057 -> Unknown command ':' - try 'help'
11:14:44.655 -> 14529165 bytes read in 604 ms (22.9 MiB/s)
11:14:45.053 -> 8992608 bytes read in 375 ms (22.9 MiB/s)
11:14:45.053 -> Found mainline kernel configuration
11:14:45.053 -> 38747 bytes read in 7 ms (5.3 MiB/s)
11:14:45.053 -> Load fdt: /boot/dtb/sun8i-r40-bananapi-m2-ultra.dtb
11:14:45.086 -> Working FDT set to 43000000
11:14:45.086 -> Failed to load '/boot/dtb/overlay/sun8i-r40-fixup.scr'
11:14:45.086 -> Kernel image @ 0x42000000 [ 0x000000 - 0x893760 ]
11:14:45.086 -> ## Loading init Ramdisk from Legacy Image at 43400000 ...
11:14:45.086 ->    Image Name:   uInitrd
11:14:45.086 ->    Image Type:   ARM Linux RAMDisk Image (gzip compressed)
11:14:45.120 ->    Data Size:    14529101 Bytes = 13.9 MiB
11:14:45.120 ->    Load Address: 00000000
11:14:45.120 ->    Entry Point:  00000000
11:14:45.120 ->    Verifying Checksum ... OK
11:14:45.219 -> ## Flattened Device Tree blob at 43000000
11:14:45.219 ->    Booting using the fdt blob at 0x43000000
11:14:45.252 -> Working FDT set to 43000000
11:14:45.252 ->    Loading Ramdisk to 49224000, end 49fff24d ... OK
11:14:45.286 ->    Loading Device Tree to 491b2000, end 49223fff ... OK
11:14:45.286 -> Working FDT set to 491b2000
11:14:45.286 -> 
11:14:45.286 -> Starting kernel ...
11:14:45.286 -> 
11:14:50.135 -> done.
11:14:50.135 -> Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
11:14:50.135 -> Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems

so thats all. it stops on it.

Before it i tryed to use ubuntu MATE 16.04 (from sd card and install to emmc). and it works

any ideas how to run armbian?

I want to use Linux on my oneplus 8t and I am excited to find that armbian has official support for this.  But before I install armbian on my phone, I am wondering if I can restore to android after I install armbian.

I have another question which may be a bit offtopic: how hard is it to add support for oneplus 8t to Mobile NixOS?

Thanks in advance.

1) Getting the drive to mount at startup. (I thought internal and SATA drives did by default but this seems not to be the case

2) Creating a share with guest permissions.

I understand that I should edit the fstb file using the UUID of the disk. I obtained the UUID but there are two listed. One for the whole disk and one for the partition. (Note The hard drive was formatted exFat in windows before being attached as whatever i did i couldn't write to it, something to do with having root permissions. I even tried taking ownership but without success)

here is the blkid command output

/dev/sda1: LABEL="data" UUID="74E3-01BF" BLOCK_SIZE="512" TYPE="exfat" PARTUUID="6c2b2d10-01"
/dev/mmcblk0p1: LABEL="armbi_root" UUID="69fa8a60-c365-456c-8d0a-7889eb4a3713" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="c0cf2841-01"
/dev/zram1: LABEL="log2ram" UUID="7269c460-6283-4374-bcba-be885c806c25" BLOCK_SIZE="4096" TYPE="ext4"
/dev/zram0: UUID="7a1deaea-e26c-45f2-9a73-ac43c6bf301e" TYPE="swap"

 here is my fstb file

UUID=69fa8a60-c365-456c-8d0a-7889eb4a3713 / ext4 defaults,,commit=120,errors=remount-ro 0 1
tmpfs /tmp tmpfs defaults,nosuid 0 0
UUID=74E3-01BF /mnt/data exfat defaults 0 2

I used the disk UUID rather than the partition however the disk is no longer visible when armbian starts. previously it was visible but unmounted. there is an entry in the /mnt/ folder called data. I was also unsure if I should enter the filetype  exfat in the fstb entry as all other example show ext4 before defaults.

Please can someone put me right and suggest the correct entry in the smb.conf file. I believe it should be something like this :-

path = /media/kealy/data

available = yes

valid users = kealy

read only = no

browsable = yes

public = yes

writable = yes

 However as there is an entry in the /mnt/ folder should path be /mnt/kealy/data instead?

Finally where should the user password go in the smb.conf or is public= yes is this necessary. The device will only be used in a family household to upload their photos from their phones.

root@mouse:/home/james# lscpu | head -5
Architecture:                            aarch64
CPU op-mode(s):                          32-bit, 64-bit
Byte Order:                              Little Endian
CPU(s):                                  8
On-line CPU(s) list:                     0-7

root@mouse:/home/james# free -h
               total        used        free      shared  buff/cache   available
Mem:            30Gi       4.1Gi        18Gi       723Mi       9.2Gi        26Gi
Swap:           15Gi          0B        15Gi

root@mouse:/home/james# df -h .
Filesystem      Size  Used Avail Use% Mounted on
/dev/sda1       800G  322G  475G  41% /home
root@mouse:/home/james# lspci
0000:00:00.0 PCI bridge: Rockchip Electronics Co., Ltd RK3588 (rev 01)
0000:01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / RX 540X/550/550X] (rev c7)
0000:01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Baffin HDMI/DP Audio [Radeon RX 550 640SP / RX 560/560X]
0002:20:00.0 PCI bridge: Rockchip Electronics Co., Ltd RK3588 (rev 01)
0002:21:00.0 Network controller: Intel Corporation Wi-Fi 6E(802.11ax) AX210/AX1675* 2x2 [Typhoon Peak] (rev 1a)
0003:30:00.0 PCI bridge: Rockchip Electronics Co., Ltd RK3588 (rev 01)
0003:31:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 05)
0004:40:00.0 PCI bridge: Rockchip Electronics Co., Ltd RK3588 (rev 01)
0004:41:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 05)
root@mouse:/home/james# modprobe amdgpu
modprobe: FATAL: Module amdgpu not found in directory /lib/modules/6.18.16-current-rockchip64

root@mouse:/home/james#

I want to use the SOC as a photo repository for a family member so they can use PhotoSync app to transfer their photos as a home NAS. I have attached a 1Tb 2.5" hard drive and was goin to set up and SMB share but notice in Armbian Config a software package for OwnCloud which looks perfect as it can be accessed via a web browser.

I have tried installing OwnCloud from Armbian Config and it installs docker but then fails downloading the Owncloud package. The error is:

Unable to find image 'owncloud/server:latest' locally

docker: Error response from daemon: manifest for owncloud/server:latestnot found: manifest unknown:manifest unknown

I've tried running Docker pull and it appears to have downloaded something but the file is only around 4kb. Ive also tried downloading an image from OwnCloudeu server but it cant find a ARMv7 image.

I'm wondering if having a hard drive attached means the daemon is looking for the image on the local drive???

could someone please point me in the right direction to installing Owncloud

Also I assume the standard install, docker runs a container in the Armbian file system. Obviously I want the storage to be on the 1Tb hard drive. can you choose a storage location in the Owncloud setup?

many thanks

It seems there is an issue with iptables in the 6.18.10-current-meson64 kernel.

I can't start Docker because of this.

```

~# iptables -L

modprobe: FATAL: Module ip_tables not found in directory /lib/modules/6.18.10-current-meson64
iptables v1.8.11 (legacy): can't initialize iptables table `filter': Table does not exist (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
```

As I run a docker version 28.X.X, it does not support nftable. (Cannot upgrade at the moment).

What can I do to solve the problem ?

Thanks
 

Debian 13 (Trixie) is installed op the orangepi and I try to install Docker and homeassistant with the armbian-config utility.

Unfortunately, this is not working.

First I try to install Docker. ( tested with docker minimal and docker engine). I receive this information : 

Package docker-ce is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

Package docker-ce-cli is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'docker-ce' has no installation candidate
E: Package 'docker-ce-cli' has no installation candidate
E: Unable to locate package containerd.io
E: Couldn't find any package by glob 'containerd.io'
E: Couldn't find any package by regex 'containerd.io'
E: Unable to locate package docker-buildx-plugin
E: Unable to locate package docker-compose-plugin
Failed to enable unit: Unit docker.service does not exist
Failed to start docker.service: Unit docker.service not found.
 

When I try to install homeassistant I receive following  :

Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 homeassistant-supervised : PreDepends: docker-ce but it is not installable
E: Unable to correct problems, you have held broken packages.
E: The following information from --solver 3.0 may provide additional context:
   Unable to satisfy dependencies. Reached two conflicting decisions:
   1. homeassistant-supervised:arm64=3.0.0 is selected for install
   2. homeassistant-supervised:arm64 PreDepends docker-ce
      but none of the choices are installable:
      [no choices]

What is wrong ? Please help
 

Armbian website says OnePlus 8t is supported with "standard support" (here: https://www.armbian.com/oneplus-kebab/). I dont know what that includes as it is not very clear.

Will one be able to do calls, send messages etc on that phone with Armbian (e.g. similar to sailfish os or ubuntu touch on their respective supported devices). I am basically asking if cellular, wifi, camera etc works fine.

I'm about to acquire Orange Pi Zero 2W for my audio project. I have read some of the forum posts related to  the SOC's native I2S, and I'd like to know if those problems mentioned in the posts have been resolved in the new kernel? Meaning that users don't have to write and compile their own device tree overlay and kernel mode driver? My project require a full duplex I2S with the CODEC as the master. Nothing fancy, just 2 channels in and 2 channels out.

Hope someone can help clear the doubts so that I know for sure I will not be buying what I can not use. Thanks

I was looking to activate the NPU on my beagley-AI chip, running armbian, and I couldn't find how.

This chip as a NPU (AM67A) on the SOC from TexasInstruments (https://api.pageplace.de/preview/DT0400.9783895766572_A50990365/preview-9783895766572_A50990365.pdf).

The loading of the NPU seems to have failed:
 

mesg | grep remoteproc
[    8.461511] k3-dsp-rproc 7e000000.dsp: configured DSP for remoteproc mode
[    8.461728] remoteproc remoteproc0: 7e000000.dsp is available
[    8.461868] k3-dsp-rproc 7e000000.dsp: register pm nitifiers in remoteproc mode
[    8.464448] k3-dsp-rproc 7e200000.dsp: configured DSP for remoteproc mode
[    8.465124] remoteproc remoteproc0: Direct firmware load for j722s-c71_0-fw failed with error -2
[    8.465164] remoteproc remoteproc0: powering up 7e000000.dsp
[    8.465271] remoteproc remoteproc0: Direct firmware load for j722s-c71_0-fw failed with error -2
[    8.465285] remoteproc remoteproc0: request_firmware failed: -2
[    8.480524] remoteproc remoteproc1: 7e200000.dsp is available
[    8.480658] k3-dsp-rproc 7e200000.dsp: register pm nitifiers in remoteproc mode
[    8.482329] remoteproc remoteproc1: Direct firmware load for j722s-c71_1-fw failed with error -2
[    8.482375] remoteproc remoteproc1: powering up 7e200000.dsp
[    8.482488] remoteproc remoteproc1: Direct firmware load for j722s-c71_1-fw failed with error -2
[    8.482501] remoteproc remoteproc1: request_firmware failed: -2
[    8.964763] platform 79000000.r5f: configured R5F for remoteproc mode
[    9.047514] remoteproc remoteproc2: 79000000.r5f is available
[    9.048055] remoteproc remoteproc2: Direct firmware load for j722s-mcu-r5f0_0-fw failed with error -2
[    9.048099] remoteproc remoteproc2: powering up 79000000.r5f
[    9.048222] remoteproc remoteproc2: Direct firmware load for j722s-mcu-r5f0_0-fw failed with error -2
[    9.048241] remoteproc remoteproc2: request_firmware failed: -2
[    9.234391] remoteproc remoteproc3: 78000000.r5f is available
[    9.234578] remoteproc remoteproc3: attaching to 78000000.r5f
[    9.402138] remoteproc remoteproc3: remote processor 78000000.r5f is now attached
[    9.505240] platform 78400000.r5f: configured R5F for remoteproc mode
[    9.547946] remoteproc remoteproc4: 78400000.r5f is available
[    9.548359] remoteproc remoteproc4: Direct firmware load for j722s-main-r5f0_0-fw failed with error -2
[    9.548400] remoteproc remoteproc4: powering up 78400000.r5f
[    9.548505] remoteproc remoteproc4: Direct firmware load for j722s-main-r5f0_0-fw failed with error -2
[    9.548521] remoteproc remoteproc4: request_firmware failed: -2
[   15.281722] Modules linked in: algif_aead rpmsg_ctrl rpmsg_char cc33xx mac80211 libarc4 snd_soc_simple_card cc33xx_sdio snd_soc_simple_card_utils crct10dif_ce panel_simple pci_endpoint_test e5010_jpeg_enc cpufreq_dt pvrsrvkm(O) pwm_fan at24 rti_wdt cfg80211 ti_k3_r5_remoteproc btti_uart bluetooth snd_soc_davinci_mcasp snd_soc_ti_udma wave5 rpi_panel_attiny_regulator snd_soc_ti_edma snd_soc_hdmi_codec snd_soc_ti_sdma videobuf2_dma_contig v4l2_mem2mem videobuf2_memops videobuf2_v4l2 videobuf2_common snd_soc_core snd_pcm_dmaengine tc358762 snd_pcm videodev ti_k3_dsp_remoteproc ti_k3_common mc snd_timer snd omap_mailbox optee_rng efi_pstore nfnetlink
[   15.285991] Modules linked in: algif_aead rpmsg_ctrl rpmsg_char cc33xx mac80211 libarc4 snd_soc_simple_card cc33xx_sdio snd_soc_simple_card_utils crct10dif_ce panel_simple pci_endpoint_test e5010_jpeg_enc cpufreq_dt pvrsrvkm(O) pwm_fan at24 rti_wdt cfg80211 ti_k3_r5_remoteproc btti_uart bluetooth snd_soc_davinci_mcasp snd_soc_ti_udma wave5 rpi_panel_attiny_regulator snd_soc_ti_edma snd_soc_hdmi_codec snd_soc_ti_sdma videobuf2_dma_contig v4l2_mem2mem videobuf2_memops videobuf2_v4l2 videobuf2_common snd_soc_core snd_pcm_dmaengine tc358762 snd_pcm videodev ti_k3_dsp_remoteproc ti_k3_common mc snd_timer snd omap_mailbox optee_rng efi_pstore nfnetlink

The usual lspci doesn't contain much:

lspci
00:00.0 PCI bridge: Texas Instruments Device b010

How should I proceed to make it work?

Thanks!

This prevents installation of kernel headers required for DKMS modules, out-of-tree drivers, or any kernel module compilation.

## Steps to Reproduce
1. Flash the latest Armbian image for `rock-3a` (branch: `current`) from the official download page.
2. Boot the device and connect to the network.
3. Run `apt update` with any standard mirror (e.g., `mirrors.tuna.tsinghua.edu.cn`, `mirror.yandex.ru`).
4. Check installed kernel version:
   ```bash
   uname -r
   # Output: 6.18.8-current-rockchip64
   ```
5. Check available headers:
   ```bash
   apt policy linux-headers-current-rockchip64
   ```

## Actual Behavior
- Installed image packages:
  ```
  linux-image-current-rockchip64  26.2.1  [installed,local]
  linux-dtb-current-rockchip64    26.2.1  [installed,local]
  armbian-bsp-cli-rock-3a-current 26.2.1  [installed]
  ```
- `apt policy` output for headers:
  ```
  linux-headers-current-rockchip64:
    Installed: (none)
    Candidate: 25.11.2
    Version table:
       25.11.2 500
          500 http://<mirror>/armbian noble/main arm64 Packages
       ... (no 26.2.1 available)
  ```

## Expected Behavior
- The `linux-headers-current-rockchip64` package version **26.2.1** should be available in the `current` branch repository, matching the kernel shipped in the image.
- Alternatively, the image should ship with packages that are already published and synchronized in the public repository.

## Impact
- Users cannot install DKMS modules (ZFS, VirtualBox, WiFi drivers, etc.).
- Development workflows requiring kernel headers are blocked.
- Confusion for users performing a "clean install" who expect a consistent system.

## System Information
- **Board:** Radxa Rock 3A
- **Armbian version:** 26.2.1 (from image filename/release)
- **Kernel:** 6.18.8-current-rockchip64
- **APT branch:** `current`
- **Distribution:** Ubuntu Noble (24.04)
- **Mirrors tested:** 
  - `http://mirrors.tuna.tsinghua.edu.cn/armbian`
  - `http://mirror.yandex.ru/mirrors/armbian/apt`
  - `http://apt.armbian.com` (redirector)

## Possible Causes (hypothesis)
1. **Publishing race condition:** The image was built after `linux-image-26.2.1` was compiled but before `linux-headers-26.2.1` was published to the public repository.
2. **Branch mislabeling:** Version 26.2.1 may have been moved to `edge` after the image was built, but the image metadata was not updated.
3. **Mirror sync delay:** The master repository has the package, but mirrors have not yet synchronized (though multiple mirrors were tested over several days).

Have some problem with Cubietrack

Sometime boot some time not

Kernel 

setenv fdtfile sun7i-a20-cubietruck.dtb

# safe low addresses
setenv kernel_addr_r  0x42000000
setenv fdt_addr_r     0x43000000
setenv ramdisk_addr_r 0x44000000

# limit relocations
setenv fdt_high 0x47f00000
setenv initrd_high 0x47f00000

mmc dev 0
mmc rescan

setenv bootargs "console=ttyS0,115200 console=tty0 ignore_loglevel loglevel=8 \
root=/dev/mmcblk0p1 rootwait rootfstype=ext4 rw \
panic=10 consoleblank=0 net.ifnames=0 biosdevname=0 enforcing=0 \
nosmp mem=1024M clk_ignore_unused"

echo ">> Boot device: mmc 0:1 ext4"

if ext4load mmc 0:1 ${kernel_addr_r} /boot/zImage; then
  echo ">> Kernel loaded"
else
  echo "### ERROR: /boot/zImage not found"
  reset
fi

if ext4load mmc 0:1 ${fdt_addr_r} /boot/dtb/${fdtfile}; then
  echo ">> DTB loaded"
else
  echo "### ERROR: dtb not found"
  reset
fi

setenv initrd_arg "-"
if ext4load mmc 0:1 ${ramdisk_addr_r} /boot/uInitrd; then
  setenv initrd_arg ${ramdisk_addr_r}
fi

bootz ${kernel_addr_r} ${initrd_arg} ${fdt_addr_r}

root@volumio:~# cd /boot
root@volumio:/boot# ls -all
total 35200
drwxr-xr-x  7 root root    4096 Mar  4 11:44 .
drwxr-xr-x 23 root root    4096 Mar  4 09:17 ..
drwxr-xr-x  2 root root    4096 Feb 28  2016 bin
-rw-r--r--  1 root root     966 Mar  4 12:04 boot.cmd
-rw-r--r--  1 root root    1038 Mar  4 12:04 boot.scr
-rw-r--r--  1 root root  101188 Jan 22  2017 config-4.4.44
-rw-r--r--  1 root root  101262 Apr 24  2016 config-4.4.8
-rw-r--r--  1 root root  133815 Mar 21  2019 config-5.0.2-sunxi
-rw-r--r--  1 root root  159559 Mar  1 17:03 config-6.6.75-legacy-sunxi
drwxr-xr-x  2 root root    4096 Mar  4 09:16 dtb
drwxr-xr-x  3 root root   12288 Sep 12  2019 dtb-5.0.2-sunxi
drwxr-xr-x  3 root root   12288 Feb  7 18:41 dtb-6.6.75-legacy-sunxi
drwxr-xr-x  2 root root    4096 Feb 28  2016 dtb.old
-rw-r--r--  1 root root       0 Mar  3 17:32 .next
lrwxrwxrwx  1 root root      24 Mar  3 16:54 script.bin -> /boot/bin/cubietruck.bin
-rw-------  1 root root 1464739 Jan 22  2017 System.map-4.4.44
-rw-------  1 root root 1460350 Apr 24  2016 System.map-4.4.8
-rw-r--r--  1 root root 2376380 Mar 21  2019 System.map-5.0.2-sunxi
-rw-r--r--  1 root root 2957247 Mar  1 17:03 System.map-6.6.75-legacy-sunxi
-rw-------  1 root root 3384008 Jan 22  2017 vmlinuz-4.4.44
-rw-------  1 root root 3367664 Apr 24  2016 vmlinuz-4.4.8
-rwxr-xr-x  1 root root 4810496 Mar 21  2019 vmlinuz-5.0.2-sunxi
-rw-r--r--  1 root root 7824568 Mar  1 17:03 vmlinuz-6.6.75-legacy-sunxi
-rw-r--r--  1 root root 7824568 Mar  4 09:16 zImage
root@volumio:/boot# uname -a
Linux volumio 6.6.75-legacy-sunxi #3 SMP PREEMPT Sat Feb  1 17:37:57 UTC 2025 armv7l GNU/Linux
root@volumio:/boot#

I wanted to install the Armbian 26.2.1 Minimal / IOT  to an Ordoid HC2 (using the XU4 distro).

Download ok - sha hash is ok - balena etcher ok - startup - ok.

Problem: When I log in the first time with "root", the "1234" as first password is not accepted.

Also, PUTTY warns that ths ssh of the armbian uses only "Diffie-hellmann-group1-sha1" which (for PUTTY) is a bit unsecure.

Any idea about the password issue?

the hardware in question: PCIe_TO_2-CH_SATA_HAT+

In expectation for the Rock 4D forum to arrive I am posting  my issue here:

The Rock 4D works and all is well
The two SATA drives work over USB to SATA adapters - that is not ideal in the long term IMHO
The HAT just arrived and i have no doubt in my mind that it can be defective in any way - i assume it is 100% operational.

But when i connect it and plug the power in the Rock 4D boots, everything else works as usual, but the HAT just sits there without any signal.

My questions:
1. How do i query the eeprom via the pins 27 & 28 (ID_SD & ID_SC), do i just enable the i2c_6 overlay?
2. What then?

I queried the ahci module with: `modinfo ahci` but it is both a built in and i suspect it does not support my device anyway?

Looking forward to try help get this nice board supported on Armbian for other FPC equipped devices.

Thanks!

I tried to install Armbian 26.2.0-trunk (https://www.armbian.com/nanopi-neo/#collapse-widget-5-0-0-0) on a NanoPi NEO Core SBC. I used Armbian Imager and wrote the latest official image (the only one available) to the SD card.

After writing the image, I see only one partition on the SD card named armbi_root. When I insert the card into the device and power it on, nothing happens — there are no boot messages or logs. I think the image is missing a bootloader.

So my questions are:

1) If I’m right that the bootloader is missing, how can I add a bootloader to the image?

2) How can I apply OverlayFS to this setup?

3) Do you have a link to a good article or tutorial on these topics?

Thanks in advance!

Being new around here I figured to drop one message here first...

So, i have this Radxa Rock 4D SBC and i am quite impressed with it

Me being me and SBC being what it is, yada... yada, i now have this hat+ from Waveshare - it is an dual SATA to PCIe adapter.

It was designed for the Raspberry pi 5 obviously but Radxa has since started putting those FPC connectors on and i really would appreciate a 24/7 NAS with a SBC footprint...

Long story short, it does not work out of the box - i have no doubt the product is okay it's just the HAT fails to initiate the OS and register.

It reportedly has an eprom with data on it but my guess is it has to have a dtb overlay active and my rock 4D lacks anything in that regard (a "sata" in the overlay name)

My issues?
1. Where is the Rock 4D forum or where do i post this issue best to?

 

It runs a software called HamClock automagically.... BUT WAIT! There is MORE!

You can exit that app and run other applications... Providing you have a mouse & keyboard (because I am a native WinWeenie) or keyboard if you are a Linux forever personage.

It also has a wireless interface that I would like to configure so it doesn't have to have an Ethernet tail tied to a port on our ISP router. I would rather it was mounted to a HDMI TV or monitor. So, I need the keyboard (and because I am a longtime WinWeenie and rodent dependent) mouse to reconfigure it.

I would like to have it use a USB Logitech Unifier Nano dongle with wireless keyboard/mouse.

By the way, the brilliant man that came up with this computer is trudging the same path I am, fighting cancer. His fight has gotten so tough he has shut down his company. I hope he gets better.

Is there already a compiled binary for this with directions,,. or do I have to master the dark arts of programming routines, subroutines, interrupts, memory fetches, writes, threads and all that then compile it into something the machine understands? Please understand I didn't even take typing in high school, so college was a real bear.... When I was in high school Jobs and Wozniak were still dumpster diving behind Xerox-Park Corporation and Radio Shack.

Any takers on this one?

Thanks in advance,

Dave, The-Other-One

I started a typical armbian build folder, as per:

https://github.com/armbian/build?tab=readme-ov-file#quick-start

But then I got this error:

[🌱] Build host OS release [ zena ]
[🌱] Build host architecture [ amd64 ]
[💥] error! [ Unsupported build system: 'zena'  ]

I know that Mint 22.3 was released just last month, but I needed something in the new Linux kernel.

I can use Mint 22.2 in another computer (where armbian is working OK)... but what is the typical delay for a new Linux Mint to become supported?

Then I tried with $ sudo apt install docker.io , and got a little further:

$ ./compile.sh 
[🚸] Docker is installed, but not usable [ can't use Docker; check your Docker config / groups / etc ]
[💥] Problem detected [ Docker installed but not usable ]
[💥] Exiting in 10 seconds [ Press <Ctrl-C> to abort, <Enter> to ignore and continue ]
Counting down: 9... 8... 7... 6... 5... 4... 3... 2... 1... 0... 
[💥] error! [ Exiting due to 'Docker installed but not usable'  ]
[💥] Exiting with error 43 [ at /home/roberto/armbian-2026-feb/build/lib/functions/logging/traps.sh:1
                exit_with_error() --> lib/functions/logging/traps.sh:1
   exit_if_countdown_not_aborted() --> lib/functions/general/countdown.sh:41
   cli_standard_relaunch_docker_or_sudo() --> lib/functions/cli/utils-cli.sh:261
     cli_standard_build_pre_run() --> lib/functions/cli/cli-build.sh:14
    armbian_cli_pre_run_command() --> lib/functions/cli/utils-cli.sh:122
                 cli_entrypoint() --> lib/functions/cli/entrypoint.sh:79
                           main() --> ./compile.sh:50

More info: my docker is version 28.2.2

$ apt list docker.io
Listing... Done
docker.io/noble-updates,now 28.2.2-0ubuntu1~24.04.1 amd64 [installed]

docker v17.6 needed. Reference: https://docs.armbian.com/Developer-Guide_Building-with-Docker/

If I remember correctly, xiaomi-elish hardware is very related to xiaomi-alioth, to the point of some of the code for PMOS being shared, obviously each hardware has it's quirks but, I think it's possible, i do have the device for testing, and I have some knowledge of programming, but I can learn more in the process.

I have rock 5c with PWM fan. I want to control the fan speed manually. Running on Armbian 25.11.1 Noble.

Sorry if its obvious I am newbie to this 

Yesterday was on nanopi-r6c with kernel 6.15.1-edge-rockchip64. I booted with this kernel but Opensuse Tumbleweed userspace (VERSION_ID="20250610"). Following command run-as-root should move Armbian Bookworm rootfs from eMMC to NVMe:

btrfs replace start /dev/mmcblk1p2 /dev/nvme0n1p2 /local/armbid

Then in dmesg:

Jun 19 18:44:38 ranc kernel: BTRFS info (device mmcblk1p2): dev_replace from /dev/mmcblk1p2 (devid 1) to /dev/nvme0n1p2 started
Jun 19 18:45:49 ranc kernel: BTRFS warning (device mmcblk1p2): failed setting block group ro: -28
Jun 19 18:45:49 ranc kernel: BTRFS error (device mmcblk1p2): btrfs_scrub_dev(/dev/mmcblk1p2, 1, /dev/nvme0n1p2) failed -28
 

After 5 minutes or so I discovered that the filesystem was corrupted, would not open: open_ctree failed: -5

As I do (very) frequent backups (differential send|receive to NAS) recreate and play back the latest single subvolume snapshot is easy, but it would become quite a drama if large multi-TB with hundreds of snapshots/subvolumes.

As the OS userspace was rolling release Tumbleweed, the btrfs-progs is very new, not the 6.2 from Bookworm. So it seems something mainline kernel rockchip64.

I will try to further pinpoint. The NanoPi-R6C is a bit DUT ATM, but I could test as well with various other combinations, ROCK3A or ROCK5B, although those have a dedicated task/use-case in my home. The 5B has 16G RAM, so easy to run VMs and loopdevs etc. I think this is not HW related, but whos knows, maybe some detailed RK35xx optimization or so.

Hello everyone, I am encountering an issue where kernel configuration changes do not take effect when building an image for the Rock 5B using the Armbian Build system.

Environment:

Board: Rock 5B

Kernel: Vendor

Release: Noble

Build Mode: Mini

Build Tag/Branch: v25.11

Specific Issue:

To ensure compatibility with Redroid containers, I need to change the kernel's CONFIG_ARM64_VA_BITS from the default 48-bit to 39-bit.

What I have tried:

I have attempted the following three methods, but none have worked:

Ran the kernel configuration tool to change CONFIG_ARM64_VA_BITS, then copied the generated .config to userpatches/linux-rk35xx-vendor.config.

Took the default config/kernel/linux-rk35xx-vendor.config, manually modified/added CONFIG_ARM64_VA_BITS=39 and CONFIG_ARM64_VA_BITS_39=y, and copied it to userpatches/linux-rk35xx-vendor.config.

Created a kernel source patch in userpatches targeting arch/arm64/configs/rockchip_linux_defconfig and arch/arm64/configs/defconfig to force CONFIG_ARM64_VA_BITS=39 and CONFIG_ARM64_VA_BITS_39=y.

Result:

Regardless of the method used, the final Armbian-generated kernel remains at VA_BITS=48. It seems my configuration changes are being overwritten or ignored during the build process.

Request:

Is there specific logic in the Vendor/RK3588 build configuration that forcibly locks VA_BITS? What is the correct way to modify this parameter for this specific board/kernel combination?

Thanks for your help!

This is my first embedded project since ~2019 so a bit out of my depth when it comes to device tree overlays. How would I write a DTO to enable audio output to this device?

Every time I pickup a new board and deploy Armbian I have to edit the `armbianEnv.txt` file and change verbosity to 7. The same question repeats in my head. Why is it not the default?

Systemd and startup messages spam up like crazy and they have nothing interesting to offer. I do care what hardware did the kernel detect or was a protocol correctly negotiated etc. I personally would have it in reverse, verbose kernel, quiet systemd. But thats just me. Could we at least have parity, if systemd verbose then make kernel verbose too, if kernel quiet then systemd quiet too.

I'm trying to understand what was the rationale for having quiet kernel and verbose systemd?

Thanks!!

As I can see on latest kernel for beta/trunk Armbian: https://imola.armbian.com/beta/pool/main/l/linux-6.18.6/linux-image-current-meson64_26.2.0-trunk.281_arm64__6.18.6-Sb6fe-D8ec8-Pe0be-C7d3eH1ff9-HK01ba-Ve377-Bc630-R448a.deb

There is no module ip_tables (should be under /lib/modules/6.18.6-current-meson64/kernel/net/ipv4/netfilter/), so iptables does not work:
"modprobe: FATAL: Module ip_tables not found in directory /lib/modules/6.18.6-current-meson64"

Is this intentional?

Thank you!

download speed on armbian

download speed without armbian

Tell me what is my problem?

I have an Ubuntu box and I have attempted to write to the SD card using Armbian ImagerImager, by selecting an image from the app as well as downloading an image to use. In both instances, I get a FLASH failure. See the attached image for the diag link.

Can anyone give me some insight?

I have a pile of bananapi-m5's, all used behind a home.arpa local network.

I am the only one here, and no one but me will ever have access to these machines.

So I need full access from any other machine on my local network.

I updated one that I am slowly configuring to drive a bigger enter5+ 3d printer.

New mobo in the rinter so I am starting from square one.

Using klipper and mainsail as web interfaces to klipper.

Now it goes to a no screen condition at about the time it used to bring up the login requester,

but I can still access it via ssh -X me & my pw.,

but don't have full access cuz x or whatever is not running.

 I need it to be running a full desktop, which it was prior to the upgrade a day or so

back but after I login from its own keyboard. The ssh -X login I have now has not even run udev,

so klipper can't find the printer which is identified as its /dev/serial/by_id, but there is not a /dev/serial now.

So, how do I make an uptodate Jammy install, think I've logged in to a fully working desktop? rpi4b's do it.

Thanks all,  Take care & stay well

BOARD="orangepizero"
BRANCH="current"
RELEASE="jammy"
BUILD_MINIMAL="yes"
PREFER_DOCKER="yes"
DOCKER_ARMBIAN_BASE_IMAGE="ubuntu:jammy"
BOOTDELAY=2
UBOOT_DEBUGGING="yes"

My command to build image is ./compile test. As I understand from source code UBOOT_DEBUGGING variable should enable such detailed uboot logs, but it seems like build framework ignored this option, I did not get detailed logs from uboot, also build logs do not contain info messages related with enabled UBOOT_DEBUGGING, etc.

P.S. Just for context - I have board wukongpih3zero (clone of orangepi zeor) and booting  is hanging at unexpected mcc1 slot instead of microsd mcc0 - that's why I need detailed boot logs.

Distribution:           Debian (armbian)

Kernel Version:      6.1.115-vendor-rk35xx

OpenZFS Version:  2.3.5

The kernel module does load.

# zfs -V
zfs-2.3.5-2~bpo13+1
zfs-kmod-2.3.5-2~bpo13+1

# zfs version
Failed to initialize the libzfs library.

Note: 

To keep this post short, I only pasted the errors from the trace below.

# strace zfs version

prctl(PR_CAPBSET_READ, 0x30 /* CAP_??? */) = -1 EINVAL (Invalid argument)
prctl(PR_CAPBSET_READ, CAP_CHECKPOINT_RESTORE) = 1
prctl(PR_CAPBSET_READ, 0x2c /* CAP_??? */) = -1 EINVAL (Invalid argument)
prctl(PR_CAPBSET_READ, 0x2a /* CAP_??? */) = -1 EINVAL (Invalid argument)
prctl(PR_CAPBSET_READ, 0x29 /* CAP_??? */) = -1 EINVAL (Invalid argument)

openat(AT_FDCWD, "/dev/zfs", O_RDWR|O_EXCL|O_CLOEXEC) = -1 ENODEV (No such device)
                               
openat(AT_FDCWD, "/usr/share/locale/en_US.UTF-8/LC_MESSAGES/zfs-linux-user.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/share/locale/en_US.utf8/LC_MESSAGES/zfs-linux-user.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/share/locale/en_US/LC_MESSAGES/zfs-linux-user.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/share/locale/en.UTF-8/LC_MESSAGES/zfs-linux-user.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/share/locale/en.utf8/LC_MESSAGES/zfs-linux-user.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/share/locale/en/LC_MESSAGES/zfs-linux-user.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
write(2, "Failed to initialize the libzfs "..., 41Failed to initialize the libzfs library.
) = 41
exit_group(1)                           = ?
+++ exited with 1 +++

The /dev/zfs file does exist

# ll /dev/zfs
crw-rw-rw- 1 root root 10, 249 Jan  9 16:48 /dev/zfs

In addition the trace also contains the following, confirming the existence of the file

faccessat(AT_FDCWD, "/dev/zfs", F_OK)   = 0

zpool also has the same issue.

I tried to enable cedrus264 encoder/decoder on my old OrangePI Lite 2 (revision 1 if I am right).

I used stulluk's repository as the base to patch the last FFMpeg revision and to add cedrus264 encoder using the new FFMpeg API. The result is built and tested. Unfortunately, I have had no success: the encoder says:

ffmpeg -f video4linux2 -input_format mjpeg -video_size 1280x720 -i /dev/video1 -c:v cedrus264 -pix_fmt nv12 -f mp4 video.mp4
ffmpeg version N-103904-gb2538ce578 Copyright (c) 2000-2021 the FFmpeg developers
  built with clang version 12.0.1 (https://github.com/llvm/llvm-project.git fed41342a82f5a3a9201819a82bf7a48313e296b)
  configuration: --enable-gpl --enable-nonfree --enable-shared --enable-frei0r --enable-gcrypt --enable-gmp --enable-gnutls --enable-ladspa --enable-libass --enable-libcaca --enable-libdc1394 --enable-libfdk-aac --enable-libflite --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libgsm --enable-libmp3lame --enable-libopus --enable-libpulse --enable-librsvg --enable-librubberband --enable-librtmp --enable-libsoxr --enable-libspeex --enable-libssh --enable-libtheora --enable-libtwolame --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libx264 --enable-libx265 --enable-opengl --enable-libdrm --enable-vdpau --enable-version3 --enable-libspeex --enable-libxvid --enable-libvpx --prefix=/util/ffmpeg --extra-cflags='-O3 -mllvm -polly -I/util/include -I/util/ffmpeg/include' --extra-ldflags='-L/util/lib -L/util/ffmpeg/lib' --enable-encoder=cedrus264 --cc=clang --cxx=clang++
  libavutil      57.  7.100 / 57.  7.100
  libavcodec     59.  9.101 / 59.  9.101
  libavformat    59.  5.100 / 59.  5.100
  libavdevice    59.  0.101 / 59.  0.101
  libavfilter     8. 10.100 /  8. 10.100
  libswscale      6.  1.100 /  6.  1.100
  libswresample   4.  0.100 /  4.  0.100
  libpostproc    56.  0.100 / 56.  0.100
Input #0, video4linux2,v4l2, from '/dev/video1':
  Duration: N/A, start: 17593.181597, bitrate: N/A
  Stream #0:0: Video: mjpeg (Baseline), yuvj420p(pc, bt470bg/unknown/unknown), 1280x720 [SAR 1:1 DAR 16:9], 30 fps, 30 tbr, 1000k tbn
Stream mapping:
  Stream #0:0 -> #0:0 (mjpeg (native) -> h264 (cedrus264))
Press [q] to stop, [?] for help
[swscaler @ 0x17450b90] [swscaler @ 0x1745e680] deprecated pixel format used, make sure you did set range correctly
[swscaler @ 0x17450b90] [swscaler @ 0x17496ea0] deprecated pixel format used, make sure you did set range correctly
[swscaler @ 0x17450b90] [swscaler @ 0x174ce7f0] deprecated pixel format used, make sure you did set range correctly
[swscaler @ 0x17450b90] [swscaler @ 0x17506140] deprecated pixel format used, make sure you did set range correctly
[swscaler @ 0x17450b90] [swscaler @ 0x1753da90] deprecated pixel format used, make sure you did set range correctly
[cedrus264 @ 0x17440360] VE Open error.
Error initializing output stream 0:0 -- Error while opening encoder for output stream #0:0 - maybe incorrect parameters such as bit_rate, rate, width or height

It seems the encoder is not enabled in the Armbian kernel 5.10.60-sunxi64 because the device descriptor is not available.

However, I will be glad to see the code reviews, test results and any other feedback. Sorry, but I am not so familiar with FFMpeg API to send pull requests.

Please visit the FFMPEG fork repository here, the default branch is cedrus264:

https://github.com/twdragon/FFmpeg

cat config-6.1.115-vendor-rk35xx | grep DM_CRYPT
CONFIG_DM_CRYPT=m

the kernel seems to have been compiled with the proper option and 

lsinitramfs initrd.img-6.1.115-vendor-rk35xx | grep 'usr.*cryptsetup'

usr/lib/aarch64-linux-gnu/libcryptsetup.so.12
usr/lib/aarch64-linux-gnu/libcryptsetup.so.12.9.0
usr/lib/cryptsetup
usr/lib/cryptsetup/askpass
usr/lib/cryptsetup/functions
usr/sbin/cryptsetup

and initramfs seems properly linked to the relevant libraries so I do not understand why device mapper remains unavailable.  At this point, I have no hypothesis except a very unlikely one

An unlikely hypothesis

Could failure to initialize the device mapper have nothing to do with dm_mod availability but be solely the side effect of 
 

Because I always unlocked the root part either from console or from a dropbear session, I understood device mapper init as an anterior step, independent from NIC availability. But is it really the case. What am I missing?

Using the last image for cubox-i (bookworn) , I m unable to get an access to internet using the default interface.

eth0 is détected but non functionnal, no eth1  card and no wifi card detected

This is a known problem :

Does someone has a recent kernel for this device ?

I've an old defconfig for kernel 5.2.1 that works (eth0 , eth1 and wifi too)

I'm slowly using this defconfig to build a more recent one (5.4.302 is ok but EOL...) 

Many thanks

So my question at this stage is: how do I know about determining whether any given board requires its own cooling?

Complete newbie here, I just want something small and silent.

[1] https://doc.yunohost.org/en/admin/get_started/install_on/arm_board/

sudo modprobe ip_tables
modprobe: FATAL: Module ip_tables not found in directory /lib/modules/6.18.0-rc6-edge-qcs6490
```

Is there another image that has this module are part of the kernel or do I need to build the kernel myself? This seems like a module that should be included for an image that is labeled as `IOT`. 

I've a rock-3a board with an NVMe device and a BTRFS filesystem using the whole disk ( no partitions )

I've seen some devices having BTRFS support in u-boot, so first thing I built the u-boot images using the extension:

cat extensions/uboot-btrfs.sh
# Enable BTRFS support in u-boot

function post_config_uboot_target__enable_uboot_btrfs_support() {
display_alert "u-boot for ${BOARD}/${BRANCH}" "u-boot: enable BTRFS filesystem support" "info"
run_host_command_logged scripts/config --enable CONFIG_CMD_BTRFS
}

And patched the configuration of the board:

git diff .
diff --git a/config/boards/rock-3a.conf b/config/boards/rock-3a.conf
index 401894fa5..90f8a8a72 100644
--- a/config/boards/rock-3a.conf
+++ b/config/boards/rock-3a.conf
@@ -15,12 +15,15 @@ BOOT_SPI_RKSPI_LOADER="yes"
IMAGE_PARTITION_TABLE="gpt"
BOOTFS_TYPE="fat"

+# Enable btrfs support in u-boot
+enable_extension "uboot-btrfs"
+
function post_family_config__rock-3a_use_mainline_uboot_except_vendor_and_add_sata_target() {
display_alert "$BOARD" "Configuring ($BOARD) standard and sata uboot target map" "info"
UBOOT_TARGET_MAP="

./compile.sh artifact BOARD=rock-3a BRANCH=current RELEASE=trixie BUILD_MINIMAL=yes BUILD_DESKTOP=no KERNEL_CONFIGURE=no COMPRESS_OUTPUTIMAGE=sha,img ROOTFS_TYPE=btrfs FIXED_IMAGE_SIZE=4096 DISABLE_IPV6=false WHAT=uboot

With this I flashed the SPI image:

root@rock-3a:~# flashcp u-boot-rockchip-spi.bin  /dev/mtd0

root@rock-3a:~# cat /proc/mtd
dev:    size   erasesize  name
mtd0: 01000000 00001000 "spi4.0"

So, then I booted it without the SD card I use for the /boot partition, used the serial port ( as it didn't autoboot )  and I saw:

=> nvme info
Device 0: Vendor: 0x2646 Rev: SBM02103 Prod: 50026B778514A843 e: Hard Disk
Capacity: 953869.7 MB = 931.5 GB (1953525168 x 512)


=> btrsubvol nvme 0:1
** No partition table - nvme 0 **
Couldn't find partition nvme 0:1
=> btrsubvol nvme 0:0
ID 257 gen 153600 path /@rootfs/
ID 257 gen 153600 path /@rootfs/
ID 259 gen 153599 path /@home/

=> ls nvme 0:0 /boot/
<DIR>         16  Sat Dec 06 08:32:08 2025  dtb
<   >          0  Sat Dec 06 08:44:38 2025  .next
<   >   37679616  Sat Nov 15 03:03:00 2025  Image
<   >    5560276  Tue Nov 11 22:48:14 202urrent-rockchip64
<   >    5560445  Sat Nov 15 03:03:00 2025  System.map-6.12.58-current-rockchip64
<   >        236  Sat Dec 06 08:54:54 2025  armbianEnv.txt<   >        200  Sat Sep 09 08:armbianEnv.txt.old
<   >          0  Tue Jun 18 18:05:14 2024  armbianEnv.txt.out
<   >       1536  Thu Aug 31 17:25:06 2023  armbian_first_run.txt.template
<   >      38518  Thu Aug 31 17:25:04 2023  boot.bmp
<   >       3180  Thu Aug 31 17:20:00 2023  boot.cmd
<   >       3252  Thu Aug 31 17:26:44 20  boot.scr
<   >     258746  Tue Nov 11 22:48:14 2025  config-6.12.57-current-rockchip64
<   >     258803  Sat Nov 15 03:03:00 2025  config-6.12.58-current-ro<   >   29107600  Tue Nov 25 21:2 2025  initrd.img-6.12.57-current-rockchip64
<   >   29108356  Sat Dec 06 08:44:34 2025  initrd.img-6.12.58-current-rockchip64<   >   29108420  Sat Dec 06 08:
  

So it can read BTRFS, but no booting, I tried manually based on some commands I get but no luck:

=> load nvme 0:0 $loadaddr /boot/boot.scr
3252 bytes read in 27 ms (117.2 KiB/s)

=> source
## Executing script at 00c00800
Boot script loaded from
** Bad device specification 0x9000000 armbianEnv **
** Bad device specification 0x9000000 armbianEnv.txt **
Couldn't find partit
Can't set block device
** Bad device specification 0x12180000 uInitrd **
** Bad device specification 0x12180000 uInitrd **
Couldn't find partition 0x1218000ck device
** Bad device specification 0x02000000 Image **
** Bad device specification 0x020000on 0x02000000 Image
Can't set block device
** Bad device specification 0x12000000 dtb/rockchipspecification 0x12000000 dtb/rockchip/rk3568-rock-3a.dtb **
Couldn't find partition 0x12000000 t set block device
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
No FDT memory address configure via "fdt addr <address>" command.
Aborting!
** Bad device specification 0x9000000 dtb/rockchiay/-fixup **
** Bad device specification 0x9000000 dtb/rockchip/overlay/-fixup.scr **
Couldn'tp/overlay/-fixup.scr
Can't set block device
** Bad device specification 0x9000000 fixup **
**0 fixup.scr **
Couldn't find partition 0x9000000 fixup.scr
Can't set block device
Applying us
## Executing script at 09000000
Wrong image format for "source" command
Unknown command 'kaslRM64 Image magic!

I'd like to get this worked, I can test anything you can provide me, I'm a n00b trying to learn a bit more about U-Boot.

Thanks in advance. 

For now, im trying to configurate a single secondary UART (UART2) to initialize with muxed Rx\Tx pins and in RS485 (with software driven RTS pin).

My current DT overlay is:

And it is partially works. Works as UART. Able to send and receive data with muxed Rx\Tx.
For RTS... its complicated. Seems RTS(PH4 GPIO) are initialized and acquired by UART2 software, and stay low during initial idling.

After im trying to send any data (echo 123 >> /dev/ttyS2), RTS goes HIGH and stuck in this state before reboot.

Im have tried to send big blob at 9600 and check the RTS with statserial.
But as i see, RTS is 1 (active???) from inital to complete and after, and never changes. 
 

Could you please tell me which image does not have netplan?

I want to compare how much resources it uses.

Thanks

how it can be open? some questions ...
P.
 

Seeking for some assistance on this.
I have NIC1 on 192.168.100.1/24 network with gateway set as 192.168.100.254 < this cant be changed. with a few PC’s connected to this.

And NIC2 on 10.10.10.1/24 with a few devices on this.

I want to be able to ping from PC1 connected to NIC1 on 192.168.100.100/24 to devices connected to NIC2 on 10.10.10.100/24

Could someone advise on the route settings I need to configure to make this work please ?
 

Seems the way is: touch /forcefsck

But this action does not fix, so we need 'somewhere': fsck.repair=yes

How do i have to do it?

Thanks.

I have burned bookworm onto a sd card,booted on it with a Rock 5B+ and installed the bootloader on the SPI flash of the board and transferred the OS to the nvme drive.

Now I I'm trying to install the new trixie image, but I can't burn it on my nvme drive.

With USBImage it does not work. It doesn't detect my nvme drive installed on my USB adapter.

With belena Etcher it throws an error during the validation of the image.

Win32Imager doesn't load at all on Windows 11.

I don't know which other tool (Windows) I could use.

I'm stuck. How can I boot again from my SD card on a Rock 5b+?

I encountered a dependency conflict while trying to upgrade the package armbian-bsp-cli-panther-x2-current to version 25.8.2. The issue seems to be a mismatch in the required version of base-files. Here's a summary of the issue:

Attempted upgrade command:

apt install armbian-bsp-cli-panther-x2-current

Error message:

armbian-bsp-cli-panther-x2-current : Depends: base-files (>= 25.8.2) but 25.8.1-12.4+deb12u11-bookworm is to be installed

Currently installed version of base-files:

base-files: 25.8.1-12.4+deb12u11-bookworm (installed)

Available versions for base-files from the repository (apt policy base-files):

Installed: 25.8.1-12.4+deb12u11-bookworm
Candidate: 25.8.1-12.4+deb12u11-bookworm
Version table:
     25.8.1-12.4+deb12u11-bookworm 500
     25.5.1-12.4+deb12u11-bookworm 500
     ...

It appears that the repository ( http://apt.armbian.com/pool/bookworm-utils/b/base-files ) does not provide the required version of base-files (25.8.2) for the arm64 architecture. Only the armhf architecture package is available, but armbian-bsp-cli-panther-x2-current depends on the arm64 version.

Could you please help investigate the issue or confirm whether the repository will be updated to include version 25.8.2 of base-files?

Thank you for your support!

Just like I do with the Debian x86 desktop. (I want to say that the NAS is configured correctly).

   /_\  _ _ _ __ | |__(_)__ _ _ _
  / _ \| '_| '  \| '_ \ / _` | ' \
 /_/ \_\_| |_|_|_|_.__/_\__,_|_||_|

 v25.8.1 for RK3318 Box running Armbian Linux 6.12.42-current-rockchip64

 Packages:     Debian stable (bookworm), possible distro upgrade (trixie)

However, I had some problems with armbian. I followed the general NFS instructions for debian. but it didn't work. 

 I followed the instructions for armbian.

I created a directory for the mount point. I copied the fstab line from my desktop, where it is known to be correct and working properly.

192.168.xx.x:/d8/d8    /mnt/d8-nas    nfs    relatime,nfsvers=3    0    0

I've tried issuing commands from the command line.

mount -vvvvv -t nfs -o vers=3 192.168.xx.x:/d8/d8 /mnt/d8-nas
mount -vvvvv -t nfs -o vers=4 192.168.xx.x:/d8/d8 /mnt/d8-nas

The result is nothing.
 

Sat Nov 22 19:56:03 root@rk3318-box>mount -vvvvv -a
/                        : ignored
/tmp                     : already mounted
mount.nfs: timeout set for Sat Nov 22 20:02:15 2025
mount.nfs: trying text-based options 'nfsvers=3,addr=192.168.xx.x'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying 192.168.xx.x prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 192.168.xx.x prog 100005 vers 3 prot UDP port 36831
mount.nfs: mount(2): No such device
mount.nfs: No such device
Status: 32

What a mystery  "No such device"?

 I have another rockchip 3228 box with an older armbian 23.11 kernel, and nfs doesn't work there either. And I tried some different builds of 24.5 24.11 25.5. I couldn't get the nfs client to work on any of them.

Can you tell me how to solve this quest?

For many months my Raspberry Pi 5 runs perfectly with Armbian. But when I try to update the system in the Discover App, I get the following error message:

The following packages have unmet dependencies: kpim6-akonadi: Kollidiert mit: knotes but 4:24.05.2+p24.04+vstable+git20240705.1500-0 is to be installed Kollidiert mit: kpim6-akonadi-notes but 4:24.08.3+p24.04+vstable+git20241129.1417-0 is to be installed 

Can someone please help me to get my system up-to-date? Thanks in advance!