All Activity

Hi, I could try to help, my board is exactly the same as yours. Can you provide me a source with instructions of how to do that?

Hello, I come across this topic as I got a couple of cheap OrangePI CM4 boards. As per I can see, the board is not yet supported by Armbian, so I would like to ask what is the current best option. I have seen BananaPI CM4 was an option, but is this still valid? Also, I have tried using the Ubuntu version (i.e. Ubuntu 22.04 with kernel 5.10.160) provided by OrangePI on mine and I have recompiled the kernel as below: This works well, but it doesn't seem supporting the NPU (i.e. there is no device "/dev/rknpu"). So I was wondering if the BananaPI CM4 above is better from that point of view. Regards,

Hello, I am facing an issue with my Youyeetoo YY3568 board. After that, I attempted to flash my own Yocto (Radxa manifest–based) wic image for the YY3568 using RKDevTool on Windows, but the flashing did not complete successfully. Since then, the board is always detected in Maskrom mode and never switches back to Loader mode. What I have tried so far: 1- Flashed prebuilt Ubuntu image (YY3568_Ubuntu_EDP.img) from the official link: https://drive.google.com/drive/folders/1D90vztL9fRfWV7laV9mdcnZ5kNpxx_tl → Board still shows Maskrom mode after flashing. 2- Flashed SDK-based image and loader built using the official documentation: https://wiki.youyeetoo.com/en/YY3568/ubuntu → Board remains in Maskrom mode. I have tried flashing from both Windows (RKDevTool) and Linux (rkdeveloptool), but the board is consistently detected in Maskrom mode. Question: How can I recover the board from Maskrom mode and bring it back into Loader mode, so that I can flash images and make the board operational again? Any guidance would be appreciated. Thank you.

psst, I ordered a board, hopefully I've time and may get it going it takes a lot of *work* to even get it working and with more often than not , no (scant) documentation (e.g. missing dram controller docs ) / codes to even get it working. btw it is good for those who wish to have board support to donate in support of armbian in support of it, it is probably the only sustainable way to do so.

I like your kind of humor

Should be there. https://github.com/armbian/build/blob/00b6e17abfd859893a39f6445715a3327fed150a/config/kernel/linux-meson64-edge.config#L355 https://cateee.net/lkddb/web-lkddb/IP_NF_IPTABLES.html

thank you. I'l give that a try when I wake again.

