Active threads

@sven-ola Have you tried booting from a microSD card? I downloaded Armbian-unofficial_26.02.0-trunk_Orangepirv2_trixie_current_6.18.18_gnome_desktop.img and flashed it to my microSD card, but it won't boot. log: sys: 0x200 try sd... bm:3 j... U-Boot SPL 2022.10_armbian-2022.10-Sd61c-P155c-H452d-V4161-B61c5-R448a (Mar 17 2026 - 03:52:17 +0000) [ 0.381] DDR type LPDDR4X [ 0.383] set ddr tx odt to 80ohm! [ 0.393] lpddr silicon init consume 11ms [ 0.394] Change DDR data rate to 2400MT/s [ 0.633] Boot from fit configuration x1_orangepi-rv2 [ 0.635] ## Checking hash(es) for config conf_18 ... OK [ 0.641] ## Checking hash(es) for Image uboot ... crc32+ OK [ 0.652] ## Checking hash(es) for Image fdt_18 ... crc32+ OK [ 0.674] ## Checking hash(es) for config config_1 ... OK [ 0.677] ## Checking hash(es) for Image opensbi ... crc32+ OK [ 0.725] U-Boot 2022.10_armbian-2022.10-Sd61c-P155c-H452d-V4161-B61c5-R448a (Mar 17 2026 - 03:52:17 +0000) [ 0.732] CPU: rv64imafdcv [ 0.734] Model: ky x1 orangepi-rv2 board [ 0.738] DRAM: 2 GiB [ 0.830] Core: 414 devices, 29 uclasses, devicetree: board [ 0.843] WDT: Started PMIC_WDT with servicing (60s timeout) [ 0.848] WDT: Started watchdog@D4080000 with servicing (60s timeout) [ 0.857] MMC: [ 0.956] *** Warning - bad CRC, using default environment [ 0.961] initialize_console_log_buffer [ 0.962] Have allocated memory for console log buffer [ 0.967] In: serial [ 0.969] Out: serial [ 0.971] Err: serial [ 1.116] k1x_qspi spi@d420c000: qspi iobase:0x0x00000000d420c000, ahb_addr:0x0x00000000b8000000, max_hz:26500000Hz [ 1.124] k1x_qspi spi@d420c000: rx buf size:128, tx buf size:256, ahb buf size=512 [ 1.131] k1x_qspi spi@d420c000: AHB read enabled [ 1.136] k1x_qspi spi@d420c000: bus clock: 26500000Hz, PMUap reg[0xd4282860]:0x0000075b [ 1.143] k1x_qspi spi@d420c000: AHB buf size: 512 [ 1.148] SF: Detected XM25QU128C with page size 256 Bytes, erase size 64 KiB, total 16 MiB List of MTD devices: [ 1.159] * nor0 [ 1.160] - device: flash@0 [ 1.163] - parent: spi@d420c000 [ 1.166] - driver: jedec_spi_nor [ 1.170] - path: /soc/spi@d420c000/flash@0 [ 1.173] - type: NOR flash [ 1.176] - block size: 0x10000 bytes [ 1.180] - min I/O: 0x1 bytes [ 1.183] - 0x000000000000-0x000001000000 : "nor0" [ 1.188] - 0x000000000000-0x000000010000 : "bootinfo" [ 1.193] - 0x000000010000-0x000000020000 : "private" [ 1.198] - 0x000000020000-0x000000060000 : "fsbl" [ 1.203] - 0x000000060000-0x000000070000 : "env" [ 1.208] - 0x000000070000-0x0000000a0000 : "opensbi" [ 1.213] - 0x0000000a0000-0x000001000000 : "uboot" [ 1.219] Failed to get fastboot key config: -19 [ 1.222] Failed to probe HUSB239: -19 [ 1.227] RGMII interface [ 1.228] eth0: ethernet@cac80000 [ 1.231] MAC mapping file path not set in environment [ 1.236] K1X: :_load_env_from_blk [ 1.247] Can't set block device [ 1.248] Net: eth0: ethernet@cac80000 [ 1.254] Hit any key to stop autoboot: 0 Loading K1-X Environment ... [ 2.260] [ 2.261] Running NVMe Scan ... [ 2.272] pcie_dw_k1x pcie@ca400000: has no power-on-status flag, use default. [ 2.277] Now init Rterm... [ 2.279] pcie prot id = 1, porta_init_done = 0 [ 2.283] Now waiting portA resister tuning done... [ 2.288] porta redonly_reg2: 00005d37 [ 2.292] pcie_rcal = 0x00005d37 [ 2.295] pcie port id = 1, lane num = 2 [ 2.298] Now int init_puphy... [ 2.301] waiting pll lock... [ 2.304] Now finish init_puphy.... [ 2.307] pcie_dw_k1x pcie@ca400000: Unable to get phy0 [ 2.312] pcie_dw_k1x pcie@ca400000: Unable to get phy1 [ 2.317] pcie_dw_k1x pcie@ca400000: PCIe interface power on, set gpio 116 to 1 [ 3.426] PCIE-0: Link down [ 3.438] pcie_dw_k1x pcie@ca800000: has no power on gpio. [ 3.441] pcie_dw_k1x pcie@ca800000: has no power-on-status flag, use default. [ 3.448] Now init Rterm... [ 3.450] pcie prot id = 2, porta_init_done = 0 [ 3.455] Now waiting portA resister tuning done... [ 3.459] porta redonly_reg2: 00005d37 [ 3.463] pcie_rcal = 0x00005d37 [ 3.466] pcie port id = 2, lane num = 2 [ 3.470] Now int init_puphy... [ 3.472] waiting pll lock... [ 3.475] Now finish init_puphy.... [ 3.479] pcie_dw_k1x pcie@ca800000: Unable to get phy0 [ 3.484] pcie_dw_k1x pcie@ca800000: Unable to get phy1 [ 4.590] PCIE-1: Link down [ 4.642] pcie_dw_k1x pcie@ca400000: has no power-on-status flag, use default. [ 4.646] Now init Rterm... [ 4.648] pcie prot id = 1, porta_init_done = 0 [ 4.653] Now waiting portA resister tuning done... [ 4.657] porta redonly_reg2: 00005d37 [ 4.661] pcie_rcal = 0x00005d37 [ 4.664] pcie port id = 1, lane num = 2 [ 4.668] Now int init_puphy... [ 4.671] waiting pll lock... [ 4.673] Now finish init_puphy.... [ 4.677] pcie_dw_k1x pcie@ca400000: Unable to get phy0 [ 4.682] pcie_dw_k1x pcie@ca400000: Unable to get phy1 [ 4.687] pcie_dw_k1x pcie@ca400000: PCIe interface power on, set gpio 116 to 1 [ 5.795] PCIE-0: Link down [ 5.807] pcie_dw_k1x pcie@ca800000: has no power on gpio. [ 5.810] pcie_dw_k1x pcie@ca800000: has no power-on-status flag, use default. [ 5.817] Now init Rterm... [ 5.819] pcie prot id = 2, porta_init_done = 0 [ 5.824] Now waiting portA resister tuning done... [ 5.828] porta redonly_reg2: 00005d37 [ 5.832] pcie_rcal = 0x00005d37 [ 5.835] pcie port id = 2, lane num = 2 [ 5.839] Now int init_puphy... [ 5.841] waiting pll lock... [ 5.844] Now finish init_puphy.... [ 5.848] pcie_dw_k1x pcie@ca800000: Unable to get phy0 [ 5.853] pcie_dw_k1x pcie@ca800000: Unable to get phy1 [ 6.959] PCIE-1: Link down [ 6.963] no nvme partition table available [ 6.964] Couldn't find partition nvme 0:1 [ 6.968] Couldn't find partition nvme 0:1 [ 6.972] Couldn't find partition nvme 0:1 [ 6.976] Couldn't find partition nvme 0:1 [ 6.980] Couldn't find partition nvme 0:1 =>

