Active threads

You can find the pinout at https://linux-sunxi.org/MicroSD_Breakout : CD is rx, CLK is tx and GND. There is a risk that using 3.3 v TTL levels on the tf card slot could fry the microsd controller so I would suggest getting the 1.8V version I mentioned earlier. So here is how I boot debian Trixie these days: (still need to figure out how to automate this but I do not know how yet using u-boot) setenv bootargs console=ttyAS0,115200 root=/dev/sda28 rw rootwait init=/sbin/init clk_ignore_unused sunxi_flash read 4007F000 boot_a sunxi_flash read 4fa00000 dtbo_a fdt addr 0x4fa00000 bootm 4007F000 - 4fa00000 Write dtb: dtc -I dtb -O dts -o tablet.dts tablet_patched.dtb dd if=tablet_patched.dtb of=/dev/sda24 status=progress conv=fsync dd if=tablet_patched.dtb of=/dev/sda25 status=progress conv=fsync You need these on host: sudo apt update sudo apt install debootstrap qemu-user-static How to prepaire the rootfs which will be flashed to userdata using fastboot: fallocate -l 8G teclast_trixie.img mkfs.ext4 -b 4096 teclast_trixie.img sudo mount -o loop teclast_trixie.img /mnt/trixie sudo mount --bind /dev /mnt/trixie/dev sudo mount --bind /sys /mnt/trixie/sys sudo mount --bind /proc /mnt/trixie/proc sudo debootstrap --arch=arm64 trixie /mnt/trixie http://deb.debian.org/debian sudo chroot /mnt/teclast /bin/bash passwd root echo "t60" > /etc/hostname apt update apt install build-essential kmod # you will need to install bunch of others but not more than 3 GB I think because fastboot wont reliably transfer more exit sudo fastboot erase userdata sudo fastboot flash userdata teclast_trixie.img How to do the raxda kernel: ./magiskboot unpack boot.img cp ../../raxda_kernel.img kernel ./magiskboot repack boot.img new_boot.img sudo fastboot flash boot_a new_boot.img sudo fastboot flash boot_b new_boot.img Wifi driver is a bit complicated(TBD): modprobe aic8800_bsp modprobe aic8800_fdrv ip link show wlan0 Here are the stock partitions: root@t60:~# blkid /dev/sda26: SEC_TYPE="msdos" UUID="2200-140B" BLOCK_SIZE="4096" TYPE="vfat" PARTLABEL="media_data" PARTUUID="a0085546-4166-744a-a353-fca9272b8e5e" /dev/sda22: UUID="dd7fd886-b74f-41cf-a5b1-bf1b47afaf8c" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="treadahead" PARTUUID="a0085546-4166-744a-a353-fca9272b8e5a" /dev/sda1: SEC_TYPE="msdos" LABEL="Volumn" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="bootloader_a" PARTUUID="a0085546-4166-744a-a353-fca9272b8e45" /dev/sda23: SEC_TYPE="msdos" UUID="4019-0FB8" BLOCK_SIZE="4096" TYPE="vfat" PARTLABEL="private" PARTUUID="a0085546-4166-744a-a353-fca9272b8e5b" /dev/sda21: UUID="a5aa7e72-84f0-40c4-9693-2a2ad5896309" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="metadata" PARTUUID="a0085546-4166-744a-a353-fca9272b8e59" /dev/sda28: UUID="f84bc812-d087-4cba-a90f-d045d40d2e44" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="userdata" PARTUUID="a0085546-4166-744a-a353-fca9272b8e60" /dev/sda4: PARTLABEL="env_b" PARTUUID="a0085546-4166-744a-a353-fca9272b8e48" /dev/sda16: PARTLABEL="vbmeta_system_b" PARTUUID="a0085546-4166-744a-a353-fca9272b8e54" /dev/sda2: PARTLABEL="bootloader_b" PARTUUID="a0085546-4166-744a-a353-fca9272b8e46" /dev/sda24: PARTLABEL="dtbo_a" PARTUUID="a0085546-4166-744a-a353-fca9272b8e5c" /dev/sda14: PARTLABEL="vbmeta_b" PARTUUID="a0085546-4166-744a-a353-fca9272b8e52" /dev/sda12: PARTLABEL="misc" PARTUUID="a0085546-4166-744a-a353-fca9272b8e50" /dev/sda9: PARTLABEL="init_boot_a" PARTUUID="a0085546-4166-744a-a353-fca9272b8e4d" /dev/sda20: PARTLABEL="empty" PARTUUID="a0085546-4166-744a-a353-fca9272b8e58" /dev/sda10: PARTLABEL="init_boot_b" PARTUUID="a0085546-4166-744a-a353-fca9272b8e4e" /dev/sda7: PARTLABEL="vendor_boot_a" PARTUUID="a0085546-4166-744a-a353-fca9272b8e4b" /dev/sda19: PARTLABEL="frp" PARTUUID="a0085546-4166-744a-a353-fca9272b8e57" /dev/sda5: PARTLABEL="boot_a" PARTUUID="a0085546-4166-744a-a353-fca9272b8e49" /dev/sda27: PARTLABEL="pstore" PARTUUID="a0085546-4166-744a-a353-fca9272b8e5f" /dev/sda17: PARTLABEL="vbmeta_vendor_a" PARTUUID="a0085546-4166-744a-a353-fca9272b8e55" /dev/sda3: PARTLABEL="env_a" PARTUUID="a0085546-4166-744a-a353-fca9272b8e47" /dev/sda25: PARTLABEL="dtbo_b" PARTUUID="a0085546-4166-744a-a353-fca9272b8e5d" /dev/sda15: PARTLABEL="vbmeta_system_a" PARTUUID="a0085546-4166-744a-a353-fca9272b8e53" /dev/sda13: PARTLABEL="vbmeta_a" PARTUUID="a0085546-4166-744a-a353-fca9272b8e51" /dev/sda11: PARTLABEL="super" PARTUUID="a0085546-4166-744a-a353-fca9272b8e4f" /dev/sda8: PARTLABEL="vendor_boot_b" PARTUUID="a0085546-4166-744a-a353-fca9272b8e4c" /dev/sda6: PARTLABEL="boot_b" PARTUUID="a0085546-4166-744a-a353-fca9272b8e4a" /dev/sda18: PARTLABEL="vbmeta_vendor_b" PARTUUID="a0085546-4166-744a-a353-fca9272b8e56" tablet.dts

