diff options
| author | Danilo M. <danix@danix.xyz> | 2026-08-08 17:09:00 +0200 |
|---|---|---|
| committer | Danilo M. <danix@danix.xyz> | 2026-08-08 17:09:00 +0200 |
| commit | e1e7cdfdca82db358bc6ded1353dd95757e76f0b (patch) | |
| tree | 4189b664bb10319768ef89c57cb9de129c841f7d /nvchecker/nvchecker.SlackBuild | |
| parent | 7540c7a53f7bc8907b264994f440089a6fb85446 (diff) | |
| download | my-slackbuilds-e1e7cdfdca82db358bc6ded1353dd95757e76f0b.tar.gz my-slackbuilds-e1e7cdfdca82db358bc6ded1353dd95757e76f0b.zip | |
docs: revise Plymouth notes for SimpleDRM and the 26.x package
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>
Diffstat (limited to 'nvchecker/nvchecker.SlackBuild')
0 files changed, 0 insertions, 0 deletions