* Achim Gratz [03-02-13 17:13]:

Achim Gratz writes:

...

Somewhere around the beginning of the year the virtual text terminals sometimes are initialized too late, so that xdm starts before these become available. If that happens you can't switch from vt7 (xdm/X11) back to any of the virtual terminal screens and have to restart xdm before these become available. Is there any setting I may have missed that influences this or is systemd simply missing a dependency here?

I have watched it doing it again after the update today: in fact all six virtual terminals had their getty processes started and I could switch between them while the boot was still in progress. As soon as kdm kicked in, I could no longer switch to any of the text terminals until I had restarted the xdm service (which I need to do blind since as soon as I switch to textmode from kdm my monitor goes into power-off).

Please comment on: https://bugzilla.novell.com/show_bug.cgi?id=801865 I see the same problem in a vbox and filed bug-report, but appears it is not carrying much weight tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Achim Gratz writes:

Done. BTW, since I'm still suspecting that this problem is an interaction with plymouth, is there any way to decativate plymouth completely or even deinstall it (I've never configured it to show any splash screens anyway)?

After wading to dozens of complaints that plymouth would not work, I've finally found the posting that told me the kernel line parameter was "noplymouth", not "plymouth=no" as I had been trying. So I've now added "nosplash noplymouth" to all my kernel lines. The bug with kdm is still there and it seems to depend on the fact that kdm now starts on the same vt that shows the (end of) the boot messages rather than switching to a new vt when starting. Let's wait for the server patch to filter into Tumbleweed… Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Factory and User Sound Singles for Waldorf Q+, Q and microQ: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

В Wed, 06 Mar 2013 10:35:58 +0100 Frederic Crozat пишет:

Le mercredi 06 mars 2013 à 10:15 +0100, Achim Gratz a écrit :

...

Achim Gratz writes:

...

Done. BTW, since I'm still suspecting that this problem is an interaction with plymouth, is there any way to decativate plymouth completely or even deinstall it (I've never configured it to show any splash screens anyway)?

After wading to dozens of complaints that plymouth would not work, I've finally found the posting that told me the kernel line parameter was "noplymouth", not "plymouth=no" as I had been trying. So I've now added "nosplash noplymouth" to all my kernel lines.

Which is incorrect.

To disable plymouth, use "plymouth.enable=0"

Removing "splash=..." from kernel command line pretty much does it for me. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Le mercredi 06 mars 2013 à 22:33 +0400, Andrey Borzenkov a écrit :

В Wed, 06 Mar 2013 10:35:58 +0100 Frederic Crozat пишет:

...

Le mercredi 06 mars 2013 à 10:15 +0100, Achim Gratz a écrit :

...

Achim Gratz writes:

...

Done. BTW, since I'm still suspecting that this problem is an interaction with plymouth, is there any way to decativate plymouth completely or even deinstall it (I've never configured it to show any splash screens anyway)?

After wading to dozens of complaints that plymouth would not work, I've finally found the posting that told me the kernel line parameter was "noplymouth", not "plymouth=no" as I had been trying. So I've now added "nosplash noplymouth" to all my kernel lines.

Which is incorrect.

To disable plymouth, use "plymouth.enable=0"

Removing "splash=..." from kernel command line pretty much does it for me.

There is a difference : unless you specify plymouth.enable=0 (or rd.plymouth.enable=0 but this will only prevent plymouth to start in initrd, it will be then started by systemd), plymouth will be be running and will handle the output to screen (even in text mode). -- Frederic Crozat SUSE -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Frederic Crozat writes:

Which is incorrect.

Well, it was even posted to this very list and had gone uncorrected. Also, the manpage tells me nothing about the kernel options and /usr/share/doc/plymouth does not even exist. The only pages with "plymouth" on opensuse.org are pages that are trumpeting it's release with the upcoming 12.3 .

To disable plymouth, use "plymouth.enable=0"

Thanks, but please have at least a README with that information. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptation for Waldorf microQ V2.22R2: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Armed with the knowledge how to _really_ switch off plymouth from the kernel command line the picture of how this happens becomes a lot more clear: with plymouth in the boot process, when vt1 gets started, the boot messages get bounced over to vt7. If kdm starts on the same virtual terminal that the boot messages are on (which it does in this case), then switching between vts becomes non-functional. If you manage to get kdm started on vt8 by switching back to any of the other vts shortly before it starts, then this does not happen, which explains why this bug hasn't been recognized before. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Samples for the Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org