Repository navigation
device/dipper: add device runtime package - #714
quatrixone wants to merge 44 commits into
Conversation
|
Thanks for putting the device package up, and for the care in it. No service that touches the modem's partitions is enabled, the descriptor stays RAM-only, the whole-disk rule covers all six LUNs (more than the Pixel 7 Pro's does), and today's NFS run was a
Smaller things: On the build: you wrote that |
b0c5132 to
2355717
Compare
|
Reproduced the requested build failure on this PR branch with The same missing-key error occurs on the retry after the build image upgrade. I have not imported or locally trusted the key. The package repository build stopped here, so there is no Omarchy 4.5.0-3 / |
|
Follow-up from the targeted Dipper package build ( The Dipper package test itself passed before the dependency install. I have not imported or trusted either key. |
|
I also checked the same |
|
Follow-up to the requested device and package checks:
The PR stays draft until the NFS-root boot reaches this image and the requested on-device evidence is captured. No personal paths, device identifiers, or wireless credentials are included in the notes. |
|
btw. I'm currently updating the https://codeberg.org/sdm845/linux/commits/branch/b4/dipper beware that official mainline firmware paths and naming may not be final. The stmfts5 got into the kernel, so touchscreen should be available. |
1afeeeb to
fb4ca19
Compare
|
Follow-up on the This push lets a This does not verify the new NFS-root boot or the requested on-device |
160f42b to
f9b04b7
Compare
|
Thanks for the work since the 13th. The package took every point: the alias loop is gone and the README lists the files, both storage rules now hide everything, the README has its SPDX line and says sleep is untested, and your notes are careful about what each boot did and didn't show. Thank you also for the plain answers on the old root's unowned units and on which Four things before this leaves draft. The first is the one that matters most to everyone else.
Smaller things: Still open from before: #502 and #500 go in first, and the run that lets this leave draft is a clean boot of main's packages with a session on the screen and the smoke report from it. I didn't build the package or the Pixel 7 Pro's images from this branch; the |
The published device tree requests Dipper firmware files that linux-firmware-qcom does not provide at its board-specific paths. Stop creating dangling aliases, keep the package dependency for generic GPU firmware, and document the phone-sourced files. Hide userdata along with every other UFS partition. Record which bring-up evidence is still unavailable.
Preserve the kernel PR review rows, stale-DTB explanation, and pre-boot/reserved-memory stop gate when the package PR is based on derekross#704.
Teach the firmware extractor to stage Dipper firmware from the owner’s vendor, modem and Bluetooth partition roots, including Qualcomm split segments. Record the fresh NFS smoke report and the failed clean-boot retry without claiming the desktop works.
Keep active-slot expectations while reading the installed device allowlist and checking every UFS whole disk. Exercise both rules with fake block devices and a RAM-only descriptor. Tested: tests/phone-smoke, the Dipper package, boot-method, firmware extraction, and tools/pr-check origin/main. Assisted-by: Codex
Distinguish the old export returned by duplicate filesystem UUIDs from the fresh Omarchy root reached after assigning a unique UUID. Record the UFS readback, package versions, firstboot progress, and unmet smoke and display gates without claiming a completed test. Checked: tools/pr-check origin/main and git diff --check. Assisted-by: Codex
Record the current UFS, display, GPU, touch and session results, and the firstboot progress through keyring and identity into services. Assisted-by: Codex
Record the services and firewall failure, the mismatch between the booted kernel and the disposable NFS root module tree, and the unverified matching-module retry. Keep the console result explicitly unconfirmed. AI assistance: Codex. Signed-off-by: quatrixone <quatrix1@gmail.com>
The NFS journal reached graphical.target and SDDM reported its session started, though neither the renderer nor visible output was verified. Record that evidence alongside the module mismatch and pending retry. AI assistance: Codex. Signed-off-by: quatrixone <quatrix1@gmail.com>
Record the matching-module RAM boot, read-only UFS guard, display probe failure, and the incomplete firstboot and SSH checks. The test root had UFW disabled, so it does not verify the firewall. AI assistance: Codex. Signed-off-by: quatrixone <quatrix1@gmail.com>
Move Dipper RAM-only whole-disk checks to derekross#916 so this PR no longer changes the shared Pixel smoke path. AI assistance: Codex. Signed-off-by: quatrixone <quatrix1@gmail.com>
Align the published firmware paths and local-backup instructions with the Dipper DTS, and record that the renderer test used the old install without a recorded kernel. Keep rmtfs out until its modem path has a gated plan. AI assistance: Codex. Signed-off-by: quatrixone <quatrix1@gmail.com>
Move the shared smoke, firmware and ram-only handling work into separate reviewable changes. AI assistance: Codex. Signed-off-by: quatrixone <quatrix1@gmail.com>
Put systemd.firstboot=off in the Dipper-only RAM boot command line. The shared firstboot package remains unchanged; the argument still needs device verification after the reset path is understood. AI assistance: Codex. Signed-off-by: quatrixone <quatrix1@gmail.com>
5a8ebb9 to
a1bbcb6
Compare
Record that the manual EA8074 test used an unpublished kernel while panel driver derekross#218 remains in review. AI assistance: Codex. Signed-off-by: quatrixone <quatrix1@gmail.com>
|
I split the shared changes as requested:
This PR is rebased onto current The required device evidence is still outstanding. The host currently sees the Mi 8's NCM/ACM Linux interfaces and an NFS TCP connection; SSH times out and Still needed before #714 can leave draft: compare the guarded-rescue device checksums with the 2026-11-09 backup and capture the reset reason; then, once the reset/fallback path is understood, boot the clean current stack and capture a visible session, |
68e5a3a to
e6bd2db
Compare
|
I completed the guarded comparison requested in the 11-18 review. A RAM-only rescue boot stayed in initramfs; all six UFS disks and all 84 backed-up partitions reported read-only, with names and sizes matching the 11-09 manifest. Phone-side SHA-256 matched 83/84 raw-source hashes from that backup. Only After the manual fastboot entry, the rescue boot exposed For the fallback gate, I propose building a rescue boot image with no NFS request, an explicit RAM-rescue mode and a built-in Update: that RAM preflight found the shared init's empty-allowlist disk guard left |
Apply the Dipper-specific overlay to the packed DTB so the disabled FTS5 node is enabled during RAM boots. Keep the source overlay with the device descriptor and compile it with the kernel build tools. The corresponding kernel DTB build now includes symbols. Exact device-side verification remains pending because the SSH host identity did not match a trusted key. AI assistance: Codex. Signed-off-by: quatrixone <quatrix1@gmail.com>
Summary
systemd.firstboot=offto avoid the console prompt; this remains unverified on the phone.ram-onlyrecovery code are split into phone-smoke: limit whole-disk guard to RAM-only devices #916, extract-vendor-firmware: follow Dipper firmware paths #917 and omamobile: keep ram-only fastboot recovery guarded #918. The package README follows the firmware paths in the Dipper DTS and uses local backup copies as input.Build and checks
tools/build-packages --local dipper --force packages/omamobile-device-dipper: passed foromamobile-device-dipper 0.1.1-1.pacman -Qlplists/usr/bin/reboot-to, the device descriptor, USB network, watchdog and UFS storage files. Package SHA-256:f0f40a3ff5fcf635f7ddc644a8d65bf037b5b56fe699b0b87df1a0af53a853dc.packages/omamobile-device-dipper/test/all,tests/dipper-probeandtools/pr-check origin/main: passed. Shared behavior and firmware tests are in their split PRs.Phone evidence and remaining gate
On 2026-11-19, a guarded rescue boot reached initramfs SSH with all six UFS disks and all 84 backed-up partitions read-only. On-device SHA-256 matched 83/84 raw-source hashes from the 2026-11-09 backup; only
logfsdiffered. The backup and full hashes stay off-repository./chosen/pureason=0x000800a1and empty pstore were read after manual fastboot entry, so they do not explain the earlier NFS resets.The first NFS-free RAM rescue preflight found that the shared init left
sdaatro=0when its writable allowlist was empty. I fixed that in #919. A RAM image built with #919's exact init (06a8cc368ce86ae6ba570208d0291c642f143019283dd0a88d99ef2365d746b3) reported all six disks and 85 partitions atro=1and returned to fastboot with its built-inreboot-to.I then verified that the existing single
bootpartition matched the 11-09 backup and flashed only that partition with the tested rescue image.reboot-to bootloaderfollowed by plainfastboot rebootreturned to the persistent rescue system, where all six disks and 85 partitions again reportedro=1. The 11-09 raw boot image remains available for restore (SHA-256e9ef7bff84d181e09de286a95b9487ec5fcb5c0cc53db3ae780d6a64ceb4fbe8). No userdata or other partition was written. This fallback contains reset failures in rescue; the cause of the earlier NFS reset remains unknown.The screen, fresh-root
networkctl status usb0,tools/phone-smoke, and current-root Adreno renderer remain unverified. The systemd firstboot argument is in the built image command line, but needs an on-device run. The previous renderer record is from the old userdata install and has no recorded kernel release; it is not a clean Omarchy/Hyprland test. The cause of thelogfsdifference is unknown; the other 83 backed-up partitions, includingpersistand bothmodemstpartitions, matched byte for byte at this check.This PR stays draft. #502 and the shared Freedreno build in #500 are prerequisites; #917 supplies the Dipper firmware extractor. A reviewed persistent install path and a clean current-stack boot with a session and smoke report are still required before Dipper can be marked supported.