All Activity

I've been trying to update the system for 2 days but I can't: sudo apt update Get:1 http://deb.debian.org/debian trixie InRelease [140 kB] Get:2 http://security.debian.org trixie-security InRelease [43.4 kB] Get:4 http://security.debian.org trixie-security/main armhf Packages [88.5 kB] Get:5 https://github.armbian.com/configng stable InRelease [5,467 B] Get:6 https://github.armbian.com/configng stable/main armhf Packages [434 B] Get:3 http://armbian.lv.auroradev.org/beta trixie InRelease [39.4 kB] Get:7 http://armbian.lv.auroradev.org/beta trixie/trixie-desktop all Packages [731 B] Get:8 http://armbian.lv.auroradev.org/beta trixie/trixie-desktop armhf Packages [2,250 B] Get:9 http://armbian.lv.auroradev.org/beta trixie/trixie-utils armhf Packages [8,303 B] Ign:9 http://armbian.lv.auroradev.org/beta trixie/trixie-utils armhf Packages Err:9 http://beta.armbian.com trixie/trixie-utils armhf Packages File has unexpected size (10737 != 8303). Mirror sync in progress? [IP: 23.186.113.5 80] Get:10 http://deb.debian.org/debian trixie-updates InRelease [47.3 kB] Get:11 http://deb.debian.org/debian trixie-backports InRelease [54.0 kB] Err:9 http://beta.armbian.com trixie/trixie-utils armhf Packages File has unexpected size (10737 != 8303). Mirror sync in progress? [IP: 23.186.113.5 80] Get:12 http://armbian.lv.auroradev.org/beta trixie/trixie-utils all Packages [3,343 B] Ign:12 http://armbian.lv.auroradev.org/beta trixie/trixie-utils all Packages Get:13 http://deb.debian.org/debian trixie/main armhf Packages [12.7 MB] Err:9 http://beta.armbian.com trixie/trixie-utils armhf Packages File has unexpected size (10737 != 8303). Mirror sync in progress? [IP: 23.186.113.5 80] Ign:12 http://beta.armbian.com trixie/trixie-utils all Packages Get:14 http://deb.debian.org/debian trixie/non-free armhf Packages [69.9 kB] Get:15 http://deb.debian.org/debian trixie/contrib armhf Packages [50.6 kB] Get:16 http://deb.debian.org/debian trixie/non-free-firmware armhf Packages [6,685 B] Get:17 http://deb.debian.org/debian trixie-updates/main armhf Packages [5,144 B] Get:18 http://deb.debian.org/debian trixie-backports/non-free armhf Packages [1,520 B] Get:19 http://deb.debian.org/debian trixie-backports/contrib armhf Packages [4,348 B] Get:20 http://deb.debian.org/debian trixie-backports/non-free-firmware armhf Packages [3,856 B] Get:21 http://deb.debian.org/debian trixie-backports/main armhf Packages [130 kB] Fetched 13.4 MB in 18s (754 kB/s) Error: Failed to fetch http://beta.armbian.com/dists/trixie/trixie-utils/binary-armhf/Packages File has unexpected size (10737 != 8303). Mirror sync in progress? [IP: 23.186.113.5 80] Error: Failed to fetch http://beta.armbian.com/dists/trixie/trixie-utils/binary-all/Packages.bz2 File has unexpected size (3942 != 3343). Mirror sync in progress? [IP: 23.186.113.5 80] Error: Some index files failed to download. They have been ignored, or old ones used instead.

Has anyone figured out an image for a v1.1 box yet?

PCIe MSI is not working. At least with an Intel iwlwifi M.2 card. For that reason, I investigated the differences between the Xunlong KY tree and the Armbian Spacemit Tree. B/c loading the "official" 552kb esos.elf seems to work (even if the Ky version is only 104kb) on the OrangePi RV2, I started to backport Xunlong changes to Armbian/Spacemit family. Newer kernel, but no luck with that MSI. There should be a DMA-transfer-complete interrupt at the end of the firmware upload. Card is working in my PC. MSI is working on OpiRV2 with NVME. Current status: board runs with spacemit-family kernel, but some minor Does-Not-Work yet: LED, onboard Wifi+BT and I need to check that special RTL eth... LG // Sven-Ola Edit: Pic it or it didn't happen. RV2 underside with WIfi card.

Hi, Just wanted to provide more info on this. When I try to load the beagle Y AI official debian image it works fine, just wondering whether the dtb is inline with the Beagle Y AI official dtb or any changes where made related to the usb host. Any help would be appreciated. Thanks!

Hi, I programmed the latest image Armbian_26.2.0-trunk.197_Beagley-ai_plucky_vendor_6.12.49_minimal.img.xz on my beagle Y AI, and connected the power and HDMI and inserted a Dell USB HID for keyboard and mouse, but in initial boot I am not able to use the keyboard and due to this not able to configure the device. Any help will be appreciated. Thanks, Ankit

