Re: [opensuse-factory] empty tty10
On 07/18/2014 08:20 AM, Dale Ritchey wrote:
On 07/18/2014 04:37 AM, Felix Miata wrote:
On 2014-07-18 09:35 (GMT+0200) Bruno Friedmann composed:
Felix Miata wrote:
Anyone know why post-13.1 vtty10 is nothing but black instead of kernel messages, if it exists at all? The system I have currently booted to Factory won't let me get past vtty6 (in runlevel 3). Others I can get there, but it's empty, or I can get there only if in runlevel 5, where it's still only black.
don't know if factory has totally switched to journald but if it the case by defaut in /etc/systemd/journald.conf those 2 lines are commented ForwardToConsole=yes TTYPath=/dev/tty10
uncomment them
had only
#ForwardToConsole=no
With first splash=verbose noplymouth boot to multi-user.target with:
ForwardToConsole=yes TTYPath=/dev/tty10
boot messages stalled at [41.64...] without producing a visible login prompt on tty1, but login prompts appeared on tty2-tty6. tty7-tty12 are unreachable. Login prompt on tty6 had this appended:
[247.656605] systemd-logind[613]: Failed to start autovt@tty6.service: Unit autovt@tty6.service failed to load: File exists.
On each return to tty6 after going to another an additional instance of that message appears on tty6.
On finally logging in on tty3 @[515...], roughly 20 additional login and systemd messages appeared on lines between "Password:" and the shell's MOTD. While typing here, more messages on tty6 followed. Logging in on tty2 produced another splash of messages.
/etc/systemd/journald.conf line 28 uncomment and change to ForwardToConsole=yes line 29 uncomment and change to
line 29 uncomment and change toTTYPath=/dev/tty10 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2014-07-18 08:26 (GMT-0400) Dale Ritchey composed:
Dale Ritchey wrote:
Felix Miata wrote:
On 2014-07-18 09:35 (GMT+0200) Bruno Friedmann composed:
Felix Miata wrote:
Anyone know why post-13.1 vtty10 is nothing but black instead of kernel messages, if it exists at all? The system I have currently booted to Factory won't let me get past vtty6 (in runlevel 3). Others I can get there, but it's empty, or I can get there only if in runlevel 5, where it's still only black.
don't know if factory has totally switched to journald but if it the case by defaut in /etc/systemd/journald.conf those 2 lines are commented
ForwardToConsole=yes TTYPath=/dev/tty10
uncomment them
had only
#ForwardToConsole=no
With first splash=verbose noplymouth boot to multi-user.target with:
ForwardToConsole=yes TTYPath=/dev/tty10
boot messages stalled at [41.64...] without producing a visible login prompt on tty1, but login prompts appeared on tty2-tty6. tty7-tty12 are unreachable. Login prompt on tty6 had this appended:
[247.656605] systemd-logind[613]: Failed to start autovt@tty6.service: Unit autovt@tty6.service failed to load: File exists.
On each return to tty6 after going to another an additional instance of that message appears on tty6.
On finally logging in on tty3 @[515...], roughly 20 additional login and systemd messages appeared on lines between "Password:" and the shell's MOTD. While typing here, more messages on tty6 followed. Logging in on tty2 produced another splash of messages.
/etc/systemd/journald.conf line 28 uncomment and change to ForwardToConsole=yes line 29 uncomment and change to
line 29 uncomment and change toTTYPath=/dev/tty10
In the wee hours I was't seeing what was plainly in front of my face, with trying to use TTYPath=/dev/console. However, now with toTTYPath=/dev/tty10 the problem remains the same, but with actually using TTYPath=/dev/tty10 as originally suggested, tty10 is reachable and has the expected messaging. tty7-tty9 do remain unreachable, as do tty11-tty12. Attempts to reach those produce no reaction on the display, a definite change from recent releases. Login prompts and logins on tty1-6 are now behaving as expected, although my manual nfs mounting script unlike previous openSUSE releases is producing messages that in openSUSE never appeared, messages like Fedora and Mageia have been producing for some time: [time] Key type dns_resolver registered [time] NFS: Registering the id_resolver key type [time] Key type id_resolver registered [time] Key type id_legacy registered -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 07/18/2014 10:38 AM, Felix Miata wrote:
On 2014-07-18 08:26 (GMT-0400) Dale Ritchey composed:
Dale Ritchey wrote:
Felix Miata wrote:
On 2014-07-18 09:35 (GMT+0200) Bruno Friedmann composed:
Felix Miata wrote:
Anyone know why post-13.1 vtty10 is nothing but black instead of kernel messages, if it exists at all? The system I have currently booted to Factory won't let me get past vtty6 (in runlevel 3). Others I can get there, but it's empty, or I can get there only if in runlevel 5, where it's still only black.
don't know if factory has totally switched to journald but if it the case by defaut in /etc/systemd/journald.conf those 2 lines are commented
ForwardToConsole=yes TTYPath=/dev/tty10
uncomment them
had only
#ForwardToConsole=no
With first splash=verbose noplymouth boot to multi-user.target with:
ForwardToConsole=yes TTYPath=/dev/tty10
boot messages stalled at [41.64...] without producing a visible login prompt on tty1, but login prompts appeared on tty2-tty6. tty7-tty12 are unreachable. Login prompt on tty6 had this appended:
[247.656605] systemd-logind[613]: Failed to start autovt@tty6.service: Unit autovt@tty6.service failed to load: File exists.
On each return to tty6 after going to another an additional instance of that message appears on tty6.
On finally logging in on tty3 @[515...], roughly 20 additional login and systemd messages appeared on lines between "Password:" and the shell's MOTD. While typing here, more messages on tty6 followed. Logging in on tty2 produced another splash of messages.
/etc/systemd/journald.conf line 28 uncomment and change to ForwardToConsole=yes line 29 uncomment and change to
line 29 uncomment and change toTTYPath=/dev/tty10
In the wee hours I was't seeing what was plainly in front of my face, with trying to use TTYPath=/dev/console. However, now with toTTYPath=/dev/tty10 the problem remains the same, but with actually using TTYPath=/dev/tty10 as originally suggested, tty10 is reachable and has the expected messaging. tty7-tty9 do remain unreachable, as do tty11-tty12. Attempts to reach those produce no reaction on the display, a definite change from recent releases. Login prompts and logins on tty1-6 are now behaving as expected, although my manual nfs mounting script unlike previous openSUSE releases is producing messages that in openSUSE never appeared, messages like Fedora and Mageia have been producing for some time:
[time] Key type dns_resolver registered [time] NFS: Registering the id_resolver key type [time] Key type id_resolver registered [time] Key type id_legacy registered
Thanks for this thread. I just installed 13.2 from openSUSE-Factory-NET-x86_64-Snapshot20140630-Media.iso, and also found that console 10 did not have the system log. Making the edit of /etc/systemd/journald.conf as described above, it now works the way I expected. Larry -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am 20.07.2014 18:53, schrieb Larry Finger:
Thanks for this thread. I just installed 13.2 from openSUSE-Factory-NET-x86_64-Snapshot20140630-Media.iso, and also found that console 10 did not have the system log. Making the edit of /etc/systemd/journald.conf as described above, it now works the way I expected.
How about making it default for openSUSE? We would need someone to split that config file into a systemd-branding-upstream and then package a systemd-branding-openSUSE. Greetings, Stephan -- Ma muaß weiterkämpfen, kämpfen bis zum Umfalln, a wenn die ganze Welt an Arsch offen hat, oder grad deswegn. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2014-07-21 07:36 (GMT+0200) Stephan Kulow composed:
schrieb Larry Finger:
Thanks for this thread. I just installed 13.2 from openSUSE-Factory-NET-x86_64-Snapshot20140630-Media.iso, and also found that console 10 did not have the system log. Making the edit of /etc/systemd/journald.conf as described above, it now works the way I expected.
How about making it default for openSUSE? We would need someone to split that config file into a systemd-branding-upstream and then package a systemd-branding-openSUSE.
Any chance of convincing upstream to make having it enabled the default? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Monday 21 July 2014 07.36:45 Stephan Kulow wrote:
Am 20.07.2014 18:53, schrieb Larry Finger:
Thanks for this thread. I just installed 13.2 from openSUSE-Factory-NET-x86_64-Snapshot20140630-Media.iso, and also found that console 10 did not have the system log. Making the edit of /etc/systemd/journald.conf as described above, it now works the way I expected.
How about making it default for openSUSE? We would need someone to split that config file into a systemd-branding-upstream and then package a systemd-branding-openSUSE.
Greetings, Stephan
I don't know if it would fit in a branding thing. I would have prefer to have an openSUSE preset for journald like the one we have for systemd ? Does that make sense ? -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch openSUSE Member & Board GPG KEY : D5C9B751C4653227 irc: tigerfoot ~~~Don't take Life too serious. Nobody gets out alive anyway!~~~ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Monday 2014-07-21 07:36, Stephan Kulow wrote:
Am 20.07.2014 18:53, schrieb Larry Finger:
Thanks for this thread. I just installed 13.2 from openSUSE-Factory-NET-x86_64-Snapshot20140630-Media.iso, and also found that console 10 did not have the system log. Making the edit of /etc/systemd/journald.conf as described above, it now works the way I expected.
How about making it default for openSUSE? We would need someone to split that config file into a systemd-branding-upstream and then package a systemd-branding-openSUSE.
You would need to take care that you do not run into the situation where both journald and rsyslog emit to tty10. That would.. lead to duplicated messages, I guess. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Mon, Jul 21, 2014 at 03:29:40PM +0200, Bruno Friedmann wrote:
On Monday 21 July 2014 07.36:45 Stephan Kulow wrote:
Am 20.07.2014 18:53, schrieb Larry Finger:
Thanks for this thread. I just installed 13.2 from openSUSE-Factory-NET-x86_64-Snapshot20140630-Media.iso, and also found that console 10 did not have the system log. Making the edit of /etc/systemd/journald.conf as described above, it now works the way I expected.
How about making it default for openSUSE? We would need someone to split that config file into a systemd-branding-upstream and then package a systemd-branding-openSUSE.
Greetings, Stephan
I don't know if it would fit in a branding thing. I would have prefer to have an openSUSE preset for journald like the one we have for systemd ? Does that make sense ?
It is not a branding ... /dev/tty10 does only exists if virtual consoles are enabled on the platform. That is that there is no /dev/tty10 on s390/x, some PPC64, some arm platforms, and even on some x86_64 platforms I'd like to see a feature that enables the journalctl tool to switch the journald from /dev/console to /dev/tty10 just like the tool klogconsole this does for the kernel log. Werner -- "Having a smoking section in a restaurant is like having a peeing section in a swimming pool." -- Edward Burr
On 07/21/2014 07:46 AM, Felix Miata wrote:
On 2014-07-21 07:36 (GMT+0200) Stephan Kulow composed:
schrieb Larry Finger:
Thanks for this thread. I just installed 13.2 from openSUSE-Factory-NET-x86_64-Snapshot20140630-Media.iso, and also found that console 10 did not have the system log. Making the edit of /etc/systemd/journald.conf as described above, it now works the way I expected.
How about making it default for openSUSE? We would need someone to split that config file into a systemd-branding-upstream and then package a systemd-branding-openSUSE.
Any chance of convincing upstream to make having it enabled the default?
OK, but how do you handle, that both syslog-ng and rsyslog would write to tty10 if installed? A conflict with systemd-branding-openSUSE? Bye, CzP (syslog-ng upstream) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (8)
-
Bruno Friedmann -
Dale Ritchey -
Dr. Werner Fink -
Felix Miata -
Jan Engelhardt -
Larry Finger -
Peter Czanik -
Stephan Kulow