Several days ago, I attempted to make a change to the kernel boot options via the Yast Bootloader module but encountered a system freeze (related to an bug/issue that I have detailed in another thread here) requiring a hard reset. I do not know if it was that very incident, but (if not, I noticed very) shortly afterwards, and ever since, I have lost the Plymouth bootsplash animation (the theme is called “openSUSE”, though I actually think that someone else better described it as “fireflies” ) whenever the system starts up (cold/hard or warm/soft boots). The monitors display the BIOS POST messages and the benign cosmetic GRUB2 error (discussed here) and then go blank until the KDM screen comes up.
On logout/shutdown, the Plymouth openSUSE/“firefiles” splash is shown as expected.
I have tried
sudo /usr/sbin/plymouthd; plymouth --show-splash
plymouth-set-default-theme --rebuild-initrd openSUSE
and even trying just mkinitrd alone.
But nothing good comes from any of that.
No mention on bugzilla of any similar problem.
Then I looked through the system log files. By searching for KMS (suspecting there might be an error there) I discovered the absence of a very different kms! Specifically, and presumably up to the point before where the bootsplash stopped working, the system log reveals that the very first entries for each boot are
imklog 5.8.11, log source = /proc/kmsg started.
rsyslogd: [origin software="rsyslogd" swVersion="5.8.11" x-pid="580" x-info="http://www.rsyslog.com"] start
Then later in the day and ever since, I see only the likes of
rsyslogd: [origin software="rsyslogd" swVersion="5.10.0" x-pid="630" x-info="http://www.rsyslog.com"] start
at the commencement of a new boot.
First off, imklog is the Kernel Log Input Module.
Second, checking Yast SM > Extras > Show History > indicates that I did update rsylog to a new version that day that the bootsplash stopped working, but there is nothing in the install history corresponding to imklog. Delving deeper, I see that imklog is actually included in the rsyslog package.
Third, I enabled plymouth debug option (by adding the plymouth:debug kernel boot option), and while I’m no expert here, it appears from the plymouth log file (by default its written to /var/log/plymouth-debug.log, though you can alter that if you wish) that things are, from Plymouth’s perspective, working as they are supposed to.
But very obviously from visual inspection of the startup process, things aren’t behaving as expected. And that’s as far as I’ve gotten so far with this. It would appear that imklog is not being initialized. Is this the root of the problem preventing the bootsplash animation from being displayed during system startup? I don’t know, but next up (when I get a chance) will be an examination of any rsyslog documentation to see what I can glean from that. Hopefully this is not a red herring.
Would appreciate any other suggestions/ideas/knowledge.