vasilito/RedBear-OS
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: verify ps2d/inputd startup-log fix on rebuilt mini ISO

Browse Source 
Update REDBEAR-MINI-BOOT-PS2D-INPUTD-LOG-FIX.md with the actual
runtime verification evidence captured at 2026-06-30T00:06:16Z:

- Both new startup log lines appear in initfs at the exact source
  line numbers (@inputd:661, @ps2d:96), proving the fix is baked
  into the running image.
- End-to-end interactive login succeeded: operator typed root +
  password at the Red Bear login: prompt and reached a
  redbear# shell (Red Bear OS v0.2.4 "Liliya").

This conclusively confirms the diagnosis: the input chain
(ps2d -> inputd -> fbcond -> getty -> login -> shell) was working
all along. The previous "freeze" was a test-harness issue (no
keystrokes sent to the guest), not an OS bug. The new log::info!()
lines make the input stack health visible in future boot logs.
This commit is contained in:
vasilito
2026-06-30 03:07:49 +03:00
parent 41045fd2f1
commit ded5331006
1 changed files with 33 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files
local/docs/boot-logs/REDBEAR-MINI-BOOT-PS2D-INPUTD-LOG-FIX.md
+33 -8
View File
@@ -77,23 +77,48 @@ output (`.expect()` messages) for the cause:
always passes this; only an issue on broken real hardware)
- `inputd: invalid argument: ...` — bad CLI arg to one-shot `inputd -A 2` (config bug)
## 5. Verified by source inspection (no clean post-fix QEMU capture)
## 5. Verified by successful interactive login (2026-06-30 02:13 UTC)
The post-fix ISO was rebuilt successfully (`build-redbear.sh redbear-mini`,
exit 0, 512 MB ISO at `build/x86_64/redbear-mini.iso` produced at 2026-06-30 02:31).
Source verification:
**Verified at runtime on the rebuilt ISO** — captured boot log from
`2026-06-30T00:06:16Z` shows both new startup lines in the initfs phase
at the exact source-code line numbers:
```
2026-06-30T00-06-16.322Z [@inputd:661 INFO] inputd: scheme:input registered, waiting for handles
2026-06-30T00-06-16.427Z [@ps2d:96 INFO] ps2d: registered producer handle, listening on serio/0 (keyboard) and serio/1 (mouse)
```
The line numbers (`@inputd:661` and `@ps2d:96`) match the source exactly,
proving the fix is in the running image.
**End-to-end interactive verification** — the operator typed `root` and a
password at the `Red Bear login:` prompt and reached an interactive shell:
```
Red Bear login: root
password:
Red Bear OS v0.2.4 "Liliya"
Built on Redox OS
redbear#
redbear#
```
This conclusively confirms the diagnosis: the input chain (ps2d → inputd →
fbcond → getty → login → shell) was working all along. The previous "freeze"
was a test-harness issue (no keystrokes were being sent to the guest), not
an OS bug. The new `log::info!()` lines make the input stack's health visible
in the boot log going forward.
Source verification (defense in depth):
- `local/sources/base/drivers/input/ps2d/src/main.rs` line 96: `log::info!(...)`
- `local/sources/base/drivers/inputd/src/main.rs` line 661: `log::info!(...)`
- `recipes/core/base/source/drivers/input/ps2d/src/main.rs` line 96: copy of above
- `recipes/core/base/source/drivers/inputd/src/main.rs` line 661: copy of above
**QEMU verification pending**: a clean post-fix QEMU boot with the new lines visible
was not captured in this session — the OVMF+`-nographic` boot path took >6 minutes
to stream the live ISO under TCG, which exceeds the session timeout. A future run
should use `accel=kvm` with the raw `redbear-mini.img` to bypass the slow bootloader
streaming, then grep the captured serial for the two new `[INFO]` lines.
## 6. Related findings (build system observations)
While diagnosing this, several build-system ergonomics issues surfaced that are