[1663] in Release_7.7_team

home help back first fref pref prev next nref lref last post

Re: Monitor jitter in 4-035

daemon@ATHENA.MIT.EDU (Naomi B. Schmidt)
Fri Feb 12 10:02:12 1999

To: Robert A Basch <rbasch@MIT.EDU>
Cc: ccount@MIT.EDU, cluster-services@MIT.EDU, release-team@MIT.EDU
In-Reply-To: Your message of "Fri, 12 Feb 1999 09:52:30 EST."
             <199902121452.JAA05768@kiko.mit.edu> 
Date: Fri, 12 Feb 1999 10:02:04 EST
From: "Naomi B. Schmidt" <nschmidt@MIT.EDU>


Hello Bob -

I asked you:

> Is there any way that we can make this persistent [i.e. the
>cammand that keeps the refresh rate on the 4-035 monitors at 60
>Hz] so that it doesn't need to be reissued manually with a new
>release? 

and you replied:

>Our install is explicitly doing '/usr/gfx/setmon -x 75hz'; the
>same command is executed after OS changes are applied, as was done
>in the recent patch release.  It was my understanding that this
>was done to provide better (less flicker-y) video on the O2, so
>changing this might not be the best general solution.

It appears that because of the ambient magnetic field in 4-035, a
refresh rate of 60 Hz is preferable to 75 Hz in that room, and the
new release, forcing it back to 75 Hz is what brought the problem
back.  However, since 75 Hz is probably preferable in locations
other than 4-035, it's probably best to have the Cluster Services
manually reset the 4-035 machines to 60 Hz whenever there is a new
release or when they reinstall a machine in that room.

Perhaps another thing that we can do is to put a sign up in 4-035
that if people perceive problems with the monitors to type this
command?   

		Naomi

home help back first fref pref prev next nref lref last post