Heres what I am seeing on my screen https://drive.google.com/file/d/1SSNnvOy-BjxAzklcAoApjS2zz1HnMn-v/view?usp=sharing Heres me messing with the headphon jack https://drive.google.com/file/d/1Z2Guva-FWYv2mu3VCPujXPoc7r_iqpB6/view?usp=sharing

I ran into what appears to be the same issue (see my log). I have added the suggested qemu-user-static package, which forced removal of another qemu- family package I had previously installed to work around problems with binfmt. Not only did it compile correctly, it also ran so much faster, as you can see in the number of log lines for this build! Thank you for the assistance and getting me on the right track with the right package selection! Best Regards, Lobosito

@tin harden A7A mainline is still a WIP.

@Thur_Wander For debugging purposes, UART is highly recommended. Use balena Etcher to write the compiled image to your SD card.

Hi, I am here in 2026 with the Amrbian 26.2.1, I've tried the proposed fix from @c0rnelius but it's not working on my OS version. If anyone has any updated solution that'd be amazing. Thank you

The most current download images for Helios64 are now all provided with linux 6.18.xx. I downloaded a minimal image and checked the dtb: it would not appear to contain the opp-microvolt patch that made Helios64 finally stable. So for the ones who have stability issues again on Helios64, I attached the patched dtb compiled for linux 6.18.xx using the exact same opp-microvolt values as in the previous dtb versions I compiled for linux 6.6 and 6.12. The current linux deb files can be downloaded from beta.armbian.com, the linux 6.18.18 deb files I used can be downloaded from here (to be installed with 'dpkg -i linux*'). In order to install the dtb, simply unzip it, copy it into the proper location, update initramfs and reboot: # install the dtb with the opp-microvolt patch: unzip rk3399-kobol-helios64.dtb-6.18.18-opp.zip cp rk3399-kobol-helios64.dtb-6.18.18-opp /boot/dtb/rockchip/rk3399-kobol-helios64.dtb update-initramfs -u reboot rk3399-kobol-helios64.dtb-6.18.18-opp.zip

