Follow-up: Ubuntu Resolute Minimal .128 validation (11 November 2026) I have completed another bounded validation run on my Orange Pi 5 Ultra, complementing the earlier Debian results. Image: Armbian_26.11.0-trunk.128_Orangepi5-ultra_resolute_vendor_6.1.172_minimal.img.xz Ubuntu 26.04 Resolute Minimal; kernel 6.1.172-vendor-rk35xx; build commit e5a400a. Hardware: 16 GB RAM, approximately 59.5 GiB SD card, root filesystem on /dev/mmcblk1p1. The imported first-boot preset was consumed successfully. Ethernet, Wi-Fi and automatic NTP synchronization worked. Initial IPv6 NTP queries timed out, then IPv4 fallback synchronized the clock around 52 seconds after boot. Area Result Memory PASS: one locked 2 GiB memtester pass; all 18 checks completed successfully. CPU / VM PASS: approximately 15 minutes, eight CPU workers plus one 4 GiB VM worker with verification; peak 76.7 C. SD storage PASS: 2 GiB CRC32C file verification; write 23.74 MiB/s, verification read 64.23 MiB/s. NVMe PASS: unmounted, raw read-only test at 1,568.35 MiB/s; no host-written sector increase. Network Functional PASS: 12/12 checks; Ethernet and Wi-Fi observations detailed below. RTC PASS: HYM8563 future-minute alarm fired, incremented its interrupt counter, and was cleared. HDMI / keyboard PASS: visible console refresh and USB keyboard Enter response confirmed manually. HDMI audio PASS: 48 kHz S16_LE stereo playback; left and right channels confirmed audible manually. Boot persistence Core PASS: two warm reboots and one cold boot after approximately 30 seconds without power. Stock Bluetooth FAIL: missing rfkill / BlueZ; details below. Ethernet negotiated 1 Gb/s with my router. Separate TCP tests measured approximately 937 Mb/s board RX and 771 Mb/s board TX. Wi-Fi measured approximately 326 Mb/s RX and 373 Mb/s TX. RX means router to board; TX means board to router. These are receiver-reported decimal Mbit/s, not MiB/s. The peer cannot validate 2.5GbE performance. Wi-Fi accumulated 232 additional TX drops during testing, with retransmissions. The iw RX packet count was also inconsistent with kernel interface counters. Similar observations already existed in my Debian .127 evidence; this does not establish a new Ubuntu regression. HDMI controller state was 2560x1440p59.95. Reboot checks confirmed changed boot IDs, the expected SD root, working network, synchronized NTP and an unchanged installed-package set. Test utilities and their libraries came from 61 DEBs in the configured Ubuntu/Armbian repositories, extracted into a separate directory. No test packages were installed into the system. The stock image lacks rfkill and BlueZ clients. ap6611s-bluetooth.service fails at ExecStartPre with 203/EXEC before firmware loading. I did not patch this image, and Bluetooth pairing remains untested. This Ubuntu image was uploaded at 03:24 UTC on 11 November, before dependency-fix PR #11331 merged at 05:26 UTC: https://github.com/armbian/build/pull/11331 This confirms the packaging problem in the older image; it does not validate the merged fix on Ubuntu. I am keeping this result with the existing issue rather than opening a duplicate. Power supply rating: 5 V / 5 A. Two ML307 modules and one 2454 radar remained GPIO powered, with unchanged wiring. Their serial functions and power margin were not tested. No USB storage device was connected this round. Not covered: USB storage/other ports, HDMI input, GPU rendering, codecs, NPU inference, camera/MIPI, eMMC/SPI or NVMe boot, analog audio, mouse interaction, RTC battery retention, full-capacity RAM/media testing, or extended stability. Command execution, evidence collection and log review were AI-assisted. I performed the physical actions and confirmed the display, keyboard and audio observations. This is bounded single-board testing, not full release certification. Selected redacted evidence archive: orangepi5-ultra-ubuntu128-validation-evidence.zip KingFalse
orangepi5-ultra-ubuntu128-validation-evidence.zip
