[2413] in Release_7.7_team
Monitor configuration issue
daemon@ATHENA.MIT.EDU (Greg Hudson)
Wed Aug 30 15:04:54 2000
Date: Wed, 30 Aug 2000 15:04:48 -0400 (EDT)
Message-Id: <200008301904.PAA12079@small-gods.mit.edu>
From: Greg Hudson <ghudson@MIT.EDU>
To: release-team@MIT.EDU
I have looked into the monitor configuration issue. Here are the
facts as far as I can determine:
* If you do not do a custom install, we run the following commands:
mouseconfig --kickstart
Xconfigurator --kickstart --hsync 30-96 --vsync 48-120
So we are the ones setting the sync ranges.
* XFree86 3.x does not appear to have any support at all for
talking to monitors; that was a fiction. So if a custom X
install is not done, all we can do is guess. If we guess
conservatively, we will not take advantage of our cluster
monitors; if we we guess liberally, we can overdrive
monitors on other types of machines.
Since we do not have any tools which can talk to monitors,
we cannot determine at boot time or at any other time
whether a machine has a cluster-quality monitor or not. (We
could guess based on the other hardware, but that wouldn't
be a very robust guess.)
I am looking into whether XFree86 4.x will help with the second issue.
Even if it does, that's probably not interested until next summer,
unless there is some separable tool we can pull out of it and use to
query the monitor at boot time.
