aboutsummaryrefslogtreecommitdiffstats
path: root/.extras/docs/plymouth-graphical-boot.md
AgeCommit message (Collapse)AuthorFilesLines
12 daysdocs: revise Plymouth notes for SimpleDRM and the 26.x packageDanilo M.1-7/+80
The research doc concluded that getting xe into the initrd was the gate for the whole splash effort. That holds for SBo 22.02.122, which has no SimpleDRM support at all, but upstream added it in 24.004.60 and uses it by default on UEFI to draw on the EFI framebuffer. On this machine that removes the prerequisite entirely, along with the firmware bloat and the per-kernel-update maintenance it implied. Also record that stage 1 is done and verified after reboot: the printk wall is gone, the rc script wall is not, which no kernel flag can fix. Add a section answering whether the boot text stays reachable behind a splash (Esc toggles it, and plymouth does its own console redirection). Replace the unreadable LQ thread with the Arch wiki as the reference, and note the repo README that plymouth is -current only. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
13 daysdocs: research notes on Plymouth graphical bootDanilo M.1-0/+340
Covers how mainstream distros implement boot splash (Plymouth from initramfs, not kernel patches), the two SBo packages available, and a two-stage plan for this machine. Key finding: xe.ko is absent from the current initrd, so there is no DRM device during the initrd phase and no surface for Plymouth to draw on. That is the prerequisite for everything else. Nothing installed or changed; research only. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>