All Activity

I noticed the same thing. It looks like the server images might have been temporarily removed, possibly during a site update or reorganization. I’d suggest keeping an eye on the official download page or checking the Armbian GitHub mirror, they usually restore missing builds pretty quickly.

Update. I fixed the issue with chatgpt now. It told me according to the logs, my board has wrong hardware, and it told me to disable the gpu with adding a file to /etc/modprobe.d/ with blacklist lima. It worked. I booted to armbian, but to my surprise it immediately showed me a message saying this image is for tesing purposes only, and not stable. I downloaded it from the official site, it was labeled as minimal console pc, for small servers or sth like that. Also, hdmi not working (I don't want to only be able to ssh to it, but if that's what it is than fine:), and during setup it was giving me wrong time, timezones, completely wrong. Don't know what should be next step, try a different dtb, or different armbian image?

Ok. I read the posts you showed me. First off, I thought this was a pretty straightforward process - installing armbian to these chinese tv boxes; so thank you for the hard truth - expect nothing to work:( Anyway, as I mentioned before, my main issue was that there is no reset button on this thing, so I had no idea how to get anything to boot, which commands, which script to run. So, thank you again for pointing me to the file. I entered the u-boot shell from uart, loaded the aml_autocript to 0x20000000 fatload usb 0:1 0x20000000 aml_autoscript and run it with autosrc 0x20000000 (the equivalent of source command I believe). It changed the bootloader, as the other post suggested, and now it boots to usb if present (haven't tried if it falls back to android, but I don't care about that anymore). I'm really glad it boots to linux, but the thing is it always ends in kernel panic before it even boots completely. I tried turning it off and on, but I always got a different kernel panic. Here are some of the logs (I posted only the kernel panic lines, and a few before - to keep the post short, but I can add some of the complete logs if necessary). Notice: after entering the kernel panic the device just hangs - no reset or action whatsoever. So I just disconnected power, and turned it on again. Another notice: the logs may actually be incomplete, because I already faced issues with uart not printing the whole text, but only the first 40-50 lines or so (example: output of the command help in the u-boot shell showed only half of them, and the last line shown looked half-printed). Dunno why this happens, maybe the RP2040 zero (which I'm using as the uart bridge adapter, running micropython script) is causing it, or something else. boot1: [ 11.642441] systemd[1]: Found device dev-disk-by\x2duuid-3563\x2d67BF.device - ProductCode armbi_boot. [ 11.657680] systemd[1]: Starting systemd-fsck@dev-disk-by\x2duuid-3563\x2d67BF.service - File System Check on /dev/disk/by-uuid/3563-67BF... [ 11.673727] systemd[1]: Starting systemd-networkd-persistent-stor[ 11.689172] [drm] Initialized simpledrm 1.0.0 for 7fe5b000.framebuffer[ 11.717710] Console: switching to colour frame buffer device 90x36 [ 11.731744] simple-framebuffer 7fe5b000.framebuffer: [drm] fb0: simpledrmdrmfb frame buffer device [ 11.835286] mc: Linux media interface: v0.10 [ 11.837173] Registered IR keymap rc-empty [ 11.852968] rc rc0: meson-ir as /devices/platform/soc/c8100000.bus/c8100580.ir/rc/rc0 [ 11.855991] rc rc0: lirc_dev: driver meson-ir registered at minor = 0, raw IR receiver, no transmitter [ 11.883334] input: meson-ir as /devices/platform/soc/c8100000.bus/c8100580.ir/rc/rc0/input0 [ 11.897040] rc rc0: sw decoder init [ 11.897461] meson-ir c8100580.ir: receiver initialized [ 11.923213] systemd[1]: Finished systemd-networkd-persistent-storage.service - Enable Persistent Storage in systemd-networkd. [ 11.959135] videodev: Linux video capture interface: v2.00 [ 12.038565] systemd[1]: Reached target usb-gadget.target - Hardware activated USB gadget. [ 12.122827] SError Interrupt on CPU3, code 0x00000000bf000002 -- SError [ 12.122857] CPU: 3 UID: 0 PID: 1158 Comm: (udev-worker) Tainted: G M 6.18.2-current-meson64 #1 PREEMPT [ 12.122869] Tainted: [M]=MACHINE_CHECK [ 12.122872] Hardware name: Amlogic Meson GXL (S905X) P212 Development Board (DT) [ 12.122878] pstate: 00000005 (nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 12.122885] pc : el00 [ 12.122973] x11: 0000000000000006 x10: ffff8000812e5a60 x9 : 1fffe000007108c1 [ 12.122983] x8 : 0000000000000001 x7 : ffff000003884600 x6 : ffff000003884608 [ 12.122993] x5 : ffff8000829eb6b0 x4 : 0000000000000025 x3 : 0000000000000021 [ 12.123002] x2 : 000000000000003b x1 : 0000000000000000 x0 : 0000000000000000 [ 12.123014] Kernel panic - not syncing: Asynchronou do_serror+0x3c/0x78 [ 12.123105] el1h_64_error_handler+0x34/0x50 [ 12.123114] el1h_64_error+0x6c/0x70 [ 12.123123] el1_abort+0x34/0x68 (P) [ 12.123130] el1h_64_sync_handler+0x50/0x104 [ 12.123138] el1h_64_sync+0x6c/0x70 [ 12.123145] lima_mmu_init+0x44/0x124 [lima] (P) [ 12.123186] lima_device_init+0x1ac/0x664 [lima] [ 12.123206] lima_pdev_probe+0xa4/do_init_module+0x58/0x23c [ 12.123364] load_module+0x1e78/0x1ed4 [ 12.123374] init_module_from_file+0x88/0xcc [ 12.123383] __arm64_sys_finit_module+0x1ec/0x300 [ 12.123393] invoke_syscall+0x48/0x10c [ 12.123408] el0_svc_common.constprop.0+0xc8/0xe8 [ 12.123418] do_el0_svc+0x20/0x2c [ 12.123428] el0_svc+0x34/0xf0 [ 12.123437] el0t_64_sync_handler+0xa0 boot2: [ 12.471539] Kernel panic - not syncing: Asynchel1h_64_error_handler+0x34/0x50 [ 12.471648] el1h_64_error+0x6c/0x70 [ 12.471656] el1_abort+0x34/0x68 (P) [ 12.471664] el1h_64_sync_handler+0x50/0x104 [ 12.471672] el1h_64_sync+0x6c/0x70 [ 12.471679] lima_mmu_init+0x44/0x124 [lima] (P) [ 12.471723] lima_device_init+0x1ac/0x664 [lima] [ 12.471744] lima_pdev_probe+0xa4/0x1bc [lima] [ 12.471764] platform1915] load_module+0x1e78/0x1ed4 [ 12.471924] init_module_from_file+0x88/0xcc [ 12.471934] __arm64_sys_finit_module+0x1ec/0x300 [ 12.471944] invoke_syscall+0x48/0x10c [ 12.471956] el0_svc_common.constprop.0+0xc8/0xe8 [ 12.471967] do_el0_svc+0x20/0x2c [ 12.471977] el0_svc+0x34/0xf0 [ 12.471988] el0t_64_sync_handler+0xa0/0xe4 [ 12.471996] el0t_64_sync+Traceback (most recent call last): boot3: [ 12.420984] Kernel panic - nx80 [ 12.421075] do_serror+0x3c/0x78 [ 12.421082] el1h_64_error_handler+0x34/0x50 [ 12.421091] el1h_64_error+0x6c/0x70 [ 12.421099] el1_abort+0x34/0x68 (P) [ 12.421107] el1h_64_sync_handler+0x50/0x104 [ 12.421115] el1h_64_sync+0x6c/0x70 [ 12.421121] lima_mmu_init+0x44/0x124 [lima] (P) [ 12.421165] lima_device_init+0x1ac/0x664 [lima] [ 12.421185] 0x200 [ 12.421335] do_init_module+0x58/0x23c [ 12.421348] load_module+0x1e78/0x1ed4 [ 12.421357] init_module_from_file+0x88/0xcc [ 12.421367] __arm64_sys_finit_module+0x1ec/0x300 [ 12.421376] invoke_syscall+0x48/0x10c [ 12.421388] el0_svc_common.constprop.0+0xc8/0xe8 [ 12.421399] do_el0_svc+0x20/0x2c [ 12.421409] el0_svc+0x34/0xf0 [ 12.421419] el0 boot4: [ 12.874949] SError Interrupt on CPU2, code 0x00000000bf000002 -- SError [ 12.874984] CPU: 2 UID: 0 PID: 1165 Comm: (udev-worker) Tainted: G M C 6.18.2-current-meson64 #1 PREEMPT [ 12.874999] Tainted: [M]=MACHINE_CHECK, [C]=CRAP [ 12.875003] Hardware name: 12.875086] x17: 0000000000000000 x16: ffff00000495fc00 x15: ffff000002098ea3 [ 12.875095] x14: 0000000000000001 x13: ffff000002098ea0 x12: ffff00000b244200 [ 12.875105] x11: 0000000000000006 x10: ffff8000812e5a60 x9 : 1fffe0000092e981 [ 12.875114] x8 : 0000000000000001 x7 : ffff000004974c00 x6 : ffff000004974c08 [ 12.875123] x5 : ffff800082a1b6b0 x4 : 0000000000000025 4 [ 12.875207] vpanic+0x320/0x364 [ 12.875215] nmi_panic+0x0/0x68 [ 12.875221] add_taint+0x0/0xbc [ 12.875227] arm64_serror_panic+0x70/0x80 [ 12.875235] do_serror+0x3c/0x78 [ 12.875242] el1h_64_error_handler+0x34/0x50 [ 12.875251] el1h_64_error+0x6c/0x70 [ 12.875260] el1_abort+0x34/0x68 (P) [ 12.875268] el1h_64_sync_handler+0x50/0x104 [ 12.875212.875453] __platform_driver_register+0x24/0x30 [ 12.875462] lima_platform_driver_init+0x20/0x1000 [lima] [ 12.875486] do_one_initcall+0x70/0x200 [ 12.875495] do_init_module+0x58/0x23c [ 12.875508] load_module+0x1e78/0x1ed4 [ 12.875516] init_module_from_file+0x88/0xcc [ 12.875526] __arm64_sys_finit_module+0x1ec/0x300 [ 12.875535] invoke_syscall+0x48/0x1

