Page 1 of 1

Plymouth error?

PostPosted: Jun 26th, '14, 12:03
by rAC
Since slightly less than a week ago my machine refuses to complete a boot to the graphical login screen. during the boot I get a failed wait for Plymouth Boot Screen to quit message. Checking journalctl -xn and systemctl service status (? I have not copied that exactly) regarding plymouth-quit-wait shows nothing further than it has failed to start. I have no real idea on where/how to proceed from here.
I can Ctl-Alt F2 and get a non graphical login.
I have tried issuing a systemctl start plymoth-wait-quit.service there (ie in tty2) and get the same error message.
I have also tried a startx which reports it cannot find an Xserver (nor a graphical display device) -- I haven't written these messages down exactly.
I am writing this from the booting and working windows partition on the machine.

Any suggestions on what to look for /look at?

Re: Plymouth error?

PostPosted: Jun 26th, '14, 15:19
by claire
Some people have reported similar problems with kernel dkms modules. It's likely a kmod bug, we sent one patch upstream recently for a similar issue. It causes the module not to load properly. https://bugs.mageia.org/show_bug.cgi?id=13547

Do you have nvidia graphics?

$ rpm -qa | grep dkms-nvidia

If so this will show you which one. If it's fairly modern then it's probably dkms-nvidia-current. Removing the package clears any conflicts and reinstalling it should then rebuild it for your kernel.

If it's fglrx you can try the same for that one, urpme dkms-fglrx and then reinstall it.

Re: Plymouth error?

PostPosted: Jun 26th, '14, 20:03
by jiml8
I had that problem recently when I installed an rc.local script. My script was one line and did not include the shebang line (!#/bin/bash or !#/bin/sh). Adding the rc.local script caused the problem, removing it solved the problem. Altering it to add the shebang solved the problem.