Active threads

I upgraded my ROCK5B in-place from Armbian Bookworm beta to Armbian Testing/Trixie beta and it turns out that no Ambian packages are seen (so not updated). The Debian Trixie packages do upgrade, as for example I just saw while doing full-upgrade: libavif16:arm64 (1.2.1-1.2) over (1.2.1-1.1) ... I thought something with my install, but also downloaded 'Armbian_25.8.0-trunk.50_Rock-5b_trixie_vendor_6.1.115_minimal.img' yesterday and it has the same issue (quick test via systemd-nspawn container on loopdev mounted image). My goal is at least to figure out what is best bootloader and kernel for the ROCK5B. So far I simply copied/cloned Armbian Bookworm rootfs from ROCK3A+NanoPi-R6C and did some ROCK5B specific changes like U-Boot, but not much more and it actually is already good enough. But before the ROCK5B becomes a 24/7 headless workhorse with long uptime, I thought better to prepare/check for newer Linux or potential issues. I already upgraded some other devices from Bookworm->Trixie and that is quite an improvement, for example KDE 6 performs much better/nicer than KDE5 in Bookworm. It currently uses U-Boot 'edge' and 'current' kernel and very important for me, both the 'vendor' and 'mainline current/edge' overlay for SERDES multi-PHY SATA on the M.2 E-key work (and also the NVMe keeps working). I need to drill a hole in the Radxa aluminum cooling case for the SATA cable (and serial console cable), that needs some time first. I can build and install U-Boot and kernel etc manually of -course, but i wonder why Armbian packages are not visible. Is it as expected or is something wrong? I assume it is just too early yet and that it is work in progress. I think maybe policies are an issue, but don't understand what it could be. Maybe someone has a hint. root@rock-5b:~# apt policy Package files: 100 /var/lib/dpkg/status release a=now 500 http://deb.debian.org/debian trixie/non-free-firmware arm64 Packages release o=Debian,a=testing,n=trixie,l=Debian,c=non-free-firmware,b=arm64 origin deb.debian.org 500 http://deb.debian.org/debian trixie/non-free arm64 Packages release o=Debian,a=testing,n=trixie,l=Debian,c=non-free,b=arm64 origin deb.debian.org 500 http://deb.debian.org/debian trixie/contrib arm64 Packages release o=Debian,a=testing,n=trixie,l=Debian,c=contrib,b=arm64 origin deb.debian.org 500 http://deb.debian.org/debian trixie/main arm64 Packages release o=Debian,a=testing,n=trixie,l=Debian,c=main,b=arm64 origin deb.debian.org 500 https://beta.armbian.com trixie/trixie-desktop all Packages release o=Armbian,a=trixie,n=trixie,l=Armbian,c=trixie-desktop,b=all origin beta.armbian.com 500 https://beta.armbian.com trixie/trixie-desktop arm64 Packages release o=Armbian,a=trixie,n=trixie,l=Armbian,c=trixie-desktop,b=arm64 origin beta.armbian.com 500 https://beta.armbian.com trixie/trixie-utils all Packages release o=Armbian,a=trixie,n=trixie,l=Armbian,c=trixie-utils,b=all origin beta.armbian.com 500 https://beta.armbian.com trixie/trixie-utils arm64 Packages release o=Armbian,a=trixie,n=trixie,l=Armbian,c=trixie-utils,b=arm64 origin beta.armbian.com 500 https://github.armbian.com/configng stable/main arm64 Packages release o=armbian.github.io/configurator,n=stable,l=armbian.github.io/configurator,c=main,b=arm64 origin github.armbian.com Pinned packages:

From the information of DietPi users, it appears that they have used UBoot v2025.04 for Orange Pi Zero 3 and it seems that the problem of incorrect detection of RAM size has been solved, especially in the version with 1 MB. It would be valuable if ArmBian was also transferred for Orange Pi Zero 3 to Uboot v2025.04, we could avoid complications during system updates and other processes that need a lot of RAM causing the system to hang up because they try to use memory addresses that are not physically there when the RAM size was incorrectly identified during booting. More info about UBoot v2025.04 with Orange Pi Zero 3: https://github.com/MichaIng/DietPi/issues/7242#issuecomment-2912290816

