Search the Community

I'm putting together a build for a 3D printer, rk3308b-s board that has no ethernet, just a Fn-link wifi chip that is a knock-off of an rtl8192fs. I pulled the OEM dts and it describes the chip as an rtl8192cs. I'm pretty sure this is an out of kernel driver and my searches indicate I put source in userpatches. What do I need to add in the board/*.csc file to build to an image with the kernel module(s)? I do have a ralink ra2400, a mt7201 and some supported realtek dongles and If connected, I could git the code build and moprobe the module to test. Ideally, I would like to incorporate the driver via dkms in a armbian build. Can someone point me to the process?

Hi, the hardware in question: PCIe_TO_2-CH_SATA_HAT+ In expectation for the Rock 4D forum to arrive I am posting my issue here: The Rock 4D works and all is well The two SATA drives work over USB to SATA adapters - that is not ideal in the long term IMHO The HAT just arrived and i have no doubt in my mind that it can be defective in any way - i assume it is 100% operational. But when i connect it and plug the power in the Rock 4D boots, everything else works as usual, but the HAT just sits there without any signal. My questions: 1. How do i query the eeprom via the pins 27 & 28 (ID_SD & ID_SC), do i just enable the i2c_6 overlay? 2. What then? I queried the ahci module with: `modinfo ahci` but it is both a built in and i suspect it does not support my device anyway? Looking forward to try help get this nice board supported on Armbian for other FPC equipped devices.

Hello! Are there any plans for a stable minimal/IOT release for the Rock 4D, and if so, what’s the timetable? Thanks!

https://www.cnx-software.com/2025/10/25/35-orange-pi-4-pro-an-allwinner-a733-edge-ai-sbc-with-up-to-16gb-lpddr5-wifi-6/ https://www.cnx-software.com/2025/07/07/allwinner-a527-t527-and-a733-datasheets-user-manuals-and-linux-sdk-released/ http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/details/Orange-Pi-4-Pro.html Another Allwinner board dropped figuring out the wifi chip is always hard, seem to be https://www.taobao.com/list/item/931793873067.htm https://pine64.sfo3.cdn.digitaloceanspaces.com/doc/datasheet/oz64/AIC8800DC Datasheet v1.0.pdf as usual, it is uncertain if drivers and firmware is after all available. Ethernet according to CNX seemed to be YT8531CA Ethernet seemed to be same as that in OrangePi Zero 3 https://www.cnx-software.com/2023/07/03/orange-pi-zero-3-allwinner-h618-sbc-ships-with-up-to-4gb-ram/ WiFi is 'more critical' these days, if it is closed sourced and no firmware, then it is good as just a door stop. Then that thare are other stuff the figure out especially the : - DRAM controller, - and various DRAM timing and configuration aspects - many other low level specific stuff to even have u-boot to boot it up to the linux prompt. - then the other devices e.g. uart etc. - then HDMI - then gpu acceleration (or at least display video, not playing media yet) - then media - and finally NPU, don't seemed documented yet - many more known or unknown unknowns, audio etc

Hi, I'm new to the forums and am looking into replacing OEM Klipper firmware on a Sovol SV06 Ace, The main board looks very similar to the MKS Skipr with the following notable differences: rk3308 B emmc soldered on No SD card. Wifi/Bluetooth added - Original boards used realtek and the latest version uses Broadcom. OEM wifi is hit or miss on connecting and hopefull will be improved with Trixie based Armbian. Sovol has mostly complied with the GPL and source/configuration files are on github. IIRC the kernel version was 5.1x I'm a long time Linux user (Slackware 8.1), have contributed OpenWRT builds and have built custom Linux kernels. I think I've mapped out the install: flash the appropriate ambian image to a formated USB2.0 drive - Ideally with wifi ssid/wpa key ssh sovol@ip login sovol/sovol. su, suspect the root passwd will be makerbase. plug in usb, id drive in dmesg and mount dd if /dev/usb* of=/devmmcblk* Unmount drive and hopefully boot and access over wifi ssh. Install/configure Kipper/Mainsail... I have a recovery path that I have tested using rkdeveloptool/upgrade_tool and the original Sovol firmware. I've perused the armbian github pages looking the MKS Skipr build but have not found it yet. I'm willing to build a tailored (stripped if worthwhile) kernel. I'd appreciate any comments about broadcom wifi access and if newer kernels and newer wpa supplicant builds improve access enough to make it worthwhile. Comments on the overall plan. Pointers Sovol RG-4Z V1.1 SIZE.pdf

For those with a Radxa Cubie A7A/A7Z, I made a custom Armbian Build using the BSP kernel. https://github.com/NickAlilovic/build/tree/Radxa-A7A https://github.com/NickAlilovic/build/releases To build your own image: git clone https://github.com/NickAlilovic/build.git --branch Radxa-A7A ./compile.sh "do not change the kernel configuration" "show csc/wip/eos/tvb" "I understand and agree" "radxa-cubie-a7a" or "radxa-cubie-a7z" rest is up to you... - Display: Installed KMSCON framebuffer console (KMS/DRM-based system console) to provide a modern system console. - Boot: Added sfdisk labeling for the 'primary' partition to ensure U-Boot splash screen and logo.bmp detection. - U-Boot: Automated latest-release retrieval from GitHub API (radxa-pkg/u-boot-aw2501) to replace static binaries. - Kernel Device: Automated copying of allwinner device a733 and added 0004-Add-Allwinner-Device-a733.patch generation for a7a, a7s, and a7z device tree variants.

Hello to everyone. Being new around here I figured to drop one message here first... So, i have this Radxa Rock 4D SBC and i am quite impressed with it Me being me and SBC being what it is, yada... yada, i now have this hat+ from Waveshare - it is an dual SATA to PCIe adapter. It was designed for the Raspberry pi 5 obviously but Radxa has since started putting those FPC connectors on and i really would appreciate a 24/7 NAS with a SBC footprint... Long story short, it does not work out of the box - i have no doubt the product is okay it's just the HAT fails to initiate the OS and register. It reportedly has an eprom with data on it but my guess is it has to have a dtb overlay active and my rock 4D lacks anything in that regard (a "sata" in the overlay name) My issues? 1. Where is the Rock 4D forum or where do i post this issue best to?

I don't see it specifically listed, but does Armbian run on the Beaglebone black?

I wonder if a port is possible and/or feasible, if it is, where can I check? I tried searching on documentations for a guide on how to start a port, but couldn't find anything. If I remember correctly, xiaomi-elish hardware is very related to xiaomi-alioth, to the point of some of the code for PMOS being shared, obviously each hardware has it's quirks but, I think it's possible, i do have the device for testing, and I have some knowledge of programming, but I can learn more in the process.

Hi I've made a new kernel Auxiliary Display Driver for TM16XX and compatible LED controllers. This driver supports various LED controller chips, including TM16XX family, FD6XX family, PT6964, and HBS658. It provides support for both I2C and SPI interfaces. I wanted it to manage the hardware on the kernel space while having an easy sysfs user space interface. It also aims to reduce the code to maintain by relaying on existing kernel features instead of recoding them. Plus, you can switch to hardware i2c/spi (instead of software gpio) depending on the pins used. You can use "vfdconf-convert" to convert your existing vfd.conf to its device-tree version. Or you can use the already converted vfd.conf of https://github.com/arthur-liberman/vfd-configurations that are listed in the device table. You don't need to manually edit your device tree, the "make" command will apply the device tree source overlay to your dtb. It comes with a service written as a simple bash script. So it's easily customizable without having to write custom C code. Instructions and source code at https://github.com/jefflessard/tm16xx-display/ Could you please give it a try and report your feedback?

Hi, I'm a long time Armbian user and overall extremely happy. It my default Linux distro everywhere! Thanks to everyone who is developing or contributing to it! Every time I pickup a new board and deploy Armbian I have to edit the `armbianEnv.txt` file and change verbosity to 7. The same question repeats in my head. Why is it not the default? Systemd and startup messages spam up like crazy and they have nothing interesting to offer. I do care what hardware did the kernel detect or was a protocol correctly negotiated etc. I personally would have it in reverse, verbose kernel, quiet systemd. But thats just me. Could we at least have parity, if systemd verbose then make kernel verbose too, if kernel quiet then systemd quiet too. I'm trying to understand what was the rationale for having quiet kernel and verbose systemd? Thanks!!

After a ton of time porting the dts for modern kernels, i have a working release for the Bobcat 300 29X Variant To compile https://github.com/sicXnull/armbian-build/tree/Bobcat-29x . ./compile.sh build BOARD=bobcat-29x BRANCH=current BUILD_DESKTOP=no BUILD_MINIMAL=yes EXPERT=yes KERNEL_BTF=no KERNEL_CONFIGURE=NO KERNEL_GIT=shallow RELEASE=bookworm Link to Prebuilt Armbian-unofficial_26.02.0-trunk_Bobcat-29x_bookworm_current_6.18.4.img.xz First check to see if you have a compatible version. Flip the unit over and check the serial number. It will start with G290 or 295. This does not work on 28 or 285. How to Flash 1) Install Rockchip Flash Tools 2) Download bootloader (rk356x_spl_loader_ddr1056_v1.10.111.bin) attached here. 3) Boot device into LOADER mode. Plug USB Cable in to back of the unit, powered off. Open the device. With it powered on hold the reset button for 1 second, then immediately let off and hold the recovery button down until the PC recognizes you in LOADER mode 4) Follow the flash procedure found here. WARNING While I2C/Spidev is functional, i did not install Helium or the Lora packet forwarder for testing. Flash this image at your own risk if you still wish to use helium mining. rk356x_spl_loader_ddr1056_v1.10.111.bin

I have a Orange Pi Zero 2W and want to install a headless ( minimal ) OS. I have tried Armbian 25.5.1. I have an Ubuntu box and I have attempted to write to the SD card using Armbian ImagerImager, by selecting an image from the app as well as downloading an image to use. In both instances, I get a FLASH failure. See the attached image for the diag link. Can anyone give me some insight?

Hi all, I would like to ask support for the board EMB-3531. I'm having problem with booting this board from SD card. Here are some informations about this board. I hope that someone can help me with it. Thank you so much! I try to erase the emmc and flash the MiniLoaderAll.bin but it doesn't help. Or i don't have a correct image with armbian for this board. https://my.kos.org.cn:5154/rockchip/EMB3531/emb3531.pdf

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.

Please help. We bought a board on AliExpress, but no one provided any documentation. And I can't ask the seller for it. Can anyone share any information? It's very difficult to figure out which pin goes where without documentation on the circuit diagrams. But given my situation, I set up two Ethernet interfaces. I haven't tested them at full capacity, but I can ping from both networks... myd lt527m 16e2d 180 e sx Thanks a lot.

clone the latest armbian/build repo, run ./compile.sh but fail. I try native or docker build, all fail.

after quite a few frustrating attempts to setup a built environment, fixing some issues, jumping over some hoops for the build, I managed to get to the 'starting point' of a build ./compile.sh [🌱] uuidgen not found [ uuidgen not installed yet ] [🌱] Using prebuilt Armbian image as base for 'ubuntu-jammy' [ DOCKER_ARMBIAN_BASE_IMAGE: ghcr.io/armbian/docker-armbian-build:armbian-ubuntu-jammy-latest ] [🌿] Docker info [ Docker 19.03.11 Kernel:4.12.14-lp151.28.91-default RAM:31.28GiB CPUs:8 OS:'openSUSE Leap 15.1' hostname 'snoopy1.internal' under 'Linux' - buildx:yes - loop-hacks:yes static-loops:no ] [🌱] Creating [ .dockerignore ] [🌱] Docker launcher [ enabling all extensions looking for Docker dependencies ] [🌱] Extension manager [ processed 27 Extension Methods calls and 82 Extension Method implementations ] [🌱] Adding rootfs encryption related packages [ cryptsetup cryptsetup-initramfs ] [🌱] Preparing rkdevflash host-side dependencies [ rkdevflash ] [🌱] Creating [ Dockerfile; FROM ghcr.io/armbian/docker-armbian-build:armbian-ubuntu-jammy-latest ] [🌱] Armbian docker image [ already exists: ghcr.io/armbian/docker-armbian-build:armbian-ubuntu-jammy-latest ] [🌱] Building [ Dockerfile via 'buildx build --progress=plain --load' ] [🔨] #0 building with "default" instance using docker driver [🔨] [🔨] #1 [internal] load build definition from Dockerfile [🔨] #1 transferring dockerfile: 2.12kB done ... [🔨] #6 [2/6] RUN echo "--> CACHE MISS IN DOCKERFILE: apt packages." && DEBIAN_FRONTEND=noninteractive apt-get -y update && DEBIAN_FRONTEND=noninteractive apt-get install -y --no-install-recommends bash git psmisc uuid-runtime bc binfmt-support bison libc6-dev make dpkg-dev gcc ca-certificates ccache cpio debootstrap device-tree-compiler dialog dirmngr dosfstools dwarves flex gawk gnupg gpg imagemagick jq kmod libbison-dev libelf-dev libfdt-dev libfile-fcntllock-perl libmpc-dev libfl-dev liblz4-tool libncurses-dev libssl-dev libusb-1.0-0-dev linux-base locales lsof ncurses-base ncurses-term ntpdate patchutils pkg-config pv qemu-user-static rsync swig u-boot-tools udev uuid-dev zlib1g-dev file tree expect colorized-logs unzip zip pigz xz-utils pbzip2 lzop zstd parted gdisk fdisk aria2 curl wget axel parallel python3-dev python3-distutils python3-setuptools python3-pip python2 python2-dev gcc-x86-64-linux-gnu gcc-aarch64-linux-gnu gcc-arm-linux-gnueabihf gcc-arm-linux-gnueabi gcc-riscv64-linux-gnu debian-archive-keyring libc6-amd64-cross g++-aarch64-linux-gnu g++ btrfs-progs cryptsetup openssh-client f2fs-tools nilfs-tools xfsprogs zerofree qemu-utils qemu-utils libudev-dev libusb-1.0-0-dev dh-autoreconf build-essential gcc-arm-linux-gnueabi gcc-or1k-elf qemu-utils [🔨] #6 0.958 --> CACHE MISS IN DOCKERFILE: apt packages. [🔨] #6 49.04 Ign:1 http://archive.ubuntu.com/ubuntu jammy InRelease [🔨] #6 49.04 Ign:2 http://security.ubuntu.com/ubuntu jammy-security InRelease [🔨] #6 97.09 Ign:3 http://archive.ubuntu.com/ubuntu jammy-updates InRelease ... [🔨] #6 200.2 Err:2 http://security.ubuntu.com/ubuntu jammy-security InRelease [🔨] #6 200.2 Temporary failure resolving 'security.ubuntu.com' ... [🔨] #6 481.5 Err:1 http://archive.ubuntu.com/ubuntu jammy InRelease [🔨] #6 481.5 Temporary failure resolving 'archive.ubuntu.com' [🔨] #6 529.5 Err:3 http://archive.ubuntu.com/ubuntu jammy-updates InRelease [🔨] #6 529.5 Temporary failure resolving 'archive.ubuntu.com' Is anyone else encountering a similar issue? The builds seemed to be failing repeatedly at DNS resolution to the repositories. Didn't manage to get past this point as the builds failed repeatedly here many minutes to like 1/2 hour and abort, many times with no successes so far. They also seem to be the same few accesses and possibly packages. [🔨] #6 481.4 Err:1 http://archive.ubuntu.com/ubuntu jammy InRelease [🔨] #6 481.4 Temporary failure resolving 'archive.ubuntu.com' [🔨] #6 529.4 Err:3 http://archive.ubuntu.com/ubuntu jammy-updates InRelease [🔨] #6 529.4 Temporary failure resolving 'archive.ubuntu.com' [🔨] #6 577.5 Err:4 http://archive.ubuntu.com/ubuntu jammy-backports InRelease [🔨] #6 577.5 Temporary failure resolving 'archive.ubuntu.com' [🔨] #6 577.5 Reading package lists... [🔨] #6 578.1 W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/jammy/InRelease Temporary failure resolving 'archive.ubuntu.com' [🔨] #6 578.1 W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/jammy-updates/InRelease Temporary failure resolving 'archive.ubuntu.com' [🔨] #6 578.1 W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/jammy-backports/InRelease Temporary failure resolving 'archive.ubuntu.com' [🔨] #6 578.1 W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/jammy-security/InRelease Temporary failure resolving 'security.ubuntu.com' [🔨] #6 578.1 W: Some index files failed to download. They have been ignored, or old ones used instead.

I'm looking for Orange Pi RV2 RISC-V support. This board is gaining popularity due to the Orange Pi manufacturer's good reputation with Arm. I have successfully built both Orange Pi and Raspberry Pi aarch64 builds on Debian from source so I'd like to know how to build Armbian for Orange Pi RV2 riscv64. What would I need to modify in the build process? Thanks!!

Is there a specific reason why orangepi cm5 isn't supported? Or is it simply because nobody has contributed? Because I am willing to add support for it if there aren't any serious issues when building armbian for this board. The webpage for the board is currently empty. I see two issues when using Armbian on orangepi cm5: 1. The ethernet and the fan won't work. There is a device tree published by Laurent Pinchart that may fix this. 2. armbian-install bricks the board. The only way to recover the device is by enabling maskrom and using rkdeveloptool to flash a new image. Other than these Armbian seems to work fine on orangepi cm5. Has anyone tried using (and also installing) armbian on this board?

I just got a mystery box from Ameridroid that contained a ODROID-GO-Ultra. Hardkernel has an old Ubuntu 20.04 image. Does Armibian support this device?

hi, im trying to make my radxa 4d in to a open media vault server, iv down loaded the file from armbian's web side but it wont boot, pluging it in to one of my raspberry pi's and useing gparted, i can only see one partision for it and can view it, dose this need a boot loader? iv also tryed downloading Debian 14 (Forky) from the armbian web site and got that to boot, but the script from armbian-config is broken ( missing stuff like php) and iv tryed the script from open media vault but that errors with eth0 missing. do i need to install a boot loader on the armbian open media vault image ?

hi guys, yesterdays announcement of Qualcomm Arduino UNO Q on some Dragonwing SoC ... but heard anybody about it already? how it can be open? some questions ... P.

Hello team, I encountered a dependency conflict while trying to upgrade the package armbian-bsp-cli-panther-x2-current to version 25.8.2. The issue seems to be a mismatch in the required version of base-files. Here's a summary of the issue: Attempted upgrade command: apt install armbian-bsp-cli-panther-x2-current Error message: armbian-bsp-cli-panther-x2-current : Depends: base-files (>= 25.8.2) but 25.8.1-12.4+deb12u11-bookworm is to be installed Currently installed version of base-files: base-files: 25.8.1-12.4+deb12u11-bookworm (installed) Available versions for base-files from the repository (apt policy base-files): Installed: 25.8.1-12.4+deb12u11-bookworm Candidate: 25.8.1-12.4+deb12u11-bookworm Version table: 25.8.1-12.4+deb12u11-bookworm 500 25.5.1-12.4+deb12u11-bookworm 500 ... It appears that the repository ( http://apt.armbian.com/pool/bookworm-utils/b/base-files ) does not provide the required version of base-files (25.8.2) for the arm64 architecture. Only the armhf architecture package is available, but armbian-bsp-cli-panther-x2-current depends on the arm64 version. Could you please help investigate the issue or confirm whether the repository will be updated to include version 25.8.2 of base-files? Thank you for your support!

...