Updating to include a few more I've successfully run... OpenMW - FOSS Engine to play Morrowind & it's KOTOR total conversion Starwind Quakespasm - FOSS engine to play Quake and it's expansions, mods & total conversions UFO: Alien Invasion - an XCom "homage" Yamagi Quake 2 - FOSS engine for Quake 2 I was able to test Quake Mods like the cyberpunk FPS prequel to a prequel to a Dreamcast mecha game "Slave Zero X: Enyo" and top down fantasy RPG "Prydon Gate". Both work great but I'll need to upgrade the eMMC before I can try larger sized conversions like Brutalist Jam III or Slayer's Testaments.

@SymbiosisSystems, Thanks for testing and reporting back. Before diving into the panic itself, a bit of context: the CPU stability overlay we packaged from the prahal/ebin-dev recipe is opt-in precisely because, thanks to the RK3399 silicon lottery, most Helios64 units don't need it. The very fact that you do need it already hints that your particular unit is sitting closer to the edge of its operating margin than a typical one. That's not blaming the hardware — just an observation that units with marginal stability often expose other weak spots that stay invisible on an "average" board. Now to the crash itself. `Asynchronous SError` in `rockchip_pcie_rd_conf` during PCI enumeration is a known bus-level abort on the RK3399 PCIe controller, not on the CPU. Our overlay has nothing to do with CPU cluster voltages here: it only raises `vdd_cpu_b` on opp00..opp06 of the A72 cluster, while PCIe sits on `vdd_logic` and separate PCIe rails which we don't touch. The PCIe x2 Gen2 lane from the RK3399 in Helios64 is wired directly to the soldered-on JMicron JMB585 SATA controller ([Kobol Wiki — SATA](https://wiki.kobol.io/helios64/sata/)), which provides the five SATA ports. So the only possible endpoint where bus scan is currently failing is the JMB585. The typical scenario goes like this: the endpoint replies with CRS (Configuration Request Retry Status) or simply doesn't respond within the completion timeout window → the root complex raises a completion abort → AArch64 sees it as an async SError. This class of bugs on the RK3399 is well documented: - [\[BUG\] rk3399-rockpro64 pcie synchronous external abort](https://lore.kernel.org/linux-pci/CAMdYzYrYHtiEXwiKxwWcKSV7Re6dG4zTvkKtZxvso+fLBRYbPQ@mail.gmail.com/T/) — same class of bus-level abort on the same SoC. - [RFC patch: configurable bus scan delay](https://www.spinics.net/lists/linux-pci/msg103350.html) — the general nature of CRS/timeout problems (the specific HBA delays from that thread don't directly apply to Helios64, since your endpoint is a fixed JMB585, not a swappable card). - [rockchip-linux/kernel#116](https://github.com/rockchip-linux/kernel/issues/116) and [#118](https://github.com/rockchip-linux/kernel/issues/118) — "Some PCIe devices cause Rockchip PCIe controller to crash in bus scan". - The [v5 series fixing the RK3399 PCIe endpoint driver](https://patchwork.ozlabs.org/project/devicetree-bindings/cover/20230418074700.1083505-1-rick.wertenbroek@gmail.com/#3135632) — CRS handling and the Configuration Enable bit. - Armbian has known about RK3399 PCIe quirks for a long time: [commit edb45f9 — "Make PCIe reset optional"](https://github.com/armbian/build/commit/edb45f9acf322fc4b27bf7efba3f14a3a432b617). So your stack trace falls into a family of long-known RK3399 PCIe problems and is unrelated to the voltage overlay. If someone — from the rockchip64 maintainers or from the community — picks up your case, here's what is usually expected to be attached to a report like this, otherwise diagnosis will inevitably hit a wall of missing data: 1. A full serial bootlog via USB-UART (Helios64 → 1500000 baud), both with the overlay and without it (just comment out `overlays=` in `armbianEnv.txt`) — to see whether the picture differs or this is an independent problem. 2. State of the SATA bays: try booting with the bays completely empty (or one drive at a time) — if the PCIe link to the JMB585 comes up cleanly without any SATA load, the problem narrows down to one of the drives rather than the link itself. 3. u-boot and BL31 (ATF) versions — `dmesg | grep -iE "u-boot|psci|bl31"`, plus `strings /boot/u-boot.bin | grep -m1 "U-Boot 20"` if you have access. 4. The full `dmesg` up to the moment of the crash — even if truncated, whatever made it out to serial. 5. The entire contents of `/boot/armbianEnv.txt`. 6. Try two extra kernel boot parameter options — this is the simplest experiment and often helps on unstable RK3399 PCIe. **a) Disable PCIe power management** (a known workaround for the broken PM on RK3399). Open `/boot/armbianEnv.txt`: ``` sudo nano /boot/armbianEnv.txt ``` Find a line starting with `extraargs=`. Two cases: - **If such a line exists** — append the parameters at its end, separated by a space. For example, it was: ``` extraargs=console=tty1 ``` Becomes: ``` extraargs=console=tty1 pcie_aspm=off pcie_port_pm=off ``` - **If there is no such line at all** — just add a new line at the very end of the file: ``` extraargs=pcie_aspm=off pcie_port_pm=off ``` Save (Ctrl+O, Enter, Ctrl+X), `sudo reboot`, try booting. To revert: remove what you appended (or delete the added line entirely) and reboot again. **b)** You can try downgrading PCIe from Gen2 to Gen1 (RK3399 Gen2 link training is regularly unstable), but that requires writing your own device tree overlay — there is no ready-made one in Armbian. And finally, to be honest: we are not PCIe stack experts and not rockchip64

Hello @jock, thank you for the quick reply! Indeed, the drivers for the 8723cs have been disabled in the rockchip64 version, as confirmed by my config file: grep -i "8723" /boot/config-$(uname -r) # CONFIG_RTL8723CS is not set # CONFIG_RTW88_8723CS is not set I found 2 GitHub repos with the uncompiled drivers for the 8723cs chipset: - https://github.com/VictorIstratii151/rtl8703bs_rtl8723cs_linux_driver - https://github.com/TinkerBoard-Android/rockchip-android-external-wifi_driver/tree/android14-rockchip I tried to compile them natively on my machine but without success. They relies on Android-specific headers that are missing in Armbian. Regarding the rockchip armhf family you mentioned, do I need to completely reinstall Armbian on my board using a different image (the 32-bit armhf one)? Do I have to use the Armbian build framework to achieve this? Or is there a way/tool to cross-compile this specific module for my current 64-bit setup? Thanks again for your help!

@Delutto Thank you for your contribution! Your changes have been successfully merged to my repo https://github.com/cdhigh/armbian_sv6256p Now the driver should work with kernels from 6.0 through 7.x.

This issue is not from u-boot but rather a board config Please see this https://github.com/armbian/build/pull/9333 and use edge kernel instead, stable doesn't include this fix Cheers !

Hello everyone. I made a direct connection between the 5V from the motherboard and the 5V from the USB ports to try and overcome the current limitation of the USB ports. However, something went wrong. I undid this direct connection, but the motherboard is still shorting the USB ports. I believe the short circuit is in that ADG3T port. Does anyone have any idea what happened? I didn't even connect anything to the USB port. Thanks.

@Evgeniy evotronik When I switch from 1 Gbps to 100 Mbps... Ethernet returns to normal.

When I ask multiple questions, it is for a reason. When you don't answer all of the questions, then I can't help you as I have to guess. So here is a guess, that you are burning the SD card on Windows. I have seen reports that on some versions of Windows, that windows will automount the FAT partition on the SD card after burning, and when it mounts it it alters it in ways that cause problems. I haven't spent any time looking into that issue, but because of what I have seen repored, I would avoid doing the burn on windows. Please try it on a linux box. As for recommended burning tool, you should follow the Armbian documentation (https://docs.armbian.com/User-Guide_Getting-Started) and use Armbian Imager.

This week's work advances on three fronts: kernel and bleedingedge alignment across Rockchip and Sunxi trees, board and platform enablement spanning RV1106 to SpacemiT, and CI hardening with self-hosted runner maintenance. On the kernel side, bleedingedge was bumped to 7.1-rc3, accompanied by cfg80211 API fixes and re-enablement of the rtl8189fs and rtl8852bs drivers for the new release. Both the rockchip64 and sunxi patch stacks for current and edge were rewritten, an upstream ptrace fix for CVE-2026-46333 was backported to linux-rockchip, and the odroidxu4-current kernel moved to 6.6.139. Platform enablement was broad. The Ayn Odin2 gained 7.0 kernel support, the Mekotronics R58X-Pro switched its vendor build to mainline U-Boot with a corrected LCD driver, and the H96 TV box advanced to U-Boot v2026.04. RV1106 transitioned from extlinux to a bootscript and gained DS1307, PCF85063, and RV8803 RTC drivers, while SpacemiT received OpenSBI, U-Boot, and BPI-F3 DTS fixups. Smaller but user-visible improvements include NanoPi M5 second USB3 port exposure via DRD0 host-mode pinning, NORCO EMB-3531 LPDDR4X variants, RK3528 USB2 PHY corrections for high-speed NCM, and UEFI x86 images enabling iwlwifi MLD and Intel SOF audio for MTL, LNL, and PTL. Infrastructure work centered on self-hosted runner reliability and supply-chain hygiene. A new runner-cleanup module provides hourly disk and memory maintenance, skips busy runners, and ships via .deb, while a maintenance watchdog was added to the SDK repository. Multiple StepSecurity hardening passes landed across build and SDK workflows, though an overly strict egress-policy was subsequently reverted after breaking builds. #Armbian #EmbeddedLinux #Rockchip #RISCV #KernelDevelopment ChangesActions: Cleanup "Release" workflow. by @vidplace7 in armbian/MorseMicro-DKMS#4Actions: Create release workflow. by @vidplace7 in armbian/MorseMicro-DKMS#3Ayn Odin2 kernel 7.0 support. by @kasimling in armbian/build#9706Build for riscv64. by @vidplace7 in armbian/MorseMicro-DKMS#5Bump actions/download-artifact from 7 to 8. by @igorpecovnik in armbian/os#464Bump versions: stable 26.5.0, nightly 26.8.0-trunk.1. by @igorpecovnik in armbian/os#461bump bleedingedge to 7.1-rc3. by @EvilOlaf in armbian/build#9806cfg80211: fix API changes for Linux 7.1. by @EvilOlaf in armbian/wifi-rtl8852bs#5change recomputer rk35xx fan speed. by @ackPeng in armbian/linux-rockchip#472ci: add maintenance watchdog + rename action.yml → build-armbian-sdk.yml. by @igorpecovnik in armbian/sdk#25ci: drop step-security/harden-runner steps (egress-policy was breaking builds). by @igorpecovnik in armbian/sdk#26desktops: ship fprintd userspace at mid tier. by @igorpecovnik in armbian/configng#918desktops: split light/dark wallpapers in gnome + bianbu postinsts. by @igorpecovnik in armbian/configng#905Disable: SpacemiT: fix RX DMA params not set when TX is running. by @pyavitz in armbian/build#9808drivers_network: bump rtl8852bs commit ref to 35d3e266 (May 17). by @igorpecovnik in armbian/build#9841drop old lcd_vk2c21 LCD driver that never worked; backport workingvinka,vk2c21 driver; fix Mekos DTs. by @rpardini in armbian/linux-rockchip#482ebyte-ecb41-pge: Add spidev overlays (RPi-compatible). by @vidplace7 in armbian/linux-rockchip#467firmware-sof-signed: move from cli/amd64 baseline to UEFI common. by @igorpecovnik in armbian/build#9857fix(deps): add Pygments to requirements.txt (rich.syntax dep). by @iav in armbian/build#9819luckfox-lyra-zero-w: Default to onboard wifi antenna, add ipex overlay. by @vidplace7 in armbian/linux-rockchip#468maintenance-watchdog: target the workflow that actually exists. by @igorpecovnik in armbian/configng#915Mekotronics R58X-Pro (vendor): use mainline u-boot for vendor; use new LCD driver. by @rpardini in armbian/build#9836module_armbian_runners: skip busy runners + ship runner-cleanup assets via .deb. by @igorpecovnik in armbian/configng#914module_qbittorrent: poll for temporary password before showing dialog. by @igorpecovnik in armbian/configng#916nanopi-m5: pin DRD0 dwc3 to host mode to expose the second USB3 port. by @SuperKali in armbian/build#9844NORCO EMB-3531: Add LPDDR4X variants support. by @retro98boy in armbian/build#9823patch/sunxi-6.12: drop two Rockchip SPI patches (not applicable to sunxi). by @igorpecovnik in armbian/build#9827postinst/gnome: enable tap-to-click + clickpad right-click out of the box. by @igorpecovnik in armbian/configng#917Potential fix for code scanning alert no. 2: Code injection. by @iav in armbian/build#9799ptrace: backport upstream fix for CVE-2026-46333 (ssh-keysign-pwn). by @SuperKali in armbian/linux-rockchip#481restore backwards compatibility. by @EvilOlaf in armbian/wifi-rtl8852bs#6rockchip rk3566: h96-TVbox: bump to uboot v2026.04. by @hqnicolas in armbian/build#9807rockchip64-6.18: rebase rk3399 dwc3 phy-reset-quirk patch for 6.18.32. by @SuperKali in armbian/build#9847rockchip64: fix RK3528 USB2 PHY regmap split for high-speed NCM. by @rubycomm in armbian/build#9785rockchip64: opt-in helios64 CPU stability overlay (current + edge). by @iav in armbian/build#9822rockchip64: rewrite patches of current and edge. by @EvilOlaf in armbian/build#9829rtl8189fs: fix compilation for 7.1 and re-enable. by @EvilOlaf in armbian/build#9813rtl8852bs: re-enable for bleedingedge. by @EvilOlaf in armbian/build#9831runner-cleanup: drop redundant age-based _diag prune. by @igorpecovnik in armbian/configng#921runner-cleanup: hourly disk + memory maintenance for self-hosted runner hosts. by @igorpecovnik in armbian/configng#913runner-cleanup: wipe _diag/pages/ alongside _work/. by @igorpecovnik in armbian/configng#919runner-cleanup: wipe ~/_diag/ on every runner each pass. by @igorpecovnik in armbian/configng#920RV1106: add support for additional RTC drivers (DS1307, PCF85063, RV8803). by @vidplace7 in armbian/build#9812RV1106: Switch u-boot from extlinux to bootscript. by @vidplace7 in armbian/build#9801SpacemiT: Fixup OpenSBI, U-Boot and BPI-F3 DTS. by @pyavitz in armbian/build#9838sunxi: rewrite kernel patches of current and edge. by @EvilOlaf in armbian/build#9828uefi-x86: enable iwlwifi MLD + Intel SOF (MTL/LNL/PTL) audio. by @igorpecovnik in armbian/build#9846Update documentation / packaging URLs. by @vidplace7 in armbian/MorseMicro-DKMS#2Update MorseMicro suite to 1.17.8. by @vidplace7 in armbian/MorseMicro-DKMS#1Update nanopi r5s udev rule tweak for persistent net interface names. by @ruabmbua in armbian/build#9811Update odroidxu4-current to 6.6.139. by @belegdol in armbian/build#9837Workaround devcontainer/ci platform issues. by @vidplace7 in armbian/MorseMicro-DKMS#6[StepSecurity] Apply security best practices. by @step-security-bot in armbian/build#9833[StepSecurity] Apply security best practices. by @step-security-bot in armbian/build#9839[StepSecurity] Apply security best practices. by @step-security-bot in armbian/sdk#24[StepSecurity] ci: Harden GitHub Actions. by @step-security-bot in armbian/build#9803[StepSecurity] ci: Harden GitHub Actions. by @step-security-bot in armbian/build#9825View the full article

This week's work advances on three fronts: kernel and bleedingedge alignment across Rockchip and Sunxi trees, board and platform enablement spanning RV1106 to SpacemiT, and CI hardening with self-hosted runner maintenance. On the kernel side, bleedingedge was bumped to 7.1-rc3, accompanied by cfg80211 API fixes and re-enablement of the rtl8189fs and rtl8852bs drivers for the new release. Both the rockchip64 and sunxi patch stacks for current and edge were rewritten, an upstream ptrace fix for CVE-2026-46333 was backported to linux-rockchip, and the odroidxu4-current kernel moved to 6.6.139. Platform enablement was broad. The Ayn Odin2 gained 7.0 kernel support, the Mekotronics R58X-Pro switched its vendor build to mainline U-Boot with a corrected LCD driver, and the H96 TV box advanced to U-Boot v2026.04. RV1106 transitioned from extlinux to a bootscript and gained DS1307, PCF85063, and RV8803 RTC drivers, while SpacemiT received OpenSBI, U-Boot, and BPI-F3 DTS fixups. Smaller but user-visible improvements include NanoPi M5 second USB3 port exposure via DRD0 host-mode pinning, NORCO EMB-3531 LPDDR4X variants, RK3528 USB2 PHY corrections for high-speed NCM, and UEFI x86 images enabling iwlwifi MLD and Intel SOF audio for MTL, LNL, and PTL. Infrastructure work centered on self-hosted runner reliability and supply-chain hygiene. A new runner-cleanup module provides hourly disk and memory maintenance, skips busy runners, and ships via .deb, while a maintenance watchdog was added to the SDK repository. Multiple StepSecurity hardening passes landed across build and SDK workflows, though an overly strict egress-policy was subsequently reverted after breaking builds. #Armbian #EmbeddedLinux #Rockchip #RISCV #KernelDevelopment ChangesActions: Cleanup "Release" workflow. by @vidplace7 in armbian/MorseMicro-DKMS#4Actions: Create release workflow. by @vidplace7 in armbian/MorseMicro-DKMS#3Ayn Odin2 kernel 7.0 support. by @kasimling in armbian/build#9706Build for riscv64. by @vidplace7 in armbian/MorseMicro-DKMS#5Bump actions/download-artifact from 7 to 8. by @igorpecovnik in armbian/os#464Bump versions: stable 26.5.0, nightly 26.8.0-trunk.1. by @igorpecovnik in armbian/os#461bump bleedingedge to 7.1-rc3. by @EvilOlaf in armbian/build#9806cfg80211: fix API changes for Linux 7.1. by @EvilOlaf in armbian/wifi-rtl8852bs#5change recomputer rk35xx fan speed. by @ackPeng in armbian/linux-rockchip#472ci: add maintenance watchdog + rename action.yml → build-armbian-sdk.yml. by @igorpecovnik in armbian/sdk#25ci: drop step-security/harden-runner steps (egress-policy was breaking builds). by @igorpecovnik in armbian/sdk#26desktops: ship fprintd userspace at mid tier. by @igorpecovnik in armbian/configng#918desktops: split light/dark wallpapers in gnome + bianbu postinsts. by @igorpecovnik in armbian/configng#905Disable: SpacemiT: fix RX DMA params not set when TX is running. by @pyavitz in armbian/build#9808drivers_network: bump rtl8852bs commit ref to 35d3e266 (May 17). by @igorpecovnik in armbian/build#9841drop old lcd_vk2c21 LCD driver that never worked; backport workingvinka,vk2c21 driver; fix Mekos DTs. by @rpardini in armbian/linux-rockchip#482ebyte-ecb41-pge: Add spidev overlays (RPi-compatible). by @vidplace7 in armbian/linux-rockchip#467firmware-sof-signed: move from cli/amd64 baseline to UEFI common. by @igorpecovnik in armbian/build#9857fix(deps): add Pygments to requirements.txt (rich.syntax dep). by @iav in armbian/build#9819luckfox-lyra-zero-w: Default to onboard wifi antenna, add ipex overlay. by @vidplace7 in armbian/linux-rockchip#468maintenance-watchdog: target the workflow that actually exists. by @igorpecovnik in armbian/configng#915Mekotronics R58X-Pro (vendor): use mainline u-boot for vendor; use new LCD driver. by @rpardini in armbian/build#9836module_armbian_runners: skip busy runners + ship runner-cleanup assets via .deb. by @igorpecovnik in armbian/configng#914module_qbittorrent: poll for temporary password before showing dialog. by @igorpecovnik in armbian/configng#916nanopi-m5: pin DRD0 dwc3 to host mode to expose the second USB3 port. by @SuperKali in armbian/build#9844NORCO EMB-3531: Add LPDDR4X variants support. by @retro98boy in armbian/build#9823patch/sunxi-6.12: drop two Rockchip SPI patches (not applicable to sunxi). by @igorpecovnik in armbian/build#9827postinst/gnome: enable tap-to-click + clickpad right-click out of the box. by @igorpecovnik in armbian/configng#917Potential fix for code scanning alert no. 2: Code injection. by @iav in armbian/build#9799ptrace: backport upstream fix for CVE-2026-46333 (ssh-keysign-pwn). by @SuperKali in armbian/linux-rockchip#481restore backwards compatibility. by @EvilOlaf in armbian/wifi-rtl8852bs#6rockchip rk3566: h96-TVbox: bump to uboot v2026.04. by @hqnicolas in armbian/build#9807rockchip64-6.18: rebase rk3399 dwc3 phy-reset-quirk patch for 6.18.32. by @SuperKali in armbian/build#9847rockchip64: fix RK3528 USB2 PHY regmap split for high-speed NCM. by @rubycomm in armbian/build#9785rockchip64: opt-in helios64 CPU stability overlay (current + edge). by @iav in armbian/build#9822rockchip64: rewrite patches of current and edge. by @EvilOlaf in armbian/build#9829rtl8189fs: fix compilation for 7.1 and re-enable. by @EvilOlaf in armbian/build#9813rtl8852bs: re-enable for bleedingedge. by @EvilOlaf in armbian/build#9831runner-cleanup: drop redundant age-based _diag prune. by @igorpecovnik in armbian/configng#921runner-cleanup: hourly disk + memory maintenance for self-hosted runner hosts. by @igorpecovnik in armbian/configng#913runner-cleanup: wipe _diag/pages/ alongside _work/. by @igorpecovnik in armbian/configng#919runner-cleanup: wipe ~/_diag/ on every runner each pass. by @igorpecovnik in armbian/configng#920RV1106: add support for additional RTC drivers (DS1307, PCF85063, RV8803). by @vidplace7 in armbian/build#9812RV1106: Switch u-boot from extlinux to bootscript. by @vidplace7 in armbian/build#9801SpacemiT: Fixup OpenSBI, U-Boot and BPI-F3 DTS. by @pyavitz in armbian/build#9838sunxi: rewrite kernel patches of current and edge. by @EvilOlaf in armbian/build#9828uefi-x86: enable iwlwifi MLD + Intel SOF (MTL/LNL/PTL) audio. by @igorpecovnik in armbian/build#9846Update documentation / packaging URLs. by @vidplace7 in armbian/MorseMicro-DKMS#2Update MorseMicro suite to 1.17.8. by @vidplace7 in armbian/MorseMicro-DKMS#1Update nanopi r5s udev rule tweak for persistent net interface names. by @ruabmbua in armbian/build#9811Update odroidxu4-current to 6.6.139. by @belegdol in armbian/build#9837Workaround devcontainer/ci platform issues. by @vidplace7 in armbian/MorseMicro-DKMS#6[StepSecurity] Apply security best practices. by @step-security-bot in armbian/build#9833[StepSecurity] Apply security best practices. by @step-security-bot in armbian/build#9839[StepSecurity] Apply security best practices. by @step-security-bot in armbian/sdk#24[StepSecurity] ci: Harden GitHub Actions. by @step-security-bot in armbian/build#9803[StepSecurity] ci: Harden GitHub Actions. by @step-security-bot in armbian/build#9825View the full article

I failed to flash the firmware of my TV box and it's now bricked. I need to re-flash it. Please tell me where the shorting point of this TV box is and how to flash it using the shorting point. Thank you.

I don't have a specific solution for you. I flashed my M1S just yesterday with the latest Minimal image and it worked just ootb. But what I recognized during tests of my self-compiled images was, that the M1S seems to be quite picky regarding the SD card and how it is flashed. My M1S showed a lot of different strange behaviors: very (I mean VERY!) slow boot, file system was read-only, no ethernet, kernel panics... I had to try different SD cards as well as different flashing tools to get it running. Interestingly the images that I flashed with Balena Etcher worked better than those flashed with the Armbian flasher. My No-HDMI-problem was solved by just using another cable... So maybe it is worth to try to just re-download the image and flash it with another tool to another SD card? Best whishes, Jojo

@well0nez keep us updated on your progress.

Hello good people. I honestly had given up on that thing, until last weekend, where I set my mind to finally get it to work. And work, it does! eMMC works, display output works without a trouble, and only today I've seen @eloirotava's comment about the 6051. And I'm calling for help again on that one. I currently am using the kernel 7.0.8-meson64 (the current edge for the tv box) and no matter what i'm doing, there's no way for me to get the correct linux-header files, to compile and install that module. May a kind soul help me? I'll post a full documentation very soon, and will probably push my work to the armbian git, once everything is clean. Thank you very much in advance!

Problem remains the same. i have cloned a new build repos and patch with pr-9626 and rebuild image. console output result remains: U-Boot SPL 2026.01_armbian-2026.01-S127a-Pa547-Hc6a9-V2b7c-Bd0d2-R448a (May 18 2026 - 10:12:32 +0200) DRAM: 1024 MiB Something wrong with the uboot timing of the dram etc.? i can supplied the timing and trimming of the board with the funtional debian bootloader saved to spi. Setting of voltage regulators etc. see attached file. Regards Rolf hardcopy.0

Been doing some RK3588 board porting and kept running into the same category of bug — dtc compiles clean, dtbs_check passes, but the board either panics on suspend or a peripheral silently fails to probe. Stuff like: Peripheral on the EE supply wired to something that only stays alive in the AO domain → suspend-resume panic Copy-pasted a GPIO bank with 32 pins, used pin 35 → kernel panic at driver probe SPI clock request exceeds PLL maximum → silent bus hang Two nodes sharing the same GIC SPI interrupt line None of these are schema violations — they require knowing the actual cross-domain constraints of the SoC, which dtc has no idea about. So I wrote a Python tool that builds an in-memory model of the power tree, clock tree, and pin assignments, then runs constraint rules against it: $ pip install soc-consistency $ socc check board.dts --soc rk3588 error[PD-001] Power domain crossing — i2c@fe2b0000 uses vcc_3v3 (EE domain) but is connected to vcc_1v8 (AO domain). Will panic on suspend. error[GP-003] GPIO index out of bounds — gpio1 pin 35 on a 32-pin bank. warn[CK-003] Clock rate mismatch — spi0 requests 50 MHz from pll_cpll (max 24 MHz). There's also a decompile command that runs dtc on a binary blob and annotates the output with peripheral names from the SoC database — useful when you're staring at a vendor DTB and have no idea which block is at which address: $ socc decompile vendor.dtb --soc rk3588 gpio0@fd8a0000 /* GPIO0 (32-pin, 3.3V) */ { cru@fd7c0000 /* CRU — Clock and Reset Unit */ { RK3588 has the most complete constraint coverage right now. The constraint format is a simple YAML file — happy to accept PRs for other SoCs. GitHub: https://github.com/gahingwoo/SoC-Consistency Docs/rules reference: in the README If you hit false positives on a real BSP DTS, open an issue — BSP files from vendors tend to have a lot of "intentional" violations that I'm still tuning the rules around.

@Nick A TY very much for your reply, I've managed to create my first build but I am a bit confused because it made an IMG with a FAT32 boot partition, is it right or did I miss something?

After many weeks of research, testing and debugging I managed to put together an Unofficial Armbian Linux build for LinknLink iSG Box SE. Version: v26.05 Rolling Kernel: 6.1.115-vendor-rk35xx Flashed and booting from eMMC. All hardware working and tested, including Ethernet, WiFi and Bluetooth. Source, build and flashing instructions here https://github.com/luisdosreis/linknlink-isg-box-se-armbian If anyone is interested I can share a test image ready to be flashed or you can (and should) build it yourselves. I plan to add a Home Assistant flavor to the build system in the future.

Yes, the device is working now. Check the forum manjaro, they put kernel from sunxi and working now.

@jock Is it possible to dump BOOTROM from Linux, or is it hidden/shadowed by ATF ? There is RK3399 dumper code at github, so i am wondering if the same can be done on RK3528.

Thank you! I ended up getting this working. For one, an update and reboot did get me the 6.18.10 kernel. Then, in the installation scripts for drivers, I just had to specify the package name for the headers explicitly, e.g. replacing: apt-get install linux-headers-$(uname -r) -y with apt-get install linux-headers-current-bcm2711 -y

I am using a Rock 5T 12GB board and have tested multiple Armbian images (24.04, 26.04, and others). Here is my experience so far: Armbian current images Audio does not work at all. When I plug in a 3.5 mm headset, nothing happens — no detection, no sound. Bluetooth works, Wi‑Fi does not. I have to manually compile the Realtek rtw89 wireless driver. After compiling, both Wi‑Fi and Bluetooth work, but still no audio output. Vendor (Radxa) images Audio works perfectly. When I plug in a headset, the system immediately detects it and asks whether it has a microphone. Sound output through the headset works as expected. However, with the vendor image I cannot use Bluetooth and Wi‑Fi at the same time. According to what I found online, the RTL8852BU chip shares internal resources. I must disable Wi‑Fi to use a Bluetooth mouse and keyboard reliably. Connecting a Bluetooth headset causes an immediate disconnect. Feedback from Radxa Radxa confirmed that the Bluetooth/Wi‑Fi coexistence issue is caused by the driver. Summary At the moment, I cannot use either the current Armbian images or the vendor images without running into major problems: Armbian: Wi‑Fi/Bluetooth OK (after manual driver build), but no audio. Vendor image: Audio OK, but Bluetooth and Wi‑Fi cannot work simultaneously. Is this a known issue, and am I the only one experiencing these problems? Thanks a lot for your support and help.

Solved it by simply removing the upstream folder which had some symlink tomfolery 1. rm -rf /lib/firmware/qcom/sm8550/ayn/ 2. apt update && apt upgrade 3. PROFIT <3

SOLVED by enable on BIOS