Active threads

I am coming from a yocto build for a dev board. I had to make u-boot patches, kernel config changes, and custom DTS tree. I'm trying to adapt this to Armbian, one step at a time. I started with building am image for sk-am62b.conf. I did not expect u-boot to boot from correctly. I was glad to see console messages, but expectedly, u-boot didn't continue. I made a new board config for this, duplicating sk-am62b.conf, but changing a critical line I made to get this to work previously. TIBOOT3_FILE="tiboot3-am62x-gp-evm.bin" Now, the boot process gets through u-boot and loads the Linux kernel. However, the kernel halts because it cannot find the root file system. Waiting for root device PARTUUID=26aa2b10-02... I confirmed the device in u-boot, and it seems to agree. Environment size: 5112/126972 bytes => echo load mmc ${bootpart} ${fdtaddr} ${bootdir}/dtb/${fdtfile} load mmc 1:2 0x88000000 /boot/dtb/ti/k3-am625-sk.dtb => run finduuid => echo part uuid ${boot} ${bootpart} uuid part uuid mmc 1:2 uuid => part uuid mmc 1:2 26aa2b10-02 I then modified my board config: BOOT_FDT_FILE="myir-6254-am62x/myir-6254-am62x.dts" But after booting, u-boot didn't acknowledge this: (From the u-boot environment) fdtfile=ti/k3-am625-sk.dtb So, I finished applying my u-boot patches that I made under the Yocto build. Some of these changes may be redundant: edited: am62x_evm_a53_defconfig + CONFIG_DEFAULT_FDT_FILE="myir-6254-am62x.dts" +CONFIG_TI_FDT_FOLDER_PATH="myir-6254-am62x" After booting into u-boot, now I see the change made: fdtfile=myir-6254-am62x.dts Then I see this: Running uenvcmd ... 14857759 bytes read in 983 ms (14.4 MiB/s) 36805120 bytes read in 1549 ms (22.7 MiB/s) Failed to load '/dtb/myir-6254-am62x.dts' libfdt fdt_check_header(): FDT_ERR_BADMAGIC No FDT memory address configured. Please configure the FDT address via "fdt addr <address>" command. Aborting! ERROR: Did not find a cmdline Flattened Device Tree Could not find a valid device tree Scanning for bootflows in all bootdevs This is not unexpected either - since the files are not the image yet. When u-boot can't find the device tree, it loads a grub interface. And when I 'e'dit that I see the line linux /Image root=PARTUUID=076c4a2a-02 rootwait rootfstype=ext4 and change it to: linux /Image root=/dev/mmcblk1p2 rootwait rootfstype=ext4 The kernel sees the rootfs, and proceeds to boot. If I change it to using the PARTUUID, as above, it also boots. If I manually place the DTB file where u-boot reported it is is looking (copied from my running yocto system) (in /dtb/) The kernel boots, without the grub interface. However, the same situation occurs, where it is waiting for the root device. Waiting for root device PARTUUID=26aa2b10-02... I have a few things going on here. I think in order to boot to an OS I need: 1) Solve why the kernel does not see the root partition when booting from u-boot (but does when I can get into the grub interface) 2) How to properly implement a custom device tree structure. I know there are overlays, but I'd prefer to just drop in my whole custom tree. Once I get there, I can proceed to implement some of the kernel modification I did within the yocto build environment, but this first. Thanks for the assistance.

@Sand_Death congrats on finding this... I also found the sunxi PCIE driver to be limited. I think someone would need to develop it a bit, or write something from scratch, in order to get more devices to work.

Basicly, a LLM has dozens of transformer layers (attention layer + ffn layer). We cannot load the whole model data, or even a single transformer layer on NPU sram(~1MB). So, we put the whole model in RAM, transport a slice of data to NPU by command stream each time, then next slice. Several times of the model size may be transported between ddr and npu. This cost is huge so I still run LLM on pure cpu.

It's ARMv7 so it could potentially run 64bit instructions. https://developer.arm.com/documentation/den0013/0400/Introduction-to-Assembly-Language/The-ARM-instruction-sets I recall reading that opi pc is running 64-bit from someone here on armbian forums now that I think about it, but don't remember where. It could also be a Mandela effect and I am completely wrong. If so, I'm sorry, did not mean to make you upset. Not hard to miss at all, or you think everybody has every single board memorized? 😉 If you included that you think it should run 32 bit instructions and has a 32bit kernel, I would have asked you to provide "uname -m" to confirm, no need to be nasty. 🙃 Kinda strange that you could get the system running with su in 64bit with a 32bit kernel though.