Alright, well, such things can happen when attempting to fix a bug and not having hw to test on hand I'll leave it to Cornelius to send a fix since he can directly verify if it works.

I implemented this from the forum @kris777 mentioned, and IT WORKED: Now, I flashed this image, and it didn't even boot. Anyway, thanks to everyone involved for helping me with this issue, and big thanks to every maintainer and contributor for keeping this distro alive, as its contribution deserves to be appreciated.

Latest nightly I found seems to work, built from source and installed klipper, etc using normal instructions online. Klipperscreen is not working but I believe I will need to build the full graphical version to get this working with my Waveshare 7" hdmi screen. Wifi and general usage of this build seems very stable. Note: I did that the lagtest ngihtly code PR for CB2 was months old, but again, it seems to work.

Been looking at getting my Helios64 back up and running after experiencing a lot of instability a few years ago. Stumbled across this thread and things look somewhat promising, but after reading through I'm unsure what I should actually do to get things running! Lots of different posts with lots of different .dtb files, seemingly PR's in to the armbian repo etc. As of today, what is the best approach to get things up and running? Do the PR's mean I should be able to just use Armbian direct from the site and have a stable NAS?

Hello, sorry for late answer, but I had no time to experiment with my rock64 board. Maybe this issue is already resolved, if so please let me know. I'm still using kernel 6.6.63 and holding kernel packages in order not to break a working home server. So I managed to temporary switch kernel to 6.12.9 again for testing (copied old /boot and corrected symlinks) and enter UART console: Here is output of U-Boot commands you asked: Hit any key to stop autoboot: 0 => setenv b => setenv c => setenv a "a/b" => setexpr b sub "a/" "" a Unknown command 'setexpr' - try 'help' => echo ${b} => setexpr c 1 + 1 Unknown command 'setexpr' - try 'help' => echo ${c} => fdt fdt - flattened device tree utility commands Usage: fdt addr [-c] <addr> [<length>] - Set the [control] fdt location to <addr> fdt move <fdt> <newaddr> <length> - Copy the fdt to <addr> and make it active fdt resize [<extrasize>] - Resize fdt to size + padding to 4k addr + some optional <extrd fdt print <path> [<prop>] - Recursive print starting at <path> fdt list <path> [<prop>] - Print one level starting at <path> fdt get value <var> <path> <prop> - Get <property> and store in <var> fdt get name <var> <path> <index> - Get name of node <index> and store in <var> fdt get addr <var> <path> <prop> - Get start address of <property> and store in <var> fdt get size <var> <path> [<prop>] - Get size of [<property>] or num nodes and store in <var> fdt set <path> <prop> [<val>] - Set <property> [to <val>] fdt mknode <path> <node> - Create a new node after <path> fdt rm <path> [<prop>] - Delete the node or <property> fdt header - Display header info fdt bootcpu <id> - Set boot cpuid fdt memory <addr> <size> - Add/Update memory node fdt rsvmem print - Show current mem reserves fdt rsvmem add <addr> <size> - Add a mem reserve fdt rsvmem delete <index> - Delete a mem reserves fdt chosen [<start> <end>] - Add/update the /chosen branch in the tree <start>/<end> - initrd start/end addr NOTE: Dereference aliases by omitting the leading '/', e.g. fdt print ethernet0. => echo ${fdtfile} rockchip/rk3328-rock64.dtb => echo ${fdt_addr_r} 0x01f00000 => echo ${kernel_addr_r} 0x02000000 => echo ${ramdisk_addr_r} 0x04000000 => ver U-Boot 2017.09-rockchip-ayufan-1065-g95f6152134 (Apr 06 2020 - 08:10:39 +0000) aarch64-linux-gnu-gcc (Ubuntu/Linaro 7.5.0-3ubuntu1~18.04) 7.5.0 GNU ld (GNU Binutils for Ubuntu) 2.30 => CTRL-A Z for help | 1500000 8N1 | NOR | Minicom 2.10 | VT102 | Offline | ttyUSB0 I have set up rock64 to boot from SSD connected over USB3-SATA adapter (bought from pine64 store) without SD-card. To make it work I flashed latest U-Boot from ayufan to SPI by this tutorial. Maybe this error because of old U-Boot, and you're right, looks like it doesn't support setexpr command djurny, thank you for looking into this. And one question I don't understand, if I should upgrade U-Boot in SPI or I should erase SPI and wirte U-boot somewhere else? And will I be able to boot directly from USB-SSD without SD-card after that?

