Active threads

[UPDATE] Manual Partition Strategy on RK322x (Kingston eMCP) - GPT Signature Error & TOS Anomaly Hi everyone, Following up on my struggle with the "Red LED" issue on this RK3228A box (Kingston eMCP). Since the Multitool wouldn't boot from the SD, I moved to a more aggressive approach using rkdeveloptool on macOS to flash Armbian images and the Multitool components directly to the internal storage. The Loader Struggle (Samsung vs. Kingston) I compiled rkdeveloptool on macOS and tested multiple loaders to initialize the RAM/Flash: • rk322x_loader_v1.10.256.bin • rk322x_loader_v1.11.253.bin • rk322x_loader_v1.10.238_256.bin None of them solved the SD boot issue. Interestingly, they identify my flash as SAMSUNG, even though the physical chip is Kingston: Flash Info: Manufacturer: SAMSUNG, value=00 Flash Size: 7216 MB | Block Size: 512 KB | Page Size: 2 KB Tested Images & Offsets (Direct Flashing via rkdeveloptool) • Armbian Community (6.1.62/Minimal 6.18.7): Tested 0x0 and 0x8000. • LibreELEC (10.0, 11 and 12): Tested 0x0 and 0x8000. • Multitool (v1.11 & Standard): Tested 0x0 and 0x2000. • Educabox (Legacy 4.4.194 / NAND): Tested 0x0. All attempts resulted in "GPT signature wrong", likely because the Secure Boot/Trust OS expects the Android rkparameter structure instead of a standard GPT. When I then changed the GPT table in parameters.txt, it sometimes wouldn't even give me a signal via serial. The Strategy: Manual Image Construction (Partition Replacement) Since full image flashing failed, I followed the "Partition Replacement" strategy to manually construct the layout. I read about it in a post titled long story LINUX on rk3229 rockchip by @fabiobassa: manually constructing the partition layout to satisfy the Bootrom's legacy requirements while injecting Armbian components into specific offsets. The parameter.txt Modification (The Key Step): The root cause of the "GPT signature wrong" error was the mismatch between the Android partition table expected by the device's Secure Boot/Trust OS and the standard GPT layout of Linux images. Original State: The stock parameter.txt defined over 12 Android-specific partitions (cache, recovery, kpanic, metadata, etc.), complicating the boot process. Modified State: I manually edited parameter.txt to consolidate all user partitions into a simplified Linux layout. I removed the Android clutter and defined a single large system partition for the RootFS. New Layout Definition: mtdparts=rk29xxnand:0x00002000@0x00002000(uboot),0x00004000@0x00004000(trust),0x00007800@0x0000A800(resource),0x00006000@0x00012000(kernel),0x00006000@0x00018000(boot),-@0x00028000(system) Component Preparation (Where the files came from) I did not use generic loaders for the boot partition. Instead, I extracted and repackaged each component on macOS to fit this new map: U-Boot (uboot @ 0x2000): I extracted the original bootloader from my device backup using dd to preserve compatibility. Command: dd if=backup_original.img of=uboot_extraido.img skip=8192 count=8192 System/RootFS (system @ 0x28000): I extracted the raw EXT4 Linux partition from the Armbian image. Command: dd if=Armbian...minimal.img of=particao_linux.ext4 skip=8192 count=2269184 Kernel (kernel @ 0x12000): Extracted vmlinuz-6.18.7-rockchip from the Armbian image and wrapped it with Rockchip headers using mkimage. Command: mkimage -A arm -O linux -T kernel -C none -a 0x60408000 -e 0x60408000 -n "Linux" -d vmlinuz... kernel.img Ramdisk (boot @ 0x18000): Extracted uInitrd from Armbian and wrapped it as a ramdisk image. Command: mkimage -A arm -O linux -T ramdisk ... -d uInitrd... boot.img Resource/DTB (resource @ 0xA800): I used the specific Device Tree Blob for this box (rk322x-box.dtb) extracted from the Armbian build and renamed it to resource.img. Afterwards, I tested with resource-linux which was linked in the original discussion, but still did not have success. The Flashing Sequence & Current Anomaly With the files prepared and the partition map redefined, I flashed the components using rkdeveloptool. The Sequence: Initialize: db rk322x_loader_v1.10.238_256.bin Partition Map: prm parameter.txt (Injecting the simplified layout). Flash Images: wl 0x2000 uboot_extraido.img (My extracted U-Boot) wl 0x4000 trust_with_ta_ga4fd2d1.img wl 0xA800 resources-linux.img (The DTB) wl 0x12000 kernel.img wl 0x18000 boot.img wl 0x28000 particao_linux.ext4 (The Armbian RootFS) The Result (The "TOS" Anomaly): The write process returns 100% Success, but the device fails to boot. The serial log (1.5Mbps) reveals a loop with a specific error: GPT 0x63337df8 signature is wrong recovery gpt fail! tag:LOADER error,addr:0x2000 hdr 633377e0 + 0x0:0x20534f54,0x20202020... The Anomaly: The error points to address 0x2000. The header read back is 0x20534f54, which is ASCII for "TOS " (Trust OS). It seems the Bootrom or the initial loader is hardcoded to expect the Trust Image at 0x2000, but my parameter.txt (and the standard Rockchip layout) places U-Boot at 0x2000 and Trust at 0x4000. Even when I flash my extracted U-Boot there, the system seems to be looking for a Trust signature. At this point, I don't know what I'm doing anymore and have spent around 20 hours in this project testing things. Any guidance on how to proceed from more experienced devs such as @fabiobassa, @Harleyyyu and @jock would be greatly appreciated to save my sleepless nights. Thanks for reading.

