*BSD News Article 7923


Return to BSD News archive

Newsgroups: comp.unix.bsd
Path: sserve!manuel.anu.edu.au!munnari.oz.au!spool.mu.edu!uwm.edu!zaphod.mps.ohio-state.edu!darwin.sura.net!wupost!newsfeed.rice.edu!rice!news.Rice.edu!rich
From: rich@Rice.edu (Richard Murphey)
Subject: Re: [XFree86]  Help needed badly
In-Reply-To: az7141633@v9001's message of Fri, 20 Nov 1992 12:25:00 GMT
Message-ID: <RICH.92Nov20095328@omicron.Rice.edu>
Sender: news@rice.edu (News)
Reply-To: Rich@rice.edu
Organization: Department of Electrical and Computer Engineering, Rice
	University
References: <20NOV199220254593@v9001>
Date: Fri, 20 Nov 1992 15:53:28 GMT
Lines: 61

In article <20NOV199220254593@v9001> az7141633@v9001 (AZ7141633) writes:
   I am facing the same problem as what both Thanh Luu and S.X. Xue faced;  but I
   could not find any replies to their queries in comp.unix.bsd.
   I would appreciate if anyone could help us get started with XFree86 and 386BSD.
   Thanks in advance.

   Sok
   Internet addr:  az7141633@ntuvax.ntu.ac.sg
   With Love from Nanyang Technological Univ of Singapore


   >X-NEWS: ntuvax.ntu.ac.sg comp.unix.bsd: 7901
   >From: tpl20@pswd.amdahl.com (Thanh Luu)
   >Subject: Problem starting up X
   >Date: 13 Nov 92 17:46:56 GMT
   >
   >I installed XFree86 and the kernel patch.  When I tried to bring up X, using
   >xinit, I got the following message:
   >
   >   XIO: fatal IO error 32 (broken pipe) on X server ":0.0"
   >   after 0 requests (0 known processed) with 0 events remaining
   >   The connection was probably broken by a server shutdown or KillClient
   >
   >What did I miss to do?  Thanks in advance.

First try redirecting the output to a file so that you get all the
error messages:
	xinit >errs 2>&1
if you are using sh, or
	xinit >&errs
if you are using csh.

Then start looking at your Xconfig file.
>From /usr/X386/lib/X11/etc/README.386BSD:


---------------- EDITING /usr/X386/lib/X11/Xconfig ----------------

You must edit /usr/X386/lib/X11/Xconfig to suit your hardware.  It
tells the X server what kind of monitor and adapter are present.  Read
the X386 man page and /usr/X386/lib/X11/Xconfig.sample first.

Once you understand the structure of Xconfig, try to find your
specific monitor and vga card in /usr/X386/lib/X11/etc/modeDB.txt.  If
your Clocks and ModeDB lines are there, grab the values there and put
them in your Xconfig.  If modeDB.txt does not have your hardware, read
/usr/X386/lib/X11/etc/XConfig.Notes for instructions on how to create
the video timing values given your vga card and monitor specs.  The
manual for your monitor and adapter should have these values.  To find
your clocks,  leave the Clocks line out of your Xconfig and run
'xinit >& xinit.out'.  If X386 can find your clocks, it will print
them out to xinit.out.  Given your clock frequency and horizontal
frequency of your monitor, the program xclk (on agate.berkeley.edu in
/pub/386BSD/0.1-ports/XFree86) can calculate a ModeDB line for you.

Unless you add more fonts, your Xconfig's FontPath line should be:
    FontPath "/usr/X386/lib/X11/fonts/misc/,/usr/X386/lib/X11/fonts/75dpi/"
If the FontPath includes non existant directories the server will exit
without any error messages which would give a clue to the cause.

Hope that helps!  Rich