https://bugzilla.suse.com/show_bug.cgi?id=1232727 https://bugzilla.suse.com/show_bug.cgi?id=1232727#c20 --- Comment #20 from Jiri Slaby <jslaby@suse.com> --- (In reply to Thomas Zimmermann from comment #19)
Hi
(In reply to Jiri Slaby from comment #18)
(In reply to Thomas Zimmermann from comment #17)
1) The default tty appers to be incorrectly set to tty1. I set it to tty0 to get a text prompt on the console, but no graphics.
FWIW tty0 is the "current" tty. I.e. tty0 should be tty1 by default. That is, they should behave the same.
Where else than tty1 could tty0 refer to?
To any tty[0-9], if something switches (by chvt/ioctl(VT_ACTIVATE)) to it.
Because with tty0, I get at least a text output on the virtual console. With tty1 (the default), plymouth falls back to ttyS0.
But with tty1, can can force graphics with plymouth.graphical. That does not seem to work with tty0.
There is not much more to say, than that it is broken :).
Another thing I noticed is that plymouth does not find these tty device files. That's why it forces text output, as I mentioned.
I have never used plymouth (no reason for it with ssd to show a wheel for one second). So how do you configure it?
Just a guess: Could it be that /dev is not mounted when plymouth starts up?
Hmm. But how can it access and work with ttyS0 and tty1? -- You are receiving this mail because: You are on the CC list for the bug.