If by “boot” you mean a separate boot partition, it is not the case here.
You have an unencrypted ESP mounted at /efi where the bootmanager and the kernel images reside.
Installation
Plymouth is available with the stable package plymouth. For the development version, use plymouth-gitAUR.
By default, Plymouth logs the boot messages into
/var/log/boot.log
, and does not show the graphical splash screen.
- If you want to see the splash screen, append
splash
to the [kernel parameters](https://wiki.archlinux.org/title/Kernel_parameters).- If you want silent boot, append
quiet
too.- If you want to disable the logging, append
plymouth.nolog
.To start Plymouth on early boot, you must configure your initramfs generator to create images including Plymouth.
mkinitcpio
Add
plymouth
to theHOOKS
array in mkinitcpio.conf./etc/mkinitcpio.conf
HOOKS=(… plymouth …)
dracut
After installing Plymouth, dracut will automatically detect it and add it to your initramfs images. If autodetection fails, you can force dracut to include Plymouth by adding the following line to your dracut configuration:
/etc/dracut.conf.d/myflags.conf
add_dracutmodules+=" plymouth "
Then regenerate your initrds.