Comment # 84 on bug 1002875 from Cliff Zhao

(In reply to Aleksey Kontsevich from comment #83)
> (In reply to Cliff Zhao from comment #81)
> > If it behaves like this, this should be another issue, please open a new
> > bug, and don't forget to attach the support-log.
> Can do but why it can't be solved here? And what is support-log?
Because it is very hard to manage. This bug already have many forking
discussions, and the problem which you are facing is different with the
reporter's scenario.

to get the supportlog:
1, $ zypper install supportutils
2, $ supportconfig
3, Upload the tar file from your system "/var/log/scc_...txz" to here as an
attachment.

> 
> >And maybe you could have a check if your problem is the same with bsc#1179625? Is the method in comment1 of that bug works for you?
> What method? It describes nothing - how to solve - steps to fix? And do not
comment1 of "that bug". 
sudo plymouth-set-default-theme --rebuild-initrd bgrt
or 
sudo plymouth-set-default-theme bgrt && dracut -f

> think it will solve anything. In Ubuntu plymouth starts immediately and user
> do not see a console at all. In SUSE starting kernel message appears in any
> case for some reason after grub which is weird!
But this is also different from your comment80's problem. It should be the
third bug, and please paste the reproduce steps there.