Another attempt, again check https://testing.armbian.de/r4s/?C=M&O=D for most recent debs. This time adding an artificial bus scan delay into the r4s dts. Another poke in the dark but perhaps...

See inline comments. Dirty SPI may cause this but without logs from serial console this is just a guess

I will try downgrading u-boot next once I find the older package somewhere. Kernel does not seem to be the cause given that it has been working fine with both my own build 6.6.122 and 6.6.128 before and rolling back not helping. New device is something I had on my mind for a while. But given the RAM and SSD prices these days, I do not really want to overspend. Not to mention that the SBC landscape has not been that great lately when it comes to compact NAS offerings. HC4 is five years old at this point. Many even recommend N100 but this is a whole different size category.

hi all. any hints to merge olimex imx8 board and compile armbian kernel 6.x and deb12 ?

hello ,my box is mortal t1 2g8rom and motherboard show mortal t2 v2.0 it's broken and i wanna make linux boot what's the most version to be able for my box

I don't know if it's useful, but folks have been attaching external GPUs to low power boards for a while. My personal favorite was sacking and desoldering a USB3 controller to reuse it's PCIE lane: https://mloduchowski.com/raspberry-pi-4-b-pci-express/ Others have run into the same BAR limitation you noted: https://www.jeffgeerling.com/blog/2020/external-gpus-and-raspberry-pi-compute-module-4/ From a practical perspective, I'm not sure how many folks would be interested in discrete GPUs, as I'm not sure these sorts of boards would have the CPU or PCIE lanes to really make use of that extra horsepower. Most would get a dedicated embedded system, or a bespoke NVidia setup. For what it's worth, I ran into an issue where the kernel was too big for u-boot to boot it, and would just throw a synchronous abort and reset. The difference between working and not working was 7 MB.

Good morning I have big problem I have tv box Transpeed-H616_ I update with orange pi But i can't back to old firmware

