Files

T

Red Bear OS cab9655a8b docs: comprehensive Phase D updates — CHANGELOG, strategy, improvement plan, boot-logs README

- CHANGELOG.md: added comprehensive 2026-06-30 entry covering
  the full ACPI fork-sync (Phases A-D) and the redbear-sessiond
  consumer port. Lists the 7 critical gaps that are now fully closed
  and the 2 still open (DMAR + _WAK infrastructure).

- local/docs/ACPI-FORK-SYNC-STRATEGY-2026-06-30.md: added Phase D
  outcome section with the Linux 7.1 cross-reference findings
  (acpi_enter_sleep_state pattern), the changes applied to acpid
  and redbear-sessiond, and the final gap-closure table.

- local/docs/ACPI-IMPROVEMENT-PLAN.md: updated "Current Truthful
  Status" to reflect that acpid now follows the Linux 7.1 sleep
  pattern with _PTS/_SST evaluation, thermal/power enumeration
  works, AML mutex is real, parse_lnk_irc validates ranges, and
  S5 works end-to-end. S1-S4 paths still need _WAK + wakeup
  vector + P-state preservation (Gap #4b scaffolded but not
  implemented). DMAR init still disabled (Gap #2 needs real-HW
  investigation).

- local/docs/boot-logs/README.md: added
  REDBEAR-MINI-BOOT-PS2D-INPUTD-LOG-FIX.md to the inventory.

Also:
- Removed scratch file local/docs/ACPI-FIX-PLAN-2026-06-30.md
  (superseded by the longer ACPI-FORK-SYNC-STRATEGY-2026-06-30.md).

2026-06-30 06:38:51 +03:00

2.7 KiB

Raw Blame History

Red Bear OS QEMU Boot Logs

This directory contains frozen QEMU boot evidence captured during validation runs of the Red Bear OS desktop target (redbear-full). The files here are point-in-time records and must not be edited to "update" build commands or package versions — doing so would invalidate them as historical evidence.

What lives here

File	What it captures
`REDBEAR-FULL-BOOT-RESULTS.md`	Reference QEMU boot capture (2026-06-09)
`REDBEAR-FULL-BOOT-EXTENDED-RESULTS.md`	Extended QEMU boot capture
`REDBEAR-FULL-BOOT-POST-VIRTIO-BLKD-FIX-RESULTS.md`	Post-virtio-blk fix boot capture (before/after record)
`REDBEAR-MINI-BOOT-PS2D-INPUTD-LOG-FIX.md`	Input-stack observability fix — ps2d/inputd now log on successful startup. Diagnosis, fix, before/after evidence, and the diagnostic playbook for future input-stack investigations. (2026-06-30)
`REDBEAR-MINI-BOOT-PS2D-INPUTD-LOG-FIX.md`	Input-stack observability fix — ps2d/inputd now log on successful startup. Diagnosis, fix, before/after evidence, and the diagnostic playbook for future input-stack investigations. (2026-06-30)

Why these are frozen

These files are the project's ground-truth evidence that a specific Red Bear build booted, reached specific init stages, and exposed specific subsystem states at a specific commit. They are the only place where "this is what we saw" is preserved verbatim. Editing them retroactively — even to fix typos — would compromise the evidentiary value.

If a build command in here looks wrong

If a build command in one of these files looks outdated, the fix is not to edit the log. The correct action is one of:

The command is still correct as-written. It was the right command at the time. Leave the log alone.
The command is outdated and the corresponding validation is being re-run. Write a NEW log file (e.g. REDBEAR-FULL-BOOT-POST-QEMU-XYZ-FIX-RESULTS.md) with the new run's evidence. Do not edit the old one.
The command is wrong and no new validation is planned. Add a one-line note at the bottom of the file: "Note: command X is now deprecated, see local/docs/BUILD-SYSTEM-IMPROVEMENTS.md for current usage." Do not rewrite the original line.

Building the current redbear-full target

The canonical v6.0 build command is:

./local/scripts/build-redbear.sh redbear-full

This script enforces the v6.0 policies (local-over-WIP recipe priority, overlay integrity, submodule hygiene, firmware presence warning) that bare make all / make live invocations from older logs do not enforce.

QEMU boot

make qemu CONFIG_NAME=redbear-mini      # Boot the latest built image in QEMU

2.7 KiB Raw Blame History