Stephen Powell wrote: > On 2010-01-11 at 15:52:56 -0500, Stanisław T. Findeisen wrote: >> I tried "VertRefresh 85" because I know this monitor can handle 1024x768 >> @ 85 Hz (well, at least it used to several years ago). Unfortunately the >> error I am getting now is: "vrefresh out of range" and I am only able to >> run X at: >> >> 720x400x16 @ 85Hz, or >> 800x600x16 @ 60Hz > > Well, we're making progress. Your monitor apparently does not support > DDC2/EDID; so the X server does not know what your monitor's horizontal > and vertical sync frequency ranges are. You have to tell it. The "safe" > assumptions that the X server is making are well below your monitor's > capabilities. What are those sync frequency ranges? > You probably don't need to compose your own modeline though. Let's see. > You told me that your monitor is a Samsung SyncMaster 550b. According to > the owner's manual, which I found on the Internet, the horizontal sync > frequency range is 30 kHz to 70 kHz, and the vertical sync frequency range > is 50 Hz to 160 Hz. The video bandwidth (maximum pixel clock) is 110 MHz. > That's less than the maximum pixel clock rate supported by the video card; > so you should be OK there, as we can see from > >> (--) s3(0): Max pixel clock at this depth is 80 Mhz Less?? > So your monitor section (you should have only one monitor section) > should look something like this: > > Section "Monitor" > Identifier "Configured Monitor" > VendorName "Samsung" > ModelName "SyncMaster 550b" > HorizSync 30-70 > VertRefresh 50-160 > Option "TargetRefresh" "75" > EndSection > > The "TargetRefresh" option is optional. If used, it will try to use only > video modes of 75 Hz vertical sync or higher. Give that a whirl and see > what happens. Make sure that you are specifying the color depth as 16 > (DefaultDepth 16 in the "Screen" section). With this I am able to run 1024x768x16 @ 75 Hz! However, I wanted 85 Hz. (**) s3(0): *Default mode "1024x768": 78.8 MHz, 60.0 kHz, 75.0 Hz (II) s3(0): Modeline "1024x768"x75.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz) (**) s3(0): Default mode "1024x768": 75.0 MHz, 56.5 kHz, 70.1 Hz (II) s3(0): Modeline "1024x768"x70.1 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz) (**) s3(0): Default mode "1024x768": 65.0 MHz, 48.4 kHz, 60.0 Hz (II) s3(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz) (**) s3(0): Default mode "1024x768": 44.9 MHz, 35.5 kHz, 87.0 Hz (I) (II) s3(0): Modeline "1024x768"x87.0 44.90 1024 1032 1208 1264 768 768 776 817 interlace +hsync +vsync (35.5 kHz) Why, in the log lines above, (((pixel clock rate) / ((v-res) * (h-res))) != v-refresh)? Here: http://en.wikipedia.org/wiki/XFree86_Modeline they say that there should be equality. For instance: in the 1st line, 78.8 MHz / (1024*768) > 100, but the horizontal refresh rate is less: 75 Hz. For instance: in the last line, 44.9 MHz / (1024*768) = 57, but the horizontal refresh rate is more: 87 Hz. Where do those modes come from, if there are none in the config file and my monitor does not support EDID? I can also see that the monitor mode I want (1024x768 / 94.5 Mhz / 68.677 kHz / 85 Hz from the monitor manual) is not on the list. Why? What do those line prefixes ((--), (==), (**), (WW), (II) etc.) in the log stand for? I would guess (WW) stands for "warning", but all the rest looks like "notice"... I also tried TargetRefresh=85 but with no success. I would say maximum pixel clock rate supported by the video card is 80 MHz and *that* is the limit?... STF http://eisenbits.homelinux.net/~stf/ OpenPGP: DFD9 0146 3794 9CF6 17EA D63F DBF5 8AA8 3B31 FE8A
Attachment:
signature.asc
Description: OpenPGP digital signature