Hi!
First time in seven years with openSuse that I need to ask for advice here ;):
As I’m always curious to know what happens during boot (and don’t like graphic boot animations), I’ve set splash=verbose to my kernel boot parameters as default. After doing a repo update one week ago, the system refuses to boot as long as splash=verbose is set. I think (hope?) this is only an issue of settings and not a bug. I did not find anything else about this, so maybe someone may help:
what I did:
use Tumbleweed X86_64
run zypper dup after 29. January 2017
set splash=verbose in the boot parameters of your preferred kernel
reboot
what happens:
systemd tells me that it “FAILED to start plymouth-start.service”
normal booting seems to continue until the system has “REACHED target switch root”
system tells me that it is “STARTING switch root”, then it freezes. The only way out is to power off the machine.
reproducable?
on the three machines I run with Tumbleweed: Yes.
I can easily circumvent this by setting splash=silent at boot, but I’d prefer a solution. plymouth is installed and seems to run at boot:
@highlander:~> systemctl status plymouth-start
● plymouth-start.service - Show Plymouth Boot Screen
Loaded: loaded (/usr/lib/systemd/system/plymouth-start.service; static; vendor preset: disabled)
Active: inactive (dead) since Sun 2017-02-05 14:17:57 CET; 9h ago
Main PID: 266 (code=exited, status=0/SUCCESS)
I tried to get a log from one of these failed boots, but I can’t find any.
-EDIT: Although this issue seems to be kernel independent, I’m running
Linux 4.9.8-1.gaf90696-default #1 SMP PREEMPT Sat Feb 4 09:04:54 UTC 2017 (af90696)
I can confirm this is happening. I like to see the system booting - it is reassuring to see these green OKs and you can see straight away if a red FAILED comes up. This will soon be obsolete - on a computer with SSD drive booting is too fast and I leave the splash screen there (you need to check the boot.log if then to see the text). However my Tumbleweed computer (my oldest computer slow enough ton follow the boot and it is an old i586 machine) suddenly came up with the “FAILED to start plymouth-start.service”. The rest of the boot was OK but before switching to the login screen it stayed quite a while in the text mode at the login prompt. But then the KDE login came up and it worked OK, however I noticed that I could not get into yast2, only yast in then terminal was working. All other functions I tried seemed to work OK - not that I did an extensive test. In my Grub2 boot line (for some reason I don’t know ???) the “splash= silent” was completely gone (normally I changed it to splash=0). I booted 3 times and always the same error message at the start and always no graphical Yast. After adding “splash= silent” the booting resumed its normal boot (but with splash screen which I hid using the escape key) and Yast2 was available again. I don’t know what happened there but I just leave the “splash= silent” for now.
Cheers
Uli
If all you want is to see the scrolling lines instead of the Plymouth splash screen, simply add plymouth.enable=0 to the Grub command line (Yast=>Bootloader) and remove the option quiet.
Also, if you are not interested in this graphic boot at all, you can uninstall Plymouth, but just doing the above will work.