Search the Community

Hello, I found this guide: https://github.com/robertojguerra/orangepi-zero-full-setup/blob/main/README2.md I followed the steps and built an Armbian image with current 6.12 kernel and now TV OUT (CVBS, Composite Video), after soldering a cable to the video pin on the board, is working on my Orange Pi One with an Allwinner H3 CPU (the patches might work for other H3/H2+ boards). I would like to get that functionality incorporated into Armbian.

Recently has appeared some 3566 tv boxes in the wild, would be doable to run armbian on them? Since Rockchip seems kinda dedicated to openness the same goes for the RK3566?

Download Armbian with HA (v25.2) Then boot the image, wait few minutes and login via http://ip_address_of_armbian_running_ha:8123 (official onboarding manual) Home Assistant Supervised is, more or less, a full blown Home assistant. Install Home Assistant on any Armbian Bookworm (experimental) Main difference between HA OS and Armbian with HA is that underlying OS here is clean Armbian Debian Bookworm and there is custom dedicated buildroot OS that is provided for a few single board computers, primarily for Raspberry Pi. We provide HA on a small selection of single board computers, but in theory, its possible to run this on (almost) all that are possible to build. I am running HA on Odroid N2+ and it works without any problems. I have z-wave network with sensors and switches, air humidifier, Android TV, Android phones, dishwasher, ... Things works flawlessly, much better then few years back when I started with home automation for a first time, with OpenHab. This time it was setup from scratch and in a matter of days, most of devices are in function, playing with automation. Tested on: Odroid N2/N2+ Odroid M1 Nanopi R4S Rock 5B Uefi-x86 Orangepi 5 Nanopi M6 Rpi400 Khadas VIM1S Khadas VIM4 (Amlogic vendor kernel trouble, failing / need inspection) Bananapi M2 Pro Provided for but untested (images you find on board downloads locations, seek them here https://www.armbian.com/download/😞 DIY Contribute Support: The supervised installation method on Armbian is not officially supported by the Home Assistant project. Additionally, installation on hardware that is not officially supported is also outside the scope of support provided by the Armbian team. You are welcome to report high-level application issues that are reproducible on the official Home Assistant Operating System (HAOS) within the Home Assistant community or here on this forum. For any hardware-related topics, you may use the this forum; however, please be aware that official support from the Armbian team is not guaranteed. single board computer hardware https://www.armbian.com/bugs home assistant functions https://community.home-assistant.io/ (make sure to bring up only issues that are application related, high level issues, that are likely present in official HAOS software)

