Return to BSD News archive
Newsgroups: comp.unix.bsd Path: sserve!manuel.anu.edu.au!munnari.oz.au!sgiblab!spool.mu.edu!uunet!psinntp!l5next!scotty From: scotty@gagetalker.com (Scott Turner) Subject: Re: Starting XFree861.1 Message-ID: <1992Oct10.100501.11881@gagetalker.com> Sender: scotty@gagetalker.com Organization: L5 Computing References: <Bvsr9F.CFv@cosy.sbg.ac.at> Date: Sat, 10 Oct 1992 10:05:01 GMT Lines: 30 In article <Bvsr9F.CFv@cosy.sbg.ac.at> peter@wiesel.cosy.sbg.ac.at (Peter Burgstaller) writes: |> Then I started xinit (also startx) then I got the following |> Message! |> |> XFree86 v1.1 Xwindow System |> (protocol version 11, revision 0 vendor release 5000) |> Configured drivers: |> VGA256(256color svga): |> ET4000,ET3000,PVGA1,GVGA,ATI,TVGA8900 |> XIO: fatal io error 32 (broken pipe) on Xserver ":0.0" |> after 0 reqests (0 known processed) with 0 events remaining. |> The connection was probably broken by the server shutdown or |> Killclient. Ah, know it well, spent _hours_ on this one myself. It's probably yer mouse. I've got the patched kernel (beta-1) and re-mknod'd my serial ports and I wound up having to use com2 to get to com1. :) Of course that was _AFTER_ I figured out I wasn't supposed to be using tty0! Too many hours on the commercial unixes... To see the error messages I fired up xinit from a telnet session from my NeXT. Someone sent me e-mail suggesting I fire up the server and redirect stderr to a file. The problem is that 386bsd doesn't have virtual terminals yet. So when the console flips into graphics mode and the server dumps out it's error messages they get flushed. Scotty