*BSD News Article 2937


Return to BSD News archive

Path: sserve!manuel!munnari.oz.au!hp9000.csc.cuhk.hk!uakari.primate.wisc.edu!ames!decwrl!csus.edu!netcomsv!mork!hasty
From: hasty@netcom.com (Amancio Hasty Jr)
Newsgroups: comp.unix.bsd
Subject: Re: X386 for 386BSD
Message-ID: <masmpyb.hasty@netcom.com>
Date: 2 Aug 92 04:00:56 GMT
References: <1992Jul31.164635.3317@lgc.com> <1992Jul31.215500.25218@zip.eecs.umich.edu>
Organization: Netcom - Online Communication Services  (408 241-9760 guest)
Lines: 49

In article <1992Jul31.215500.25218@zip.eecs.umich.edu> dmuntz@dip.eecs.umich.edu (Daniel A Muntz) writes:
>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 
>
Due to X386 being a new port, Rich compiled X11R5 with -g and -O.
>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

/dev/vga major number is 12 and minor number is 0.

>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).
>
Have you applied the patches to the kernel?

For informational purposes:
I am running X386-2E 1.0 (the server) in Speedup mode.
svga card Diamond SpeedStar (et4000 chipset) 1MB
486/33 MHz 64K cache
8 megabyte of memory


>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.

After you have applied the kernel patches and if the problem persists,
send me e-mail so I can take care of the problem.

 Rich and I ported X11R5 and X386

>The clients I've tried work fine.
>
>  -Dan
>

Amancio Hasty