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:
- Using
PARTUUIDorPARTLABELincryptdevice=parameter does not work withplymouth-encrypthook.
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)
FlickerFreeBoot
Fedora had made some work on FilckerFreeBoot. Here are some usable url:
Let's we bring this to ArchLinux :)
—This unsigned comment is by Dragonwater (talk) 13:14, 10 May 2021 (UTC). Please sign your posts with ~~~~!
Now I can say, the command The kernel command line is too long, "quiet splash" just be needed for me.
And far, the command "video=efifb:nobgrt" can be used to hidden vendor logo Dragonwater (talk) 13:34, 10 May 2021 (UTC)
Plymouth is not necessary for flicker-free boot
It could be worth mentioning that Plymouth is not always necessary for a flicker free-boot.
Following the steps in Unified kernel image and setting bgrt_disable kernel parameter achieves the same result, as long as you don't have to enter any passphrase (no encryption, or disk decrypted with keyfile..). I didn't test it but it might even work when using an encrypted boot partition with Grub, since the password is entered before anything else is done.
-- Cvlc (talk) 00:06, 31 December 2021 (UTC)
"Secure Boot disabled" plymouth warning - available starting with GNOME 43
The plymouth developers are working on a warning that should be displayed during boot if Secure Boot is disabled (and especially if LUKS encryption is enabled and a password should be requested). Secure Boot and this warning should prevent keyloggers from getting the LUKS password. At the moment however, no warning will be shown, although the "Secure Boot warning" functionality is already included in the latest plymouth-gitAUR version 22.02.122. The Secure Boot warning functionality is disabled. This is because the plymouth developers are waiting until the "Secure Boot warning" functionality is also implemented in the future version 43 of gnome; as can be seen in the last comment of this merge request:
We were talking to @aday about this last week, we don't really want to enable the plymouth feature until the GDM feature is also confirmed; it'd be really confusing to just see the red icon in plymouth without the explanation of what it means in gdm too. - Richard Hughes @hughsie · 1 month ago
DasMenschy (talk) 15:03, 26 September 2022 (UTC)
Editing the plymouth-start unit
@Lahwaacz the rest of the tips are useful, but in this case, I'm not sure there's a way around editing that file, as the mkinitcpio hook needs to pull the unit into the initrd image. Kelvie (talk) 20:52, 27 December 2023 (UTC)
- Actually removed it for now, going to test it some more and maybe find a better way to do it (maybe modifying the hook) Kelvie (talk) 00:19, 28 December 2023 (UTC)