Hello @Malay! Same for you: cannot reproduce. Can you rebuild with SKIP_ARMBIAN_REPO=yes? This builds a little longer but skips cached stuff. Alternatively, rm -r ./cache from the build dir. To help with this, I will start the following commands on my PC and upload the results later to https://privat-in.de/ (Download section). LG // Sven-Ola

Was running Ubuntu Noble and mpv-0.37 is from Noble-repo. On Trixie the mpv is version 0.40 (Debian Trixie repo) which somehow does not seem work with the ffmpeg-v4l2request. Are you running Trixie or Bookworn? Is your device Opi5-Plus or RK3588? So far on my Opi5-Plus no luck with 10Bit Hevc or any 10Bit video on mpv with mainline kernel.

Hi everyone, I have rock 5c with PWM fan. I want to control the fan speed manually. Running on Armbian 25.11.1 Noble. Sorry if its obvious I am newbie to this

This video should give you the information you need for setting up a usb debug uart connection:

@Nick A I am not sure whether you can help release some versions of image with ufs supported, as I tried to compile from source with @chainsx git, but not once successful. If you can release the relevant versions of ufs support image? Thanks

@Nick A Hi Nick, how are you? I have a motherboard identical to the one in the photo you posted, with an AXP313A. I tried the image you recommended, but the Wi-Fi didn't work. Could you give me any advice?

Update on NanoPi M4v2 ... I pulled the most recent Armbian build, and manually ran the build for the M4v2, and it fails on kernel patch "general-gpio-driver-no-sleep". See pastebin at https://paste.armbian.com/puvorasuco for failed build. Checking upstream at https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git, it looks like branch 6.18.y already has the subject patch, and was pushed today. Since both the rockchip and rockchip64 families use mainline kernel, I just submitted a PR that kills that patch for both. See https://github.com/armbian/build/pull/9368.

Hi, It seems that the Odroid N2 armbian builds do not support using armbianEnv.txt AT ALL. See this forum entry from 2021: I am facing the same issue with Armbian 26.2.1 Minimal dmesg shows the following: [ 0.000000] Kernel command line: root=UUID=c8906fe5-129c-4388-840c-58c43c541176 rootwait rootfstype=ext4 splash=verbose console=ttyAML0,115200 console=tty1 consoleblank=0 coherent_pool=2M loglevel=1 ubootpart=001c9d62-01 libata.force=noncq usb-storage.quirks= cgroup_enable=memory with the following in /boot/armbianEnv.txt: verbosity=1 console=both overlay_prefix=meson rootdev=UUID=c8906fe5-129c-4388-840c-58c43c541176 rootfstype=ext4 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u I also tried adding extraargs= but nothing ends up in the command line. The old forum entry does mention editing the boot.ini to manually append it to bootargs, however I am not sure where that is located in the image and how to modify it. I tried both booting with petitboot and without, both show the same issue.

