Plymouth is used to show splash screens during system boot and shutdown. It is a more modern alternative to fbsplash and provides flicker-free animated boot splashes with support for progress bars, solar flares, and other nifty things. In addition to OpenRC, it also has full systemd support. Since it is a boot splash tool, Plymouth does not provide background eye-candy for the ttys way fbsplash does (meaning it shows no decoration on the consoles after the system has booted).
- 1 Installation
- 2 Configuration
- 3 Usage
- 4 Tips
- 5 See also
- 6 External resources
Specific kernel options must be altered in order to get Plymouth working properly. Use the genkernel --menuconfig all command (or equivalent) in order to modify the kernel configuration.
It is highly advised to disable the Linux bootup logo. On some systems having the bootup logo displayed seems to cause problems.
Device Drivers ---> Graphics Support ---> [ ] Bootup logo --->
Be sure to enable kernel modesetting (KMS) for the system's respective graphics card.
KMS for Intel cards
Device Drivers ---> Graphics Support ---> <*> Direct Rendering Manager (XFree86 4.1.0 and higher DRI support) ---> <*> Intel 8xx/9xx/G3x/G4x/HD Graphics [*] Enable modesetting on intel by default
If this is the user's first time modifying settings for on-board Intel GPUs the Intel article should be referenced for additional configuration.
KMS for Nvidia cards (Nouveau drivers)
Device Drivers ---> Graphics support ---> <*> Direct Rendering Manager (XFree86 4.1.0 and higher DRI support) ---> <*> Nouveau (nVidia) cards
If this is the user's first time changing settings for the NVIDIA graphics card using the nouveau driver be sure to reference the nouveau article for additional information.
KMS for Nvidia cards (official drivers)
To use the official Nvidia drivers see the wiki's official Nvidia-drivers article.
So far the results of using official Nvidia-drivers are untested with Plymouth.
KMS for Radeon cards
Device Drivers ---> [*] Staging drivers ---> [*] Enable modesetting on radeon by default
If this is the user's first time setting up a Radeon graphics card be sure to reference the radeon article for further information.
USE flags for sys-boot/plymouth Graphical boot animation (splash) and logger
||Enable extra debug codepaths, like asserts and extra output. If you want to get meaningful backtraces see https://wiki.gentoo.org/wiki/Project:Quality_Assurance/Backtraces|
||Enables smooth transition to GDM|
||Add support for x11-libs/gtk+ (The GIMP Toolkit)|
||Provides abstraction to the DRM drivers (intel, nouveau and vmwgfx at this moment)|
||Adds support for printing text on splash screen and text prompts, e.g. for password|
||Build static versions of dynamic libraries as well|
The sys-boot/plymouth package can be installed by running:
emerge --ask sys-boot/plymouth
/etc/plymouth/plymouthd.conf - the sole configuration file for Plymouth. It can be left untouched. Selecting theme is described in further section.
There are currently two initramfs generators that support Plymouth. Either one will produce essentially the same result. Determining which to use, is entirely the choice of the user. This article does not go into detail on troubleshooting failed results. So, choosing the more comfortable initramfs would be a wise choice. Using genkernel-next is recommended, since many users are already familiar with using genkernel.
At this point in time, normal genkernel cannot create an initramfs with a Plymouth theme included. Therefore, in order to proceed, either dracut or sys-kernel/genkernel-next will need to be selected, in order to build an initramfs capable of including a Plymouth theme. From this point onward, this configuration guide will continue presuming genkernel-next has been selected, since it is marked stable in the Portage tree and is essentially a drop in replacement for normal genkernel. Instructions for Dracut will be provided, although they are far from a full configuration.
Continue by enabling the
plymouth USE flag in /etc/portage/package.use in order for Portage to emerge genkernel-next properly:
echo "sys-kernel/genkernel-next plymouth" >> /etc/portage/package.use
emerge --ask sys-kernel/genkernel-next
Use a text editor of choice to enable Plymouth and the Plymouth theme in genkernel-next's configuration file:
# Enable splashutils in early space (initrd). Default is "no". # SPLASH="no" # Installs (or not if set to "no") Plymouth into the initramfs. If "splash" will be # passed to GRUB_CMDLINE_LINUX_DEFAULT at boot Plymouth will be activated. PLYMOUTH="yes" # Embeds the given Plymouth theme into the initramfs. PLYMOUTH_THEME="solar"
The SPLASH variable listed in the file above should be set to "no". The SPLASH variable configures an option for the fbsplash bootsplash loader (media-gfx/splashutils) NOT Plymouth.
Then use genkernel-next to generate the initramfs (note that Plymouth requires udev):
genkernel --udev initramfs
When using genkernel-next, skip the Dracut section, that immediately follows this section.
Dracut (sys-kernel/dracut) is an alternative initramfs generator created by the Fedora development team. Before reading the rest of Dracut guide, here is a fun fact: both Plymouth and Dracut are cities in Massachusetts. This is speculation. However, it would appear, the creators of these programs might have taken this into consideration.
Follow this link for Dracut installation instructions. Dracut should enable Plymouth automatically if it is installed.
Manual initramfs creation
When creating a manual initramfs, for example using Custom_Initramfs, it is possible to bundle Plymouth.
udev USE flag for Plymouth (it will not display anything until udev is properly initialized). Otherwise udev will need to be added to the initramfs as well.
echo "sys-boot/plymouth -udev" >> /etc/portage/package.use
emerge --ask sys-boot/plymouth
Then, populate the initramfs with the plymouth files and theme. While it may be done manually, the better way is utilizing /usr/libexec/plymouth/plymouth-populate-initrd. It will deliver all the binaries, config and themes needed (only the theme that is enabled, so do not forget to re-execute when changing theme).
The script will copy all the files to selected directory.
Add this code snippet to the initramfs generation script, just before the initramfs packing:
.... # populate plymouth if available if [ -x /usr/libexec/plymouth/plymouth-populate-initrd ] then /usr/libexec/plymouth/plymouth-populate-initrd -t $INITRAM_DIR fi ....
Finally, update the actual init script in initramfs:
.... # Plymouth needs /dev/pts mounted mount -t devtmpfs none /dev mkdir /dev/pts mount -t devpts /dev/pts /dev/pts .... # early in the process start plymouthd and show splash if [[ -x /usr/sbin/plymouthd -a -x /usr/bin/plymouth ]] then mkdir -p /run/plymouth /usr/sbin/plymouthd --attach-to-session --pid-file /run/plymouth/pid --mode=boot /usr/bin/plymouth show-splash fi ....
Plymouth automatically registers itself with systemd to show splash screens during shutdown and restart. No additional configuration is required.
There is a plugin for Plymouth that extends a single line version of OpenRC's status to the framebuffer. It can be installed via:
emerge --ask sys-boot/plymouth-openrc-plugin
No additional configuration for the plugin is necessary, it should be operational next time Plymouth is ran. To remove this functionality simply uninstall the plugin.
Additionally, make sure that the RC is non-interactive. Edit the /etc/rc.conf file:
When using GRUB2, an update to GRUB2's configuration file must be made in order to enable the splash screen during early boot. Append the options
quiet splash to the GRUB_CMDLINE_LINUX_DEFAULT variable. You might also want to adjust the resolution in the GRUB_GFXMODE variable to match the desired resolution for the monitor, and set GRUB_GFXPAYLOAD_LINUX to "keep" in order to preserve the graphics mode during the entire boot.
This all can be performed by modifying the /etc/default/grub configuration file:
GRUB_CMDLINE_LINUX_DEFAULT='quiet splash' GRUB_GFXMODE=1366x768x24 GRUB_GFXPAYLOAD_LINUX=keep
After emerging Plymouth a number of themes will be pulled in automatically, however more Plymouth themes can be downloaded from the web and installed manually. Extract the downloaded themes to the Plymouth theme directory: /usr/share/plymouth/themes
Make sure each new theme is contained in its own folder (just like the default themes that are installed) or they will not be detected by Plymouth.
Once the themes have been extracted verify successful extraction by requesting Plymouth to generate a list of all available themes. Do this using the plymouth-set-default-theme command:
Assuming the solar theme is desired as the system's theme, run:
The solar theme will be used for the rest of the examples in this article. Simply replace
solaranywhere it appears with one of the other themes listed when using the plymouth-set-default-theme command to set a different theme.
When using OpenRC with genkernel, the theme will also need to be referenced in genkernel-next's configuration file. This is outlined in the Genkernel-Next configuration section above.
It is possible to create themes for Plymouth. See the Theme creation article for more information.
Regenerate the initramfs using the genkernel or dracut command, depending on which generator you've chosen earlier:
As long as the configuration has been performed properly, this will pack the selected Plymouth theme into the initramfs.
Then regenerate GRUB config to use the initramfs and apply your GRUB2 graphical settings:
grub-mkconfig -o /boot/grub/grub.cfg
For Plymouth to work as intended the proper GRUB2 video modules must also be loaded. Generally the correct video modules are loaded by default on Gentoo, so inserting additional ones is not usually needed. If frame buffer or video problems are being experienced with GRUB2, be sure to investigate missing modules as a possible culprit.
According to the README file distributed with Plymouth, boot messages are dumped to /var/log/boot.log after the root filesystem has been mounted read-write.
- Fbsplash — a Gentoo implementation of a bootsplash screen to provide some eye candy during boot up, shut down or while working on a terminal without X.