Skip to content
Draft
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
44 commits
Select commit Hold shift + click to select a range
89f04f7
device/dipper: add device runtime package
quatrixone Nov 12, 2026
4c15958
device/dipper: complete runtime package defaults
quatrixone Nov 12, 2026
c9ae509
NOTES: record Dipper package probe and backup check
quatrixone Nov 12, 2026
155c651
NOTES: record Dipper touch probe
quatrixone Nov 13, 2026
45b8440
docs: record Dipper NFS desktop smoke
quatrixone Nov 13, 2026
d7758ed
device/dipper: remove broken firmware aliases
quatrixone Nov 13, 2026
070a440
docs(dipper): keep FTS5 and NFS evidence together
quatrixone Nov 13, 2026
3bc80f2
dipper: record NFS probe and enable EA8074
quatrixone Nov 14, 2026
f3e0dfa
dipper: list exact firmware paths requested by DTS
quatrixone Nov 14, 2026
77b877c
device/dipper: record unreachable current NFS boot
quatrixone Nov 14, 2026
410e699
dipper: record verified userdata backup
quatrixone Nov 14, 2026
814c63d
dipper: note upstream firmware path changes
quatrixone Nov 15, 2026
c7c493b
omamobile: allow ram-only fastboot recovery
quatrixone Nov 15, 2026
5fd66b0
NOTES: record 2026-11-15 RAM retry
quatrixone Nov 15, 2026
a381ab2
DEVICES: track Dipper as WIP
quatrixone Nov 15, 2026
566fcdb
dipper: honor watchdog limit and report storage state
quatrixone Nov 15, 2026
92dadd5
docs(dipper): update firmware paths to current DTS
quatrixone Nov 16, 2026
1ab3c9b
docs(dipper): keep device matrix entry in one place
quatrixone Nov 16, 2026
aef5124
docs(dipper): qualify FTS5 reconstruction
quatrixone Nov 16, 2026
b1eb39f
docs(dipper): record guarded rescue boot
quatrixone Nov 16, 2026
a5f0a89
docs(dipper): record initial setup blocker
quatrixone Nov 16, 2026
0e2a95a
docs(dipper): record firstboot retry limits
quatrixone Nov 16, 2026
7cbb328
docs(dipper): record isolated NFS smoke report
quatrixone Nov 16, 2026
1b193b0
docs(dipper): record visible lock screen
quatrixone Nov 16, 2026
af6307c
device/dipper: map firmware from owner partitions
quatrixone Nov 16, 2026
4147199
dipper: use WCN3990 firmware request paths
quatrixone Nov 16, 2026
ea62fa0
docs(dipper): record visible RAM console and NFS retry
quatrixone Nov 16, 2026
93d1279
docs(dipper): distinguish NFS retries from installed root
quatrixone Nov 16, 2026
bb3bbe2
docs(dipper): record base DTB and NFS export comparisons
quatrixone Nov 16, 2026
d3678ca
phone-smoke: preserve slot checks with Dipper storage guard
quatrixone Nov 16, 2026
a3c2903
docs(dipper): record fresh current-stack NFS handoff
quatrixone Nov 16, 2026
ce5fd3f
docs(dipper): record repeated current-stack smoke results
quatrixone Nov 17, 2026
958b467
docs(dipper): record NFS firstboot module mismatch
quatrixone Nov 18, 2026
af4395a
docs(dipper): record SDDM session start
quatrixone Nov 18, 2026
f52f164
docs(dipper): record guarded NFS retry limits
quatrixone Nov 18, 2026
f726d19
device/dipper: split shared smoke changes from package
quatrixone Nov 18, 2026
b33aacb
device-dipper 0.1.1: defer rmtfs until modem plan
quatrixone Nov 18, 2026
0a7872b
device/dipper: split shared helpers from package
quatrixone Nov 18, 2026
a1bbcb6
device/dipper: disable systemd firstboot prompt
quatrixone Nov 18, 2026
139e21d
DEVICES: qualify Dipper panel test kernel
quatrixone Nov 18, 2026
e6bd2db
device/dipper: record guarded backup comparison
quatrixone Nov 19, 2026
81fb758
device/dipper: record RAM rescue fallback preflight
quatrixone Nov 19, 2026
d1287ae
device/dipper: verify persistent rescue fallback
quatrixone Nov 19, 2026
3206168
device/dipper: enable the FTS5 overlay in RAM boots
quatrixone Nov 19, 2026
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
49 changes: 38 additions & 11 deletions device/dipper/BRINGUP-M1.md
Original file line number Diff line number Diff line change
@@ -1,14 +1,35 @@
<!-- SPDX-License-Identifier: MIT -->
# Xiaomi Mi 8 (dipper): RAM-only first light

