Talk:Plymouth

AGP module not loaded before graphics module when using plymouth hook

I was getting a "[drm:radeon_agp_init [radeon]] *ERROR* unable to acquire AGP: -19" error at boot, after "starting version 219" and before plymouth took over the screen when following the instructions. E.g. hooks="base udev plymouth ...", despite having modules="via_agp radeon ...".

Not sure if it's a problem with the current plymouth hook but I removed it from mkinitcpio.conf, rebuilt initramfs and the error goes away -and- I still have plymouth on boot. --Kit (talk) 21:13, 21 May 2015 (UTC)

ShowDelay=5

/etc/plymouth/plymouthd.conf
[Daemon]
Theme=spinner
ShowDelay=0 

delay 5 is for a long time kde

—This unsigned comment is by Rzax666 (talk) 03:23, 2 November 2018‎. Please sign your posts with ~~~~!

The cryptdevice kernel parameter does work?

The wiki currently states that:

Warning:

• Using PARTUUID or PARTLABEL in cryptdevice= parameter does not work with plymouth-encrypt hook.

However, my encrypted system boots with:

   options	"cryptdevice=UUID=deadbeef-dead-beef-dead-deadbeefbeef lvm root=/dev/mapper/foobar rw add_efi_memmap quiet loglevel=3 rd.udev.log_priority=3 vt.global_cursor_default=0 splash acpi_osi=""!Windows 2015"" initrd=\EFI\arch\intel-ucode.img initrd=\EFI\arch\initramfs-linux.img"

This implies that it does work

Shoaloak (talk) 20:44, 17 June 2020 (UTC)

No, UUID is not the same thing as PARTUUID. See Persistent block device naming. -- Lahwaacz (talk) 20:52, 17 June 2020 (UTC)