I don’t know about Odroid n2 but all the 2025.11 builds with graphical ui get stuck when the initial setup is completed and message appears “now booting to graphical session” and never boots 2024 builds do boot and stay normal I am using mainline uboot via spi boot.

Hi there, I also bought one (V1.5) and tried to use armbian. Unfortunately, I managed to brick it. I booted your image @johlnx from sd, that worked. Then I overwrote the internal EMMC with your image and the box won't boot anymore. Any idea how I can fix it? I made an backup of the original image, but I also read that it may be incomplete because of read protection in uboot of the emmc? I also tried to get into MaskMode by pressing the button and connecting the USB 2.0 to my Windows-PC but no device is discovered. I attached the serial uboot log. Hope somebody has a suggestion how i can boot something again. Thanks boot_with_armbian_sd_insert.log boot_without_sd_insert.log

Hello everyone! I am running Armbian in a BTV11 box (Amlogic S905X3) alongside the "meson-sm1-sei610.dtb". My cabled ethernet connection is working fine but not WIFI. No networks are found. I have already tried alternatives like meson-sm1-sei610-ethfix.dtb, that leads to my ethernet to also stop working. At first the Kernel was looking for `brcmfmac4330-sdio.seirobotics,sei610.bin` firmware, that doesnt exist in Armbian. So I made a symlink pointing to a generic `brcmfmac4330-sdio.bin`. Saw that similar fixes worked for other people. This is what I see from logs: `sudo dmesg`: [ 8.451121] brcmfmac: F1 signature read @0x18000000=0x16044330 [ 8.456690] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4330-sdio for chip BCM4330/4 [ 8.488102] usbcore: registered new interface driver brcmfmac [ 8.495653] brcmfmac mmc2:0001:1: Direct firmware load for brcm/brcmfmac4330-sdio.clm_blob failed with error -2 [ 8.858975] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available [ 8.871034] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4330/4 wl0: Oct 25 2011 19:34:12 version 5.90.125.104 [ 13.975072] brcmfmac: brcmf_sdio_readframes: read 97 bytes from channel 1 failed: -84 [ 13.979176] brcmfmac: brcmf_sdio_rxfail: abort command, terminate frame, send NAK [ 14.014920] brcmfmac: brcmf_sdio_readframes: RXHEADER FAILED: -84 [ 14.017205] brcmfmac: brcmf_sdio_rxfail: abort command, terminate frame, send NAK [ 16.618796] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout [ 16.639467] ieee80211 phy0: brcmf_netdev_open: failed to bring up cfg80211 [ 18.506857] ieee80211 phy0: brcmf_p2p_create_p2pdev: timeout occurred [ 18.507694] ieee80211 phy0: brcmf_cfg80211_add_iface: add iface p2p-dev-wlan0 type 10 failed: err=-5 [ 22.171208] brcmfmac: brcmf_sdio_readframes: RXHEADER FAILED: -84 [ 22.171730] brcmfmac: brcmf_sdio_rxfail: abort command, terminate frame, send NAK [ 24.554983] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout [ 24.575580] ieee80211 phy0: brcmf_run_escan: error (-110) More info available from Armbian monitor: https://paste.armbian.com/zuwididupe Does anyone have any insight that might help me figure out whats wrong with my box's WIFI?

