Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!howland.reston.ans.net!europa.eng.gtefsd.com!uunet!news.univie.ac.at!fstgds15.tu-graz.ac.at!fstgds01.tu-graz.ac.at!not-for-mail
From: chmr@edvz.tu-graz.ac.at (Christoph Robitschko)
Newsgroups: comp.os.386bsd.questions
Subject: Re: Xserver crashes (repost) + future platform
Date: 19 Aug 1993 22:13:26 +0200
Organization: Technical University of Graz, Austria
Lines: 65
Message-ID: <250mt6INNns@fstgds01.tu-graz.ac.at>
References: <CBzCrz.Ayv@latcs1.lat.oz.au>
NNTP-Posting-Host: fstgds01.tu-graz.ac.at
X-Newsreader: TIN [version 1.2 PL1]
In article <CBzCrz.Ayv@latcs1.lat.oz.au> M.C. Wong (wongm@latcs5.lat.oz.au) wrote:
> Hi,
> I am running 386bsd 0.1 + pk 0.2.4 + XFree86-1.2 (using syscons-2.0)! Recently
> I have run into frequent crashes in X server, when running ico. I am not very
> concerned about what programs are running, but I just wonder why it will crash
> that easily. I just try to avoid X crashing in the middle of some serious work.
> On the other hand, I have run out of disk space, and taps into the reserved
> area of disk space (ie df will show 104% of disk usage). I wonder if this is
> causing the problem ?
Don't think so.
> So, is there a way of restoring the virtual console to text mode ? I attempt
> to use syscons ioctl as follows :
> main() {
> FILE *fp;
> int fn;
> /* tty02 is the virtual console which I run X all the time */
> if ((fp = fopen("/dev/tty02", "rw")) == NULL) {
> perror("textmode");
> exit(-1);
> }
> fn = fileno(fp);
> ioctl(fn, CONS_80x25TEXT, 0); /* can't actually remember the ioctl constant */
> }
Just a side note: You can simplify this program to
main() { int fn;
if ((fn = open("/dev/tty02", 0) == -1) {
perror("open"); exit(1); }
if (ioctl(fn, ...) == -1) perror("ioctl"); }
> But it doesn't switch me back to text mode (80x25). I wonder if anyone has the
> solution for this ?
The X server captures the screen from syscons, and only the X server can
restore to text mode. You might have to remove /tmp/.X0-lock to be able
to start the X server again.
> Also, having installed syscons-2.0 as my console driver, I still can't run
> more than 1 X server on each different virtual console. Has anyone successully
> run more than 1 X server with syscons-2.0 in each of the virtual console ? Could
> you please drop me a few lines how you get that working ?
You have to use the X servers that were supplied with syscons. They are
patched XFree-1.2 servers. Log in to the first VT, and type "startx".
Switch to the second VT (have to use CTRL-ALT-Fx here instead of ALT-Fx),
and type "startx -- /usr/X386/bin/X386-syscons :1". Works perfectly --
I have just tried it.
If you start your server automatically using xdm or something, you also
have to include the :1 flag for the second server.
> One last thing. Will the port of 386bsd go as far as onto Alpha AXP, and
> PowerPC based PCs in the future ?
I doubt many people will have such machines *to play with* in the near future.
> Thanks in advance!
You're welcome.
Christoph