# HSIMC · T736 HDMI Two-Board Reproducibility Guide

**Artifact:** HRI-HSIMC-T736-HDMI-TWO-NODE-PUBLIC-EVIDENCE-C0-001-20261015  
**Public reference:** https://hsimc.tech/rd/t736/hdmi/  
**Source:** Historical physical engineering work on AIS B and USA2, 11–14 October 2026  
**Status:** Public engineering method. **Not** a universal production firmware, automatic installer or device certification.

## 1. What the two boards have proven / 双板真实验收

| Dimension | AIS B | USA2 |
| --- | --- | --- |
| Native Linux HDMI route and DRM connected/EDID | PASS | PASS |
| Interactive LightDM / Xorg / XFCE desktop | PASS | PASS |
| FHD 1920×1080 @ 60 Hz physical image | **HUMAN PASS** | **HUMAN PASS** |
| QHD 2560×1440 @ 60 Hz physical image | **HUMAN PASS** | **HUMAN PENDING** |
| QHD EDID / XRandR mode | MACHINE PASS | MACHINE PASS |
| 1080p monitor hotplug | Not independently scoped | HUMAN PASS |
| GUI still active after a later boot | MACHINE PASS | MACHINE PASS |

The boards were tested in actual laboratory conditions. These results do not prove that every T736 firmware, monitor, cable, hotplug event, startup or HDMI feature is certified or reliable under all conditions.

## 2. Why two separate fixes were necessary / HDMI 不等于桌面

**Layer A — Native Linux device route.** The inspected Allwinner T736 vendor BSP initially enabled the DSI display path and disabled the HDMI path in its live Linux device tree. On **each board separately**, engineers captured and independently verified the native boot source, then built an offline candidate changing only the necessary HDMI/DSI display status properties. Kernel and ramdisk bytes remained unchanged.

**Layer B — Xorg compatibility.** After native DRM could read a connected HDMI monitor and its EDID, Xorg still crashed during output-property initialization on this vendor BSP. A separately verified AArch64 library filtered problematic vendor DRM BITMASK properties **only inside the Xorg subprocess** via a LightDM Xserver wrapper. This recovered Xorg/XFCE without globally changing the Linux libdrm installation or reflashing firmware.

The same method was accepted on AIS B and then USA2. However, its compatibility is specific to the measured BSP/Xorg/libdrm stack and failure signature. A new system must pass an independent compatibility gate.

## 3. Six gates for the next board / 下一块板的六个门槛

**G0 — Real hardware identity.** Observe the actual board manufacturer and revision, physical connectors, firmware/OS/kernel, Ethernet MAC and network configuration, storage partitions, available recovery methods and operator authority.

**G1 — Native source preservation.** Read and independently verify **that board's own** boot/firmware source and restore materials. A matching SoC part number does not prove the full boot image is interchangeable. Never start with an AIS B or USA2 raw boot image as the default for a third node.

**G2 — Offline minimum change.** Compare the actual source device tree. For the inspected BSP, only three display-route properties were changed; the new board's reality must be inspected before adopting those assumptions. Prove byte-identical kernel/ramdisk, a valid output image, complete digest and exact reversibility.

**G3 — Bounded human authority.** Define one operator-approved research change with exact target, SHA256 pre/post checks, safe protection of USB storage, controlled restart and a realistic rollback/rescue boundary. A successful POC by one operator does not grant someone else permission to flash a different device.

**G4 — GUI compatibility as a separate gate.** Verify DRM connector and EDID first. Only if the same Xorg/vendor DRM issue is reproduced and ABI is compatible should the scoped Xorg workaround be considered. Do not export LD_PRELOAD globally or treat the workaround as a certified general driver.

**G5 — Machine plus physical acceptance.** Record the actual active mode, connected EDID, Xorg/LightDM state and keyboard/mouse usability, then record the real human-visible image at FHD and QHD separately. A display mode available in software is not automatically a screen that was seen.

## 4. Practical pitfalls / 实际踩坑记录

- **HDMI cable plugged in, but no output:** the native Linux FDT route may still be DSI-only. Check the kernel DRM connector before changing XRandR modes.
- **HDMI connector visible, but black GUI:** the kernel route and EDID can work while Xorg crashes. Read Xorg/LightDM logs instead of repeatedly swapping screens.
- **Another day's Boot ID stops the installer:** Linux Boot ID is transient. Read and bind it to the duration of one bounded transaction; retain stable physical identity and original source-integrity checks.
- **Entire active FDT SHA256 changes between boots:** byte-level FDT metadata may differ even while the saved original properties match. Preserve the original boot partition digest; examine device-tree properties and pin the actual current-boot FDT if required.
- **FDT permission denied:** a root-readable system endpoint needs authorized read-only access. Do not change system permissions or throw away already accepted backup fragments.
- **Running desktop treated as an MCP contract:** HDMI, browser, local MCP server and canonical Work/Authority are separate layers. A displayed page is not authorization to write or execute.

## 5. Relationship to HSIMC MCP / Reality-to-Work

A human-visible GUI enables a local operator to work with a physical node. It is a **presentation and work-entry capability**, not a Canonical Writer and not a substitute for the node's Authority, Work, Reality or receipt chain.

The third board must obtain **its own** node identity and applicable human supervisor authorization. Do not copy previous nodes' local ledger, SSH credentials, SIM routes, vendor-specific firmware secrets or private backup files. Treat the browser, Local Portal and MCP work contract as independently addressable layers.

## 6. Available public references

- [T736 physical Reality R&D overview](https://hsimc.tech/rd/t736/)
- [Earlier bilingual engineering field guide](https://hsimc.tech/rd/t736/ecosystem/evidence/engineering-field-guide-20261012/)
- [T736 capability continuation](https://hsimc.tech/rd/t736/continue/)
- [Machine-readable scoped acceptance](https://hsimc.tech/rd/t736/hdmi/acceptance.json)

## 7. What is not publicly distributed

The Mac-only private recovery vault holds native board-specific boot/UFS/FDT data, original/candidate images and rollback evidence. Those files are not linked from this public page and are **not available as generic downloadable firmware**.

This guide does not include private SSH material, node-specific runtime identifiers, unpublished raw images, credentials, local MCP databases, or an actionable privileged flashing script.

The original two-board work was a supervised engineering POC. New-node provisioning, commercial use, physical execution, contractual authority and any broader hardware certification require their own independent acceptance.

---

**HSIMC · The Human Reality Infrastructure Company**  
**GENAI NATIVE DOCUMENT · PUBLIC, SHAREABLE URL**  
Public URL: https://hsimc.tech/rd/t736/hdmi/  
Sharing this page does not create or expand access or execution authority.