**Status (2026-11-12):** the newest RAM boot used the Dipper FTS5 node enabled directly in a local kernel tree. `stmfts` registered as `event2`; the screen was not visually verified, and no physical touch was captured on that boot. The preceding corrected overlay boot captured contact, changing X/Y and release. All recorded UFS partition flags were read-only, `/dev/sda` was absent, and `0x85fc0000–0x8a8fffff` remained reserved. No UFS partition was written. Rebuildable kernel DTS and repository overlay sources are now proposed in kernel PR #249 and this PR; the test images predate those commits. Earlier boots are recorded in [NOTES.md].
**Status (2026-11-18):** a fresh Omarchy 4.5.0-3 NFS root runs on the phone
with `omamobile-omarchy 0.1.45`. Two phone smoke runs confirmed the USB link,
display connector and all UFS disks read-only. Both found no render node, no
multitouch input, and no Hyprland or shell session. Firstboot with the 0.1.8
service-enable change reached user setup, but UFW failed because the NFS root
had modules for a different kernel release. Matching modules are now in the
disposable root; a phone reboot and smoke test with them are pending. The NFS
journal later showed the graphical target and SDDM session starting, without
visual confirmation or a captured renderer. A rescue framebuffer was
unblanked, but that result was also not visually confirmed. Exact evidence
and limits are in [NOTES.md]. No persistent image was flashed; the descriptor
and installer still have no Dipper install path.

**Status (2026-11-15):** a RAM-only `fastboot boot` reached the Omarchy 4.5.0-3 NFS root with `omamobile-omarchy 0.1.45`. Its journal records the handoff, the UFS guard setting all six whole-disk nodes and all 85 partitions read-only, both packed-DTB `removed-region` nodes, the initramfs guard, and the `qcom_wdt` device; direct UFS `ro` readback was not captured. In a later 20-second-watchdog NFS retry, `/proc/iomem` showed `0x85fc0000–0x8a8fffff` reserved and `networkctl status usb0` reported routable/configured. Systemd was still `initializing`; it did not reach multi-user, and `tools/phone-smoke`, watchdog feeder state, direct UFS `ro` readback and the visible screen remain unverified. The phone later returned to the existing ext4 root. The 60-second setting was rejected by the driver, so the package now uses 30 seconds (driver maximum 31); a fresh boot with that packaged setting remains unverified. The diagnostic root used volatile journals and temporary early-SSH wiring; those changes are not in the package. No flash or explicit UFS-write command was issued. Image hash, source commits and evidence limits are in [NOTES.md].

**Previous status (2026-11-14):** a fresh rootfs was built with Omarchy 4.5.0-3 and `omamobile-omarchy 0.1.45`; all build-time rootfs smoke checks passed. The Dipper kernel and EA8074 panel module also built. A RAM-only NFS test did not reach that new root: a later SSH session reported the existing kernel (`g2a318a96ae9d-dirty`) and an `ext4` root. `reboot-to bootloader` returned the phone to fastboot. The test image showed no firstboot log or created test account. `/proc/iomem`, UFS read-only flags, `tools/phone-smoke`, `networkctl status usb0` and the visible desktop were not captured. No flash command was issued; incidental userdata writes by the existing ext4 system could not be ruled out. Earlier RAM boots and test limits are recorded in [NOTES.md].

A retry of image `d7bdde5e35b5c78a5878ebf4df28effefca35bed9a26c39098f473278d233ead` was accepted by `fastboot boot`, but the host saw no ARP reply and a 10-second capture contained no SSH, RPC or NFS packets. The root handoff remains unverified. The exported image was checked on the host: it has Omarchy 4.5.0-3, `omamobile-omarchy 0.1.45`, `omamobile-device-dipper 0.1.0`, all seven runtime dependencies and 375 package-owned `/usr/lib/systemd/system/*.service` files; the three old unowned units and WLAN helper are absent. No phone-side `phone-smoke`, `networkctl status usb0`, `/proc/iomem`, UFS flags or display observation could be collected from this boot. No flash or explicit UFS-write command was issued; with the running root unknown, incidental writes cannot be ruled out.

