Path: utzoo!mnetor!uunet!husc6!mailrus!tut.cis.ohio-state.edu!allosaur.cis.ohio-state.edu!bob From: bob@allosaur.cis.ohio-state.edu (Bob Sutterfield) Newsgroups: comp.windows.x Subject: Re: R2 problems Message-ID: <10451@tut.cis.ohio-state.edu> Date: 13 Apr 88 16:33:01 GMT References: <490@lamont.Columbia.edu> Sender: news@tut.cis.ohio-state.edu Organization: The Ohio State University Dept of Computer & Information Science Lines: 22 Keywords: Sun 3/280 high-res monitor In article rapatel@porthos.rutgers.edu ( Rakesh Patel) writes: |I had (and still have) a problem getting the X11R2 server to run |properly on a Sun 4/260C. It attempts to autoconfigure for the |appropriate board. Its find the cgtwo board, succefully opens it ... |but fails in an mmap call... then finds the bwtwo and runs. However, |since I am running with the color monitor, I never see anything on |the color monitor. Here is the error it returns: In article <490@lamont.Columbia.edu> rbd@lamont.Columbia.edu (roger davis) writes: >Has anyone had any success with Release 2 on Sun high-res monochrome >monitors? Look at XSun(1), "BUG" number 3, regarding having only the correct special files in /dev for the monitor and frame buffer you have actually attached. Our 3/260C displayed the same symptoms as you describe until I rm'd /dev/bwtwo0 so that it wasn't even available to be Probe()d. Hi-res monochrome will likely be subject to the same auto-configuration constraints. -=- Bob Sutterfield, Department of Computer and Information Science The Ohio State University; 2036 Neil Ave. Columbus OH USA 43210-1277 bob@cis.ohio-state.edu or ...!att!osu-cis!bob