Active threads

@jshkol I think the best way to support both the Orange Pi and Radxa A733 is to use the Orange Pi repository as the base. Radxa uses containers to build U-Boot and the kernel, which makes the Armbian scripts complicated and messy. Dok2b was able to build a Debian image for Cubie using Orange Pi's sources. https://github.com/dok2d/cubie-a7z-debian/tree/master/scripts

@alexc This happens on their kernel too, I created a topic on their forum (https://forum.radxa.com/t/hailo8-pcie-fw-control-timeout-on-cubie-a7a-with-asmedia-pcie-switch/31023), I suspect that the problem is on the Allwinner side and a patch is needed not even from Radxa but from Allwinner. But yesterday I was looking at their forum and there are quite a lot of complaints about the PCIe line, but this remains unanswered, I suspect that they think this is a feature and not a bug. If you need any other help or further study of the problem, I am ready to help in any way I can.

moved to tvboxes

edit: nope it looks like that the server was blacklisted somewhere in my adblocker blacklist.

@Ovaday First of all, thank you for the initiative. This repository contains the files that will be used as example to enable your board in Armbian: https://github.com/hqnicolas/ArmBoardBringUp The example file you're referring to is this one: https://github.com/hqnicolas/ArmBoardBringUp/blob/main/config/boards/h96-tvbox-3566.tvb The boot settings you should use may vary considerably from this reference, but your device will need a configured bootloader. https://github.com/hqnicolas/ArmBoardBringUp/tree/main/patch/u-boot/v2026.04/board_h96-tvbox-3566 You will need to focus on the new kernels like: https://github.com/hqnicolas/ArmBoardBringUp/tree/main/patch/kernel/archive/rockchip64-7.1/dt The repository you need to interact with to include these files is this one: https://github.com/armbian/build You need to validate everything before publishing, so do some hard work using this compiler: https://docs.armbian.com/Developer-Guide_Overview/

I again apologize, even though I can not see what was "hostile" in what I wrote. I simply misunderstood and apologized for that, even though I think you are the passive aggressive one here. I am so sorry. (I will add you to ignore list so I will never accidentally interact with you again, so no need to leave the community if it is due to me)

After a few days of testing I have to say it works great. No issue whatsoever. Stable, usb, eth, wifi, bt works. Great work!

I have a few of those and when connected to RPi5 PSU and set to 12V, it can power my Rock5B with NVME SSD and some other peripherals as well.

I tested the new driver in my box (the router and box are in two different rooms). As you can see, just as @WallaceWebs mentioned, the upload speed has improved significantly. Before merging this pull request, the speed was 8.25Mbps, and now it is 33.46Mbps. Idle Latency: 11.17 ms (jitter: 1.63ms, low: 10.02ms, high: 12.42ms) Download: 38.57 Mbps (data used: 22.8 MB) 97.38 ms (jitter: 31.45ms, low: 16.86ms, high: 432.50ms) Upload: 33.46 Mbps (data used: 54.8 MB) 127.94 ms (jitter: 41.37ms, low: 28.14ms, high: 628.78ms) Packet Loss: 0.0%

@8lall0 Thank you very much for helpfull comittment. I put the changes into the Repro. New Release 0.7

I haven’t tested this yet but there’s some work done on vp9 and vc1 support for Allwinner. https://github.com/jernejsk/linux-1/tree/vp9-v1 https://github.com/jernejsk/linux-1/tree/vc1-v2

I'm trying to use the radxa 4k camera with armbian. The camera worked on Radxa OS but i wanted to have more camera drivers, hence why I made a custom armbian build with more drivers enabled. The /boot/dtb/ folder was missing so I tried to get the same structure as what I have on my radxa zero3 /boot/dtb/qcom/overlay/qcs6490-radxa-cm-q64-rpi-cm5-io-cam0-imx415.dtbo /boot/dtb/qcom/qcs6490-radxa-dragon-q6a.dtb armbianEnv.txt rootfstype=ext4 user_overlays=qcs6490-radxa-dragon-q6a-cam1-radxa-camera-4k overlay_prefix=qcs6490 overlays=radxa-dragon-q6a-cam1-radxa-camera-4k fdtfile=qcom/qcs6490-radxa-dragon-q6a.dtb usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u I used the overlays that I build with radxa overlays both use 6.18.2-current-qcs6490

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.

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.

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!

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.

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 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!