Before that retry, the 84-partition read-only backup was revalidated and `userdata` was recaptured to a private off-repository file archive from an ext4 mount using `ro,noload`. GNU tar preserved numeric ownership, modes, sparse files, ACLs and xattrs; zstd integrity and a full tar listing passed. This supersedes the older possibly stale userdata archive. It is a file-level, non-atomic archive, not a raw partition image.

A separate RAM NFS-root run used image `a2d435a7430e7e4c145c61cdb9866d16929731859d91c7105e6bfcaf9e3e9dd7` with the rebased #503 init. BusyBox `mount` switched to the test NFS root; all six disk flags and all 85 partition flags were `ro=1`. Systemd reached the multi-user target with `RuntimeWatchdogSec=60s`, and SSH remained available. `reboot-to bootloader` returned the phone to fastboot. The exported root was a generic Arch base; this did not test the Omarchy desktop or link-loss recovery. Full results are in [NOTES.md].
The FTS5 driver from [touch #219] is merged into linux-omarchy-mobile. The
Dipper board DTS from [DTS #220] is merged too (2026-11-11), and the EA8074
panel driver is under review in [panel #218].
The EA8074 panel test and the corrected FTS5 touchscreen hardware test are
recorded in [NOTES.md]. Both used RAM boots; no UFS partition was written.
The EA8074 panel test is recorded in [NOTES.md]. The FTS5 touchscreen
registered and physical taps produced touch events on 2026-11-13; see
[NOTES.md]. End-to-end touch use in a visible Omarchy session remains
unverified.
On 2026-11-09, a guarded RAM boot was used to capture all 84 GPT partitions
other than `userdata` (the phone has no `super`); source and compressed-image
checksums passed. The separate live userdata archive also passed its checksum
Expand Down Expand Up @@ -59,7 +80,8 @@ archive's checksum file. Do not boot if either backup is missing or fails.
without changing UFS, and the screen stays lit because simpledrm holds the
panel's VCI and VDDIO rails. If it goes dark about 30 seconds in, record
`dmesg | grep -i -E 'regulator|simple'` and stop.
Before booting, decompile the exact packed DTB on the laptop with
**Pre-boot DTB check:** before running `fastboot boot`, decompile the exact
packed DTB on the laptop with
`dtc -I dtb -O dts` and verify it contains both
`removed-region@86200000` and `removed-region@89100000`. On the phone,
before touching the screen or doing any other test, verify
Expand Down Expand Up @@ -113,16 +135,21 @@ repository; the SSH public key and generated host key stay in the local output.
persistent writer.
- The initramfs has no Arch root yet. A later hard NFS-root mount can freeze the
root session if the host drops; use it only for a RAM-only probe. NFS-root
needs a root with `RuntimeWatchdogSec=60s`, because `kill -9 -1` stops the
userspace feeder before systemd can take over. It must never fall through to
writable userdata.
must configure systemd's hardware watchdog within the kernel driver's limit.
The Dipper `qcom_wdt` driver's `0xFFFFF` tick limit at 32764 Hz gives a
maximum timeout of 31 seconds. Systemd rejected 60 seconds in the
2026-11-15 test; the package now uses 30 seconds for both runtime and reboot
watchdogs. A fresh boot with that packaged setting still needs verification.
It must never fall through to writable userdata.
- Wi-Fi needs firmware and the phone's own WLAN address. Read identity files
from `persist` with `debugfs` (read-only) before enabling that service; never
mount `persist`.
- The exact systemd journal line from the earlier failed `qcom_wdt` timeout
change was not retained. The 2026-11-10 NFS test root reached systemd with
`RuntimeWatchdogSec=60s`; NFS link-loss recovery and the Omarchy desktop on
that root remain untested.
- The 2026-11-15 test journal records
`Failed to set watchdog hardware timeout to 1min: Invalid argument` with
`RuntimeWatchdogSec=60s`; udev also timed out before SSH became available.
The earlier 2026-11-10 NFS test used `RuntimeWatchdogSec=20s` and reached
multi-user. NFS link-loss recovery and the Omarchy desktop on the current
Omarchy root remain untested.
- FTS5 controller probe and physical contact/coordinate/release events passed
on 2026-11-12 (see [NOTES.md]); Hyprland input delivery and GPU rendering
remain untested on the phone.
Expand Down
Loading
Loading