Return to BSD News archive
Newsgroups: comp.unix.bsd Path: sserve!manuel.anu.edu.au!munnari.oz.au!spool.mu.edu!umn.edu!math.fu-berlin.de!news.belwue.de!news.uni-tuebingen.de!mailserv!zxmsd01 From: zxmsd01@mailserv.zdv.uni-tuebingen.de (Gunther Schadow) Subject: Re: Starting XFree861.1 Message-ID: <zxmsd01.720135105@mailserv> Sender: news@softserv.zdv.uni-tuebingen.de (News Operator) Organization: Comp. Center (ZDV) U of Tuebingen, FRG References: <Bvsr9F.CFv@cosy.sbg.ac.at> <RICH.92Oct8131302@kappa.Rice.edu> <905@felix.Sublink.Org> Date: Mon, 26 Oct 1992 21:31:45 GMT Lines: 52 In <905@felix.Sublink.Org> eb@felix.Sublink.Org (Enrico Badella) writes: >In article <RICH.92Oct8131302@kappa.Rice.edu> Rich@rice.edu writes: >>In article <Bvsr9F.CFv@cosy.sbg.ac.at> peter@wiesel.cosy.sbg.ac.at (Peter Burgstaller) writes: >> >> 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. >> >I had this same problem when I impatiently tried to build XFree82-1.1 >without reading all the docs. I couldn't get it to work setting the >various parameters in XConfig. >The last try I gave it was to rebuild everything leaving out all the >drivers that weren't necessary, in my case ET4000. Now it >works wonderfully and and prints this message: > > XFree86 v1.1 Xwindow System > (protocol version 11, revision 0 vendor release 5000) > Configured drivers: > VGA256(256color svga): > ET4000 While I cannot rebuild the server because of disk space, I use the one provided at agate.berkeley.edu, and it just works fine. However there is somethiong about it you won't beleve: If I try to start xinit from a fresh-booted state, it will stopp immediately with the above message. Now, if I do any /dev/fd (floppy) access with either mtools or cat /dev/rfd0a, X will come up afterwards with no problems. It sonds hard to beleve, and I never got a response about that fact whenever I reported it in the past. But it is proved, I mean, I am not silly. There is another thing: X works exactly until cron is running /etc/daily (the standard one), after that it neglects any Key event. Any Ideas? -Gunther ------------------------------------------------------------------------------- Gunther Schadow, e-mail: Gunther@mailserv.ZDV.Uni-Tuebingen.DE Sudetenstrasse 25, Phone: (49) 7071/37527 7400 Tuebingen, Germany.__________Stop__________Horn Please!__________O.K. TATA -- ------------------------------------------------------------------------------- Gunther Schadow, e-mail: Gunther@mailserv.ZDV.Uni-Tuebingen.DE Sudetenstrasse 25, Phone: (49) 7071/37527 7400 Tuebingen, Germany.__________Stop__________Horn Please!__________O.K. TATA