If I have the time I'll do a PR. I also ended up modifying and compiling a new hciattach_opi binary, to get bluetooth to come up.

Hi everyone. I'm new here. I found and ordered a 4-inch touchscreen with an ili9488 and xpt2046 on AliExpress. I was thinking about connecting it to a Raspberry Pi Zero 2W for my 3D printer's KlipperScreen. Since I had accelerometers connected to spi0, I connected the display and touchscreen to spi1. I thought it would be easy, since I found an article about connecting an ili9341 display to an Orange Pi Zero 3 for the same purpose: https://3dtoday.ru/blogs/3c60a2061c/dnevnik-tronxy-crux-1-displei-klipperscreen-seipery. But I'm new to Linux, so I followed guides to configure Klipper, literally copying and pasting commands. I'm using a ready-made mainsailos 64-bit. I spent almost a week trying to get the display working. I tried various ready-made libraries, but most of them gave me errors. For example, only after a couple of days of trying to use fbcp-9341 did I realize it doesn't support touch input, which isn't what I need, and that the library is only designed for 32-bit systems. I tried using AI based on the article with and without 3dtoday. But the best I could achieve was after some .dtbo file was /dev/fb1 and /dev/event0. When running one Python script, the screen displayed rectangles with gradients from white to black, but after changing the .dtbo file, when I ran the same script, I only got a black screen with multicolored dull horizontal stripes. I couldn't display any color other than black, white, and gray. I followed most of the steps suggested by the AI, since, as I already said, I'm a Linux noob. I'd be glad if someone could help me. My connection pins: Display -> Zero 2W CS - GPIO18(CE0.SPI1) RST - GPIO26 DC - GPIO13 SDI - GPIO20(MOSI.SPI1) SCK - GPIO21(SCK.SPI1) BL(LED) - GPIO6 Touch_CK - GPIO21(SCK.SPI1) Touch_CS - GPIO17(CE1.SPI1) Touch_DI - GPIO20(MOSI.SPI1) Touch_DO - GPIO19(MISO.SPI1) Touch_PEN - GPIO12 Note: I'm from Russia and my English is pretty bad, so all text was translated using a translator. I'm attaching a photo of the latest result I was able to achieve.

