You are not logged in.
Pages: 1
There are several things about booting with plymouth, this is the boot process::
1 > [PROBLEM 1] Before the splash there's a message saying:
/dev/sdX recovering journal
/dev/sdX clean XX/XX contigious files2 > Plymouth starts
3 > [PROBLEM 2] After 2 or 3 seconds it changes to a black screen (I guess for loading KDM)
4 > KDM takes a long time to show cursor and then a few more to start Gnome-shell
5 > [PROBLEM 3] Plymouth keeps running on tty1 using 15% of CPU permanently at least it is killed
[P1[ How could I remove this message, my kernel command line includes the quiet option
[P2] Is there any way to avoid this black screen and keep plymouth until it gets to Gnome-shell (using automatic login)
[P3] Does plymouth needs to be kept running?
I have all plymouth related on systemctl enabled (except for different login managers) including kdm-plymouth
Offline
The first part is not a problem, it is an error message. This is supposed to happen if your filesystem is not clean.
Offline
I know the first part is not a problem with plymouth but that message is displayed whether the system is clean or not, sometimes it only shows
/dev/sdaX clean
I guess is some kind of fsck when the initram is loaded, since this message didn't show up when I used FBsplash and put it before base and udev in the HOOKS array in mkinitcpio.conf
I don't understand why it fsck at the beggining if that's another hook in the end, so it should be doing a double fsck?
Offline
I know the first part is not a problem with plymouth but that message is displayed whether the system is clean or not, sometimes it only shows
/dev/sdaX clean
I guess is some kind of fsck when the initram is loaded, since this message didn't show up when I used FBsplash and put it before base and udev in the HOOKS array in mkinitcpio.conf
I don't understand why it fsck at the beggining if that's another hook in the end, so it should be doing a double fsck?
Whenever I had Plymouth installed Arch was never able to switch intitramfs's root on shutdown forcing Arch to shutdown uncleanly, this doesn't happen when Plymouth is uninstalled. It seems as though Plymouth really is only designed for Fedora, I've never been able to get it working properly, there are so many bugs with it.
Offline
@awbs, I used plymouth for about a week, but removed it because I thought it kind of pointless to put up a splash screen for a split second. But my shutdowns were fine with plymouth. Considering that it is something that runs from the initramfs, when you used it, did you have the shutdown hook in mkinictpio.conf?
Offline
@awbs, I used plymouth for about a week, but removed it because I thought it kind of pointless to put up a splash screen for a split second. But my shutdowns were fine with plymouth. Considering that it is something that runs from the initramfs, when you used it, did you have the shutdown hook in mkinictpio.conf?
Yes, I had the shutdown hook enabled. The splash screen staying up for a second seems to be a bug, Plymouth used to launch immediately with almost no blank screens throughout my bootup, and it only flashes for a second and when the DE starts up.
Offline
[...] and it only flashes for a second and when the DE starts up.
See also this Thread/Post.
Knowing others is wisdom, knowing yourself is enlightenment. ~Lao Tse
Offline
I'm sure it shutdown cleanly, this message appears always, even when I used fbsplash
I think is part of the HOOK "base" since when I put the fbsplash hook before it, the message was hidden but if I put it after base the message appears and then fbsplash.
Login into console and starting X automatically makes a little faster the login so there isn't a lot of time between plymouth and the DE.
About plymouth using the CPU after loading the DE has been fixed automatically ![]()
Offline
Pages: 1