http://blog.armbian.com/content/images/2026/01/githubhighlights-2.png This week’s Armbian development saw a major cleanup of legacy toolchain code, alongside numerous board-specific improvements and kernel updates. Support was added for the Nuvoton MA35D1 NuMaker IoT board, while the BananaPi CM4/M2S and Khadas VIM3L boards received updated U-Boot bootloaders. Several fixes addressed hardware compatibility, including Bluetooth on Orange Pi Zero2, Type-C issues on Helios64, and build stability for the Raspberry Pi 4B. The release also introduced enhanced audio support for Genio devices and new AV1 patches for Rockchip64. Continuous integration workflows were reorganized, and the Ubuntu Resolute image build was enabled, reflecting ongoing efforts to streamline and modernize the Armbian build system. "get completely rid of dead code toolchain stuff", pt2. by @rpardini in armbian/build#9218"get completely rid of dead code toolchain stuff", pt3. by @rpardini in armbian/build#9252"get completely rid of dead code toolchain stuff", pt4 - fixes. by @rpardini in armbian/build#9256Add post-build Armbian extension for burnable JetHub boards. by @QwaSeeK in armbian/build#8844BananaPi CM4/M2S: Update u-boot to v2026.01. by @pyavitz in armbian/build#9250board: add Nuvoton MA35D1 NuMaker IoT board support. by @TuAFBogey in armbian/build#9205bunch o' fixes: 6.18/current .configs (uefi-all/meson64) + boards KERNEL_TARGET + meson64 6.18 pcie debork again-again. by @rpardini in armbian/build#9247ci: organize GitHub Actions into meaningful categories. by @igorpecovnik in armbian/build#9260Enable Ubuntu Resolute image build. by @iav in armbian/build#9164Fix OP-TEE build on Ubuntu Jammy (older binutils). by @TuAFBogey in armbian/build#9249Fix Panther-X2. by @sicXnull in armbian/build#9243Fix typec on pinebook pro. by @amazingfate in armbian/build#9245genio: add alsa-ucm-conf + ucm2 config for working audio in userspace. by @rpardini in armbian/build#9235genio: collabora: bump to collabora's 6.19-rc5. by @rpardini in armbian/build#9251Helios64: fix Type-C PHY registration. by @iav in armbian/build#9158khadas-vim3l: u-boot: update v2026.01 u-boot fanciness. by @rpardini in armbian/build#9257mainline: bump edge to rc5. by @EvilOlaf in armbian/build#9244Meson64: Delete patches that are not required. by @pyavitz in armbian/build#9239meson64: remove upstreamed patch for 6.18.6 and rewrite the rest. by @EvilOlaf in armbian/build#9266mixtile-core3588e: alias ethernet0 to gmac0 for stable MAC address. by @rpardini in armbian/build#9237orangepizero2: fix bluetooth in edge kernel. by @EvilOlaf in armbian/build#9242radxa-zero2: fancy u-boot v2026.01 // minimal+full fusb302 enablement. by @rpardini in armbian/build#9253rockchip64-6.19: arm64: dts: rockchip: describe pcie ethernets on FriendlyElec NanoPC-T6. by @rpardini in armbian/build#9238Rockchip64: Add verisilion av1 patches. by @amazingfate in armbian/build#9240rockchip64: Helios64: fix Type-C PD negotiation. by @iav in armbian/build#9255rpi4b: fix build and boot issues. by @EvilOlaf in armbian/build#9267sunxi-current: recover lost Makefile entries. by @EvilOlaf in armbian/build#9236sunxi: bump current and edge to latest minor. by @EvilOlaf in armbian/build#9229sunxi: resolve some cross patch dependencies. by @EvilOlaf in armbian/build#9232sunxi: switch current and edge back to auto bumping. by @EvilOlaf in armbian/build#9234u-boot: run binwalk on all the produced u-boot bins (always). by @rpardini in armbian/build#9192Update jethome j200 kernel patchset, uboot to 2025.04. by @adeepn in armbian/build#9231View the full article

Hi @ff255, There is an effort to add this calculation in the U-Boot bootscript. I'll have a look at doing this during updates to initramfs or kernel, good suggestion! Groetjes,

Thank you very much! Regards, Chris

Best do what? Disable a systemd service? sudo systemctl disable --now systemd-resolved.service https://www.freedesktop.org/software/systemd/man/latest/systemd-resolved.service.html

update on this. I did try to install Helium/Helium Miner and it does not work. ill work on the devicetree to get that functionality present but for now be warned.

fixed

Hi @ff255, Next time, you can indeed try to calculate the load addresses using the following method: kernel_load_addr_r = (trunc( (fdt_load_addr_r + fdt_size + 1 + 64KiB) / align_to) + 1) * align_to ramdisk_load_addr_r = (trunc( (kernel_load_addr_r + kernel_size + 1) / align_to) + 1) * align_to With align_to being the alignment boundary - 2MiB for ARM64 and for other platforms it depends on their architecture, 4KiB is a safe and sane boundary to align to. edit (again): The +1 is to prevent an OBOE in U-Boot; if the next load_addr starts immediately after with no padding, the logic in U-Boot wrongly accuses the images to overlap The +64KiB is the "fdt_extrasize" which should allow for any possible addition to the DT by any of the (DT fixup) scripts. Groetjes,

Yay, it booted! 😃👏 @djurny , thank you very much! 🙏 bootlog from UART console Sorry, I gave wrong size for DT file... That seems right: /boot/dtb-6.12.9-current-rockchip64/rockchip# ls -l |grep rock64 -rw-r--r-- 1 root root 54333 Jan 12 2025 rk3328-rock64.dtb I guess it's ok until DT is smaller than align size So AFAICS if kernel size will grow, I should just re-calc the values? But now I got another problem, with this kernel HDMI suddenly stopped working... and all 3 LEDs (dc in, pwr, stby) are ON at the same time... although this seems to be a separate topic.. UPD: after apt-mark unhold kernel, dtb, firmware packages, apt-updating (to 6.12.58 kernel) and rebooting HDMI started to work again! For me this topic is solved, thank you once again! 👍 (Now I just wonder where that load address values come from, and why they didn't auto-change on kernel upgrade...)

