Return to BSD News archive
Newsgroups: comp.unix.bsd
Path: sserve!manuel!munnari.oz.au!sgiblab!zaphod.mps.ohio-state.edu!caen!umeecs!dip.eecs.umich.edu!dmuntz
From: dmuntz@dip.eecs.umich.edu (Daniel A Muntz)
Subject: Re: X386 for 386BSD
Message-ID: <1992Jul31.215500.25218@zip.eecs.umich.edu>
Sender: news@zip.eecs.umich.edu (Mr. News)
Organization: University of Michigan EECS Dept., Ann Arbor
References: <1992Jul31.164635.3317@lgc.com>
Date: Fri, 31 Jul 1992 21:55:00 GMT
Lines: 28
In article <1992Jul31.164635.3317@lgc.com> danson@lgc.com (Doug Anson) writes:
>I pulled X386 binaries off of agate for 386BSD. I noticed that the
>X server is *11 MEG* in size -- is this for real? How much swap is
Try stripping it.
Has anyone gotten the server to work? What are the major and minor numbers
for /dev/vga? I tried the numbers for /dev/console and /dev/null (in case
it didn't really need /dev/vga) and with either, X fails without giving
any useful error message. X386 is dying of a bus error (i.e., if I run
X386 w/o xinit or startX, it generates a bus error).
I run X386 under Mach 2.6 on a different partition, so the hardware should
be okay, and I brought over my Xconfig (merged with Xconfig.sample), ~/.x*, etc.
(card: Orchid PD IIs ET4000 1meg)
Message when /dev/vga exists:
X386 Version 1.2E 1.0.1 / X Window System
(protocol Version 11, revision 0, vendor release 5000)
XIO: fatal IO error 32 (Broken pipe) on X server "(null)"
after 0 requests (0 known processed) with 0 events remaining.
The connection was probably broken by a server shutdown or KillClient.
The clients I've tried work fine.
-Dan