some things are happening at the bleeding edge https://lore.kernel.org/u-boot/?q=a733 pay attention to u-boot, the most important thing are dram controller, pmic, mmc/sd etc then of course kernel as well https://lore.kernel.org/linux-sunxi/?q=a733

Take some time but I was able to identify the CLK pin. Shorting the marked pins (CLK and GND in this case) was able to switch MaskRom mode. Note: in early boot stages the eMMC CLK only working in legacy mode (24Mhz).

Sorry in advance, but this is a bit of a dive. But, I haven't seen this fully captured and explained anywhere, and think this would be a useful thing to know for anyone who's doing arm64 development on a PC, which seems very relevant here ... I started pulling this thread when moving some software from Ubuntu Jammy to Noble, where the arm64 build process went from 20 mins to 50 mins. When I was done, it below to 15 min, and all I did was poke some flags for qemu's emulated CPU. The TL;DR version is that setting the environment variable QEMU_CPU to something like "cortex-a53" or "max,pauth-impdef=on" or even what I settled on, "max,pauth=off" saves massive amounts of time, and should be used anywhere you are running debootstrap, apt, or python in an emulated environment. However, you can't blindly set it everywhere because these flags are not defined for other architectures and will cause a hard stop when emulating PC or RISC-V. This has also shown up in the Armbian Build System. If you want to see this first hand, use the example here. Just save the following in test.sh: echo -n "testing... " for i in $(seq 2 10000); do is_prime=1 j=2 while ((j*j <= i)); do if (( i % j == 0)); then is_prime=0 break fi ((j++)) done if (( is_prime == 1 )); then echo $i > /dev/null fi done echo "done" And then run it in docker after ensuring a few things are installed ... ~ $ sudo apt install binfmt-support qemu-user-static ~ $ time docker run --rm -it --platform linux/arm64 -v .:/test ubuntu:noble /test/test.sh testing... done real 0m37.620s user 0m0.013s sys 0m0.022s ~ $ time docker run --rm -it --platform linux/arm64 -v .:/test ubuntu:jammy /test/test.sh testing... done real 0m4.700s user 0m0.011s sys 0m0.023s And we can wrestle that performance back by fiddling with QEMU flags ... ~ $ time docker run --rm -it --platform linux/arm64 -v .:/test --env QEMU_CPU=max,pauth=off ubuntu:noble /test/test.sh testing... done real 0m4.694s user 0m0.011s sys 0m0.024s So qemu bug? Not quite. The qemu emulator is a host application, and is the same both jammy and noble docker images, and I think the root cause was found here, and first appears in Ubuntu Lunar (23.10). The short version looks like gcc's stack protection logic wasn't operating as expected as the stack layout is a little different than it is on PC, a CVE was filed, and the "fix" is now stressing a slow code path in qemu. For the record, my heart goes out to "steev" and his slow, hours-per-bisect march to the answer. Pulling that thread a bit more, the QEMU Documentation has the following to say on the subject of arm64 pointer authentication: The qemu docs also suggest that the qemu impdef algorithm is the default, but I've not seen this on my version. It's possible this may be addressed in a much newer version of qemu, but that's not available in the Noble repos. It could be overridden via tonistiigi/binfmt (but I've not yet tested that). For what it's worth, it's not possible to just add a simple wrapper to qemu fix this either, as seen in this Github Example, and that's due to the Linux Kernel Binfmt Interface. The 'F' flag forces the kernel to store a handle to the specified emulator, and make it available in chroot and Docker contexts, and that doesn't help if it's only the wrapper it grabs and not the emulator binary. Similarly, it's not possible to pass additional flags via this interface, so without a change to the qemu binary, the QEMU_CPU environment variable may be the only way to work around this immediately. The other curious bit is what does QEMU_CPU=cortex-a53 enable to recover qemu speed? The answer is absolutely nothing. it just turns CPU features off. At a glance, I'm not sure if that something qemu is doing indirectly, or glibc conditionally enables at runtime. If anyone knows better than I here, please drop a comment. The curious can check can via: ~ $ docker run --rm -it --platform linux/arm64 ubuntu:noble cat /proc/cpuinfo processor : 0 model name : ARMv8 Processor rev 0 (v8l) BogoMIPS : 100.00 Features : fp asimd aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm jscvt fcma lrcpc dcpop sha3 sm3 sm4 asimddp sha512 sve asimdfhm dit uscat ilrcpc flagm sb paca pacg dcpodp sve2 sveaes svepmull svebitperm svesha3 svesm4 flagm2 frint svei8mm svef32mm svef64mm svebf16 i8mm bf16 rng bti mte mte3 sme smei16i64 smef64f64 smei8i32 smef16f32 smeb16f32 smef32f32 smefa64 mops hbc CPU implementer : 0x00 CPU architecture: 8 CPU variant : 0x0 CPU part : 0x051 CPU revision : 0 ~ $ docker run --rm -it --platform linux/arm64 --env QEMU_CPU=cortex-a53 ubuntu:noble cat /proc/cpuinfo processor : 0 model name : ARMv8 Processor rev 4 (v8l) BogoMIPS : 100.00 Features : fp asimd aes pmull sha1 sha2 crc32 cpuid CPU implementer : 0x41 CPU architecture: 8 CPU variant : 0x0 CPU part : 0xd03 CPU revision : 4

