You are not logged in.
(Note: this is cross-posted from http://chakra-project.org/bbs/viewtopic.php?pid=9135 , thought some people here could be interested )
Yes guys, I managed to get plymouth working - and I mean for real, with the graphics candy included. Here come some easy steps for installing it on your machine. This procedure could change from time to time as I will try to make things run even smoother and easier for the end user. Also, Chakra will include Plymouth by default soon.
Before we start:
Be aware that to get the graphical boot screen you need to have KMS in early start. At the moment the only driver doing it right with just a few modifications is the intel one, however this is going to change soon. Look in the arch forums or wiki for more details on that.
So, are you ready? First things first:
git clone git://git.chakra-project.org/chakra/plymouth
This will download our PKGBUILD for plymouth. The plymouth you'll build is branded for Chakra, but you can change this, if you know what you're doing Now:
cd plymouth
makepkg --skipinteg
sudo pacman -U <name of the package>
Then you can set your plymouth theme. Spinfinity looks great, so:
sudo plymouth-set-default-theme spinfinity
That's it. Now the tricky parts:
- Edit your mkinitcpio.conf. You have to add "plymouth" to your hooks. Put it the earlier you can, but NOT before base and udev, otherwise things won't work! A sane config is to put it after base udev and autodetect
- Rebuild your ramdisk (mkinitcpio -p kernel26)
- In your /boot/grub/menu.lst, you have to change the kernel line. Add "quiet" and "splash". If you're on KMS, remove any video= or vga= directive. If you're not on KMS, add a vga=whatfitsyou directive to visualize decently the text bar
Reboot, and enjoy it!
At the moment the only small caveat is that plymouthd does not get killed. Some people used a small workaround by making start a daemon that killed plymouthd. This is not a great solution (at least if you're using a login manager such as kdm or gdm). I will work on a patch to get kdm do a smooth transition from plymouth (gdm already has it). What will need to be done afterwards, is to add into /etc/rc.d/kdm (or gdm) start phase a call to "plymouthd quit --retain-splash" to make things work. Until this moment will come, just make it die somehow
Feedback welcome. Thanks to Jan and Heller for starting to work on this, the plymouth developers (halfline and brejc8 mainly) for their unvaluable help, and PirateJonno for the plymouth-git package, which I admit I stole some code from
Last edited by drf (2009-10-02 18:36:08)
Offline
I tried it now, hoping for a good result next reboot! I don't understand the last part though. Is it crucial? Where do I add this line? Will my computer boot now? In another guide, I was told to add the daemon "plymouth" to /etc/rc.conf. Do I need to do this now?
Offline
There is no plymouth daemon in this package, as it's mostly needed for testing. You need to issue as root "killall plymouthd" when you log in
Offline
There is no plymouth daemon in this package, as it's mostly needed for testing. You need to issue as root "killall plymouthd" when you log in
Hello drf.
I think to kill plymounth quite we can add:
kill all plymounth
To rc.local locaded in /etc
Shell Scripter | C/C++/Python/Java Coder | ZSH
Offline
Oooh, I have been waiting for this, hopelessly checking http://chakra-project.org/wiki/index.php/Plymouth from time to time.
Thanks for the update! Will try it in a moment (hope I will be back).
Offline
drf wrote:There is no plymouth daemon in this package, as it's mostly needed for testing. You need to issue as root "killall plymouthd" when you log in
Hello drf.
I think to kill plymounth quite we can add:
kill all plymounth
To rc.local locaded in /etc
Also at the moment the change that makes more sense to me is putting it into /etc/rc.d/kdm, since it's right before the xserver kicks in. But for a complete integration, some patches to kdm, gdm or whatever are needed. A patch for gdm already exists, i'll look into doing something similar for kdm
Offline
Hey! It's great seing plymouth working on archlinux. I just tried it (you can see a video here: http://qik.com/video/3076771), and it works quite good, except that there are two relative big delays at the beginning and I couldn't notice a smooth transition to gdm.
Thank you very much for working on that, archlinux is actually only the second distribution (after Fedora) with a working KMS + plymouth for me.
Offline
Just tested, works great (including power off, does not break suspend nor resume) except for the pause before SLiM starts, but I believe this is to be expected right now. Rebranded it to Arch, too
Just a note, the PKGBUILD by default installs chakra's /etc/system-release.
Last edited by fijam (2009-10-02 19:56:01)
Offline
Thank you guys for testing Yes, as you can see from the url, it's the PKGBUILD for chakra but rebranding it is just about changing the logo file and 2 lines in the scripts
Offline
It works very fine here. I also have these glitches, but other than that it's nice. I just don't like the loading bar in the bottom, is it possible to remove it? I mean, just see the picture and the little snake
Offline
Glad to hear its actually working. I'll do my best to get my package to work, with the right logos etc.
"You can watch for your administrator to install the latest kernel with watch uname -r" - From the watch man page
Offline
Great Well, it is possible, you just have to change the theme and you can roll your own, of course. It would be great to have a real arch theme.
PirateJonno: you need very few modifications, check the source. Consider that now I'm also doing some additions for Chakra, so it would be great if you can get your pure Arch package to work.
Offline
I just tried and I do not have a login manager. Interesting enough plymouth stalls and seems to be waiting for a login manager (I guess this was what it was build for) and the only way to get out it is to change to another tty.
drf: Thanks for making the PKGBUILD available.
Last edited by Ashren (2009-10-02 21:37:50)
Offline
I just tried and I do not have a login manager. Interesting enough plymouth stalls and seems to be waiting for a login manager (I guess this was what it was build for) and the only way to get out it is to change to another tty.
Exactly. You probably should kill it in your rc.local when you switch runlevel, or simply issue "plymouth quit" (better)
drf: Thanks for making the PKGBUILD available.
You're welcome
Offline
Those using Gnome and looking for a smooth transition between plymouth and gdm might find this interesting: http://lists.freedesktop.org/archives/p … 00126.html
I guess I won't be seeing this in SLiM anytime soon
Offline
Unfortunately I don't seem to be able to get it to work any better than previously. For one, the "message" command sent to the plymouth daemon seems to crash it on startup (though it works great on shutdown). Additionally, the progress stops updating once I enter runlevel 5, although at least the plymouthd process is actually still running this time. Can anyone confirm these issues or is it just something about my computer? I'm not using kernel modesetting btw, but once the runlevel issue is resolved it should be possible to show a graphical splash on the framebuffer (which works but hangs at runlevel 5 and GDM doesn't seem to be able to take over the display). I'll keep fiddling around for a bit but if no one else is having these problems i may as well update the arch package.
"You can watch for your administrator to install the latest kernel with watch uname -r" - From the watch man page
Offline
The "message" command is still not working in Plymouth itself, from what the developers said. As soon as they will clean up the new DRM infrastructure they'll be on that.
Offline
i think use --libexecdir=/usr/lib is better than move files handly in PKGBUILD.
Offline
are the .a file necessary in the package? seems "!libtool" option didn't delete them
Offline
seems it should be "plymouth quit --retain-splash" not "plymouthd quit --retain-splash"
Offline
i think use this is the better way to start plymouth shutdown mode in plymouth.function:
if [ "$0" == "/etc/rc.shutdown" ]; then
/sbin/plymouthd --mode=shutdown
/bin/plymouth --show-splash
fi
so that we won't see default arch shutdown information.
Offline
i think use this is the better way to start plymouth shutdown mode in plymouth.function:
if [ "$0" == "/etc/rc.shutdown" ]; then /sbin/plymouthd --mode=shutdown /bin/plymouth --show-splash fi
so that we won't see default arch shutdown information.
You mean use this under "Sending SIGTERM To Processes" case?
Offline
no, at the end of plymouth.funtion file.
and delete "Sending SIGTERM To Processes" case
Offline
Awesome! Thanks! It's super cool!
Offline
no, at the end of plymouth.funtion file.
and delete "Sending SIGTERM To Processes" case
Thanks!
Offline