nV News Forums

 
 

nV News Forums (http://www.nvnews.net/vbulletin/index.php)
-   NVIDIA Linux (http://www.nvnews.net/vbulletin/forumdisplay.php?f=14)
-   -   Screen mode validation (http://www.nvnews.net/vbulletin/showthread.php?t=84735)

Surmoka 01-21-07 01:40 PM

Screen mode validation
 
Hi,

I'm trying to get my 20" TFT monitor (Fujitsu-Siemens Scaleoview s20-1w) running at a 75Hz refresh rate. The native resolution is 1680x1050, I'm using DVI, and on my Geforce 6600 card with driver version 1.0-9629 (1.0-9746 gave me a lockup, but according to the changelog, it shouldn't make any real differences for me anyway) this is what I get using EDID:

(--) NVIDIA(0): DFP-0: 155.0 MHz maximum pixel clock

Taking that into account, the timings I'm trying to force on the poor critter are:

ModeLine "1680x1050" 152.86 1680 1712 1856 1912 1050 1051 1056 1066 #75Hz

and here's a snippet from what I get via a 9th level verbosity in the X server log:

(II) NVIDIA(0): Validating Mode "1680x1050":
(II) NVIDIA(0): 1680 x 1050 @ 75 Hz
(II) NVIDIA(0): Mode Source: X Configuration file ModeLine
(II) NVIDIA(0): Pixel Clock : 152.86 MHz
(II) NVIDIA(0): HRes, HSyncStart : 1680, 1712
(II) NVIDIA(0): HSyncEnd, HTotal : 1856, 1912
(II) NVIDIA(0): VRes, VSyncStart : 1050, 1051
(II) NVIDIA(0): VSyncEnd, VTotal : 1056, 1066
(II) NVIDIA(0): H/V Polarity : +/+
(WW) NVIDIA(0): Mode is rejected: Mode (1680 x 1050) is too large for DFP
(WW) NVIDIA(0): Native Resolution (Max: 640 x 480).

Now that's beyond me where it gets that 640x480 from. Interestingly, it "falls back" to 1680x1050 using nvidia-auto-select and switches to the correct native resolution, using 60Hz refresh rate.

Could someone enlighten me concerning this matter? Is there any way to convince the driver that the native resolution is a bit higher than 640x480?

(I know TFT screens don't flicker at 60Hz, it's not why I'm trying to run it at 75Hz. It's the number of frames per second displayed on my monitor I want to increase.)

thanks in advance,
s.

xbobmx 01-21-07 01:52 PM

Re: Screen mode validation
 
See http://us.download.nvidia.com/XFree8...ppendix-d.html under the heading "Option "ModeValidation"". You probably want

Option "ModeValidation" "NoDFPNativeResolutionCheck".

zander 01-21-07 02:10 PM

Re: Screen mode validation
 
Please also see http://www.nvnews.net/vbulletin/showthread.php?t=46678; an nvidia-bug-report.log file generated after X has been started with -logverbose 6 would provide more information on where the incorrect native resolution came from.

Surmoka 01-22-07 04:49 AM

Re: Screen mode validation
 
1 Attachment(s)
Thanks for the replies.

Strangely enough, after applying NoDFPNativeResolutionCheck into the X config file, the driver - still invalidating my precious 1680x1050 - says:

(WW) NVIDIA(0): Native Resolution (Max: 1440 x 900).

and there's no indication of where this assessment may be coming from.
I don't have an nvidia-bug-report.log file currently at hand (I'm at wr0k), only an X server log done with -logverbose -6 which I'm trying to attach now.

I'm absolutely unsure of this being a bug, a feature, neither or both. Just curious.

AaronP 01-22-07 11:53 AM

Re: Screen mode validation
 
According to the bug report you attached, 1680x1050 is being rejected because its vertical refresh rate (59.9 Hz) doesn't match the range specified (exactly 75.0 Hz). You'll need to remove the 75 Hz constraint from xorg.conf if you want to run that mode:
Code:

(II) NVIDIA(0): Display Device found referenced in MetaMode: DFP-0
(II) NVIDIA(0): Mode Validation Overrides for FUS S20-1W (DFP-0):
(II) NVIDIA(0):    AllowNon60HzDFPModes
(II) NVIDIA(0): Frequency information for FUS S20-1W (DFP-0):
(II) NVIDIA(0):  HorizSync  : 30.000-82.000 kHz
(II) NVIDIA(0):  VertRefresh : 75.000 Hz
(II) NVIDIA(0):    (HorizSync from EDID)
(II) NVIDIA(0):    (VertRefresh from VertRefresh X Config Option)
(II) NVIDIA(0):
(II) NVIDIA(0): --- Building ModePool for FUS S20-1W (DFP-0) ---
(II) NVIDIA(0):  Validating Mode "1680x1050":
(II) NVIDIA(0):    1680 x 1050 @ 60 Hz
(II) NVIDIA(0):    For use as DFP backend.
(II) NVIDIA(0):    Mode Source: EDID
(II) NVIDIA(0):      Pixel Clock      : 146.25 MHz
(II) NVIDIA(0):      HRes, HSyncStart : 1680, 1784
(II) NVIDIA(0):      HSyncEnd, HTotal : 1960, 2240
(II) NVIDIA(0):      VRes, VSyncStart : 1050, 1053
(II) NVIDIA(0):      VSyncEnd, VTotal : 1059, 1089
(II) NVIDIA(0):      H/V Polarity    : +/+
(WW) NVIDIA(0):    Mode is rejected: VertRefresh (60.0 Hz) out of range
(WW) NVIDIA(0):    (75.000 Hz).


Surmoka 01-23-07 03:49 AM

Re: Screen mode validation
 
Quote:

Originally Posted by AaronP
According to the bug report you attached, 1680x1050 is being rejected because its vertical refresh rate (59.9 Hz) doesn't match the range specified (exactly 75.0 Hz). You'll need to remove the 75 Hz constraint from xorg.conf if you want to run that mode:
Code:

(II) NVIDIA(0): Display Device found referenced in MetaMode: DFP-0
(II) NVIDIA(0): Mode Validation Overrides for FUS S20-1W (DFP-0):
(II) NVIDIA(0):    AllowNon60HzDFPModes
(II) NVIDIA(0): Frequency information for FUS S20-1W (DFP-0):
(II) NVIDIA(0):  HorizSync  : 30.000-82.000 kHz
(II) NVIDIA(0):  VertRefresh : 75.000 Hz
(II) NVIDIA(0):    (HorizSync from EDID)
(II) NVIDIA(0):    (VertRefresh from VertRefresh X Config Option)
(II) NVIDIA(0):
(II) NVIDIA(0): --- Building ModePool for FUS S20-1W (DFP-0) ---
(II) NVIDIA(0):  Validating Mode "1680x1050":
(II) NVIDIA(0):    1680 x 1050 @ 60 Hz
(II) NVIDIA(0):    For use as DFP backend.
(II) NVIDIA(0):    Mode Source: EDID
(II) NVIDIA(0):      Pixel Clock      : 146.25 MHz
(II) NVIDIA(0):      HRes, HSyncStart : 1680, 1784
(II) NVIDIA(0):      HSyncEnd, HTotal : 1960, 2240
(II) NVIDIA(0):      VRes, VSyncStart : 1050, 1053
(II) NVIDIA(0):      VSyncEnd, VTotal : 1059, 1089
(II) NVIDIA(0):      H/V Polarity    : +/+
(WW) NVIDIA(0):    Mode is rejected: VertRefresh (60.0 Hz) out of range
(WW) NVIDIA(0):    (75.000 Hz).


With all due respect, this is a misunderstanding. There are more tries from the driver to validate a suitable 1680x1050 mode and the 75Hz one I specified explicitely gets removed because of the native resolution being allegedly 1440x900 at max.
I don't want to remove the 75Hz constraint since it's the very point of the whole mess from my part: to get it running at 75Hz.

AaronP 01-23-07 12:50 PM

Re: Screen mode validation
 
Oh, I'm sorry, I misunderstood because the 60Hz mode is listed as the native mode for the panel. In this case you do need the "NoDFPNativeResolutionCheck" override. According to the log, only the "AllowNon60HzDFPModes" override is being applied.

Surmoka 01-23-07 04:43 PM

Re: Screen mode validation
 
Quote:

Originally Posted by AaronP
Oh, I'm sorry, I misunderstood because the 60Hz mode is listed as the native mode for the panel. In this case you do need the "NoDFPNativeResolutionCheck" override. According to the log, only the "AllowNon60HzDFPModes" override is being applied.

Thanks for pointing that out, I thought I already applied that option by specifying "NoDFPNativeResolutionCheck" with a new line of Modevalidation directive. However, it was not in effect because the correct syntax is to put all modifiers into one line, separated by commas.

After forcing all my will on the monitor, I got a garbled screen with obvious line sync problems. Seems to me as raising the refresh rate above 60Hz in 1680x1050 is beyond the display capabilities in terms of pixel clock, no matter how much I tighten the mode timings (that is, narrowing the space offscreen for synchronization).
It was 75Hz though. :)

trodas 10-02-09 06:17 PM

Re: Screen mode validation
 
Very interesting.
So, a linux version of nVidia drivers let user bypass the cursed 60Hz limit?

I having very similar problem with Windows and FX5600XT Gigabite AGP card. On CRT - 100, 120 even 150Hz refresh is not a problem. Using DVI, suddently, 60Hz is the max. I can't seems to force it to 75Hz...
Check there: http://www.nvnews.net/vbulletin/show...13#post2097513

I do wonder, if the drivers CAN be modified/hacked somehow to disable this 60Hz limit for DVI. All I want is 1280x1024 in 75Hz :(


All times are GMT -5. The time now is 06:16 AM.

Powered by vBulletin® Version 3.7.1
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Copyright 1998 - 2014, nV News.