@billymore I was able to detect my transpeed box using the toothpick trick. Here are some links that might help figure it out. Maybe even going on irc and asking the sunxi guys. https://oftc.catirclogs.org/linux-sunxi/search?q=tx1 https://groups.google.com/g/linux-sunxi/c/OrktE3duFDA

Hello, I'm stuck as well. I tried to boot on different version of Armbian made for H313 (X96Q) but without success (burning image on USB drive, booting with AV FEL button pressed during boot). LED remains RED and no booting. I tried miniarch. I tried to enter fel mode via USB and Debian virtual Machine witout succcess (the TX1 does not appear as USB peripheral during my USB FEL attempts).

Thank you OP, I used HeliOS64 for a long time until it started to get disconnected after few hours of use that that was annoying. And so I stopped using it. I have just started using Claude-code. I am missing a remote backup solution. Claude-code gave me encouragement to revive it. I got directed to https://www.armbian.com/helios64/ to download, the only issue I found was that initially my 2.5Gbe worked and then after reboot stopped. Cloud code help me get that fixed. Below is what got it working again: # Step 1: Enable 2.5GbE (then reboot) echo "overlays=rk3399-pcie-gen2" | sudo tee -a /boot/armbianEnv.txt sudo reboot # Step 2: Install driver & Tailscale sudo apt update && sudo apt install -y build-essential dkms git linux-headers-current-rockchip64 cd /usr/src && sudo git clone https://github.com/awesometic/realtek-r8125-dkms.git r8125-9.013.02 cd r8125-9.013.02 && sudo ./dkms-install.sh Best of luck

@Nick A Thank you for your excellent work! I managed to compile it myself and shared it with someone who has the same board (IK316-EMCP_V1.0). 1. Changed kernel preemption mode from full preemption to voluntary preemption. 2. Added MediaTek Wi-Fi drivers (MT7601U etc). 3. Embedded kernel headers. https://github.com/cdhigh/armbian_build/releases/tag/v20250306

Hello Orima, Thank you for asking. I am doing well. I've been mainly distracted by an online drawing class. I will try to make a complete written guide in the weekend. It will be a new project in my github, and I will make a new thread here.

i had to do it on my own, no worries but it surprised me about it.

This recipe does not work for me. Could you please explain in more detail which exact Armbian image you are using and what exactly needs to be done to get the sound working?

@Brow Mosh Have you tried extracting your arndroid dts to find the gpio settings for emmc? The only other thing I can suggest at this point is trying mainline U-Boot booted over USB (FEL). Booting mainline U-Boot via FEL completely bypasses SD.

Thank you all... I was able to install Armbian on the H96 Max M9 thanks to all of your help.

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.

