I see, I had a look at my workstation running Linux and I don't know why I thought it was showing the messages at tty00. But now I know a lot more and I still got a way to retrieve console messages if X locks up.
Thanks a lot for the patience and pointing me in the right direction :) Cheers!, Adrian. 2015-06-27 17:14 GMT+02:00 Eric Schnoebelen <[email protected]>: > Adrian Christiansen writes: > - Aha, this is great news! I did as you said and enabled the ttyE0 in > - /etc/ttys, I didn't disable console in /etc/ttys since I still want > - the messages to show up on ttyE0. > > The entries in /etc/ttys control which devices have gettys > running on them. It does nothing to control where the kernel > emits messages. > > - This made me able to use ttyE0, and > - login. As you pointed out already I do actually need to set console to > - off in /etc/ttys to stop getty opening a login: promt in xconsole. > - However this makes the messages only show up in xconsole, not on > - ttyE0, this is not the behaviour I want, constty didn't work either. > - > - I guess I'm a bit confused about all of this. But I still would like > - the messages sent to /dev/console to show up on ttyE0. Not just in the > - xconsole. Is there a way to do this? > > No. NetBSD (and traditional UNIX in general), has only *one* > console device. aka, one device where kernel messages are emitted. > > xconsole(1) uses ioctl to set the flag TIOCCONS, which, > according to the tty(4) manual page: > > TIOCCONS int *on > If on points to a non-zero integer, redirect kernel > console output (kernel printf's) to this terminal. > If on points to a zero integer, redirect kernel > console output back to the normal console. This > is usually used on workstations to redirect kernel > messages to a particular window. > > Kernel messages can only go to one terminal. (and /dev/klog, > which syslogd(8) uses to pick them up.) xconsole says the pty it > has opened is that terminal. > > - 2015-06-26 23:28 GMT+02:00 Eric Schnoebelen <[email protected]>: > - > Adrian Christiansen writes: > - > - This makes me wonder if it is an issue with drmkms at all. So I'm > - > - thinking more that this is an issue with xdm or xconsole being setup > - > - wrong?, haven't changed any settings since installing. > - > > - > xconsole(1) is functioning as designed. It acquires the console > - > messages by telling the kernel that the pty it has opened is the > - > console. > - > > - > Thus, getting attempts to run on it. > > "gettings"? My fingers must be overriding my brain while typing. :D > I meant "gettys". > > - > If you wish to have xconsole(1) capture the console messages, > - > but have getting running on the F1 tty, edit /etc/ttys to > - > disable the getty running on console, and enable the one on > - > ttyE0. > > -- > Eric Schnoebelen [email protected] http://www.cirr.com > "Love means giving selflessly, excluding none and including all." -- Rama
