# SeaBIOS ## Identification [[SeaBIOS|SeaBIOS]] is a legacy BIOS-compatible payload that can run on Coreboot. [[ChromeOS|ChromeOS]] uses the Blink rendering engine and provides `crosh`; historical developer-mode/legacy-boot workflows used keyboard shortcuts to reach alternate boot paths. USB-to-RS-232 adapters provide serial-console access for low-level diagnosis. ## Notebook evidence - [[Scanned_20260730-1719#PDF page 32 — SeaBIOS/Coreboot on Chromebook-class hardware|PDF page 32: SeaBIOS/Coreboot on Chromebook-class hardware]] — The page captures a Chromebook conversion workflow: enable a lower-level shell, install or use alternate firmware, then boot Parrot/GRUB or diagnose by serial. It is the clearest bridge so far from consumer appliance to general-purpose computer. - [[Scanned_20260730-1719#PDF page 33 — Libreboot, Chromebook firmware resources, mobile Linux, and disk archives|PDF page 33: Libreboot, Chromebook firmware resources, mobile Linux, and disk archives]] — The author is identifying projects that remove vendor firmware or mobile-OS dependence while retaining recoverable archives. The page joins laptop firmware freedom, mobile Linux, and portable backup. - [[Scanned_20260730-1719#PDF page 75 — Coreboot/Libreboot summary and supported operating systems|PDF page 75: Coreboot/Libreboot summary and supported operating systems]] — This is the notebook’s capstone. Everything previously collected—serial access, IOMMU, USB, SPI, iPXE, alternate OSes, encryption, Tor/Tails, open drivers, and vendor-independent recovery—is gathered beneath open firmware. “The Federation” is the proposed architecture: a common pre-OS substrate that can host multiple independently governed operating environments. ## Relationships and overlays The source places this note in a shared evidence cluster with [[ChromeOS|ChromeOS]] · [[DAR|DAR]] · [[Gemini PDA|Gemini PDA]] · [[Libreboot|Libreboot]] · [[MrChromebox Firmware Utility Script|MrChromebox Firmware Utility Script]] · [[Scanned_20260730-1706|Scanned_20260730-1706]]. Within the larger collection, this evidence extends [[Vendor-Agnostic Recovery|vendor-agnostic recovery]] and [[Continuity Architecture|continuity architecture]] by showing how software, hardware, identity, and pre-OS control depend on recoverable interfaces. ## Evidentiary status and open leads Determine exact board name, firmware write-protect state, recovery image, backup ROM, and rollback procedure before any flash operation. ## Source - [[Scanned_20260730-1719|Scanned_20260730-1719]]