http://blog.armbian.com/content/images/2026/02/githubhighlights-2.webpThis week’s Armbian development saw significant progress across multiple areas, including desktop environment enhancements, kernel updates, and expanded hardware support. Notable changes include the addition of GNOME desktop options, improvements to XFCE organization, and updates to U-Boot for several boards. The team introduced new board images and logos, refined Docker automation and documentation, and standardized numerous software modules for better maintainability. Kernel advancements featured bumps to 6.19-rc8, integration of ZFS v2.4.0, and targeted fixes for Rockchip and Odroid platforms. Community governance and build processes were also strengthened, alongside the deprecation of Matrix and OFTC chat utilities. These updates collectively improve user experience, system stability, and future development agility. Add community governance and improve documentation. by @igorpecovnik in armbian/armbian.github.io#197Add DESKTOP_APPGROUPS_SELECTED to stable XFCE desktop target. by @igorpecovnik in armbian/armbian.github.io#198Add documentation for ARMBIAN_DOCKER_AUTO_PULL build switch. by @igorpecovnik in armbian/documentation#865Add GNOME desktop and reorganize XFCE in stable targets. by @igorpecovnik in armbian/armbian.github.io#199Add Khadas Mind, Minisiforum logo and Orangepi 6 Plus. by @igorpecovnik in armbian/armbian.github.io#203Add manual append for standard UEFI images. by @igorpecovnik in armbian/armbian.github.io#204Add zfs-zed to GLOB pattern in ZFS configs. by @igorpecovnik in armbian/os#426armbian-kernel: add AMD DC support for UEFI boards. by @igorpecovnik in armbian/build#9324armbianmonitor: fix error message at the end of every report. by @EvilOlaf in armbian/build#9325bcm2711 Family: Remove post_family_tweaks_bsp__rpi_firmware func. by @pyavitz in armbian/build#9331Board images for Orange Pi RV2 and Orange Pi R2S. by @sven-ola in armbian/armbian.github.io#201Bump BesTV R3300-L U-Boot. by @retro98boy in armbian/build#9303Bump CAINIAO CNIoT-CORE U-Boot. by @retro98boy in armbian/build#9304Chat utilities: remove missing package. by @igorpecovnik in armbian/build#9334ci: run all unit tests on schedule and main branch workflow_dispatch. by @igorpecovnik in armbian/configng#727clang: enable colored diagnostic output for kernel compilation. by @iav in armbian/build#9310Deprecate Matrix. by @EvilOlaf in armbian/build#9318Deprecate OFTC and matrix. by @EvilOlaf in armbian/documentation#872docker: add automatic image pull cronjob and cleanup system. by @igorpecovnik in armbian/build#9265feat: add reusable board definitions to image JSON generator. by @igorpecovnik in armbian/armbian.github.io#202Fix missing Cinnamon menu by removing outdated Cinnamon menu applet blob.. by @schwar3kat in armbian/build#9300fix(software): correct stderr redirection placement in docker commands. by @igorpecovnik in armbian/configng#746fix(software): fix netdata module issues and add test cleanup. by @igorpecovnik in armbian/configng#747fix: motd: handle empty temperature values in printf. by @igorpecovnik in armbian/build#9296followup #9164 2ba0766 - add ubuntu resolute,questing to optional-cli. by @iav in armbian/build#9320forge1: switch to RK3506J variant and add OPTEE support. by @igorpecovnik in armbian/build#9326json: add kernel_version field to images output. by @igorpecovnik in armbian/armbian.github.io#206Kernels 6.18 needs ZFS v2.4.0. by @igorpecovnik in armbian/os#425mainline-kernel: bump 6.19 to 6.19-rc8. by @rpardini in armbian/build#9332mainline: bump to 6.19-rc7. by @EvilOlaf in armbian/build#9294networking: relax networkd-wait-online to avoid multi-NIC timeouts. by @igorpecovnik in armbian/build#9311Odroid XU4: remove upstreamed patches. by @igorpecovnik in armbian/build#9306odroidm1: u-boot v2026.01 + kernel fix for ethernet. by @rpardini in armbian/build#9333OrangePi 3 LTS: Update U-Boot to v2026.01 and Linux DTS "and other fixups". by @pyavitz in armbian/build#9323Re-enable build targets after fixing their assembly. by @igorpecovnik in armbian/armbian.github.io#200refactor(docker): use upstream docker-ce for bookworm, distro for others. by @igorpecovnik in armbian/configng#726refactor(immich): standardize module and update postgres interface. by @igorpecovnik in armbian/configng#733refactor(network): standardize modules and add hidden WiFi support. by @igorpecovnik in armbian/configng#739refactor(pihole): standardize module with docker.io and improve detection. by @igorpecovnik in armbian/configng#734refactor(software): move docker check to install command. by @igorpecovnik in armbian/configng#738refactor(software): standardize 33 docker modules with modern patterns. by @igorpecovnik in armbian/configng#736refactor(system): harden armbian_firmware module with standard conventions. by @igorpecovnik in armbian/configng#744refactor(system): standardize headers and ZFS modules with improved hardening. by @igorpecovnik in armbian/configng#742refactor(wireguard): consolidate status checks and simplify module interface. by @igorpecovnik in armbian/configng#731refactor: standardize ghost and mysql docker modules. by @igorpecovnik in armbian/configng#728Resolving boot issues. by @rvdr in armbian/build#9329Rockchip 6.19: drop upstreamed patches. by @igorpecovnik in armbian/build#9309rockchip/64: import mainlined patch to fix gpio . by @paolosabatino in armbian/build#9328rockchip64-6.18: fix helios64 pcie patch. by @igorpecovnik in armbian/build#9315rockchip64-current: rewrite patches. by @EvilOlaf in armbian/build#9313rockchip64-current: rewrite patches due to upstream changes in 6.18.8. by @EvilOlaf in armbian/build#9319rockchip64: fix clang build error. by @paolosabatino in armbian/build#9307rockchip: fix gpio-ir-recv stack dumps, other minor fixes. by @paolosabatino in armbian/build#9317SMART AM40: Bump U-Boot. by @retro98boy in armbian/build#9302sun55i aftercare. by @EvilOlaf in armbian/build#9321sunxi a523: Adding support for PCIe, SPI Flash and Iommu. by @rvdr in armbian/build#9280sunxi: drop unneeded patches. by @EvilOlaf in armbian/build#9312targets: change community builds from forky to trixie. by @igorpecovnik in armbian/armbian.github.io#207Update header level for Pi-hole Explained section. by @igorpecovnik in armbian/configng#748Update odroidxu4-current to 6.6.122. by @belegdol in armbian/build#9322Update sm8250 current kernel config. by @retro98boy in armbian/build#9292Use EDGE branches for Orangepi 6 and Minisforum R1S. by @igorpecovnik in armbian/armbian.github.io#205uwe5622: fix compilation with clang on Linux 6.19. by @iav in armbian/build#9314[RFC] qcs6490: fix patched dtb not compiled. by @amazingfate in [#9301](https://github....View the full article

