[2414] in Release_7.7_team
Re: Monitor configuration issue
daemon@ATHENA.MIT.EDU (Greg Hudson)
Wed Aug 30 15:31:16 2000
Date: Wed, 30 Aug 2000 15:31:10 -0400 (EDT)
Message-Id: <200008301931.PAA12242@small-gods.mit.edu>
From: Greg Hudson <ghudson@MIT.EDU>
To: Greg Hudson <ghudson@MIT.EDU>
Cc: release-team@MIT.EDU
In-Reply-To: <200008301904.PAA12079@small-gods.mit.edu>
> Since we do not have any tools which can talk to monitors,
Ken Raeburn pointed me at a small tool called read-edid, which does
not appear to be part of XFree 3.x, which can talk to the monitor. I
verified that it seems to get sync rates for:
* The kind of monitor which came with the GX1
* The newish Sun VGA monitor I happen to have on my test
machine
I can check on the GX110 monitors as soon as I can get a root shell on
a machine with that kind of monitor, but it seems very likely that
they will work too.
So, we could dump read-edid into the install miniroot, run it, and
choose a more conservative default when it fails. That would solve
all the problems except that a cluster machine might change monitors
between the time it is installed and when it is deployed. To solve
that problem, we would need to get read-edid into the release and
reconfigure the sync rates at boot time.
> I am looking into whether XFree86 4.x will help with the second
> issue.
According to the read-edid page, "XFree86 4 (but not version 3)
integrates this functionality on some video cards, so read-edid isn't
needed then." So when there is a Red Hat release including XFree86 4,
we can probably ditch read-edid and just use native materials.
