Comprehensive Guide: Installing Armbian on the TX10 PRO (Allwinner H313) Introduction This technical guide documents the complete process for deploying Linux on the TX10 PRO Android TV Box (Allwinner H313). Due to hardware variations and kernel compatibility issues common on these devices, establishing a functional Armbian environment requires specific images, DTBs, and configuration steps. This documentation is designed to streamline the installation process and avoid common hardware compatibility problems. Technical Specifications & Environment The procedures in this guide were validated on a TX10 PRO with the following hardware: Component Specification ---------------- ----------------------------------- SoC Allwinner H313 (sun50iw9p1) CPU Quad-core Cortex-A53 (ARM64) Memory 1 GB LPDDR3 (Samsung eMCP) Storage 8 GB eMMC Board Revision WFTECH_V2.0 Device Codename titan-p1 Product walley Stock OS Android (Modified Build) Bootloader U-Boot Tested Kernel Linux 6.12.64 (bookworm) Tested working image: Armbian-unofficial_26.02.0-trunk_X96q-v1-3_bookworm_current_6.12.64_minimal.img.xz Kernel: Linux 6.12.64 bookworm Base OS: Debian Bookworm Server Target: X96Q DDR3 / Allwinner H313 Although this image is labeled for the X96Q DDR3, it successfully booted on my TX10 PRO with the WFTECH_V2.0 board and Allwinner H313 SoC. Hardware revisions vary, so compatibility with other TX10 PRO units is not guaranteed. ⚠ Crucial Hardware Warning TV box manufacturers frequently change internal components (RAM layout, Wi-Fi chipsets, and board revisions) without changing the product name. Always verify your board revision before proceeding. Using the wrong Device Tree Blob (DTB) can result in an unbootable system. Advantages & Disadvantages of Running Linux Advantages: Cost Efficiency Much cheaper than a Raspberry Pi or other SBC. Enclosure Included Comes with a case and power supply. Low Power Consumption Runs quietly with very low power usage, making it suitable for lightweight servers. Disadvantages: No Official Support Linux support depends entirely on community-maintained images. Thermal Throttling Cheap passive cooling causes overheating during heavy workloads. Weak eMMC Storage Internal storage may wear out under frequent writes. Slow I/O USB ports are usually USB 2.0 only. No SATA, NVMe, or native Gigabit Ethernet. Driver Problems Wi-Fi, Bluetooth, and hardware video acceleration usually require manual setup. Prerequisite Hardwares: MicroSD Card (8GB or larger) MicroSD Card Reader (Cost: 0.45 USD ) HDMI Monitor (Tv) USB Keyboard Ethernet Adapter Integrated Wi-Fi rarely works immediately on bookworm Linux. A wired Ethernet connection is strongly recommended for initial setup. Installation Process Step 1 — Download Armbian Official Armbian images generally do not include all hardware support for the H313. Download a trusted community image designed for Allwinner H313/H616 boards using the 6.12.64 kernel. USE THIS: Armbian-unofficial_26.02.0-trunk_X96q-v1-3_bookworm_current_6.12.64_minimal.img.xz Step 2 — Flash the SD Card ⚠ Warning Avoid using the Linux dd command if you are unfamiliar with it. Selecting the wrong drive can permanently erase your computer. Instead, use BalenaEtcher. Flashing Steps: Install and open BalenaEtcher. Insert your MicroSD card. Click Flash from File. Select the downloaded .img.xz image. Click Select Target. Choose your MicroSD card carefully. Click Flash! Wait until flashing and verification reach 100%. Safely eject the card. Step 3 — Hardware Setup Before powering on: Insert the MicroSD card. Connect HDMI. Connect USB keyboard. Connect USB Ethernet. Connect power. Step 4 — First Boot The first boot performs: Filesystem expansion Initial setup System configuration This may take several minutes. Expected boot sequence: U-Boot ↓ Linux Kernel ↓ Armbian Login Prompt Step 5 — Initial Login Default credentials: Username: root Password: 1234 After logging in you will be required to: Change the root password Create a normal user Configure timezone Configure locale Step 6 — Verify Network Built-in Wi-Fi will probably not work. The board uses the SSV6x5x / SV6256 chipset which requires extra drivers. Verify Ethernet: ip a ping -c 3 1.1.1.1 Step 7 — Update the System Enable network time: sudo timedatectl set-ntp true Then update: sudo apt update sudo apt upgrade -y Step 8 — Install to eMMC (Optional) Once everything works from the SD card: sudo armbian-config Navigate to: System ↓ Install ↓ Boot from eMMC Follow the installer. After completion: Shut down Remove the SD card Boot from internal storage Hardware Compatibility Working - perfectly HDMI Output USB Ports USB Ethernet Known Issues Wi-Fi - Not working Requires manual compilation of the SSV6256 driver. Graphics No hardware acceleration. Software rendering only. DTB Compatibility Boot success depends heavily on selecting the correct DTB. Different board revisions may require different DTBs. Best Practices Test from SD First Never install to eMMC before confirming that everything works. Backup Android Create a backup of the original Android firmware before modifying internal storage. DTB Troubleshooting If the device: Boot loops Shows a black screen Fails to boot Mount the SD card on another computer. Open: armbianEnv.txt Try different H313/H616 DTB files until the system boots successfully.