It is already an old thread, but if someone stumbles over this situation, that compile.sh breaks at update-binfmt errors, check if qemu-user-binfmt is installed on the host linux system. do: sudo apt install qemu-user-binfmt and you should be fine again.

Thank you for hints. Curl approach is not working, too big file for request. Here is log file of build which was adviertised to push into pastbin (debug=yes option was passed) log-build-8431ff32-1cf8-4fe6-9eeb-6f46f683c875.log.zip

I managed to get a device tree from Android. The veil has been lifted))) android-dtbo_MYD-lt527m-16e2d-180-e-sx.dts

Hm interesting. Didn't know this exists. But if it doesn't work I suggest to run a build with also DEBUG=yes set and then share the whole log using the curl command provided at the end. May give some clues if this fails to apply or works as intended.

I have took this variable from Here. Actually the first thing I tried to observe is uart logs. But they are very minimalistic like that: U-Boot SPL 2024.01-armbian-2024.01-S866c-P6b16-Ha5c2-V367a-Bb703-R448a (Apr 29 2025 - 02:50:09 +0000) DRAM: 512 MiB Trying to boot from MMC1 It's from offial image from website, but the compiled image on my side has the same logs and effect

never heard of that one before. Serial console is enabled by default on all boards (lookup your board manual on where to connect) which also outputs uboot logs while on early boot stage. For increased kernel verbosity set verbositoy to 7 in /boot/armbianEnv.txt

Great！ Thanks a lot! I will try it to se if Diablo II can run tonight!

You can download dgVoodoo2 from here: https://community.pcgamingwiki.com/files/file/572-dgvoodoo-2/ (Unfortunately, newer versions of dgVoodoo2 won't work with Wine/Proton.) Extract the archive, then copy dgVoodoo2_79_1/MS/x86/d3d9.dll to the game's folder (just like Dxvk). Then, copy the Dxvk's d3d11.dll, dxgi.dll to the game's folder. If done right, you will see that the Dxvk HUD shows the game uses D3D11 API.

@chris178 I am currently working on a solution. Radxa typically uses rsetup and extlinux.conf to load overlays during boot; however, Armbian uses armbian-config along with boot.cmd and boot.scr. I have decided to use armbian-config to load the overlays instead.

http://blog.armbian.com/content/images/2026/01/githubhighlights-2.webpThis week’s Armbian development saw significant kernel upgrades across multiple platforms, including meson64, rockchip64, and UEFI, with several branches bumped to versions 6.18 and 6.19. Notable hardware support enhancements were introduced, such as SPI controller support for Allwinner A523, new board additions like mixtile-core3588e, and improved compatibility for devices including Radxa and Youyeetoo. The build system received stability and performance improvements, featuring parallel repository generation, refined CI scripts, and fixes for repository management in concurrent environments. Kernel configuration updates enabled additional filesystems and tickless idle for mvebu devices. Several patches addressed hardware initialization, network, and desktop issues, while deprecated packages were removed for a leaner build. Overall, the changelog reflects a strong focus on expanding hardware support, refining build infrastructure, and maintaining kernel currency. add allwinner: a523: Support SPI controllers patch series. by @EvilOlaf in armbian/build#9124allow build on forky host. by @amazingfate in armbian/build#9153CI: add watchdog action script and adjust log cleaning parameter. by @igorpecovnik in armbian/build#9147Fix repository management script for parallel execution. by @igorpecovnik in armbian/build#9163fix: replace comm with grep to support uutils coreutils. by @cantalupo555 in armbian/build#9148kernel configs - enable EROFS as module, ditto overlayfs & F2FS. by @tabrisnet in armbian/build#9135kernel: mvebu: enable tickless idle. by @neheb in armbian/build#9139meson64-6.19: de-bork PCIe, again (missed a patch from 6.18). by @rpardini in armbian/build#9151meson64: bump edge to 6.19; current 6.12 -> 6.18. by @EvilOlaf in armbian/build#9069meson64: bump edge to 6.19; current 6.12 -> 6.18 (nonsquash). by @rpardini in armbian/build#9146Missing variable in board config - address JSON matrix warnings. by @igorpecovnik in armbian/build#9144mixtile-core3588e: add board with vendor and edge branches (Joshua Riek + fixes). by @rpardini in armbian/build#9119Modify radxa-e54c board config to fix leds, network and Gnome desktop init.. by @schwar3kat in armbian/build#9111radxa-cubie-a5e: maint and fixes. by @EvilOlaf in armbian/build#9152Remove libfuse2t64 from package list. by @igorpecovnik in armbian/build#9155Repo tools: add parallel repository generation support. by @igorpecovnik in armbian/build#9150Revert few Rabbit's suggestions that broke repository management. by @igorpecovnik in armbian/build#9156rockchip64-6.18: Enable HDMI1 and audio for HDMI0/1 on CM3588-NAS. by @rpardini in armbian/build#9138rockchip64: add edge kernel support for Youyeetoo YY3588. by @SuperKali in armbian/build#9137rockchip64: fix broken patch in 6.18.3, rewrite everything. by @EvilOlaf in armbian/build#9157uefi-all: bump edge to 6.19 (except loong64); legacy 6.6 -> 6.12; current/cloud 6.12 -> 6.18. by @EvilOlaf in armbian/build#9086uefi-loong64-edge: bump to 6.19. by @amazingfate in armbian/build#9149View the full article

