Plymouth primarily uses KMS (Kernel Mode Setting) to display graphics. If you can’t use KMS (e.g. because you are using a proprietary driver) you will need to use framebuffer instead. In EFI/UEFI systems, plymouth can utilize the EFI framebuffer, otherwise Uvesafb is recommended as it can function with widescreen resolutions. If you have neither KMS nor a framebuffer, Plymouth will fall back to text-mode.
su pacman -Syu pacman -S plymouth plymouth-theme-condres
Add i915 or nvidia or nouveau or radeon
nano /etc/mkinitcpio.conf
MODULES="i915"
plymouth-set-default-theme -R condres
Add Plymouth to hooks array in mkinitcpio.conf. It must be added, after udev autodetect to make it work.
nano /etc/mkinitcpio.conf
Add Plymouth to hooks array:
HOOKS="base udev plymouth autodetect ..."
Rebuilding the kernel image:
mkinitcpio -p linux
Grub now needs to work with the Plymouth configuration:
nano /etc/default/grub
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash resume=UUID=xxxxxxx"
grub-mkconfig -o /boot/grub/grub.cfg
Finally, the Plymouth demon must be “killed” at the end of the boot process. This can be done with a rc.local command:
nano /etc/rc.local
/bin/plymouth quit --retain-splash
Change the systemd service for graphical login
systemctl disable gdm systemctl enable gdm-plymouth.service or systemctl disable sddm systemctl enable sddm-plymouth.service or systemctl disable lightdm systemctl enable lightdm-plymouth.service
reboot and enjoy plymouth Condres OS