I’m using the DEVMFC version [https://github.com/devmfc/debian-on-amlogic]. Additionally, I took the `/boot` partition and copied all the files from the Devmfc_Ubuntu-Oracular_6.12.11-meson64_Minimal-25.01.24.img.xz image. Then, I downloaded the same version available from the Armbian community, but with a graphical interface: Armbian_community_25.5.0-trunk.4_Aml-s9xx-box_noble_current_6.12.12_xfce_desktop.img.xz. I first flashed the Armbian image onto a USB drive. Then, in the `/boot` partition, I moved all existing root files into a `/backup` folder. After that, I copied the files from the DEVMFC version into the root of the `/boot` partition on the USB drive. Surprisingly, when I tried to boot this setup on a TV Box similar to the Vontar X4, which has an S905X4 processor, it actually booted! It prompted me to create a root password, a regular user, set the language, and select a time zone. Then, it successfully launched into X for the graphical interface. However, it seems that USB ports were either disabled, or the system froze—the login screen was visible, and the keyboard cursor was blinking, but no input was possible. I believe this is a solid starting point for getting Armbian images with a graphical interface running on S905X4 (Meson SC2), S905W2 (Meson S4), and S905Y4 (Meson S4) processors. Even without hardware-accelerated graphics, it should still be usable for basic applications like Notepad, text editors, spreadsheets, calculators, terminal access, and other simple tasks. Has anyone else made progress running Armbian on the S905X4?

Hello, I have a Tanix TX6-A TV box and I’ve tried many Armbian builds, including the ones from https://armbian.com/boards/tanix-tx6 and ophub. However, the onboard Wi-Fi does not work on any of them. Has anyone found an Armbian image that works properly with the Tanix TX6-A, including Wi-Fi support?

I've this old tv box from a brazilian brand, called Intelbras IZY Play, the OEM appears to be SDMC, with the codename DV8038, it uses the s805x SoC. From what I've looked, it should be compatible using the files meson-gxl-s805x-p241.dtb u-boot-s905x-s912 The device does not have an SD card slot, so i'm trying to do it with a flash drive, however, after flashing it with balenaEtcher and doing the necessary changes to the files in my Windows PC, I cannot get it to boot, it justs enters a loop of showing the splash screen, turning off, showing the splash screen, and so on. I'm trying to turn it on pressing the hidden button that it has between the usb ports with a paper clip while I connect the power cable, if I do that without the USB stick on, it boots into a sort of recovery/fastboot screen similar to what android phones have. I've tried all variants of Armbian Bookworm, and I'm flashing Jammy as I write this post to test it as well, if it does work I will update the post.

--- Hey everyone! Long-time lurker, first post here. I picked up one of those cheap RK3229 TV boxes and decided to see how far I could push it on a mainline kernel — no Android, no BSP, no blobs. What started as curiosity about whether rkvdec actually worked on kernel 6.6 turned into a full rabbit hole of GStreamer pipelines, PHY register dumps, and DRM memory bandwidth math. The whole debugging and documentation process was done collaboratively with Claude (Anthropic's AI assistant), which made it a lot easier to dig into kernel driver internals and iterate on the pipeline without spending weeks at it. All the results were validated on real hardware. Sharing here in case it saves someone else the same rabbit hole. --- [GUIDE] Hardware H.264 decode at 720p — mainline kernel 6.6, GStreamer, no blobs After spending some time on my RK3229 TV box running Armbian 24.2.5 Bookworm (kernel 6.6.22-current-rockchip), I got hardware H.264 decode working at 720p real-time using only mainline kernel drivers and open-source GStreamer plugins. Posting here in case it helps others. --- What works - H.264 720p@30fps fully hardware decoded via rkvdec (the mainline V4L2 stateless decoder) - Direct HDMI output via kmssink (DRM/KMS — no X11, no Wayland needed) - Audio output via ALSA (HDMI or analog) - YouTube streaming with audio+video in sync using a small proxy server What doesn't work and why - 1080p: The decoder itself handles it, but writing ~90 MB/s of NV12 frames to uncached DRM memory saturates the Cortex-A7 memory bus. Not a software problem — there's no fix without DMA-BUF zero-copy between rkvdec and the DRM subsystem. - YouTube in a browser: Browsers do their own software decode — no VA-API bridge exists for rkvdec on mainline. Even with a desktop environment installed, frame rate will be unusable. - HEVC / AV1: Not supported by rkvdec on RK3228/RK3229. --- The GStreamer pipeline # Local H.264 file — video only gst-launch-1.0 filesrc location=video.mp4 ! qtdemux ! h264parse \ ! v4l2slh264dec ! videoconvert ! kmssink driver-name=rockchip sync=true # YouTube streaming with audio (requires proxy — see repo) gst-launch-1.0 -e \ souphttpsrc location="http://PROXY_IP:8091/play?v=VIDEO_ID&q=720&fmt=ts" automatic-redirect=true ! \ tsdemux name=demux \ demux. ! queue ! h264parse ! v4l2slh264dec ! videoconvert ! kmssink driver-name=rockchip sync=true \ demux. ! queue ! aacparse ! avdec_aac ! audioconvert ! audioresample \ ! "audio/x-raw,rate=44100,channels=2" ! alsasink device=hw:2 Key points: - v4l2slh264dec is the stateless GStreamer element — do not use h264_v4l2m2m (that's for stateful decoders like RPi) - kmssink driver-name=rockchip uses /dev/dri/card0 (Rockchip DRM display), not the Lima GPU - For YouTube, MPEG-TS (fmt=ts) is required — fragmented MP4 with empty_moov breaks GStreamer cap negotiation --- Why this is different from Jock's media framework Jock's framework uses kernel 4.4 + RKMPP proprietary blobs. This uses kernel 6.6 mainline + rkvdec upstream driver + open-source GStreamer. No blobs, works with current Armbian, survives kernel upgrades. --- Requirements - Armbian 24.x with kernel 6.6-current-rockchip (kernel 5.15 / Bullseye not tested — V4L2 stateless API wasn't stable until 5.18) - GStreamer 1.22 from Debian Bookworm sudo apt install -y gstreamer1.0-tools gstreamer1.0-plugins-base \ gstreamer1.0-plugins-good gstreamer1.0-plugins-bad \ gstreamer1.0-libav gstreamer1.0-alsa --- Repo with scripts and full setup guide https://github.com/Reinoldo-Ozy/rk322x-mediaplayer Includes the yt-play playback script and the proxy server (yt_proxy.py) with systemd unit. The README covers the full setup, performance numbers, and a detailed limitations section. Tested on a generic MXQ Pro-style box with RK3229, 2 GB RAM, Armbian 24.2.5 Bookworm, kernel 6.6.22-current-rockchip, DTB rk322x-box.dtb.

i have an android tv box. model name: tx 10 pro. i want to install ARMbian on it. there is a reset button under the av port. it has 2 gb of ram and 4 gb of rom (though the internet says 8G ram and 128G rom, also the android ui too). i have enabled both usb debugging and oem unlocking from the android developer option menu. the tv box can go to recovery mode using adb command. until going to the recovery mode, the adb connects perfectly but whenever it goes into recovery mode, the adb cant connect to the tv box. it consists option for fastboot inside the recovery mode but whenever i try to apply any command (e.g. fastboot/adb) the tv box doesnt show up among the devices when the device is in recovery mode. As there is no zip file for direct linux installation that i can use with flash from usb option. and the reset button beneath the av port does nothing, ive tried to flash multiple ARMbian Img files using both rufus and etcher but the screen just goes black whenever i press and hold the reset button beneath the av port. there is no option to install twrp as neither adb nor fastboot can connect whenever the device is in recovery mode. what to do?

Basically it has 1 gb ROM 8gb ram h3 chip and I HAVE put many img files on SD card NONE of them boot and as soon as I take the SD card out it boots into android perfectly fine... I'm lost on words and what to do I have also tried FEL mode on linux but the request times out with error -7 power supply is 5v 2a which is fine for this so not that and I'm using a 256gb a1 rated SD card. This is from a generic Chinese tv box called meecom and it has ADX-H-V1.0 written on it. I also changed the dtb files a lot but it still gave no display or sign that it was booted into armbian idk what to do help ( btw I repasted it that's why it has no thermal putty on it)

I’m really happy to share that I finally managed to port the SV6256P (SSV6X5X) SDIO Wi-Fi driver from the legacy Linux 4.4 kernel to modern kernels. This repository contains my working port for Linux kernel 6.12 and newer, with updated mac80211/cfg80211 integration so the driver can build and run on recent Armbian systems. The chipset is commonly used in many low-cost TV boxes and embedded devices, but the original driver only supported legacy kernels (4.4). Now it’s functional again on modern systems, at least on my tested hardware (Allwinner H616 / X96 Q via SDIO). Repository link: https://github.com/cdhigh/armbian_sv6256p I’m quite excited to finally see this old Wi-Fi chip working on a 6.x kernel 🙂 [ 4.774151] ssv6x5x: importing configuration from /lib/firmware/ssv6x5x-wifi.cfg [ 4.778281] tu_ssv6xxx_sdio_init, probe @(____ptrval____) [ 4.779483] TU_SSV6XXX_SDIO mmc3:0001:1: Probing SDIO bus [ 4.779513] ssv6xxx_set_sdio_clk: set sdio clk 25000000Hz [ 4.799668] TU_SSV6XXX_SDIO mmc3:0001:1: vendor = 0x3030 device = 0x3030 [ 4.825421] TU_SSV6XXX_SDIO mmc3:0001:1: dataIOPort 0x10000 regIOPort 0x10020 [ 4.849181] TU_SSV6XXX_SDIO mmc3:0001:1: dataIOPort 0x10000 regIOPort 0x10020 [ 4.849530] TU_SSV6XXX_SDIO mmc3:0001:1: CHIP ID: SSV6006C0 [ 4.850373] ssv6x5x ops chk: tx=1 start=1 stop=1 config=1 add_if=1 rm_if=1 conf_filter=1 wake_txq=1 [ 4.850402] ssv6x5x chanctx chk: any=1 all=0 emulate=1 add=1 rm=1 chg=1 assign=0 unassign=0 [ 4.850409] ssv6x5x chanctx ops set but not complete [ 4.850424] Attach SSV6006 family HAL function [ 4.858285] MAC address from e-fuse [ 4.858311] EFUSE configuration [ 4.858315] Read efuse chip identity[79000000] ip link show: 6: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DORMANT group default qlen 1000 link/ether xx:xx:xx:xx:xx:xx brd ff:ff:ff:ff:ff:ff

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.

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!

Is it possible to switch the operation to the OpenWRT system OR Linux OR DTB Q17 android tv box = Tanix TX11 android tv box = Q1 android tv box .... Works but ≠ X96Q android tv box AND ≠ Tanix TX1 android tv box .... It doesn't work current system firmware: Android 14 specs: - ARM Cortex-A53 - 32 bit - Mali-G31 - Allwinner H313 - arm,sun50iw9p1 4 GB RAM DDR3 32 GB HDD model = "sun50iw9"; compatible = "arm,sun50iw9p1";

Hello, I have H96 Max TV box with RK3528 chip (4GB RAM, 64GB eMMC, Android 13, build RZX.V01.20240924). Board: RK3528_DDR3_8X4_V12. Problem: Box does not boot from TF card at all. No HDMI output, no DHCP lease, nothing. What I have: TF card slot on the box 1x USB 2.0 port, 1x USB 3.0 port No serial/UART adapter (DEBUG header visible on PCB but not connected) Android 13 still working on EMMC ADB access with root What I tried: Built Armbian with BOARD=rk3528-tvbox BRANCH=legacy BUILD_MINIMAL=yes RELEASE=trixie Extracted DTB from Android boot partition, added to image Wrote image to TF card with dd Verified RKNS header at sector 64 - correct Tried replacing idbloader with one from our custom U-Boot build Original U-Boot on EMMC appears to ignore TF card completely Question: How to make original U-Boot boot from TF card? Or is there a way to install Armbian to EMMC safely while keeping ability to recover? Device AIDA64 info: Model: H96_Max_RK3528 Device: rk3528_box Hardware: rk30board Thank you!

These instructions are for Amlogic CPUs for TV Boxes. Note: If you have previously run other distributions on the box such as coreelec the below installation will not work. You will need to restore the original android firmware before attempting the install. coreelec changes the boot environment in ways that are incompatible with these Armbian builds. Download links: Weekly Community Rolling Builds: https://www.armbian.com/amlogic-s9xx-tv-box/ or build your own image using the Armbian build framework Once you download your chosen build, you need to burn the image to an SD card. Generally balenaEtcher is recommended as it does a verification of the burn. Also be sure to use high quality SD cards. Once you have the SD card with your chosen build, then you need to edit the boot configuration file on the SD card. In the BOOT partition of the SD card there will be a file /boot/extlinux/extlinux.conf, that you need to edit. There will also be a extlinux.conf.template file to use as a reference. You will need to add a line into the extlinux.conf file for the Device Tree (dtb) file you will be using for your box. Place this line before the APPEND line as shown in the .template file. Basically you need to have the correct dtb for your box. You may need to attempt to use different dtb files until you find the one that works the best for your box's hardware (there are a bunch of dtb files in /boot/dtb/amlogic/... to try depending on your cpu architecture and hardware). It is unlikely that there will be a matching dtb file for your TV box. The idea is to find the one that works best for your box. This may mean that you try booting with different dtb files until you fine one that works good enough for your needs. By searching the forums you will find information about what dtbs other users have found work best for different boxes. Because you are booting from an SD card, you can easily try different dtb files. The dtd files are named by cpu family. So for example dtb files for the s905x2 cpu are named meson-g12a-*. Below there is a table that shows the identifiers for each familiy (g12a for s905x2 in this case). Next you need to copy the correct uboot for your box. This is needed for how these builds boot on amlogic boxes. There are four different u-boot files located in the /boot directory: u-boot-s905, u-boot-s905x-s912, u-boot-s905x2-s922, u-boot-s905x3 You need to copy (note copy not move) the u-boot file that matches your cpu to a new file named u-boot.ext in the /boot directory So for example with a TX3 mini box that has an s905w cpu you would copy u-boot-s905x-s912 to u-boot.ext: cp u-boot-s905x-s912 u-boot.ext (See table below for more details on which u-boot to use for which cpu) Once you have your SD card prepared you need to enable multiboot on the box. There are different ways documented to do this, but the most common is the "toothpick" method. The "toothpick" method means to hold the reset button while applying power to the box. The reset button is often hidden and located at the back of the audio/video jack connector. By pressing that button with a toothpick or other such pointed device you can enable multiboot. What you need to do is have the box unplugged, have your prepared sd card inserted, then press and hold the button while inserting the power connector. Then after a bit of time you can release the button. (I don't know exactly how long you need to hold the button after power is applied, but if it doesn't work the first time try again holding for longer or shorter times). You should now be booting into armbian/linux. Note that the first boot takes longer as it is enlarging the root filesystem to utilize the entire SD card. After you are satisfied that your box is working correctly for your needs you can optionally copy the installation from the SD card to internal emmc storage (assuming your box has emmc). (Note: Installing to emmc has some risks of bricking your box. Don't do this unless you feel you understand how to reinstall your box's android firmware) You install armbian to emmc by running the shell script in the /root directory: install-aml.sh. Note: It is not possible to install into emmc on boxes with the s905 cpu (s905x, s905w, s905x2, etc however should all be supported). It is recommended that you make a backup of emmc first. Also be prepared if anything goes horribly wrong with your emmc install to reinstall the android firmware using the Amlogic USB Burning Tool to unbrick your device. If you have or can find an original android firmware on the internet and you can generally (but not always) recover a bricked box using the Amlogic tool and the original firmware file. Mapping from CPU to uboot and dtb: u-boot-s905 s905 - gxbb u-boot-s905x2-s912 S905X - gxl S905W - gxl S905D - gxl S905L - gxl S805X - gxl S912 - gxm A311D - gxm u-boot-s905x2-s922 S905X2 - g12a S922 - g12b u-boot-s905x3 S905X3 - sm1 Not supported or not tested S805 - S905W2 - S905X4 - S805X2 - s4 A113D - axg A113X - axg Note: Followup posts in this thread should be limited to comments to improve or better understand these instructions. Other issues should be posted as new questions in the Amlogic CPU Boxes sub-forum.

Hello everyone, I am reaching out to see if anyone in the community has successfully managed to get the internal Wi-Fi working on a box with the Realtek RTL8703bs chip. I have a MXQ Pro max (t9-RK3328) and I am using the latest Armbian build (Armbian_community_26.2.0-trunk.904_Rk3318-box_trixie_current_6.18.30_minimal.img.xz) provided by @jock for RK3318/RK3328 TV boxes. Here is the situation: 1. Using `rk3318-config` with `rk3318-box-led-conf1`, the chip is correctly powered and detected on the SDIO bus. 2. `dmesg` shows: `mmc1: new high speed SDIO card at address 0001`. 3. The hardware ID is confirmed as `024c:b703`. My questions : - Has anyone ever managed to make this specific chip (RTL8703bs) work on Armbian? - Does anyone have a patched driver (`.ko`), a specific `.dtbo` overlay, or a workaround that doesn't require recompiling the entire kernel from scratch? Here is my system log for reference: https://paste.armbian.com/ecadekazaz Thank you very much for your time and any advice you can share!

@ssdm2nvme Hi, whats up? I tried everything you recommended, including following some other tutorials beforehand, but I still can't get past the TV box's "BIOS" screen. It keeps restarting repeatedly, and I can never actually access the system. Do you have any idea what it could be?

Hi Ive just installed the latest version of Armbian (Ubuntu Noble+KDE) and everything works fine except it looks like it is not detecting my TV resolution correctly. I can choose 1920x1080@120hz but if I try yo go to 4K I can only select 24Hz I attach armbian monitor logs url, modetest and kscreendoctor My cable is HDMI 2.1 Any help would be appreciated modetest -c trying to open device '/dev/dri/card1'... is not a KMS device trying to open device '/dev/dri/card0'... done opened device `RockChip Soc DRM` on driver `rockchip` (version 1.0.0 at 0) Connectors: id encoder status name size (mm) modes encoders 83 82 connected HDMI-A-1 1880x1060 35 82 modes: index name refresh (Hz) hdisp hss hse htot vdisp vss vse vtot #0 4096x2160 24.00 4096 5116 5204 5500 2160 2168 2178 2250 297000 flags: phsync, pvsync; type: driver #1 4096x2160 23.98 4096 5116 5204 5500 2160 2168 2178 2250 296703 flags: phsync, pvsync; type: driver #2 3840x2160 30.00 3840 4016 4104 4400 2160 2168 2178 2250 297000 flags: phsync, pvsync; type: driver #3 3840x2160 29.97 3840 4016 4104 4400 2160 2168 2178 2250 296703 flags: phsync, pvsync; type: driver #4 3840x2160 25.00 3840 4896 4984 5280 2160 2168 2178 2250 297000 flags: phsync, pvsync; type: driver #5 3840x2160 24.00 3840 5116 5204 5500 2160 2168 2178 2250 297000 flags: phsync, pvsync; type: driver #6 3840x2160 23.98 3840 5116 5204 5500 2160 2168 2178 2250 296703 flags: phsync, pvsync; type: driver #7 1920x1080 120.00 1920 2008 2052 2200 1080 1084 1089 1125 297000 flags: phsync, pvsync; type: driver #8 1920x1080 119.88 1920 2008 2052 2200 1080 1084 1089 1125 296703 flags: phsync, pvsync; type: driver #9 1920x1080 100.00 1920 2448 2492 2640 1080 1084 1089 1125 297000 flags: phsync, pvsync; type: driver #10 1920x1080 60.00 1920 2008 2052 2200 1080 1084 1089 1125 148500 flags: phsync, pvsync; type: driver #11 1920x1080 59.94 1920 2008 2052 2200 1080 1084 1089 1125 148352 flags: phsync, pvsync; type: driver #12 1920x1080 50.00 1920 2448 2492 2640 1080 1084 1089 1125 148500 flags: phsync, pvsync; type: driver #13 1920x1080 30.00 1920 2008 2052 2200 1080 1084 1089 1125 74250 flags: phsync, pvsync; type: driver #14 1920x1080 29.97 1920 2008 2052 2200 1080 1084 1089 1125 74176 flags: phsync, pvsync; type: driver #15 1920x1080 24.00 1920 2558 2602 2750 1080 1084 1089 1125 74250 flags: phsync, pvsync; type: driver #16 1920x1080 23.98 1920 2558 2602 2750 1080 1084 1089 1125 74176 flags: phsync, pvsync; type: driver #17 1680x1050 59.88 1680 1728 1760 1840 1050 1053 1059 1080 119000 flags: phsync, nvsync; type: driver #18 1600x900 60.00 1600 1624 1704 1800 900 901 904 1000 108000 flags: phsync, pvsync; type: driver #19 1280x1024 60.02 1280 1328 1440 1688 1024 1025 1028 1066 108000 flags: phsync, pvsync; type: driver #20 1152x864 75.00 1152 1216 1344 1600 864 865 868 900 108000 flags: phsync, pvsync; type: driver #21 1280x720 60.00 1280 1390 1430 1650 720 725 730 750 74250 flags: phsync, pvsync; type: driver #22 1280x720 59.94 1280 1390 1430 1650 720 725 730 750 74176 flags: phsync, pvsync; type: driver #23 1280x720 50.00 1280 1720 1760 1980 720 725 730 750 74250 flags: phsync, pvsync; type: driver #24 1280x720 30.00 1280 3040 3080 3300 720 725 730 750 74250 flags: phsync, pvsync; type: driver #25 1280x720 29.97 1280 3040 3080 3300 720 725 730 750 74176 flags: phsync, pvsync; type: driver #26 1280x720 24.00 1280 3040 3080 3300 720 725 730 750 59400 flags: phsync, pvsync; type: driver #27 1280x720 23.98 1280 3040 3080 3300 720 725 730 750 59341 flags: phsync, pvsync; type: driver #28 1024x768 60.00 1024 1048 1184 1344 768 771 777 806 65000 flags: nhsync, nvsync; type: driver #29 800x600 60.32 800 840 968 1056 600 601 605 628 40000 flags: phsync, pvsync; type: driver #30 720x576 50.00 720 732 796 864 576 581 586 625 27000 flags: nhsync, nvsync; type: driver #31 720x480 60.00 720 736 798 858 480 489 495 525 27027 flags: nhsync, nvsync; type: driver #32 720x480 59.94 720 736 798 858 480 489 495 525 27000 flags: nhsync, nvsync; type: driver #33 640x480 60.00 640 656 752 800 480 490 492 525 25200 flags: nhsync, nvsync; type: driver #34 640x480 59.94 640 656 752 800 480 490 492 525 25175 flags: nhsync, nvsync; type: driver props: 1 EDID: flags: immutable blob blobs: value: 00ffffffffffff004dd9057901010101 011e010380bc6a780a0dc9a057479827 12484c2108008180a9c0714fb3000101 01010101010108e80030f2705a80b058 8a005a227400001e023a801871382d40 582c45005a227400001e000000fc0053 4f4e5920545620202a33300a000000fd 0017790e883c000a20202020202001bf 020367f05861605d5e5f621f10140513 0420223c3e1203110265663f402f0d7f 071507503d07bc570601670403830f00 006e030c004000b8442b008001020304 67d85dc401788003eb0146d000480382 88627697e200cbe305df01e40f030030 e6060d018aac10011d007251d01e206e 2855005a227400001e000000000000a3 2 DPMS: flags: enum enums: On=0 Standby=1 Suspend=2 Off=3 value: 0 5 link-status: flags: enum enums: Good=0 Bad=1 value: 0 6 non-desktop: flags: immutable range values: 0 1 value: 0 4 TILE: flags: immutable blob blobs: value: 84 max bpc: flags: range values: 8 8 value: 8 kscreen-doctor -o Output: 1 HDMI-A-1 ea40cb77-73bf-4175-8970-22f84927f147 enabled connected priority 1 HDMI replication source:0 Modes: 1:4096x2160@24.00*! 2:4096x2160@23.98 3:3840x2160@30.00 4:3840x2160@29.97 5:3840x2160@25.00 6:3840x2160@24.00 7:3840x2160@23.98 8:1920x1080@120.00 9:1920x1080@119.88 10:1920x1080@100.00 11:1920x1080@60.00 12:1920x1080@60.00 13:1920x1080@59.94 14:1920x1080@50.00 15:1920x1080@30.00 16:1920x1080@29.97 17:1920x1080@24.00 18:1920x1080@23.98 19:1680x1050@59.88 20:1600x900@60.00 21:1280x1024@60.02 22:1152x864@75.00 23:1280x720@60.00 24:1280x720@60.00 25:1280x720@59.94 26:1280x720@50.00 27:1280x720@30.00 28:1280x720@29.97 29:1280x720@24.00 30:1280x720@23.98 31:1024x768@60.00 32:800x600@60.32 33:720x576@50.00 34:720x576@50.00 35:720x480@60.00 36:720x480@60.00 37:720x480@59.94 38:720x480@59.94 39:640x480@60.00 40:640x480@59.94 Custom modes: None Geometry: 0,0 1821x960 Scale: 2.25 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown HDR: incapable Wide Color Gamut: incapable ICC profile: none Color profile source: sRGB Color power preference: prefer efficiency and performance Brightness control: supported, set to 100% and dimming to 100% Color resolution: automatic (10), range: [8; 8] bits per color Allow EDR: unsupported Sharpness control: unsupported Automatic brightness: unsupported Thank you

Hi @Tavares R You should definetly check the "Media framework installer v0.1" by Jock, on this link -> https://forum.armbian.com/topic/34923-csc-armbian-for-rk322x-tv-box-boards/page/10/#comment-102655 Also, this other link contains a repo to install some patched libs to at least use decoded video -> https://forum.armbian.com/topic/32449-repository-for-v4l2request-hardware-video-decoding-rockchip-allwinner/ Hope it helps, but reality check is the rk3229 is just too weak to properly handle a full DE running a modern browser... Something also worth trying is to enable the "cpu-hs" overlay. it will "overclock" the rk3229 from 1200Mhz to 1400Mhz, giving some extra performance, but keep low expectations... PS: Are you brazillian by any means? Tavares is a very common last name in Brazil.

I created this account just to thank you, man. Thank you so much, it worked perfectly here. Finally, my old TV box has another use besides collecting dust.

TV Box Name: Intelbras IzyPlay Board name: DV8038 CPU: Amlogic S805X (GXL Meson, Rev D) Armbian build file name: Armbian_community_26.2.0-trunk.821_Aml-s9xx-box_trixie_current_6.18.26_minimal.img.xz DTB file used: meson-gxl-s805x-p241.dtb Kernel Version: 6.18.26-current-meson64 Distribution Installed: Debian 13 (Trixie) Working Ethernet: Yes Max Ethernet Speed that works: 100 Mbps Does wifi work: Yes Does bluetooth work: No Does HDMI audio work: Not tested (headless setup) Additional Comments: - Board has 1GB RAM (908MB available) and 7.3GB eMMC - HDMI output works (tested on a DELL P2219H) - Reset button is between USB1 and USB2 ports - USB2 port is required for booting (closest to power input) - To boot from USB: hold reset button while applying power, release after 15 seconds

Hi, so after many hours of trial and error I have managed to get the latest Armbian with Kernel 6.1.27 running on my old mxq s805 tv box. Albeit only thing that is not working is hdmi output and wifi. So for anyone else trying to accomplish something similar, my steps were: https://github.com/hzyitc/armbian-onecloud Downloaded the latest release of this build for the onecloud device as it also runs on the s805 amlogic chipset (props to the developer for still updating) Burn the image to your sd card. Then after the image is burned, create a textfile on the root of the sd card and name it „uEnv.txt“ Paste the following and adjust the .dtb file to your corresponding device. My case is the mxq LINUX=/uImage INITRD=/uInitrd #VMODE=1080P50HZ VMODE=1080P FDT=/dtb/meson8b-mxq.dtb APPEND=root=LABEL=armbi_root rootfstype=ext4 rootflags=data=writeback rw console=ttyAML0,115200n8 console=tty0 no_console_suspend consoleblank=0 fsck.repair=yes net.ifnames=0 Save the file, insert the sd card in your device connect it to LAN and ssh in to the device (check the ip in your router) So, ssh root@your.ip.adress.x Password is 1234 by default. And that is that. I currently have it running for 4hrs with no outage. PiHole and PiVPN both installed and running. I hope this could help anyone out trying on a similar device. Credit goes to the devs and contributors. I just put the pieces together and made it work as my own builds wouldnt run so I resorted to this much better solution. p.s: If anyone is interested for my reasoning of updating from a old build, it was because i was using 5.14 rc2 kernel that was bugging with wireguard. And as mentioned no hdmi output and no wifi. Wifi should be fixable hdmi rather not to my understanding. Take care and have fun

To my knowledge, there are two versions of this device: the "old" version and the new version, which has a 6031 Wi-Fi chip. Here are the two DTS files extracted from the original android tv firrmware for each hardware version. Hope it helps. Tanix_TX1_6031_DTS.txt Tanix_TX1_DTS.txt