Hi Wanted to try this Debian rolling release with Linux v6.18 from https://www.armbian.com/rockpie/ page, but both links there https://dl.armbian.com/nightly/rockpi-e/Forky_current_minimal https://dl.armbian.com/nightly/rockpi-e/Plucky_current_minimal lead to a 404 page on github.com. Thanks, Chris

Have solved another todo: grab overlay *.dtbo from Ky/Xunlong. There is still some quirks with SD/TF read/write speed (UHS / 1.8v mode). Also applied for Armbian maintainership on orangepirv2 in advance. Had some experiments with that M.2 to PCIe adapter I recently got. That oversized thing is an older Radeon with an Opi RV2 mounted on top. That does not work (no, card is so old it does not require extra 12V). Second image is a even older Nividia Geforce, That one shows up with "lspci" but does not work b/c no RiscV drivers (that's expected). Next ist an TP-Link / Aquantic 10 GbE Ethernet card. That one works, even without that extra power supply from the PC next to it. Not sure, if the Spacemit CPU can handle the ten gigs... Last image: the 2280-to-PCIe adapter with the eternal SATA power feed cable. LG // Sven-Ola

Hi everyone, and sorry for my poor English. I'd like to enable PWM on my CM3588 nanoPC with the latest Armbian Trixie version. Can anyone who's managed to get the PWM working properly tell me which pin to connect the PWM signal to and what exactly to do to enable it? Thanks to anyone who replies.

Thank you Pearo, What does "S/N" mean? I just ended up using my orange pi zero 3 gpio without the additional DTS, which made connector numbering available in the gpioinfo command... There were comments that made it sound not really necessary, and it was more work than I wanted to take on. The solution for me was: https://forum.armbian.com/topic/33800-orange-pi-zero-3-gpio/#findComment-181191 This was 2 years ago, and I haven't even thought about it, all this time.

I really hope that Orange Pi engineers learn to make Armbian patches, enter the community and give funding accordingly

Hallo, in want to start with odroid n2+ to organize a PV System with smart-power-meter(s) ... To reduce th amount of components I want to use min. 2x UART's from the odroid (without using the console port) + RS485 Transceiver(s) ... I understand that your dtbo file add support for the Uart's of the 40 pin Socket ! ? After upgrading to linux kernel-6.18.5 i need such a dtbs / dtb0 file... Where can I download these files atually ? Bye

How best to do that? I've been treating systemd like a rattlesnake which I've seen in record breaking size, 7 feet long and the size of my calf. I was about 6, my stepfather was farming, had come in for lunch, opened the door to go back out and plow, slammed the door, reached over it for a cheap busted shotgun and a shell. reopened the door and took the head off it. 85 years ago. I haven't had a whole lot of use for a rattlesnake since although I've seen hundreds. Blacksnakes OTOH are goodfellows. They keep the rodents away by eating them.

After applying the following two kernel patches which I understand are valid for mainline kernel only, I can use the display properly with a resolution 3440x1440 and refresh rate of 60Hz: patchwork.kernel.org [RFC,v1] drm/meson: venc: add support for HDMI DMT modes up to 3840x2160 -... github.com/chewitt/linux WIP: drm/meson: add support for higher bandwidth DMT modes committed Jan 5, 2026 xdarklight +3 -3 There's a report from a user with a DELL U3415W monitor and a Khadas VIM3 statin… - But having both patches applied or not does not matter, in general with mainline kernel the display is flickering/shaking only during boot, any idea how to get this addressed? thx

I've read that page and I can't seem to get it working with the image both jock and Victor Picinin recommended yet it doesn't boot off the eMMC nor the SD. I'm at the end of my rope!

Hi, As I can see on latest kernel for beta/trunk Armbian: https://imola.armbian.com/beta/pool/main/l/linux-6.18.6/linux-image-current-meson64_26.2.0-trunk.281_arm64__6.18.6-Sb6fe-D8ec8-Pe0be-C7d3eH1ff9-HK01ba-Ve377-Bc630-R448a.deb There is no module ip_tables (should be under /lib/modules/6.18.6-current-meson64/kernel/net/ipv4/netfilter/), so iptables does not work: "modprobe: FATAL: Module ip_tables not found in directory /lib/modules/6.18.6-current-meson64" Is this intentional? Thank you!