Arch Linux

no, it gets included automatically by /etc/rc.d/functions

@hicham.haouari, i don't know if your problem caused by enable gdm transition. actually you don't need to do any thing. because it will load everything in /etc/rc.d/functions.d/ automaticly.

should i include plymouth.functions in rc.shutdown ?

@jarryson: The problem isn't theme-specific. It's that no (or empty?) messages are passed to the display_message function of the splash/theme plugin when booting up, so it doesn't show any, whereas it does when shutting the computer down.

just posted a howto on the forum : http://bbs.archlinux.org/viewtopic.php?pid=685134#p685134

however, i still can't figure out howto activate it on shutdown

@hicham.haouari: would you please post a howto or something in the forum so other's could know how to do that.

plymouth should be launched at shutdown, see "plymouth.functions"

plymouth isn't launched at shutdown, should i add sthg to /etc/rc.shutdown ?

for gdm transition to work, the following item must be patched :
- gdm
- xorg
- the graphics driver (intel,radeon, nouveau)

I tested the patches on my machine and it is working great

@grubber, you can change a theme. Because partition is not writable when plymouth actived, so there is no way to do that for now.

if you have any suggestion for that, plz let me know.

Boot messages don't show up for me. Shutdown messages work fine. Anyone else got this problem?

Also, isn't there a way to log the messages somewhere? (/var/log/boot.log?)

now offical libdrm removed the support of random drm, you must compile libdrm your self.

I couldn't compile the package. Here is what i got:

...
...
...
checking for PANGO... yes
checking for GTK... yes
checking for DRM... configure: error: Package requirements (libdrm libdrm_intel libdrm_radeon libdrm_nouveau) were not met:

No package 'libdrm_radeon' found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables DRM_CFLAGS
and DRM_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.

make: *** No targets specified and no makefile found. Stop.
==> ERROR: Build Failed.
Aborting...

My libdrm version is: 2.4.17-2

@jithin1987:

It is intentional, because it's a -git build

The plymouth-git installed version is the current date and not the version specified here.
plymouth-git: (local=20091207-1 aur=20091202-1)

Is this intentional?

What does it depend on in base-devel for runtime? Note that base-devel is not required to be listed for makedepends.

add depend: base-devel

FOR AIT USERS: not recommoned to upgrade to kernel 2.6.32, I couldn't find a way to get KMS and plymouth work fine together.

SEE: http://bbs.archlinux.org/viewtopic.php?id=86211

Arch never uses anything but /usr/lib, so there's no point in checking.

update! works again!

thanks, daenyth. i make some of the changes, but not all of them.

why must remove the "if [ -z "$LIB" ]" case?

I don't think default.so needs to be removed any more.

You should patch the file while it's in srcdir too..

You can replace the failing plymouth-set-default-theme.patch with this: http://omploader.org/vMndiaw

There should be an "|| return 1" bit with the patch lines in case they fail.

with the new changes from earlier today trunk works fine for me again.

yes, this patch is no longer work, so i disabled it.

it just prevent to create the log viewer. seems no big deal.

