plymouth: keep the daemon off the system console

2026-10-02T07:56:57Z

OpenWrt builds the kernel without CONFIG_VT, so BOOT_TTY never exists and plymouth falls back to the first serial device it finds, which is the system console. It opens that console, watches it for input, puts it in raw mode and locks every termios bit, so a shell sharing it loses its cursor keys, its interrupt character and a share of everything typed. Forcing details mode along the way also costs the splash its renderer. Carry a patch that makes --graphical-boot keep plymouth away from a console altogether and pass it from both entry points. The faked "splash" kernel argument and --ignore-serial-consoles go with it, both implied now, as does --attach-to-session, which redirected the console into plymouth's pty with TIOCCONS and stopped kernel messages reaching the serial port. Signed-off-by: Daniel Golle

plymouth: add boot splash for KMS devices

2026-09-26T09:21:06Z

Plymouth draws a boot splash straight onto a DRM device and holds the display until whatever follows it takes over, so nothing of the boot is visible between reset and the user interface. On a board with no framebuffer console that is the only way to put anything on screen early. Built without the framebuffer backend, without systemd and upstart integration, and without gtk, pango and freetype, so the runtime needs only libpng and libdrm. msgfmt is needed at build time, for the themes that are built and then not installed. Neither binary answers to --version, so the CI version probe is answered by test-version.sh instead. No theme is installed and none is named in the daemon configuration: a theme is a package of its own and selects itself when it is installed. Four patches are carried. Two are build fixes for musl, which has neither rpmatch() nor execinfo.h. The other two are bugs, both submitted upstream. The drm renderer drops master immediately after opening the device, so every connector probe runs as a client that is not drm master; the kernel declines it a forced probe and returns a cached status of "unknown", and the renderer gives up with "Could not initialize heads", which leaves the splash able to light only a display something else has already probed. The escape key tears the splash down for a text view, guarded only on a VT existing, so on a kernel with CONFIG_VT but no framebuffer console the dummy driver is bound, the text goes nowhere and the screen turns black. Signed-off-by: Daniel Golle

video/utils/plymouth, branch master

plymouth: keep the daemon off the system console

plymouth: add boot splash for KMS devices