Hi Armbian_25.5.1_Rpi4b_bookworm_current_6.12.28 broken after last upgrade. I run apt upgrade which installed kernel 6.18.10. It breaks ZFS. Provided ZFS version, 2.3.2, supports kernels up to 6.14. Don't forget a snapshot before "apt upgrade" 🙂 Regards, Chris

what board did you replace it with?

I have a T9 2017 rk3328 box running Ubuntu xcfe many hours for downloading. There are not problems but xcfe displays lunchs himself many times and i have to close 20 or more instances of this application when checking the progress. Box is not crashed by this funny clonning. is it possible to avoid this? p.d. la test trunk

Hi there! I've got 2 of these industrial android boards (s2809-mb-v1.8c) and I've been trying to get armbian running on the. For a while but so far no success. These 2 boards were sold as being tinker boards but I believe that they are EVBs instead. Here are some photos: https://ibb.co/4wTm20s9 https://ibb.co/Z6PfvZCr https://ibb.co/HTFWLKTS I have also managed to find a link to the Chinese seller: https://m.globalsources.com/product/quad-core-board_1195354789f.htm Debug method: UART2 (because they don't have HDMI only LVDS and EDP ports) PMIC: RK808 So far trying to run them on the latest armbian 26 and 25 gets stuck at Starting Kernel. Ive managed to find a version 20 for the miqi board that loads kernel and boots into armbian bullseye but stops before login using a single core only and only 512mb of ram, anything beyond that just never starts the kernel using tinker and tinker-s DTBs. I have also managed to get a full dump of a current android image that is running correctly on one of the board and extracted: loader, kernel, dtb from the partitions. Extracting the images was painful cause none of the rk (linux rkdeveloptool, rkdev and rkandroidtool) methods worked.. only through uboot so that was painful to get 16mb parts from some of the images and join them all. Has anyone ever encountered any of these boards? Maybe anyone has an idea on how to get them up and running? Thanks for your help and sorry if this post is under the incorrect forum.

My ROCK3A has a jumper option to disable SPI clock, so whole SPI will be bypassed and only SD-card works then. I power with fixed 12V (USB-C pigtail). I do not know now what version the board/PCB is. AFAIR from Radxa docs other versions have no such jumper. Maybe you already tried/know all this. Maybe wipe the SPI via rkdevelop. W.r.t. Rockchip SBC's (various brands) I am a bit confused what boot-device prefence/priority is. From schematics I saw it depends on a resistor value, but many boards in the world and endless resistor values possible.

@guy cal Igor just fixed that: https://github.com/armbian/configng/pull/765

Hi all, For whom who are looking for the image to be installed on this box: I have the same mxq box with H3 SoC and I flashed the Tritium H3 (libre) armbian image successfully and playing with it for year. Wifi not working, not sure about Bluetooth because I don't use them at all. Currently it works as my cups printer server for my brother usb printer.

This device is not yet fully compatible with the mainline Linux kernel. Realtek USB 2.5GbE adapters, in particular, are known to have issues when used over USB 3 on these devices. The vendor-provided kernel reportedly offers better tuning for these adapters, though it is still not entirely flawless.

As amazingfate (the Armbian dev for this device) clearly stated on the forum: cellular and camera are not working, only display, touch, wifi, and bluetooth are functional—so it won't replace your phone OS for calls and texts

Can confirm. S905X5M is a different beast than the S905X. If there's interest, I can start another thread with an image and status, once this is somewhat more stable. Currently booting, but not without some debug console interaction on power up. In the meantime, code's up at https://github.com/tparys/build/tree/odroidc5 if anyone wants to go poking

Hello, I hope you don't have any problem. Maybe me and my brother have defective or more unstable helios64 than you. Only thing I can say that Prahal share here the specifics files rk3399-kobol-helios64.dtb-6.XX.xx-L2-hs400-opp in this forum since two years ago my helios64 and my brother's helios64 work stable only with it. I back to 6.12.58 Kernel with rk3399-kobol-helios64.dtb-6.12.xx-L2-hs400-opp file and freeze firmware/kernel with armbian-config.