Might this have something to do with the changes made to "plymouth-set-default-theme"? "plymouth-set-default-theme.patch" is no longer correct (see http://cgit.freedesktop.org/plymouth/commit/?id=8e70c530ea2937ac5a621e7974e35554108f2e2b). (I also think the no-gtk patch is no longer working, either.)

you can also use git checkout to get a specific commit:

_git_wanted_commit='d63a2aec8d3d155b6eaf664114c77c126ddbce9e'
git checkout $_git_wanted_commit

however:
1. If you do this you won't be on a branch anymore. You have to checkout back to master before you can pull updates:
git checkout master
git pull

2. It works only if you have the "history"(or however it's called) for that commit. If you used depth=1 on the initial checkout it won't work.

https://bugs.freedesktop.org/ is the place to file bugs according to http://www.freedesktop.org/wiki/Software/Plymouth

see also http://stackoverflow.com/questions/1526670/git-better-way-for-git-revert-without-additional-reverted-commit

it is possible to checkout and then revert to desired revision, see http://www.gitready.com/intermediate/2009/03/16/rolling-back-changes-with-revert.html .
As far as I understood, you can use 'git revert HEAD~1 -n -m 1' to revert the newest commit, 'git revert HEAD~1 -n -m 2' for others. We could also post a ticket to bugzilla/trac/smth else if we knew the address.

@boris.inetss: i don't think makepkg can hold an git version.

anyone knows how to fallback to a commit?

jarryson, can you fix the revision number, which works? As far as I know this http://cgit.freedesktop.org/plymouth/commit/?id=d63a2aec8d3d155b6eaf664114c77c126ddbce9e was working correctly.

It shows a black rectangular box at the top left corner of the screen. I cannot confirm why this is happening but when I rebuild initrd removing plymouth hook things become fine [obviously plymouth doesn' work.].

it's not working well recently. and i have no idea to solve it for now.

It does indeed work now. Thank you :)

i got the same error. i know why now. it caused by plymouth-no-gtk.patch. just disable the patch it would be fine.

i ll update PKGBUILD later

I left the pkgbuild at default settings, --without-default-plugin. However, I just tried it with --with-default-plugin and had the same error.

by default it compile with "--with-default-plugin" in this PKGBUILD, have you enabled that parameter?

Frustrating. It fails to build for me at the moment. I'm using libdrm-newest with what you posted below, and xf86-video-intel-newest. However, iirc, the downgraded ones also do the same thing.

Relevant section:

./plugin.c:371: error: 'ply_renderer_head_t' has no member named 'pixmap'
./plugin.c: At top level:
./plugin.c:418: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'on_motion_notify_event'
./plugin.c:430: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'on_key_event'
make[5]: *** [x11_la-plugin.lo] Error 1

Ideas?

http://cgit.freedesktop.org/plymouth/commit/?id=08466deaf8203ddff508d492056d2e9f705724e9

Possibly related to that git entry. Reversing the patch didn't seem to help (only 80% sure I did it properly though :D). I give up for now.

Edit: Combined posts.

it's ok to use libdrm-newest. just need add "--enable-radeon-experimental-api --enable-nouveau-experimental-api" just as arch offical did and then recompile libdrm-newest.

infact i don't know why it checks such dependences. it can't use both radeon and nouveau drm modules.

it's work,but:
- for properly shutdown i turn on gdm-transition in .pkgbuild (btw i use gdm).
- it doesn't want to confirure i had to downgrade libdrm from libdrm-newest to 2.4.13 (simon says: no package found - libdrm-radeon, libdrm-nevouwe:D), so my video-intel-newest doesn't want to work anymore.
but still it's the first time when plymouth work for me.
god bless you man.

yes, of course. At lease work fine here with ATI cards with KMS. don't forget follow the information after installion.

does it work now?

adopted..and update the package

@PirateJonno: ok, if you don't really need it, i 'll try to maintain it. ;)

jarryson: plymouth still isn't working for me, and I don't really need it since fbsplash works fine now and I have an nvidia card. Do you want to become maintainer of this package?

i modified a little, fix some issue in the PKGBUILD. thanks PirateJonno and drf's PKGBUILD.

http://archlive-pkg.googlecode.com/files/plymouth-git.tar.gz

shutdown can directly go into plymouth without display default information. (plymouth.function)

use --libexecdir=/usr/lib to change /usr/libexec to /usr/lib/plymouth

change a better logo and background color..

Hello, please check: http://bbs.archlinux.org/viewtopic.php?id=81406 . With some modifications to the hooks/install, plymouth will also work for graphical mode

ok, thank. i'll try it tomorrow

Hi Ophys. No problem, I just wish I could get it to work better. If by kernel image you mean the initcpio then yes, plymouth does need that to work. However, if you have some way of starting things without a kernel image, the *-initcpio files should list everything that needs to be available to the kernel and the commands you should use to start plymouth. I'll assume that if you know enough to run without a kernel image you'll be able to decipher these two files, but if not feel free to ask.

Hi! thanks you for this package. i installed it, no error while compilation, but now it doesn't work. no errors, kernel panic, it's just like i didn't installed it. i don't use kernel image, it's necessary to run plymouth?
sorry for my bad english.

Hi onestep_ua
Right back at you for packagekit :). If you want to debug it you can edit the /lib/initcpio/hooks/plymouth file and add the --debug option to plymouthd. There are also numerous times the client (/bin/plymouth) is run in /etc/rc.d/functions.d/plymouth but it's probably not worth the effort as any errors will most likely happen in the daemon. At the moment the main bug, which stops plymouth when the runlevel changes to your usual one (3 or 5), seems to be in sysvinit itself, which you can check by pinging the daemon (from /bin/plymouth) at the end of /etc/rc.sysinit and the start of /etc/rc.multi. I suspect the problem is that init isn't aware of plymouthd as it starts before sysvinit itself, but remains a child process of it, but I don't really know enough unix system programming to fully understand the sysvinit source. Thanks for your help :)
PS. I haven't actually used this for a while, but the 0.7.0 release seems to fail spectacularly. Are you seeing any progress bar at all in text mode?

