Just managed to distract myself some more in this outrageous heat here in the UK and can confirm that the RELEASE=stable (6.18) build (from compile.sh) boots ok after some tweaking. It got stuck on "Starting Kernel" but when I added these lines to /boot/armbianEnv.txt to see why it failed, then it booted ok - dunno why. I think keep_bootcon was the important bit. extraargs=earlycon=uart8250,mmio32,0x02500000 keep_bootcon ignore_loglevel loglevel=8 The other problem then was getting the ethernet to work which I did by creating a device tree overlay file - much the same as other here is it only seems be working at 100M unlike the 1000M in the 5.15 kernel. The extra problem seemed to be that the wifi driver would periodically crash and cause a kernel-panic. The following DTS file pulls the ethernet down to 100M and disables the wifi to stop it crashing. You then compile this into a .dtbo file, copy it to /boot/overlay-user and reference it in armbianEnv.txt with this line user_overlays=opi4a-network-fix The opi4a-network-fix.dts syntax to create it is as follows ... apart from that I can't get it to do much more, so will go down the 5.15 bookworm route until things change /dts-v1/; /plugin/; / { compatible = "xunlong,orangepi-4a", "allwinner,sun55i-t527"; /* Maintain working Ethernet at 100M address 1 */ fragment@0 { target-path = "/soc/ethernet@4510000"; __overlay__ { phy-mode = "rgmii-id"; phy-handle = <&ext_rgmii_phy>; status = "okay"; mdio { #address-cells = <1>; #size-cells = <0>; ext_rgmii_phy: ethernet-phy@1 { compatible = "ethernet-phy-ieee802.3-c22"; reg = <1>; max-speed = <100>; }; }; }; }; /* Hard disable the unstable wireless MMC controller block */ fragment@1 { target-path = "/soc/mmc@4021000"; __overlay__ { status = "disabled"; }; }; };

@bedna I tried disabling zram, both with armbian-config (so disabling it in /etc/default/armbian-zram-config) and also adding extraargs=zswap.enabled=0 on /boot/armbianEnv.txt, but the swap still show up htop and mounted in the lsblk output. What am I missing?

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