Package Details: plymouth-git 0.9.5.r84.ge554475-4

Git Clone URL: (read-only, click to copy)
Package Base: plymouth-git
Description: A graphical boot splash screen with kernel mode-setting support (Development version)
Upstream URL:
Licenses: GPL
Conflicts: plymouth, plymouth-legacy, plymouth-nosystemd
Provides: plymouth
Submitter: PirateJonno
Maintainer: Taijian
Last Packager: Taijian
Votes: 256
Popularity: 2.30
First Submitted: 2009-05-02 09:53
Last Updated: 2021-06-29 08:25

Dependencies (8)

Required by (132)

Sources (14)

Latest Comments

1 2 3 4 5 6 ... Next › Last »

Taijian commented on 2021-07-09 11:26

@whynothugo: Could you post your complete HOOKS entry from mkinitcpio.conf?

Also: What does your disc layout look like and are you sure that your initramfs is not on an encrypted partition?

whynothugo commented on 2021-07-08 16:06

I'm using the systemd hook, and adding the sd-encrypt hook did not work for me.

When the system starts, I get prompted for the disk password and plymouth starts after that.

d_fajardo commented on 2021-07-02 06:12

Any update on this infinite loop / trailing 0's?

invidian commented on 2021-06-28 22:42

Once again the latest update is flagging an infinite update loop. Is there a fix?

Yep, evil trailing 0 strikes again :(

d_fajardo commented on 2021-06-28 17:11

Once again the latest update is flagging an infinite update loop. Is there a fix?

bdeshi commented on 2021-06-28 05:30

@Taijian I'm sorry but could you double-check that please? it works with plain encrypt hook too, without systemd-boot or systemd init hook.

how I checked:

  • # cryptsetup --persistent refresh /dev/sdXY -- removed any persistent flags
  • removed those flags from cryptdevice kernel command parameter too, and rebooted.
  • # dmsetup table -- confirmed no flags are present
  • added flags back, eg ... cryptdevice=UUID=<UUID>:<mapped_name>:allow-discards,no-read-workqueue,no-write-workqueue ...
  • regenerated bootloader config (grub) & initramfs, using plymouth-encrypt patched as my last comment.
  • rebooted and checked with # dmsetup table that all three flags were present.

Taijian commented on 2021-06-27 21:54

@bdeshi: The kernel command line parameters you are trying to use only work in a systemd-based boot setup. You need to switch out plymouth for sd-plymouth and encrypt for sd-encrypt (and a bunch of other hooks too - best have a look at the wiki).

bdeshi commented on 2021-06-27 20:28

hi, I've been using the no-*-workqueue options in cryptdevice param with cryptsetup's encrypt initcpio hook, but these echo warnings at boot with plymouth-encrypt. could you patch please? (copied from the default encrypt hook file)

diff --git a/usr/lib/initcpio/hooks/plymouth-encrypt b/-
index a623deb..0000000 100644
--- a/usr/lib/initcpio/hooks/plymouth-encrypt
+++ b/-
@@ -51,9 +51,15 @@ EOF

     for cryptopt in ${cryptoptions//,/ }; do
         case ${cryptopt} in
-            allow-discards)
+            allow-discards|discard)
                 cryptargs="${cryptargs} --allow-discards"
+            no-read-workqueue|perf-no_read_workqueue)
+                cryptargs="${cryptargs} --perf-no_read_workqueue"
+                ;;
+            no-write-workqueue|perf-no_read_workqueue)
+                cryptargs="${cryptargs} --perf-no_write_workqueue"
+                ;;
                 echo "Encryption option '${cryptopt}' not known, ignoring." >&2

KenFromBarbie commented on 2021-06-06 08:13

I have an infinite update loop where with every check it wants to update to the same version over and over again:

:: Searching AUR for updates...

:: 1 Packages to upgrade.

1 aur/plymouth-git 0.9.5.r84.ge554475-1 -> 0.9.5.r84.ge554475-3

x70b1 commented on 2021-05-08 14:06

@Taijian That works perfect. Thanks!