On Fri, 24 Oct 2003, Leonardo Canducci wrote: > On Thu, Oct 23, 2003 at 06:55:37PM -0700, Mark Vojkovich wrote: > > > (WW) NVIDIA(0): The user specified HorizSync "52.000-95.000" has been > > > adjusted > > > (WW) NVIDIA(0): to "52.000-83.000" (the intersection with > > > EDID-specified > > > (WW) NVIDIA(0): HorizSync "30.000-83.000") > > > (II) NVIDIA(0): AcerAL718: Using hsync range of 52.00-83.00 kHz > > > (II) NVIDIA(0): AcerAL718: Using vrefresh range of 50.00-75.00 Hz > > > (II) NVIDIA(0): Clock range: 12.00 to 350.00 MHz > > > ... > > > > > > so hsync and v sync are changed. why? and more on: > > > > Because your monitor says it can't do above 83kHz. According > > to the monitor EDID, your hsyc range is 30.000-83.000. > > > > > what's that EDID thing? why is my display called CRT? how could I fix > > > things to use both 1280, 1024 and 800 resolutions? > > > > The EDID is the block of information the monitor gave the graphics > > card about its capabilities. You should specify 30.000-83.000 > > for your HorizSync range. > > thank you so much! now I've set hsync 30-83 and 800x600 mode works fine. > I supposed I could trust acer.com specifications... and I was wrong. > as always even good brands cheat people about specs (not to mention that > vsync and hsync are not even reportend in the 4 pages stupid manual that > came with my display). I wish they could care more about linux users. > > anyway is there a way to probe vsync too with edid? > where could I learn more about edid? I think if you start the server verbosely it prints the whole EDID out into the XFree86.0.log file. Eg. "startx -- -logverbose 6" > > bye > > PS btw: dpms stands for Display Power Management Signaling and should > have nothing to do with my problem. am I right? DPMS doesn't have anything to do with which modes work and which don't, if that's what you mean. Mark. _______________________________________________ XFree86 mailing list XFree86@xxxxxxxxxxx http://XFree86.Org/mailman/listinfo/xfree86
