4.4c/4.4d's fix was screendump-verified on amd64: the framebuffer console mechanism works and [VMName] genuinely reaches the screen for the first time. Verifying that screendump surfaced three more issues, each given its own item per SS25.0 rule 3 rather than folded in silently: - 4.4e (fixed this session, see prior commit): console_putc() forwarded raw '\n' to vt100_putc() without '\r', corrupting line-start columns. - 4.4f (open, not root-caused): character glyphs render vertically flipped. - 4.4g (open, not root-caused): most of the framebuffer stays blank despite hundreds of lines of boot output that should have scrolled through it. Confirmed via a second screendump after the 4.4e fix that 4.4f and 4.4g are both independent of the \r/\n bug -- unchanged before and after. Added evidence/ as a new tracked location for durable proof screenshots, distinct from the existing gitignored fb/ (disposable local eyeballing, per the 2026-08-07 decision to stop tracking it). Linked from the relevant 4.4c/4.4d/4.4e/4.4f/4.4g entries. 4.4c and 4.4d remain unchecked -- their Done-when criteria require a three-arch screendump match against the serial log, not yet attempted on aarch64/riscv64. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
6.4 KiB
1280x800px
6.4 KiB
1280x800px