On 9 Oct 2002, Michel [ISO-8859-1] D�nzer wrote:
> [...]
>
> > Section "Monitor"
> > Identifier "Generic LCD Panel 1024x768"
> > VendorName "Unknown"
> > ModelName "Unknown"
> > HorizSync 31.5-48.5
> > VertRefresh 40-70
>
> [...]
>
> > (II) R128(0): Generic LCD Panel 1024x768: Using hsync range of
> > 31.50-48.50 kHz
> > (II) R128(0): Generic LCD Panel 1024x768: Using vrefresh range of
> > 40.00-70.00 Hz
> > (II) R128(0): Clock range: 12.50 to 250.00 MHz
> > (II) R128(0): Not using mode "640x480" (hsync out of range)
> > (II) R128(0): Not using mode "640x480" (hsync out of range)
>
> No, it's not ignoring the sync ranges you provide. ;)
I have looked into this a bit while working on Don Hardaway's problem,
which seems to be more or less the same issue. One odd thing that I saw was
that you have to up the VertRefresh way past the frequencies that the driver
reports it is using. For examples
(II) R128(0): Monitor0: Using hsync range of 30.00-90.00 kHz
(II) R128(0): Monitor0: Using vrefresh range of 30.00-120.00 Hz
(II) R128(0): Clock range: 12.50 to 250.00 MHz
yet the driver indicates that it is using something much lower
R128(0): Mode "1024x768": 108.0 MHz, 64.8 kHz, 82.6 Hz
(II) R128(0): Modeline "1024x768" 108.00 1024 1072 1086 1312 768 769 772 784
+hsync +vsync
It made me think that something isn't being calculated right, but I have
not chased it down any further than this.
Stuart
Stuart R. Anderson [EMAIL PROTECTED]
Network & Software Engineering http://www.netsweng.com/
1024D/37A79149: 0791 D3B8 9A4C 2CDC A31F
BD03 0A62 E534 37A7 9149
_______________________________________________
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert
