Repository navigation
device/tegu MODEM-PLAN: the SIM test runbook for 2026-11-03 - #167
Conversation
A gated runbook for the first SIM on the palmtop, cheetah's first-SIM-test with the 9a's names and gaps: the RIL is not installed and its unit requires cheetah's modem start, which is masked here, so the runbook installs omamobile-modem-sit and adds a drop-in; the SIM goes in with the palmtop on and the CP unpowered, so no bootloader power-off round costs a slot-B try; calls are out because no audio route exists on the 9a; sessions stay short and attended because of the link-cycling hangs of 2026-10-29. Read-only steps first, a stop condition and rollback for each, and the identifier rules.
…t drop Requires Tried on the palmtop: a drop-in with an empty Requires= leaves omamobile-modem.service required, since systemd never resets a dependency list. SIM-2 now copies omamobile-sitd.service into /etc without that line. SIM-0 to SIM-2 are done on the palmtop; nothing starts.
|
One correction at 426d3c7, found by running the first steps tonight: a drop-in with an empty Requires= doesn't drop omamobile-modem.service (systemd never resets a dependency list), so SIM-2 now copies omamobile-sitd.service into /etc with that line removed and the 9a's transient modem unit in After=. SIM-0 to SIM-2 are done on the palmtop (omamobile-modem-sit 0.3.3 installed, both units disabled, no APN yet); nothing starts until the card is in. |
|
Thanks for writing this up so carefully and so early. The layout is exactly what I want for a first SIM: read-only steps first, the SIM inserted with the CP off, calls left out until there's an audio route, and the recording rules spelled out. It's also good to see you caught the drop-in problem in SIM-2 yourself and fixed it. Before 11-03 I'd like five things changed, because this is the riskiest session the palmtop has had:
A few smaller ones:
None of this is about the plan's shape, which is good. It's that a SIM, a transmitting radio and an unqualified power-off path together leave less room than the GNSS sessions did. |
…t, and runs on real packages The slot-B precondition and a one-hang cap head the runbook, citing the AGENTS line that is on main. Every stop of the modem unit by hand becomes an attended reboot, since a profile stop hard-reset the palmtop once and the power-off path is unqualified; SIM-11's checksum compare moves to after the reboot. SIM-1 now requires a real install of omamobile-modem (0.1.10 once derekross#148 and derekross#163 merge) with pacman -Qkk clean and the profile's sha256 recorded, and omamobile-modem-sit 0.3.4, since 0.3.3's state reads cycle the CP link. The start script the runbook relies on is committed under device/tegu/bringup. Smaller: no calls to the palmtop during the test and what to do if a release isn't confirmed, the cluster watchdog reset named for a hang, test -d for the CPIF check, the unit copy marked temporary, the Linux poweroff question answered, the network no longer named.
|
All of it at 39aa3e0 (main merged in first, no conflicts).
Smaller: "nobody calls the palmtop's number during the test" with what to do if the journal says a release wasn't confirmed (radio off, record, end with SIM-11's reboot; sitd's safety stop would only time out on the masked unit); the hang stop names the cluster watchdog reset, with RebootWatchdogSec kept only for a hung shutdown; |
…atcher-off fallback The runbook stops the modem only by an attended reboot, so the start script's header no longer says to stop it with systemctl. SIM-1's fallback of 0.1.8 with the old watcher off can't be followed: 0.1.8's profile_start starts the watcher unconditionally, and turning it off would be a hand edit that SIM-1's own pacman -Qkk check rejects. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Thank you, this is a careful answer to every point, and the runbook now reads the way I'd want for a first SIM: one spare cycle, never a hand stop, the NV compare right after the reboot, a real package install. Thanks too for committing the start script; reading it next to the runbook was useful straight away. I've pushed two small edits to your branch (
On my side, I'll try to get #148, #163 and #156 merged well before the 3rd. |
…s#167) The Pixel 9a's first SIM session as a gated runbook: read-only steps first, the SIM inserted with the CP off, calls left out until there's an audio route. Slot B must be marked (the runbook doesn't mark it) and one hang ends the day. The modem is never stopped by hand: every stop is an attended reboot or poweroff, with the NV checksum compare right after the boot. The modem profile is a real package install (0.1.10 with omamobile-modem-sit 0.3.4) with pacman -Qkk clean and its sha256 recorded. The start script is committed under device/tegu/bringup/. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The palmtop's first SIM arrives on 2026-11-03. This adds the gated runbook for that day to device/tegu/MODEM-PLAN.md, in the plan's style (command, Expect/Pass, stop condition, Rollback, risk per step; read-only steps first): package tests on the laptop, the RIL install, wiring omamobile-sitd to the 9a's hand modem start (its unit Requires= the 7 Pro's omamobile-modem.service, which the 9a doesn't run), the backup check, inserting the SIM with the palmtop on and the CP unpowered (a power-off round on the 9a can cost a slot-B try), modem to ONLINE under a dead-man, a read-only SIM probe, registration and IMS, data and a ping, SMS both ways, then radio off, checksums again and an attended reboot. Calls are out of this test: the 9a has no voice audio route yet (TAS2572 amplifiers, no earpiece path), so they stay a later signalling-only step.
It also records what the 9a has and lacks for the test, what to expect, what stays unqualified after a pass (suspend with the modem on; long ONLINE sessions, after the eight link-cycling hangs of 2026-10-29) and what is recorded without identifiers: no ICCID, IMSI, IMEI, number, carrier name, APN or message text.
Docs only; tools/pr-check passes.