Hi @sicxnull, @Nick A thank you very much for your support. Probably last night I was very confused when I wrote my post. Of course the v5.1 updated will be nice to have but looking better I can say to you and to @ventara that the armbian image suggested from Nick to Trauma (https://github.com/NickAlilovic/build/releases/download/20250306/Armbian-unofficial_25.05.0-trunk_X98h_bookworm_edge_6.12.11_xfce_desktop.img.xz) works fine on X96Q vs 5.1 only things the led in front remain always red and that why I was thinking it doesn't boot. Ethernet port works but wifi doesn't work. Never mind ethernet is enough. On the other side when I compare the two release (sicxnull and Nick) I didn't realize that I copy two times the same image on two different sd (I was really too tired) so don't consider the indication that I give you apart the wifi chip. That is right!

Oh great. Then I'll steal borrow your dts and replace the one currently in the framework later

6.12.y

on which kernel did you test?

Here is the opi3lts DTS I use. Eth, WIFI and BT work as they should. If someone feels like running a diff and making the adjustment. sun50i-h6-orangepi-3-lts.dts

Today all works, thank you for all who fixed this problem 🙂 apt update Get:1 http://security.debian.org trixie-security InRelease [43,4 kB] Get:2 http://deb.debian.org/debian trixie InRelease [140 kB] Get:3 http://deb.debian.org/debian trixie-updates InRelease [47,3 kB] Get:5 https://github.armbian.com/configng stable InRelease [5 467 B] Get:4 http://armbian.lv.auroradev.org/beta trixie InRelease [39,4 kB] Get:6 http://deb.debian.org/debian trixie-backports InRelease [54,0 kB] Get:7 http://security.debian.org trixie-security/main armhf Packages [88,8 kB] Get:8 http://deb.debian.org/debian trixie/non-free armhf Packages [69,9 kB] Get:9 http://deb.debian.org/debian trixie/non-free-firmware armhf Packages [6 685 B] Get:10 https://github.armbian.com/configng stable/main armhf Packages [434 B] Get:11 http://deb.debian.org/debian trixie/main armhf Packages [12,7 MB] Get:12 http://deb.debian.org/debian trixie/contrib armhf Packages [50,6 kB] Get:13 http://deb.debian.org/debian trixie-updates/main armhf Packages [5 144 B] Get:14 http://deb.debian.org/debian trixie-backports/main armhf Packages [133 kB] Get:15 http://deb.debian.org/debian trixie-backports/contrib armhf Packages [4 368 B] Get:16 http://deb.debian.org/debian trixie-backports/non-free-firmware armhf Packages [3 856 B] Get:17 http://deb.debian.org/debian trixie-backports/non-free armhf Packages [1 520 B] Fetched 13,4 MB in 12s (1 073 kB/s) 32 packages can be upgraded. Run 'apt list --upgradable' to see them.

I tried integrating the suggestion into the actual device tree. Feel free to test: https://testing.armbian.de/Armbian-unofficial_26.02.0-trunk_Orangepi3-lts_trixie_current_6.12.64_minimal.img.xz

Hey! i've been browsing and reading this thread for the past couple of days but i cant seem to find any version3 images. if i try to boot from sdcard, most of the times the led stays red, or turns blue but doesnt give any picture. Can i get some help with this?

On my Orange Pi 3 LTS I don't use ethernet, only wifi and it works OK... maybe that's why I didn't notice the problem... but here is some information about ethernet on Pi 3 LTS https://forum.armbian.com/topic/19846-orange-pi3-lts/page/11/#comment-226536

Specifically the file you want to look at is aml_autoscript What happens on a normal amlogic TV box is when the hidden reset button is pressed during boot, the boot loader looks for this file and runs it. This file then changes the stored uboot environment such that subsequent boots follow a new boot flow to boot first from sd or USB and fall back to android. If you follow the logic you can find the actual boot commands in the other files that get called.

Then If you look in the /boot folder, There are the scripts the Armbian system uses to get uboot to boot on amlogic. Generally Armbian uses extlinux for booting using a chain loaded uboot binary.