I am using rk3588-sd-debian-bookworm-core-6.1-arm64-20250123.img.gz It is excellent asides from lacking NPU support. Before I go down the path of learning kernel compilation and scanning poorly documented Rockchip repositories, has anyone got a current version of Armbian that includes NPU support? If not, is there any good guide to using a cross-compile system and integrating third part drivers?. On a slightly different topic I would prefer to not use fuse file systems and run off the NVME drive directly. Are there any resources on this?

the issue about can't be recognized has been fixed，but the p2p mode still can't work

I tried the image from "armbian.atomonetworks.com" and the exact same thing happens. Thanks, I'll compare the images.

I ran compile.sh and got an error message which looked weird It couldn't find the directory .tmp/work-3efc55a6-9478-4508-91c4-5637c4b1e593 and would stop all work I created the directory and then it worked What the heck is that about? My linux x86 system is gentoo and not debian. I do have debian in vmware fusion on my mac. I use it to chroot my gentoo arm systems since it is much faster than cross compiling. For fun I tried again on a different directory and got a new error message This time it is .tmp/work-032fc96c-9055-4b10-86a8-b46b65980a11 The board I try to work with is YY3568 The problem doesn't seem to appear if I don't ask to let me change the kernel configuration

The latest Linux kernel brings expanded hardware support for MediaTek and Rockchip, enhanced graphics drivers, and more. Collabora played a key role in this release, with no less than 20 authored contributors! View the full article

ZFS-DKMS doesn't work on vanilla image https://dl.armbian.com/longanpi-3h/Bookworm_current_minimal Image is freshly burnt to the SD card. root@longanpi-3h:~# apt update root@longanpi-3h:~# apt install zfs-dkms root@longanpi-3h:~# modprobe zfs modprobe: ERROR: could not insert 'zfs': Exec format error root@longanpi-3h:~# modinfo zfs | grep -v parm filename: /lib/modules/6.12.23-current-sunxi64/updates/dkms/zfs.ko version: 2.3.1-1~bpo12+1 license: CDDL license: Dual BSD/GPL license: Dual MIT/GPL author: OpenZFS description: ZFS alias: zzstd alias: zcommon alias: zunicode alias: znvpair alias: zlua alias: icp alias: zavl alias: devname:zfs alias: char-major-10-249 srcversion: 2742833EE1C14D857611F06 depends: spl name: zfs vermagic: 6.12.23-current-sunxi64 SMP mod_unload aarch64 root@longanpi-3h:~# file /lib/modules/6.12.23-current-sunxi64/updates/dkms/zfs.ko /lib/modules/6.12.23-current-sunxi64/updates/dkms/zfs.ko: ELF 64-bit LSB relocatable, ARM aarch64, version 1 (SYSV), BuildID[sha1]=f87455b001529d816f09e1498e63a902d1af9be5, not stripped root@longanpi-3h:~# uname -a Linux longanpi-3h 6.12.23-current-sunxi64 #1 SMP Thu Apr 10 12:39:41 UTC 2025 aarch64 GNU/Linux logs After doing apt upgrade, reinstalling dkms module result is the same.

Awesome work as always. Cant wait until the 25.05 upgrade is available for my Rock5b

That was installed on my test machine which wasn't upgraded to latest (.115) yet.

If Rockchip reads this: knock it off and use a reasonable speed for console on your devices!

You delete all files in that folder.

Then I will not hold my breath

I guess the problem is that I'm using a simple 2 character password. It has been working fine until now. I'll try a long password next time. Update: Nope, still fails with a longer password.

Check journalctl/syslog for clues.

If nvme is correctly recognized code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } armbian-install should do.

https://debug.armbian.de for obtaining low level logs to debug further.

？？？It's turned into a brick, where's your img file

I'd probably try to code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } dd the Armbian image directly onto sda and boot.

@Nick A Thank you so much. I build with x98h version, both Ethernet and Wifi worked. Wifi only has problem when use command "reboot", wlan0 is disappear. But if I unplug power and plug again, then wifi is work again.

I got uart data from GPIO pin, when I press start button it returns as follows: It seems to be an error from the device tree file or the uboot version

I built and tested it with the rc version of kernel 6.15 it works. Waiting for Armbian to support 6.15😄

Why can I not sign in with GitHub ?

maybe its related to the kernel config parameter CONFIG_HZ_xyz - depending on which of them is set for the different kernels?