# Coreboot ## Identification Coreboot is open-source system firmware that performs platform hardware initialization and then hands control to a payload such as SeaBIOS, GRUB, or EDK2. The notebook treats it as a pre-OS control and recovery layer, not as a universal drop-in replacement for every vendor firmware image. ## Notebook evidence - [[Scanned_20260730-1719#PDF page 28 — Installer and firmware utilities; Q4OS, VirtualBox, Pop!_OS, Coreboot|PDF page 28: Installer and firmware utilities; Q4OS, VirtualBox, Pop!_OS, Coreboot]] — The page asks how software reaches hardware: Windows installers, local emulation, camera-device management, a Debian install, VM isolation, then firmware replacement. The question mark beside firmware upgrades appropriately marks uncertainty about whether an application manages configuration or actually flashes firmware. - [[Scanned_20260730-1719#PDF page 29 — Coreboot, Pop!_OS, Go, IPFS, CERN, and boot research questions|PDF page 29: Coreboot, Pop!_OS, Go, IPFS, CERN, and boot research questions]] — The author is imagining a bootable node rather than merely a desktop: open firmware, a Linux userland, portable network services, and a recovery partition or live environment. “48-8K” may be a project-size or memory note, but is too uncertain to interpret. - [[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 73 — Leah Rowe, Minifree, Libreboot, osboot, and “federation”|PDF page 73: Leah Rowe, Minifree, Libreboot, osboot, and “federation”]] — The technical pursuit becomes explicitly political and organizational. “Federalism” appears to name a model in which independent hardware, firmware, operating systems, archives, and communities cooperate without a single vendor controlling the whole stack. - [[Scanned_20260730-1719#PDF page 74 — Libreboot support, free-software institutions, science-fiction federations, and Austin’s “Fed”|PDF page 74: Libreboot support, free-software institutions, science-fiction federations, and Austin’s “Fed”]] — “Federation” is being tested across technical support, free-software institutions, fiction, and local architecture. The author is searching for a durable metaphor: distinct members retain identity while sharing rules and infrastructure. - [[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 [[CERN|CERN]] · [[ChromeOS|ChromeOS]] · [[DAR|DAR]] · [[Free Software Foundation|Free Software Foundation]] · [[Gemini PDA|Gemini PDA]] · [[GNU GRUB|GNU GRUB]] · [[Go programming language|Go programming language]] · [[InterPlanetary File System|InterPlanetary File System]] · [[Libera Chat|Libera Chat]] · [[Libreboot|Libreboot]] · [[Minifree|Minifree]] · [[MrChromebox Firmware Utility Script|MrChromebox Firmware Utility Script]] · [[OmniOS|OmniOS]] · [[ONVIF|ONVIF]] · [[Index - People#Leah Rowe|Leah Rowe]] · [[Pop!_OS|Pop!_OS]] · [[Q4OS|Q4OS]] · [[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 Classify each tool as installer, emulator, discovery client, VM, or flasher. Never infer firmware-flashing capability from a product name. ## Source - [[Scanned_20260730-1719|Scanned_20260730-1719]]