I tried all the images including Armbian and the result is the same. The disk is a Silicon Power P34A60 256 GB NVME not SATA

Ultra is not the standard OPi5 nor OPi5Pro, AFAIR it is also RK3588 v.s. RK3588S wich is a major difference w.r.t. PCIE Use a recent kernel/image, see https://armbian.com/boards/orangepi5-ultra And report brand and type of the M.2 NVME SSD. Some people have asked similar question and turned out to be a M.2 SATA SSD

orangepi@orangepi5ultra:~$ dmesg -T | grep -Ei 'pcie|nvme|ltssm|link fail|fe150000' lspci -nn lsblk [Thu Jul 9 14:07:43 2026] vcc3v3_pcie30: 3300 mV, disabled [Thu Jul 9 14:07:43 2026] reg-fixed-voltage vcc3v3-pcie30: Looking up vin-supply from device tree [Thu Jul 9 14:07:43 2026] vcc3v3_pcie30: supplied by vcc5v0_sys [Thu Jul 9 14:07:43 2026] reg-fixed-voltage vcc3v3-pcie30: vcc3v3_pcie30 supplying 3300000uV [Thu Jul 9 14:07:43 2026] vcc3v3_pcie2x1l0: 3300 mV, enabled [Thu Jul 9 14:07:43 2026] reg-fixed-voltage vcc3v3-pcie2x1l0: Looking up vin-supply from device tree [Thu Jul 9 14:07:43 2026] vcc3v3_pcie2x1l0: supplied by vcc12v_dcin [Thu Jul 9 14:07:43 2026] reg-fixed-voltage vcc3v3-pcie2x1l0: vcc3v3_pcie2x1l0 supplying 3300000uV [Thu Jul 9 14:07:43 2026] reg-fixed-voltage vcc3v3-pcie-eth: Looking up vin-supply from device tree [Thu Jul 9 14:07:43 2026] vcc3v3_pcie_eth: supplied by vcc12v_dcin [Thu Jul 9 14:07:43 2026] vcc3v3_pcie_eth: 3300 mV, enabled [Thu Jul 9 14:07:43 2026] reg-fixed-voltage vcc3v3-pcie-eth: vcc3v3_pcie_eth supplying 3300000uV [Thu Jul 9 14:07:44 2026] rk-pcie fe180000.pcie: invalid prsnt-gpios property in node [Thu Jul 9 14:07:44 2026] rk-pcie fe190000.pcie: invalid prsnt-gpios property in node [Thu Jul 9 14:07:44 2026] rk-pcie fe190000.pcie: Looking up vpcie3v3-supply from device tree [Thu Jul 9 14:07:44 2026] rk-pcie fe180000.pcie: Looking up vpcie3v3-supply from device tree [Thu Jul 9 14:07:44 2026] rk-pcie fe190000.pcie: Looking up vpcie3v3-supply property in node /pcie@fe190000 failed [Thu Jul 9 14:07:44 2026] rk-pcie fe180000.pcie: Looking up vpcie3v3-supply property in node /pcie@fe180000 failed [Thu Jul 9 14:07:44 2026] rk-pcie fe190000.pcie: no vpcie3v3 regulator found [Thu Jul 9 14:07:44 2026] rk-pcie fe180000.pcie: no vpcie3v3 regulator found [Thu Jul 9 14:07:44 2026] rk-pcie fe150000.pcie: invalid prsnt-gpios property in node [Thu Jul 9 14:07:44 2026] rk-pcie fe150000.pcie: Looking up vpcie3v3-supply from device tree [Thu Jul 9 14:07:44 2026] rk-pcie fe190000.pcie: IRQ msi not found [Thu Jul 9 14:07:44 2026] rk-pcie fe190000.pcie: use outband MSI support [Thu Jul 9 14:07:44 2026] rk-pcie fe190000.pcie: Missing *config* reg space [Thu Jul 9 14:07:44 2026] rk-pcie fe190000.pcie: host bridge /pcie@fe190000 ranges: [Thu Jul 9 14:07:44 2026] rk-pcie fe190000.pcie: err 0x00f4000000..0x00f40fffff -> 0x00f4000000 [Thu Jul 9 14:07:44 2026] rk-pcie fe190000.pcie: IO 0x00f4100000..0x00f41fffff -> 0x00f4100000 [Thu Jul 9 14:07:44 2026] rk-pcie fe190000.pcie: MEM 0x00f4200000..0x00f4ffffff -> 0x00f4200000 [Thu Jul 9 14:07:44 2026] rk-pcie fe190000.pcie: MEM 0x0a00000000..0x0a3fffffff -> 0x0a00000000 [Thu Jul 9 14:07:44 2026] rk-pcie fe190000.pcie: Missing *config* reg space [Thu Jul 9 14:07:44 2026] rk-pcie fe170000.pcie: invalid prsnt-gpios property in node [Thu Jul 9 14:07:44 2026] rk-pcie fe190000.pcie: invalid resource [Thu Jul 9 14:07:44 2026] rk-pcie fe170000.pcie: Looking up vpcie3v3-supply from device tree [Thu Jul 9 14:07:44 2026] rk-pcie fe180000.pcie: IRQ msi not found [Thu Jul 9 14:07:44 2026] rk-pcie fe180000.pcie: use outband MSI support [Thu Jul 9 14:07:44 2026] rk-pcie fe180000.pcie: Missing *config* reg space [Thu Jul 9 14:07:44 2026] rk-pcie fe180000.pcie: host bridge /pcie@fe180000 ranges: [Thu Jul 9 14:07:44 2026] rk-pcie fe180000.pcie: err 0x00f3000000..0x00f30fffff -> 0x00f3000000 [Thu Jul 9 14:07:44 2026] rk-pcie fe180000.pcie: IO 0x00f3100000..0x00f31fffff -> 0x00f3100000 [Thu Jul 9 14:07:44 2026] rk-pcie fe180000.pcie: MEM 0x00f3200000..0x00f3ffffff -> 0x00f3200000 [Thu Jul 9 14:07:44 2026] rk-pcie fe180000.pcie: MEM 0x09c0000000..0x09ffffffff -> 0x09c0000000 [Thu Jul 9 14:07:44 2026] rk-pcie fe180000.pcie: Missing *config* reg space [Thu Jul 9 14:07:44 2026] rk-pcie fe180000.pcie: invalid resource [Thu Jul 9 14:07:44 2026] rk-pcie fe170000.pcie: IRQ msi not found [Thu Jul 9 14:07:44 2026] rk-pcie fe170000.pcie: use outband MSI support [Thu Jul 9 14:07:44 2026] rk-pcie fe170000.pcie: Missing *config* reg space [Thu Jul 9 14:07:44 2026] rk-pcie fe170000.pcie: host bridge /pcie@fe170000 ranges: [Thu Jul 9 14:07:44 2026] rk-pcie fe170000.pcie: err 0x00f2000000..0x00f20fffff -> 0x00f2000000 [Thu Jul 9 14:07:44 2026] rk-pcie fe170000.pcie: IO 0x00f2100000..0x00f21fffff -> 0x00f2100000 [Thu Jul 9 14:07:44 2026] rk-pcie fe170000.pcie: MEM 0x00f2200000..0x00f2ffffff -> 0x00f2200000 [Thu Jul 9 14:07:44 2026] rk-pcie fe170000.pcie: MEM 0x0980000000..0x09bfffffff -> 0x0980000000 [Thu Jul 9 14:07:44 2026] rk-pcie fe170000.pcie: Missing *config* reg space [Thu Jul 9 14:07:44 2026] rk-pcie fe170000.pcie: invalid resource [Thu Jul 9 14:07:44 2026] rk-pcie fe150000.pcie: IRQ msi not found [Thu Jul 9 14:07:44 2026] rk-pcie fe150000.pcie: use outband MSI support [Thu Jul 9 14:07:44 2026] rk-pcie fe150000.pcie: Missing *config* reg space [Thu Jul 9 14:07:44 2026] rk-pcie fe150000.pcie: host bridge /pcie@fe150000 ranges: [Thu Jul 9 14:07:44 2026] rk-pcie fe150000.pcie: err 0x00f0000000..0x00f00fffff -> 0x00f0000000 [Thu Jul 9 14:07:44 2026] rk-pcie fe150000.pcie: IO 0x00f0100000..0x00f01fffff -> 0x00f0100000 [Thu Jul 9 14:07:44 2026] rk-pcie fe150000.pcie: MEM 0x00f0200000..0x00f0ffffff -> 0x00f0200000 [Thu Jul 9 14:07:44 2026] rk-pcie fe150000.pcie: MEM 0x0900000000..0x093fffffff -> 0x0900000000 [Thu Jul 9 14:07:44 2026] rk-pcie fe150000.pcie: Missing *config* reg space [Thu Jul 9 14:07:44 2026] rk-pcie fe150000.pcie: invalid resource [Thu Jul 9 14:07:44 2026] rk-pcie fe190000.pcie: PCIe Linking... LTSSM is 0x3 [Thu Jul 9 14:07:44 2026] rk-pcie fe180000.pcie: PCIe Linking... LTSSM is 0x3 [Thu Jul 9 14:07:44 2026] rk-pcie fe170000.pcie: PCIe Linking... LTSSM is 0x3 [Thu Jul 9 14:07:44 2026] rk-pcie fe150000.pcie: PCIe Linking... LTSSM is 0x0 [Thu Jul 9 14:07:44 2026] rk-pcie fe190000.pcie: PCIe Linking... LTSSM is 0x3 [Thu Jul 9 14:07:44 2026] rk-pcie fe170000.pcie: PCIe Linking... LTSSM is 0x3 [Thu Jul 9 14:07:44 2026] rk-pcie fe150000.pcie: PCIe Linking... LTSSM is 0x1 [Thu Jul 9 14:07:44 2026] rk-pcie fe190000.pcie: PCIe Linking... LTSSM is 0x3 [Thu Jul 9 14:07:44 2026] rk-pcie fe170000.pcie: PCIe Linking... LTSSM is 0x3 [Thu Jul 9 14:07:44 2026] rk-pcie fe150000.pcie: PCIe Linking... LTSSM is 0x1 [Thu Jul 9 14:07:44 2026] rk-pcie fe180000.pcie: PCIe Link up, LTSSM is 0x130011 [Thu Jul 9 14:07:44 2026] rk-pcie fe180000.pcie: PCI host bridge to bus 0003:30 [Thu Jul 9 14:07:44 2026] pcieport 0003:30:00.0: PME: Signaling with IRQ 154 [Thu Jul 9 14:07:47 2026] rk-pcie fe170000.pcie: PCIe Link Fail [Thu Jul 9 14:07:47 2026] rk-pcie fe170000.pcie: failed to initialize host [Thu Jul 9 14:07:47 2026] rk-pcie fe190000.pcie: PCIe Link Fail [Thu Jul 9 14:07:47 2026] rk-pcie fe190000.pcie: failed to initialize host [Thu Jul 9 14:07:47 2026] rk-pcie fe150000.pcie: PCIe Link Fail [Thu Jul 9 14:07:47 2026] rk-pcie fe150000.pcie: failed to initialize host [Thu Jul 9 14:07:47 2026] rockchip-pm-domain fd8d8000.power-management:power-controller: Looking up pcie-supply from device tree [Thu Jul 9 14:07:47 2026] rockchip-pm-domain fd8d8000.power-management:power-controller: Looking up pcie-supply property in node /power-management@fd8d8000/power-controller failed [Thu Jul 9 14:07:47 2026] reg-fixed-voltage pcie20-avdd0v85: Looking up vin-supply from device tree [Thu Jul 9 14:07:47 2026] pcie20_avdd0v85: supplied by vdd_0v85_s0 [Thu Jul 9 14:07:47 2026] pcie20_avdd0v85: 850 mV, enabled [Thu Jul 9 14:07:47 2026] reg-fixed-voltage pcie20-avdd0v85: pcie20_avdd0v85 supplying 850000uV [Thu Jul 9 14:07:47 2026] reg-fixed-voltage pcie20-avdd1v8: Looking up vin-supply from device tree [Thu Jul 9 14:07:47 2026] pcie20_avdd1v8: supplied by avcc_1v8_s0 [Thu Jul 9 14:07:47 2026] pcie20_avdd1v8: 1800 mV, enabled [Thu Jul 9 14:07:47 2026] reg-fixed-voltage pcie20-avdd1v8: pcie20_avdd1v8 supplying 1800000uV [Thu Jul 9 14:07:47 2026] reg-fixed-voltage pcie30-avdd0v75: Looking up vin-supply from device tree [Thu Jul 9 14:07:47 2026] pcie30_avdd0v75: supplied by avdd_0v75_s0 [Thu Jul 9 14:07:47 2026] pcie30_avdd0v75: 750 mV, enabled [Thu Jul 9 14:07:47 2026] reg-fixed-voltage pcie30-avdd0v75: pcie30_avdd0v75 supplying 750000uV [Thu Jul 9 14:07:47 2026] reg-fixed-voltage pcie30-avdd1v8: Looking up vin-supply from device tree [Thu Jul 9 14:07:47 2026] pcie30_avdd1v8: supplied by avcc_1v8_s0 [Thu Jul 9 14:07:47 2026] pcie30_avdd1v8: 1800 mV, enabled [Thu Jul 9 14:07:47 2026] reg-fixed-voltage pcie30-avdd1v8: pcie30_avdd1v8 supplying 1800000uV 0003:30:00.0 PCI bridge [0604]: Rockchip Electronics Co., Ltd Device [1d87:3588] (rev 01) 0003:31:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:8125] (rev 05) NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS mtdblock0 31:0 0 16M 0 disk mmcblk0 179:0 0 58.2G 0 disk ├─mmcblk0p1 179:1 0 1G 0 part /boot └─mmcblk0p2 179:2 0 56.6G 0 part /var/log.hdd / zram0 254:0 0 3.9G 0 disk [SWAP] zram1 254:1 0 200M 0 disk /var/log orangepi@orangepi5ultra:~$

orange pi 5 ultra Orange Pi 1.0.0 Jammy with Linux 5.10.160-rockchip-rk3588 NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS mtdblock0 31:0 0 16M 0 disk mmcblk0 179:0 0 58.2G 0 disk ├─mmcblk0p1 179:1 0 1G 0 part /boot └─mmcblk0p2 179:2 0 56.6G 0 part /var/log.hdd / zram0 254:0 0 3.9G 0 disk [SWAP] zram1 254:1 0 200M 0 disk /var/log [Thu Jul 9 13:41:39 2026] rk-pcie fe150000.pcie: PCIe Link Fail [Thu Jul 9 13:41:39 2026] rk-pcie fe150000.pcie: failed to initialize host