*BSD News Article 28939


Return to BSD News archive

Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msuinfo!agate!howland.reston.ans.net!gatech!rutgers!fdurt1.fdu.edu!sun490.fdu.edu!brian
From: brian@sun490.fdu.edu (Brian Domenick)
Newsgroups: comp.os.386bsd.questions
Subject: xfree-2.1 on NetBSD-current ?
Message-ID: <1994Mar29.040741.13366@sun490.fdu.edu>
Date: 29 Mar 94 04:07:41 GMT
Organization: Fairleigh Dickinson University
Lines: 45


	I have just installed the Xfree2.1 binary distribution on
my march 5 Netbsd current pc. It states in the README.NetBSD if
you get the following error to check your kernal config file
for XSERVER and UCONSOLE. I have done this as well as looked at
the /dev directory entry for ttyv0 which is major #5 ,minor #31.
I also put in rc ldconfig /usr/X386/lib .

	I have previously had Xfree86-2.0 on this machine until
about 2hr ago.

	Does anybody have any ideas ? 

	Thanks in advance, The error messages follow .

				Brian Domenick
				brian@yoda.fdu.edu

-----------------------------------
start of xdm : interactive - xdm -nodaemon

ld.so: xdm: libX11.so.4.10: No such file or directory

-----------------------------------------
start of starx - 


XFree86 Version 2.1 / X Window System
(protocol Version 11, revision 0, vendor release 5000)
Operating System: NetBSD 
Configured drivers:
  VGA256: server for 8-bit colour SVGA (Patchlevel 0):
      et4000, et3000, pvga1, wd90c00, wd90c10, wd90c30, wd90c31, gvga, ati,
      tvga8800cs, tvga8900b, tvga8900c, tvga8900cl, tvga9000, clgd5420,
      clgd5422, clgd5424, clgd5426, clgd5428, clgd6205, clgd6215, clgd6225,
      clgd6235, clgd543x, ncr77c22, ncr77c22e, cpq_avga, oti067, oti077

Fatal server error:
xf86OpenConsole: CONSOLE_X_MODE_OFF failed (Inappropriate ioctl for device)
Was expecting pccons driver with X support
Check your kernel's console driver configuration and /dev entries

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.