Armbian 25.11.2 Noble XFCE (BSP Kernel: 6.1.115) + PanVk - mesa 26.0 (https://launchpad.net/~ernstp/+archive/ubuntu/mesaaco) + Box64 arm64 v0.4.1 652da4fbc (https://ryanfortner.github.io/box64-debs/) + proton-10.0-4-amd64-wow64 (https://github.com/Kron4ek/Wine-Builds/releases/download/proton-10.0-4/wine-proton-10.0-4-amd64-wow64.tar.xz) + DXVK-stripped v1.10.3 ~50fps@720p (low settings) box64 environment variables: Injustice Gods Among Us Ultimate Edition

Hello, I have some troubles with this TVBOX: it runs armbian and other distros correctly, using the meson-gxm-t95z-plus.dtb but sometimes wifi goes into kernel panic at boot, and when it does, the whole system becomes unstable (i.e. not rebooting, eth0 hangs...). I have extracted the original .DTB from the only firmware that exists for this box, the ancient 6.0 Marshmellow Android (I guess it's a 3.x kernel...). I attach it to this message hoping someone more expert than me can help in making it work ina more stable manner. I attach a picture of the board also, it reads "M8S". Box has 2GB ram and 16GB eMMC, brcmfmac wifi/bt and ZTE PHY chip. meson1.dtb