Subject: Re: X windows problem
To: None <hibitek@globalserve.net>
From: Robert Alexander Baxter <alex@santa.asf.alaska.edu>
List: netbsd-help
Date: 06/18/1998 12:20:24
Igor wrote:
> 
> I recommend you do not mess with the RAMDAC ...; This question about
> chipset is not for a beginner!!! You may burn your terminal. I think the
> first thing to establish is what is on the server side. It provides logs
> that also show most of the  problems with the server.
> 

I disagree.  Knowing exactly which chipset, RAMDAC, etc. you
have is a good idea for anyone using XFree86.  I think you
will be less likely to hurt something if you are running the
server with the exactly correct hardware parameters to begin with.

Besides, you will only hurt your monitor if you push the refresh
rates (Hsync, Vsync) too high.  If you have correctly entered your
monitor's timing values into the XF86Config file, changing the
RAMDAC will not change the refresh rates which the XFree86 server
throws out or keeps.  It might change the refresh rates the server
would consider using if you told it you had a 200MHz versus a 175MHz
RAMDAC, for instance, but it would still compare the chosen modes
with your monitor timings before choosing which modes to allow switching
to.

>
> Robert Alexander Baxter wrote:
> 
> > Dave Clark wrote:
> > >
> > > I'm running xwindows on the 1.3.1 i386 port.  Xwindows is
> > > basically fine but I've had one problem since I started:
> > > the actual pointer only appears on my screen as a grey
> > > square.  I'm new to xwindows so I'm unsure how to proceed.
> > >
> >
> > Perhaps there is a problem with your particular X server
> > not programming your video adapter's hardware cursor
> > correctly.  This may not be something which you can fix
> > with X commands and/or utilities.
> >
> > What kind of video adapter (brand, model number, chipset,
> > chipset version, memory size, RAMDAC type and version) are
> > you using?
> >
> > -Alex (:-)
> >  alex@santa.asf.alaska.edu
>