So the workaround is to set cpu freq max to 1 MHz. I still have to use a ghetto cooler 5000 when running a process that maxes out the CPU. Seems Duo running 10C+ at idle with latest kernel and Noble. I can live with that as long as I know. The default is 1.2 MHz max which runs too hot at 1.3V.

Java UIO Java UIO offers robust Java interfaces optimized for Linux Userspace IO, emphasizing high performance. Engineered from scratch, it leverages contemporary kernel APIs, libraries, and cutting-edge code generation methodologies, embodying a state-of-the-art cross-platform solution. Rather than reinventing established paradigms, Java UIO harnesses existing standards, avoiding redundant development commonly observed in other IO libraries. Seamlessly supporting JDK 25 LTS, this framework integrates Project Lombok to streamline code, enhancing readability and conciseness. 🌍 The 32-bit & FFM Reality With Java 25, there is no more support for X86_32, and ARM32 has limited JDKs available. While FFM (Foreign Function & Memory API) is the future, it is not supported on X86_32 or ARM32. For now, JavaUIO moves into the future providing a high-performance path for ARM32, while fully supporting ARM64 and X86_64.

Just to add, Armbian boots upto systemd and then gets stuck at loading some scripts. This image gives some additional information.

Hi, So, Previously this massage (No emmc) appeared if the preinstalled Android was able to boot up completely and then restarted by repowering while the sdcard was inserted or the tvbox was rebooted while the sdcard was in the slot, however this got fixed if the device was powered off during the android bootanimation but after accidentally installing an incomplete image of latest armbian release I am no longer able to get the emmc working even after trying restarting at various boot levels. I have found others experiencing the same issue in this post but according to the circumstances I am in I think my issue might have a different solution. Any way through which this issue can be solved ? This might help : root@multitool:~# dmesg -T | grep mmc2 [Tue Jan 6 21:06:28 2026] mmc_host mmc2: Bus speed (slot 0) = 2343750Hz (slot req 400000Hz, actual 390625HZ div = 3) [Tue Jan 6 21:06:28 2026] mmc_host mmc2: Bus speed (slot 0) = 50000000Hz (slot req 50000000Hz, actual 50000000HZ div = 0) [Tue Jan 6 21:06:28 2026] mmc2: Card stuck in programming state! __mmc_switch [Tue Jan 6 21:06:28 2026] mmc2: error -110 whilst initialising MMC card I have also attached the whole dmesg log and lsblk output if needed. multitool-ssh-output.txt

Hi all, Is there any working way to enable detailed logs from uboot? I am using fresh main branch (latest commit is 4648add1450c1b26bb29bf412ef054b0e978947d) . I have created following config inside userpatches/config-test.conf.sh file 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.

I guess the image was built from a pending pull request for testing before merge. Since it has been merged now it should work. Make sure your framework clone is up to date (git pull).

@Werner can you please tell how did you built this image: https://testing.armbian.de/Armbian-unofficial_26.02.0-trunk_Radxa-cubie-a5e_trixie_edge_6.18.2_minimal.img.xz ? Image I get with: ./compile.sh build BOARD=radxa-cubie-a5e BRANCH=edge BUILD_DESKTOP=no BUILD_MINIMAL=yes KERNEL_CONFIGURE=no RELEASE=trixie seems to be far away from your result. First and foremost it does not boot 😉 I ask because of two reasons: - I'd love to be able to build myself an image that I'm running. - I need to be able to mount ZFS volumes. I'm unable to install `zfs-dkms` and `zfsutils-linux` when using your image. `apt` says that kernels newer than 6.14 are not supported. I'd also appreciate any tips or resources that would help me to get 6.12.x (or whatever lower than 6.14). I experimented a bit but without luck. I saw that it seems that `current` branch should not be supported on radxa-cubie-a5e board but I somehow got an image that at least has 6.12.63 in its name. It doesn't bring much because it does not boot.

Oh, I understand. Camera, hardware video decoder and hardware video encoder - they all appear now as /dev/videoX devices, because new hardware videocodec accelerator driver (or standalone video decoder and video encoder drivers) became V4L2 kind of driver. Also thanks for the reference link.

The ffmpeg conversation in https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20847 suddenly stopped 2 weeks ago. Does it seem like there's a big obstacle suddenly, or just a well deserved engineer vacation going on?

How did you apply dgVoodoo2 ? I download the archieve file it is a bunch of dll.