Skip to content

← Firmware Downloads

Post-install setup · Reborn (Y2Linux) · Y2

Claude investigation prompt — Y2 deep suspend, 2026-10-08

Debian-based Linux with a fast clickwheel interface for the Innioasis Y2.

Instructions published by the project, shown here word for word.

Firmware Downloads →Install guide

Claude investigation prompt — Y2 deep suspend, 2026-10-08

You are working locally with me on Y2Linux for the Innioasis Y2 / MT6582. Investigate and fix the remaining intermittent full-system suspend failure, then work toward reliable normal automatic suspend and resume. Continue the existing investigation using its actual evidence. Implement justified local source fixes and validate them; do not stop at a generic list of hypotheses. Coordinate physical trials and owner installation when needed.

Workspace: /home/luca/Dokumente/Code/Y2Linux. These links refer to local files, including uncommitted documentation and ignored hardware archives. A GitHub checkout alone does not contain this handoff.

Read first, in this order

  1. Repository instructions (/home/luca/Dokumente/Code/Y2Linux/AGENTS.md).
  2. Latest handoff (/home/luca/Dokumente/Code/Y2Linux/docs/planning/NEXT-SESSION-HANDOFF.md).

    The October 8 evening and morning entries at the top are authoritative. Older NOT_RUN, not-deployed, cleanup and installation instructions farther down are historical where superseded. Do not execute historical cleanup.

  3. Current platform state (/home/luca/Dokumente/Code/Y2Linux/docs/CURRENT_PLATFORM_STATE.md).
  4. Full investigation and validation report (/home/luca/Dokumente/Code/Y2Linux/docs/validation/Y2-PLATFORM-V1-DEEP-SLEEP-FINAL.md).

    Prioritize sections 21–28, 30–32, and the unresolved failures in the handoff.

  5. Roadmap (/home/luca/Dokumente/Code/Y2Linux/docs/planning/platform-v1-roadmap.md)

    and gap audit (/home/luca/Dokumente/Code/Y2Linux/docs/planning/roadmap-gap-audit.md). Follow its “Standing milestone-boundary rule” before activation, closure or a material hardware, memory or production scope change. A planning row is not hardware authorization.

  6. Morning machine summary (/home/luca/Dokumente/Code/Y2Linux/docs/validation/data/y2-deepsleep03-overnight-20261008.json)

    and evening machine summary (/home/luca/Dokumente/Code/Y2Linux/docs/validation/data/y2-deepsleep03-evening-20261008.json).

Installed baseline and latest findings

The last verified image is DEEPSLEEP-FINAL-03, root v1.33:

On installation boot 0132fb21-8462-4f77-9faf-3a7e7f1b8429, normal automatic policy requested kernel suspend at BOOTTIME398.407s. Retained PM stops at DPM_PREPARED, sequence8. The device callback ring ends after successful codec, MMC and 11008000.i2c returns, last at398.638s. No SPM entry or return is recorded. An unclean reset produced boot 81dce40c-9bb5-4f14-8465-c7e80ba3c602. The owner did not restart it that night. RGU raw0 and absent morning pstore panic do not identify the reset cause. A successful final I2C callback does not identify I2C as the blocker. Similar pre-SPM failures occurred on clean02.

The pending product recovery guard matches exact03 and failed boot0132fb21. Subsequent automatic requests refuse with sleep_recovery_required. Preserve this evidence and guard; another long unplugged wait will not diagnose the failed suspend path while the guard prevents entry.

The evening inspection found an orderly application/user-requested poweroff of boot81dce40c around09:55:39 CEST, followed about16 seconds later by boot ad0d5416-1a4a-453c-a008-704b3ae88ceb. Use host captures and per-boot BOOTTIME for chronology: the device wall clock is unreliable. Over that roughly seven-hour unplugged boot the journal estimate fell57%→32%, SPM entries/resumes stayed0/0, and421 recovery-guard refusals occurred. CPU0 runtime DORMANT works, but BOOTTIME and MONOTONIC advance together, showing no full-system sleep. At17:00 CEST the connected device was Charging31%, taint0, player responsive and paused, PCM closed, radios/scan off, ext4 counters0 and charger faults0. SOC is provisional and voltage-derived; no measured pack current, coulomb count or calibrated capacity exists. Reverify live state before using these dated observations as current.

Raw evidence and matching artifacts

Source and diagnostic entry points

Preserve established corrections and independent gaps

The earlier duplicate CPU/cluster PM entry corrupted saved GIC enable masks and broke timer/storage interrupts after resume. That correction is built into03 and has narrow physical confirmation. The filesystem freeze inversion backport, single-write PM request correction, synthetic USB-budget wake-source removal, maintenance wake-count refresh and receipt/journal corrections are also included. Retain these; inspect the report before reopening a fixed cause.

Independent warm-start display and user-poweroff defects remain open. Do not repeat the failed y2-display-recover.ko experiment. The untracked ovl-reset.h and display reset diagnostic are not production fixes. A successful single return does not supersede an intermittent failure without repeat evidence.

Hardware workflow and completion criteria

SSH endpoint was [email protected], pinned key /home/luca/.ssh/y2linux_ed25519; keep strict host-key checking. Acquire the nonblocking shared host lease /tmp/y2-platform-v1-device.lock before physical access and hold it across the entire operation. Do not steal another session's lease. First archive identity, retained PM/pstore, boot ledger, guard and journal before any change. Read-only inspection and local source work can proceed without repeated permission requests.

Before a device-mutating diagnostic, present the concrete bounded experiment and obtain owner agreement for its hardware actions. Preserve operation locks, recovery guard semantics, battery/charging protections, bounded backstop and failure stop. Never automatically retry a failed suspend or bypass a source check. External observer-module taint and console debugging must be recorded and excluded from clean product qualification. The owner alone flashes any reviewed successor with the preserving BOOTIMG/Y2ROOT selections; retain Y2DATA and all protected partitions. Do not perform raw MMIO experiments, change memory layout, delete evidence or modify Git identity. No push/release/issue closure is requested.

Start by reconciling the latest archives with the exact03 suspend/device PM code. Rank evidence-backed hypotheses and choose the smallest diagnostic that can distinguish them. Capture the actual blocked task/instruction or failing transition with matching symbols when existing evidence cannot localize it. Make the smallest causal fix, add meaningful regressions, and use targeted validation for localized changes. Use full required qualification for a new packaged candidate or architecture/memory changes.

Physical acceptance must demonstrate same-boot RTC and Power returns, repeated clean cycles, actual SPM residence, normal automatic-policy operation and maintenance re-entry, restored application/audio/input/storage/USB, and clear kernel/filesystem error checks. Proceed through completed controlled 30-minute, two-hour and endurance gates on the same reviewed source, with fresh unplugged battery endpoints. The previous30-minute run was owner-interrupted after943.164 seconds and did not pass. Report limits honestly; never infer full sleep from a dark screen, CPU DORMANT counters or stable displayed SOC.

Keep the handoff, validation report, machine summaries, roadmap and gap audit current. Finish with the root-cause evidence, exact source/artifact identities, changes, tests and hardware results, remaining gaps and the next concrete owner action. If a physical action needs my input, complete the independent analysis and prepare the reviewable experiment first.

These are Reborn (Y2Linux)'s own instructions, shown here word for word.

Published by the schulzcode/y2linux project [1] [3]