Hi!

First of all thank you for maintaining that piece of software - it seems that it's not so easy. :) I'd like to help you in this - I know some C and have experience in bash scripting, but I just cant figure out where to start - there are no logs, all I see is "could not log bootup" message when my system starts. Can you tell me how you debug it?.. :)

it only vaguely works atm. the post-install message explains how to configure it, but I don't suggest using it unless you know some C or bash and want to figure out whats wrong with it

can this work in arch?how to config?

no

is this working already?

looks like the new release isn't going to work too well. However while packaging it I noticed that the framebuffer devices on arch have been moved by the recent udev update, which I have fixed for this package. also added /etc/system-release just to be safe

0.7.0 has been released. I'll try it out and package soon if possible

added libtool to makedepends. thanks :)

I think libtool needs to be added to the dependencies - otherwise compile fails with:

configure.ac:17: warning: macro `AM_PROG_LIBTOOL' not found in library
configure.ac:17: error: possibly undefined macro: AM_PROG_LIBTOOL
If this token and others are legitimate, please use m4_pattern_allow.
See the Autoconf documentation.

Thanks! :)

thanks for the heads-up :). I'm not too fussed about trying it out at this stage, as the problem with klibc was fairly small anyway. However I will adjust the initcpio hook and anything else that may need changing when uclibc (and busybox?) move into core.

uclibc is now available in the testing repo

Hi flamelab. Eventually the boot messages will be surpressed but I've disabled that as it is basically too hard at the moment. Once Arch makes the switch to uclibc I will try and sort it out.

More importantly, does your bar stop when you enter runlevel 3 or 5? Because that's the major bug I've been trying to fix.

Plymouth worked here, but the boot messages were appearing behind the bar, and that was some kind of a mess, but it worked :p

no, 0.7 isn't out yet. I just updated the dependencies, the package is still broken

"
Comment by: PirateJonno on Fri, 10 Jul 2009 10:36:10 +0000

all fixed.
"
for vers 0.7?

all fixed.

Depends on fakeroot, autoconf, and automake to build.

I've just tried doing the stuff the Chakra project has done but it didn't make it past the runlevel change. So I guess it's either a bug in something extra in this package or something to do with the newer plymouth from git. I'd try with 0.6.0 but it doesn't have a shutdown splash and 0.7.0 should be out soon. Unless Chakra uses a different init system to Arch... has anyone here ever tried it?

any updates on this?

ok, wait for you good news, thanks very much.

if you're prepared to wait a bit i'll look into it. I've got exams at the moment though so it's not a priority for me atm

any one tried that?

i don't know how to use.

looks the the Chakra project beat me to it:
http://chakra-project.org/code/index.php/browse/tools:/plymouth/
haven't tested it yet but apparently it works

@jarryson: yeah, everyone else has that problem as well. read below for more details. No, the new klibc is no longer needed.

Note that now without klibc-plymouth the text plugins will look all messed up, but at least they don't lock up the system. The graphical plugins look fine but do lock it up. I'm working on it, hopefully I may find a way to fix it

it works now, and no kernel panic anymore, but i still can't switch to tty1 or tty7

i have already add plymouth to rc.conf and set runlevel to 3.

but plymouth do work, i can see the process bar and the keyboard isn't dead, if i press alt + ctrl + del, it will success reboot.

is it because i did't replace the klibc?

Uploaded a new package that removes the klibc-plymouth dependency, because it seems to be causing some issues. I've added a help message post-install which is more complete than comments here. Also, it turns out GDM has to be patched for a smooth transition to occur so I've removed support for that for now.

yes at the moment plymouth will die when your runlevel changes to 3/5
the plymouth daemon script should make it quit, add it to your rc.conf
I wouldn't do anything else before the runlevel issue is fixed, but the plymouth mailing list and ubuntu forums have some theme info I think. you might be better off just working from the examples if you know C though. be aware that graphical themes are dangerous atm because of the runlevel crash.

yes, now it works for me.
But I see it only for 10 seconds,
Before init and after the rc.sysinit it switches to the terminal, with "ply_client --quit --retain-splash
ply_client --wait" Without it, plymouth doesn't exit

How can i create my own plymouth-theme?

ok, it looks like those ugly things are SHA1 hashes of libc.so, so i'm not going to be able to fix it properly. I could do a workaround to just put klibc-Zh0XrRHYDWcJswHOxmN71_z1whQ in provides directly, but i'm not sure thats a good idea. what do you think?

I just looked at my klibc-extras and it says the same thing (klibc-Zh0XrRHYDWcJswHOxmN71_z1whQ)
looks like 'UqSadMgryalzKq_XarP9XnQvbXQ' is something generated in the PKGBUILD.
I'll look into it but for now I'd suggest you go back to stock klibc and remove the mount command and --attach-to-session option from /lib/initcpio/hooks/plymouth, then regenerate your initcpio.

http://pastebin.com/m1a2a3c23

ouch. I'm not too sure what any of that means short of a corrupt disk or something. what happens when you do 'pacman -Qi klibc-extras' and 'pacman -Qi klibc-plymouth'?

yes ,
HOOKS="base udev autodetect pata scsi sata filesystems plymouth"

I built plymouth-git again and there was an error message:
missing dependency for klibc-extras : klibc-Zh0XrRHYDWcJswHOxmN71_z1whQ
missing dependency for klibc-kbd : klibc-Zh0XrRHYDWcJswHOxmN71_z1whQ
missing dependency for klibc-module-init-tools : klibc-Zh0XrRHYDWcJswHOxmN71_z1whQ
missing dependency for klibc-udev : klibc-Zh0XrRHYDWcJswHOxmN71_z1whQ
missing dependency for mkinitcpio : klibc>=1.5.15-2

ok, well does HOOKS in /etc/mkinitcpio.conf start with "base"? because the base install file should add everything in /usr/lib/klibc/bin/ to your initcpio. you could also gunzip/uncpio the image to check if /bin/replace exists

/usr/lib/klibc/bin/replace
exists in my filesystem

kbblak: looks like your klibc-plymouth did not build properly as replace should be in your initcpio.
check to see if '/usr/lib/klibc/bin/replace' exists on your filesystem

the building of plymouth worked fine for me.
But at the boot I get a kernel panic:

...
Loading initramfs
init: 36: replace: not found
init: 36: replace: not found
Kernel panic - not syncing: Attemped to kill init!

I replaced klibc with klibc plymouth

@PirateJonno, thx for reply, i am using rc8 because i need KMS for ATI cards, and only in airlied's git kernel repo have this. is it one reason why i met kernel panic? but seems fedora support plymouth with ATI KMS. i'll try it without the klibc-plymouth later.

sorry for my english.

Also, I forgot to say that you should remove the mount command from /lib/initcpio/hooks/plymouth (if you want to use the default klibc). Hopefully we'll be able to merge the plymouth patch into the default klibc in the future (it's pretty small), but I want to hold off on this for now because there's no point in doing so until plymouth works properly

@jarryson: you can use the default klibc if you remove the --attach-to-session option from /lib/initcpio/hooks/plymouth. This may be another issue with your particular setup though, I'm not sure. Is there a reason you're using the rc8 kernel? The 2.6.29 kernel has been released.

@devildante: thanks for your help. I thought ubuntu was using upstart rather than sysvinit (i'm not sure though). maybe they have something similar anyway

@jarryson: Plymouth *is* working with KMS on Arch, I'm using it :)

@PirateJonno: Yeah, that should be it. I'll look into the init patches from Ubuntu for this.

and i even don't know how to see any output or log why plymouth can't work and kernel panic.

i am using 2.6.29 rc8 with ATI KMS. when i enable plymouth, i always met kernel panic, no matter which klibc i use.

of course i mkinitcpio again and again.

with klibc-plymouth, i met kernel panic with something like "replace commond can't find"

with klibc in repo, i rebuild plymouth-git, and then i can see the background change, but the keyboard light keep flashing, so i know kernel panic again.

was it because plymouth can't work with KMS in arch?

Thanks for that devildante. Just thought I'd add that at the moment I suspect the crash is happening because /sbin/plymouthd is started before /sbin/init but is effectively a child process as it was started by /lib/initcpio/init (which both have PID 1). This might mean that /sbin/init somehow interferes with plymouthd as an unrecognised child process when the runlevels change. If this is the case we'd need to either patch init or somehow detach the plymouth daemon from the init process. Someone else might be better aware of how to do this than I am.

Good news: I've found a (temporary) solution for stopping the runlevel crash :)
You just edit /etc/rc.sysinit and add the following lines:
"ply_client --quit --retain-splash
ply_client --wait"
This stops Plymouth before the runlevel switch. One inconvenient is that there is some text messages from init and /etc/rc.multi that appear, thus not allowing for a text-free boot.

haha thanks DonGiovanni. I guess I'll hold on to it for a while longer...
I still need some help to figure out whats going on at the runlevel switch, I may post to the mailing list tomorrow.

I oprphan this package, because PirateJonno seems still to be involved! He brought this package up...

no problem Memphyx, hope it works for you

Thanks for the advice Piratejonno ... I will try here!

Memphyx, yes I know, this is a problem with the package at the moment, as damoxc pointed out.
I've gone ahead and patched klibc to allow /dev/pts to be mounted (http://aur.archlinux.org/packages.php?ID=26679), which means that the text theme will work and the boot messages will be hidden. However this doesn't solve the crash at runlevel 3/5 and also requires you to actually have the folder /dev/pts on your root filesystem. I added it by firing up my arch install cd, mounting my root partition and creating it there. I'm not sure if there's an easier way to do this as udev takes over /dev before (I think) the root fs is mounted read/write.
Here is a new package that fixes the aforementioned issues and adds in /dev/pts support. If you don't want to patch klibc, just remove the --attach-to-session option from plymouthd in hook-plymouth-initcpio and comment out the mount line in install-plymouth-initcpio. Also remove the dependency on klibc-plymouth from the PKGBUILD.
here is the updated package: (http://rapidshare.com/files/236184945/plymouth-git-20090523-1.src.tar.gz.html). I strongly advise you to use the text theme for now.
PS. This is getting quite dangerous so please don't use this package unless you know what you are doing and want to fix the runlevel crash.

Hello

Then compile it to check my file /etc/makepkg.conf, even more so, still do not know where to apply the patch. What procedure take me to face the screen below?


Grateful for any help:

can't find file to patch at input line 3
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- usr/sbin/plymouth-set-default-plugin.orig 2009-04-30 22:32:34.097235695 +1200
|+++ usr/sbin/plymouth-set-default-plugin 2009-04-30 22:21:11.613970231 +1200
--------------------------
File to patch:

oops, looks like i need to update the initcpio install script as well. I'll put up a new package soon

Ok I've prepared a new tarball at http://rapidshare.com/files/236145444/plymouth-git-20090523-1.src.tar.gz.html
it now creates a plymouth-build folder as per the Arch git PKGBUILD guidelines, and to set the default plugin you should now use /usr/sbin/plymouth-set-default-theme

There's been some updates to plymouth's git which now breaks this package.

the framebuffer script looks like all it does is create the /dev/fbx devices
http://pastebin.com/f6173e748

and it looks like console-setup merely sets the console font, keyboard map and creates the ttys.
http://pastebin.com/f71214831

ok so looks like kms needs no further input in this package, and that ubuntu script doesn't seem to be doing anything extra except for keyboard support. again maybe someone wants to try adding the /dev/ttys to the initcpio, and it might pay to look at the ubuntu 'framebuffer' and 'console_setup' init scripts that are listed as prerequisites. i don't have a copy on hand so i'm not sure whether they contain anything important or not

http://bazaar.launchpad.net/~marceloshima/plymouth/ubuntu/annotate/head%3A/debian/initramfs-tools/scripts/local-top/plymouth

That's the Ubuntu initrd script btw.

http://bbs.archlinux.org/viewtopic.php?id=69083 explains how to enable the kms driver in initrd on the stock kernel.

Also, just to clarify my update the other day did change a few typos in the scripts and i made the logo a white 'arch' instead of black because it looks better on solar. the INSTALL file also said something about kms drivers, so if you have an intel card you might like to check that out

That gentoo thing was just some guy in the mailing list trying to compile it himself, so I don't think there's a package of it yet. Reading through that yeah you might be right, it might help to add /dev/tty[01] to the install file but as far as i remember, doing that made no difference for me. the 'init' script in initcpio doesn't really do much at all, its kinit that seems to be causing the issues with /dev/pts and by the time the runlevel changes the initcpio is long gone. Feel free to fiddle around yourself though.

:)
Yeah, it seemed problematic when I played with it. I wonder: are you doing everything with the hooks? I was pretty sure I would have to change the 'init' script in the mkinitcpio package for the thing to work right. But maybe you are already far beyond that point...
Also, in the "INSTALL" file there is a description of how to work plymouth, targetted towards gentoo. I don't know, maybe there is a gentoo package now that one could learn from.

out of date? lol this isn't even release-quality yet :P. Anyway I've pretty much given up on getting this to work. Somehow plymouthd stops functioning after rc.sysinit and before rc.multi, and I have no idea why. The process is still running but maybe it hangs or something due to the runlevel change. I've prepared a patch for klibc which might allow message logging (from plymouthd --attach-to-session) to work (http://pastebin.com/m9780f6), but I haven't tested it yet and I'm too scared to patch my own kinit. the patch is for runinitlib.c which is part of kinit. A few other things todo include adding shutdown splash support and doing something better on a stat_fail, as well as encrypted volume support. I tried getting it to run on tty8 but the system messages moved to so that didn't help. I'll keep watching this package if anyone has any questions

You mean the phenix-test-plugin.sh? That's just for testing I think. I've been using a similar script to test which does a chvt 1 instead of 8 and it works fine. That's not to say that starting on vc/8 isn't a good idea, I'm just not sure how to do it. I'll do some more testing when I get the chance. Thanks by the way for your input :)

The only reference I can find about vt/8 is here:
http://ubuntuforums.org/showpost.php?p=6892088&postcount=83

Take a look at the phenix.sh script. Dunno - that script never worked for me :D

ok I looked at the ubuntu ppa but couldn't find any reference to vc/8. Can anyone clue me in as to how to get it to do this? I think maybe console=tty8 in the kernel command line would do it but won't that move the boot messages as well?

I'm pretty sure all the GDM transition does is create a file that supposedly tells GDM to start on tty1 instead of 7 but so far I haven't seen this working. Turns out the crash is due to init itself so I'll have a poke around in the source and see what I can work out. Yes putting it on tty8 would be a good idea but im not sure if this would allow the smooth GDM transition to happen at all. I'll give it a try though, I don't even have kernel modesetting on my card so it doesn't matter to me anyway :P

Looking at the ubuntu scripts it seems like it should be put on vc/8, but I'm not 100% on that, just incase it's of any use.

Ah, I didn't see that about the functions. Doh.
Too bad it is showing all these difficulties. About the GDM thing: I would guess it depends on it if you compile the gdm transition...but I am not sure either :D

Hi Blind. You can stop the crash by using a text plugin, but this makes the boot messages all screwy. Sorry if I wasn't more clear about that. I don't think its actually a crash but probably more that the splash takes over input/output on vc/1 and then hangs at the daemons. The functions script is sourced automatically in /etc/rc.d/functions. Also I should add that this may depend on GTK and GDM but I can't be sure.

Build worked for me.
However, I get a complete crash at the daemons.
You don't source /etc/rc.d/functions.d/plymouth in the /etc/rc.d/plymouth daemon starter.
I hope that you will be able to fix the bugs...good luck, anyhow.

Hi. Sorry that it didn't work for you, for whatever reason. I just downloaded the tarball and tried to compile with makepkg and it worked fine for me. Can you look at config.log because it seems that will tell you what the first configure error was. I'm pretty sure the -p option is correct, did the package create the file plymouth-git/pkg/usr/sbin/plymouth-set-default-plugin? I haven't really figured out the dependencies yet so make sure you have all the autotools, intltool, autoconf etc installed.

have to manually compile and the first attempt, I was presented this error:

From git: / / git.freedesktop.org / git / plymouth
* Branch master -> FETCH_HEAD
Already up-to-date.
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, `build-tools'.
libtoolize: linking file `build-tools/ltmain.sh '
libtoolize: Consider adding `AC_CONFIG_MACRO_DIR ([m4]) 'to configure.ac and
libtoolize: rerunning libtoolize, to keep the correct libtool macros in-tree.
libtoolize: Consider adding `-I m4 'to ACLOCAL_AMFLAGS in Makefile.am.
configure.ac: 9: installing `build-tools/compile '
configure.ac: 17: installing `build-tools/config.guess'
configure.ac: 17: installing `build-tools/config.sub '
configure.ac: 13: installing `build-tools/install-sh '
configure.ac: 13: installing `build-tools/missing '
src / Makefile.am: installing `build-tools/depcomp '
checking for gcc ... gcc
checking for C compiler default output file name ...
configure: error: in `/ tmp / yaourt-tmp-Jeferson / git-aur-plymouth / plymouth-git / src / plymouth ':
configure: error: C compiler can not create executables
See `config.log 'for more details.
make: *** No targets specified and no make file found. Stop.
==> ERROR: Build Failed.
Aborting ...
Error: Makepkg was unable to build plymouth-git package.

comm: file 1 is not in sorted order

On Monday, this after having to manually compile and try the makepkg:
make [2]: Leaving directory `/ home / Jeferson / Desktop / plymouth-git / src / plymouth / scripts'
make [1]: Leaving directory `/ home / Jeferson / Desktop / plymouth-git / src / plymouth / scripts'
make [1]: Entering directory `in / home / Jeferson / Desktop / plymouth-git / src / plymouth '
make [2]: Entering directory `in / home / Jeferson / Desktop / plymouth-git / src / plymouth '
make [2]: Nothing to be done for `install-exec-am '.
make [2]: Nothing to be done for `install-data-am '.
make [2]: Leaving directory `/ home / Jeferson / Desktop / plymouth-git / src / plymouth '
make [1]: Leaving directory `/ home / Jeferson / Desktop / plymouth-git / src / plymouth '
can not find file to patch at input line 3
Perhaps you used the wrong-p or - strip option?
The text leading up to this was:
--------------------------
| --- Usr / sbin / plymouth-set-default-plugin.orig 2009-04-30 22:32:34.097235695 +1200
| + + + Usr / sbin / plymouth-set-default-plugin 2009-04-30 22:21:11.613970231 +1200
--------------------------
File to patch:

Some instructions to get this to run:
1) install it
2) add plymouth to HOOKS in /etc/mkinitcpio.conf
3) update your initcpio
4) add 'splash' to your kernel command line, along with (probably) vga=0x318
To change the theme run plymouth-set-default-theme as root and update initcpio

This package is NOT READY YET, I only put it up here in case people want to test it out. Feel free to try it but be aware that only graphical plugins work at the moment, logging support is disabled and something causes it to fail when the daemons are started.