*BSD News Article 62347


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!nntp.coast.net!chi-news.cic.net!uwm.edu!msunews!netnews.upenn.edu!dsinc!ub!newserve!rebecca!CNSVAX.ALBANY.EDU!JK7023
From: jk7023@CNSVAX.ALBANY.EDU (Jaime)
Newsgroups: comp.unix.bsd.netbsd.misc
Subject: Re: Xfree86
Date: 15 Feb 1996 23:21:49 GMT
Organization: University of Albany, SUNY
Lines: 17
Distribution: world
Message-ID: <4g0f6d$d4q@rebecca.albany.edu>
References: <4fveum$5a4@venera.isi.edu>
Reply-To: jk7023@CNSVAX.ALBANY.EDU
NNTP-Posting-Host: cnsvax.albany.edu

In article <4fveum$5a4@venera.isi.edu>, gaetan@isi.edu (Gaetan Feige) writes:
>I have insatlled Xfree86 easily on a linux system. However
>on the exact same machine I get 
>X connection to :0.0 broken( explicit kill or server shutdown)
>when I installed Xfree with netbsd.

	When I had problems like this, I checked the file ~/.xsession-errors. 
This was mostly useful when I was using xinit, though.  So, if it didn't say 
anything that was useful, I would use xdm and then check the file 
/usr/X11R6/lib/X11/xdm/xdm-errors (or something like that.)

	Keep in mind that a lot of your errors might be in the file
/etc/XF86Config.  For example, an improperly set mouse device or monitor size. 
I couldn't get XFree86 to work until I set my mouse driver to /dev/tty01. 
(Isn't that supposed to be what MS-DOS calls COM2?)

							Jaime