Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!mit-eddie!ll-xn!ames!sdcsvax!ucbvax!ZERMATT.LCS.MIT.EDU!RWS
From: RWS@ZERMATT.LCS.MIT.EDU (Robert Scheifler)
Newsgroups: comp.windows.x
Subject: Making X.V11R1 on Sun 3
Message-ID: <870925173407.8.RWS@KILLINGTON.LCS.MIT.EDU>
Date: Fri, 25-Sep-87 17:34:00 EDT
Article-I.D.: KILLINGT.870925173407.8.RWS
Posted: Fri Sep 25 17:34:00 1987
Date-Received: Sun, 27-Sep-87 05:32:08 EDT
References: <8709252040.AA02904@nrl-aic.ARPA>
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 29


    Date: Fri, 25 Sep 87 16:40:34 edt
    From: Alan Schultz <schultz@nrl-aic.ARPA>

    First, let me be more specific: the machine is a Sun 3/160 with the COLOR
    monitor. Op sys 3.4 is running on it. Device wise, it has bwtwo0 and
    cgtwo0 (and console in addition to all the normal things.) We just set
    this machine up last week, and the only thing we changed in the
    configuation was MAXUSERS to 8 instead of 4 for larger system tables.
  		
    PROBLEM: 
       The screen darkens starting from the top of the screen, moving
    slowly down the screen. It takes ~6 - 8 seconds for the screen to be
    darkened! With X.V10R4, it happened almost instantaneously.
    NEXT, NOTHING HAPPENS! No large X cursor, nothing. A ps from another
    terminal shows (depending on how I start it) xinit and X as existing, but
    in an "I" state. I wait for 5 minutes, and still nothing, so I then kill
    the processes from another terminal.

    HELP!

Your confusion is covered in the Xsun man page; I guess you didn't read
it.  The solution is to remove the bwtwo0 entry from /dev.  With it
there, the server autoconfig assumes you actually have a screen attached
to that frame buffer, and since the mono screen is defined as screen 0,
the initial xterm and cursor is placed there, where you can't see it.

Note that color is *slow* on the Sun.  You can use the -mono option to
the server to get speed at the expense of color.