Hey OP, the Loader.zip link is dead. Mind resharing it? Can't proceed without it. Thanks!Hey OP, the Loader.zip link is dead. Mind resharing it? Can't proceed without it. Thanks!

If you plan to add this to the Armbian framework to have it included, I suggest to bring the drive in a dkms compatible state and create an extension (https://github.com/armbian/build/tree/main/extensions) to add this driver to specific boards. I know that other out-of-tree wifi drivers are added here (https://github.com/armbian/build/blob/main/lib/functions/compilation/patch/drivers_network.sh), however this is already a huge mess and I won't allow any more additions, rather than looking forward to some point in the future when this is dissolved in to individual extensions which make things hopefully more maintainable. AI will probably a huge help in this matter.

my rock64 sometimes hangs with unknow reason. Enabling/testing watchdog did not help. Does hardware watchdog is working at all ? some outputs: # dmesg | grep -i watchd [ 0.838922] dw_wdt ff1a0000.watchdog: No valid TOPs array specified [ 0.928770] rk_gmac-dwmac ff540000.ethernet: Enable RX Mitigation via HW Watchdog Timer [ 3.920201] systemd[1]: Using hardware watchdog 'Synopsys DesignWare Watchdog', version 0, device /dev/watchdog0 [ 3.921218] systemd[1]: Watchdog running with a hardware timeout of 28s. # wdctl Device: /dev/watchdog0 Identity: Synopsys DesignWare Watchdog [version 0] Timeout: 28 seconds Timeleft: 18 seconds Pre-timeout: 0 seconds After doing kernel panic via echo c > /proc/sysrq-trigger device not rebooting. On raspberry pi that test is working fine.

i am running a H96(model RK3318) android tv box, its old, i have lost itss remote as well. basically noow i am tryinh to install ambrain os on it, but the conditon now is , even the android id now visible on the tv/monitor, basically when i insert the power cable on the display "boot" is showing with blue light. after few sec, some number like "07:01" is showing, but when i connect my htmi cable, the tv is detecting the htmi. but its showing no signal. basically there is no output on the display. i have tried many methods, there is no problem in htmi, or tv or cable. the andoird itself not booting. and the sd card method for ambrain also not working . tried the toothpick method and everything. but still its nott working!. i dont know why there is no output on the display. i dont know whhat issue. usb, htmi, everything is working. even charger also working.

I have been able to download it from the first page, are you sure?

i used grub at the end of the day and booted from nvme.

If Windows can see the share but has trouble connecting, it's also worth checking the SMB version being used on both sides. I've run into cases where enabling the correct SMB protocol or recreating the saved Windows credentials fixed the issue right away.

I tried 0.6, wifi not working, i own one with EA6521. I made it work on 0.5 changing the .dts a little bit (thanks to Claude) Quote: cat /proc/device-tree/seekwcn_boot/gpio_chip_en 2>/dev/null | od -An -tu4 603979776 285212672 0 # Fix seekwcn_boot GPIOs sed -i 's/gpio_host_wake = <0x24 0x06 0x01>/gpio_host_wake = <0x24 0x12 0x00>/' /tmp/x88pro.dts sed -i 's/gpio_chip_wake = <0x24 0x10 0x00>/gpio_chip_wake = <0x24 0x11 0x00>/' /tmp/x88pro.dts sed -i 's/gpio_chip_en = <0x24 0x11 0x00>/gpio_chip_en = <0x24 0x06 0x00>/' /tmp/x88pro.dts # Fix sdio-pwrseq reset-gpios sed -i 's/post-power-on-delay-ms = <0x8c>/reset-gpios = <0x24 0x06 0x01>;\n\t\tpost-power-on-delay-ms = <0x8c>/' /tmp/x88pro.dts # Disable wireless-bluetooth and wireless-wlan nodes sed -i '0,/status = "okay"/{/wireless-bluetooth/{n;n;n;n;n;n;n;n;n;s/status = "okay"/status = "disabled"/}}' /tmp/x88pro.dts # Verify seekwcn_boot node grep -A 12 'seekwcn_boot {' /tmp/x88pro.dts cp /boot/dtb/rockchip/rk3528-x88pro.dtb /boot/dtb/rockchip/rk3528-x88pro.dtb.bak dtc -I dts -O dtb /tmp/x88pro.dts -o /boot/dtb/rockchip/rk3528-x88pro.dtb 2>/dev/null # 3. Fix module loading mv /etc/modules-load.d/aic8800-btlpm.conf /etc/modules-load.d/aic8800-btlpm.conf.disabled echo "blacklist aic8800_bsp" > /etc/modprobe.d/blacklist-aic.conf echo "blacklist aic8800_btlpm" >> /etc/modprobe.d/blacklist-aic.conf echo "blacklist aic8800_btlpm_sdio" >> /etc/modprobe.d/blacklist-aic.conf echo "extraargs=modprobe.blacklist=aic8800_bsp,aic8800_btlpm,aic8800_btlpm_sdio" >> /boot/armbianEnv.txt # 4. Build skw modules dkms add -m ea6621q -v 1.0 2>/dev/null || true dkms build -m ea6621q -v 1.0 dkms install -m ea6621q -v 1.0 # 5. Set module load order cat > /etc/modules-load.d/skw.conf << 'EOF' skw_bootcoms skw_sdio skw skwbt EOF Right now i cannot try it, if someone else wants to try this... EDIT: the if in the wifi section of the provisioning doesn't detect correctly, the searched directory doesn't exists so it won't install the module

I managed to start de A5E from nvme, but upgrading the packages fails. Installing armbian-firmware_26.8.0-trunk.125_all.deb failed With: data.tar lzma error.... Several months ago I got the same error but ignored it. Now everything is almost working, I tried to find out what went wrong. I can extract package with dpkg-deb -x on another system. MD5sum is the same on A5E and other system. This problem occurs on sdcard and nvme card. Btw: it is the 4G version of the A5E. Any idea how I can solve this?

Hi @NHO, copy the Armbian kernel and boot with this: yes probably. You will also need the correct *.dtb in /boot - you need to rename / replace k1*.dtb->x1*.dtb e.g. if you run the original uboot. The GPU probably does not work, since Mesa does / will not support the K1 imagination GPU. You need the Bianbu GPU binaries and userspace tools (...wayland...) that matches them. The spacemit-gpu-addon.sh script (see green [solution] button on top of this page) uses a copied / stripped down version of the Bianbu Repo to install Gnome/Wayland but I doubt that this works under Gentoo Linux.

Hello, what's the current status of kernel 6.18+ on the rock 2F? I haven't tried building it on my own yet, I just need Wi-Fi and USB working with a fairly recent kernel as 6.1 is way too old now.

I have an AD-Z33 V1.2 which has the same rockchip as the xt-q8l-v10 but I cannot get it to start in Maskrom mode for eemc/bootloader flashing. Can anyone shed some light on how I can do this?

hi. I gave up a long time ago. but now I found the board in the closet and decided to look again. I made a typo in the marking. I have rk3518. can you upload your firmware backup to google drive. or whatever suits you.

@sr4armbian You could try building your own X98H image and use the kernel headers from your build. Your kernel headers will be in the build/output/debs directory, and the image will be in the build/output/images directory. I would recommend starting with a fresh install with this new image and kernel headers. git clone https://github.com/NickAlilovic/build.git --branch v20250306 cd build ./compile.sh choose "Do not change kernel configuration" choose "Show CSC/WIP/EOS/TVB" choose "I understand and agree" choose "X98H" choose "edge" rest is up to you... I used this method to get my display working. But that was a while ago.

Hi everyone, I'm running a few services on an Armbian-based SBC and need a reliable SMTP Service Provider for system alerts, backup reports, and application notifications. Has anyone here used SMTP Service Provider iDealSMTP with Armbian, or compared it with other SMTP solutions for lightweight ARM servers? I'm interested in deliverability, ease of setup, and long-term reliability. I'd appreciate any experiences or recommendations. Thanks!

Patched the .dtb for v6.1, currently not yet in final format. I will probably create a commit to Armbian with a .dts for our board. I am attaching the dtb/dts just to keep track of the progress. Here are results of the RKNN test launch: rknn_api/rknnrt version: 2.3.2 (429f97ae6b@2025-04-09T09:09:27), driver version: 0.9.8 model input num: 1, output num: 1 input tensors: index=0, name=input, n_dims=4, dims=[1, 224, 224, 3], n_elems=150528, size=150528, fmt=NHWC, type=INT8, qnt_type=AFFINE, zp=0, scale=0.007812 output tensors: index=0, name=MobilenetV1/Predictions/Reshape_1, n_dims=2, dims=[1, 1001, 0, 0], n_elems=1001, size=2002, fmt=UNDEFINED, type=FP16, qnt_type=AFFINE, zp=0, scale=1.000000 custom string: Begin perf ... 0: Elapse Time = 8.06ms, FPS = 124.12 ---- Top5 ---- 0.935059 - 156 0.057037 - 155 0.003881 - 205 0.003119 - 284 0.000172 - 285 So: CPU: OK GPU: OK via Panfrost NPU: OK, RKNN inference works on RKNPU rk3566-box-X88PRO20-npu.dtb rk3566-box-X88PRO20-npu.dts

Refer to the experiences here: I think someone wrote that the mainline kernel has NPU support. Is this NPU going to load only models that are in the Rockchip model repository?

This week's updates center on new board enablement, Rockchip platform refinements, and tooling and kernel maintenance. Board support expanded across multiple silicon families, with the addition of Seeed Studio reComputer RK3576/RK3588 DevKits and the Anbernic RG DS handheld image. The EasePi A2/R2 received substantial revisions to its board configurations and device trees, alongside a vendor logo transition to Linkease. SpacemiT K1 boot support was updated, and per-SoC LINUXCONFIG separation was introduced for the TQ family to better isolate kernel configurations. Rockchip received the bulk of low-level improvements. Notable changes include AUX recovery for USB-C DP Alt Mode in the dw-dp driver, device-tree-based LED configuration for the r8169/r8125 controllers, and an updated patch ensuring stable PCIe Ethernet MAC addresses across many boards. Additional fixes resolve slow WiFi on the NanoPi R76S via SDIO SDR104, enable Bluetooth on the Orange Pi 5 Ultra edge kernel, and restore the tm16xx driver on current kernels. On the tooling and maintenance side, Armbian Imager 2.0 was released, the mainline kernel was bumped to 7.1-rc6, and the rtl8192eu driver was re-enabled following a cleanup of compilation warnings. A previously merged USB gadget NULL pointer fix was reverted pending further evaluation. #Armbian #EmbeddedLinux #Rockchip #SBC #KernelDevelopment Changesmainline: bump to 7.1-rc6. by @EvilOlaf in armbian/build#9922Add Anbernic RG DS board image and Anbernic vendor logo. by @crackerjacques in armbian/armbian.github.io#326Add jellyfin-ffmpeg release constraints and ip-wrapper for easepi-r2. by @ifroncy01 in armbian/build#9942arm64: dts: overlay: add radxa display 8hd for rock5t. by @Ken-Vamrs in armbian/linux-rockchip#498board-vendor-logos: update EasePi vendor logo to Linkease. by @ifroncy01 in armbian/armbian.github.io#321drm: rockchip: dw-dp: add AUX recovery for USB-C DP Alt Mode. by @mingzhangqun in armbian/linux-rockchip#494easepi-r2/a2: fix device tree. by @jjm2473 in armbian/linux-rockchip#491feat(boards): Add Seeed Studio reComputer RK3576/RK3588 DevKit support. by @baorepo in armbian/build#9719Give each TQ SoC family its own LINUXCONFIG. by @schmiedelm in armbian/build#9924Introducing Armbian Imager 2.0. by @SuperKali in armbian/imager#143Milk-V Jupiter disable EEPROM node. by @pyavitz in armbian/build#9944nanopi-r76s: fix slow WiFi by enabling SDIO SDR104. by @SuperKali in armbian/build#9929net: r8169: add device tree based LED configuration for r8125. by @mingzhangqun in armbian/linux-rockchip#497orangepi5-ultra: enable Bluetooth on edge kernel via hci_bcm. by @pdapandapda in armbian/build#9697Revert "rockchip64: fix USB gadget NULL pointer crash in eth_get_drvinfo (6.18 + 7.0)". by @EvilOlaf in armbian/build#9926rockchip64: enable back tm16xx driver for current kernel. by @paolosabatino in armbian/build#9941rockchip64: update "describe PCIe Ethernet controllers" patch for stable MAC (many boards). by @rpardini in armbian/build#9933rtl8192eu: re-enable and fix tons of compilation warnings. by @EvilOlaf in armbian/build#9927SpacemiT: Update K1 boot support. by @pyavitz in armbian/build#9930Treat imx93 as slow hardware. by @schmiedelm in armbian/armbian.github.io#323Update EasePi A2/R2 board configs and device trees for improved hardware support. by @ifroncy01 in armbian/build#9907Update VERSION. by @EvilOlaf in armbian/build#9938View the full article

This week's updates center on new board enablement, Rockchip platform refinements, and tooling and kernel maintenance. Board support expanded across multiple silicon families, with the addition of Seeed Studio reComputer RK3576/RK3588 DevKits and the Anbernic RG DS handheld image. The EasePi A2/R2 received substantial revisions to its board configurations and device trees, alongside a vendor logo transition to Linkease. SpacemiT K1 boot support was updated, and per-SoC LINUXCONFIG separation was introduced for the TQ family to better isolate kernel configurations. Rockchip received the bulk of low-level improvements. Notable changes include AUX recovery for USB-C DP Alt Mode in the dw-dp driver, device-tree-based LED configuration for the r8169/r8125 controllers, and an updated patch ensuring stable PCIe Ethernet MAC addresses across many boards. Additional fixes resolve slow WiFi on the NanoPi R76S via SDIO SDR104, enable Bluetooth on the Orange Pi 5 Ultra edge kernel, and restore the tm16xx driver on current kernels. On the tooling and maintenance side, Armbian Imager 2.0 was released, the mainline kernel was bumped to 7.1-rc6, and the rtl8192eu driver was re-enabled following a cleanup of compilation warnings. A previously merged USB gadget NULL pointer fix was reverted pending further evaluation. #Armbian #EmbeddedLinux #Rockchip #SBC #KernelDevelopment Changesmainline: bump to 7.1-rc6. by @EvilOlaf in armbian/build#9922Add Anbernic RG DS board image and Anbernic vendor logo. by @crackerjacques in armbian/armbian.github.io#326Add jellyfin-ffmpeg release constraints and ip-wrapper for easepi-r2. by @ifroncy01 in armbian/build#9942arm64: dts: overlay: add radxa display 8hd for rock5t. by @Ken-Vamrs in armbian/linux-rockchip#498board-vendor-logos: update EasePi vendor logo to Linkease. by @ifroncy01 in armbian/armbian.github.io#321drm: rockchip: dw-dp: add AUX recovery for USB-C DP Alt Mode. by @mingzhangqun in armbian/linux-rockchip#494easepi-r2/a2: fix device tree. by @jjm2473 in armbian/linux-rockchip#491feat(boards): Add Seeed Studio reComputer RK3576/RK3588 DevKit support. by @baorepo in armbian/build#9719Give each TQ SoC family its own LINUXCONFIG. by @schmiedelm in armbian/build#9924Introducing Armbian Imager 2.0. by @SuperKali in armbian/imager#143Milk-V Jupiter disable EEPROM node. by @pyavitz in armbian/build#9944nanopi-r76s: fix slow WiFi by enabling SDIO SDR104. by @SuperKali in armbian/build#9929net: r8169: add device tree based LED configuration for r8125. by @mingzhangqun in armbian/linux-rockchip#497orangepi5-ultra: enable Bluetooth on edge kernel via hci_bcm. by @pdapandapda in armbian/build#9697Revert "rockchip64: fix USB gadget NULL pointer crash in eth_get_drvinfo (6.18 + 7.0)". by @EvilOlaf in armbian/build#9926rockchip64: enable back tm16xx driver for current kernel. by @paolosabatino in armbian/build#9941rockchip64: update "describe PCIe Ethernet controllers" patch for stable MAC (many boards). by @rpardini in armbian/build#9933rtl8192eu: re-enable and fix tons of compilation warnings. by @EvilOlaf in armbian/build#9927SpacemiT: Update K1 boot support. by @pyavitz in armbian/build#9930Treat imx93 as slow hardware. by @schmiedelm in armbian/armbian.github.io#323Update EasePi A2/R2 board configs and device trees for improved hardware support. by @ifroncy01 in armbian/build#9907Update VERSION. by @EvilOlaf in armbian/build#9938View the full article

Hello everyone! I'm using this patch set from github to run armbian on x88pro13 (which has RK3528 with Mali 450 MP2). Everything seems to work fine (even wifi), but i'm not able to enable hw acceleration on kodi interface (it shows llvmpipe, so it's sw rendering) Do you have any hints on how to do that? Because at the moment i get 80% cpu just for the kodi gui. Thanks!

I see similar issues with some s905x2 and some s905c3 boxes I have. I've never dug into the issue to see what is happening, but the workaround that works for my cases is that when the boot from emmc fails, I boot from an SD card (I have an SD card ready just for this). Then reboot from emmc, and then it usually will boot. For some reason a successful boot from SD clears up something that then allows the emmc to boot properly. This is what works for me, don't know if your situation is the same or different but you can try.