nV News Forums

 
 

nV News Forums (http://www.nvnews.net/vbulletin/index.php)
-   NVIDIA Linux (http://www.nvnews.net/vbulletin/forumdisplay.php?f=14)
-   -   [beta driver] DVI EDID problem (http://www.nvnews.net/vbulletin/showthread.php?t=78723)

romen 10-22-06 07:51 PM

[beta driver] DVI EDID problem
 
Is there any workaround for this bug?

Code:

(WW) NVIDIA(0):    Mode is rejected: Mode (1440 x 900) is too large for DFP
(WW) NVIDIA(0):    EDID (Max: 1280 x 1024).

It looks like this happens only when the monitor is linked by DVI cord, while the old style analog cord works without problem (I couldn't test this, I've only desumed it by other people experience).
The same happen with others WideScreen resolution, both in versions 9625 and 9626 (which I'm currently running).

I'd like to know if there's any temporary workaround while waiting it get fixed in further release. (There are already many bugreport about this issue so I don't report mine).

About validation process:
Code:

(II) NVIDIA(0): Frequency information for Samsung SyncMaster (DFP-0):
(II) NVIDIA(0):  HorizSync  : 30.000-81.000 kHz
(II) NVIDIA(0):  VertRefresh : 56.000-75.000 Hz
(II) NVIDIA(0):    (HorizSync from EDID)
(II) NVIDIA(0):    (VertRefresh from EDID)
(II) NVIDIA(0):
(II) NVIDIA(0): --- Building ModePool for Samsung SyncMaster (DFP-0) ---
(II) NVIDIA(0):  Validating Mode "1440x900":
(II) NVIDIA(0):    1440 x 900 @ 60 Hz
(II) NVIDIA(0):    Mode Source: EDID
(II) NVIDIA(0):      Pixel Clock      : 106.50 MHz
(II) NVIDIA(0):      HRes, HSyncStart : 1440, 1520
(II) NVIDIA(0):      HSyncEnd, HTotal : 1672, 1904
(II) NVIDIA(0):      VRes, VSyncStart :  900,  903
(II) NVIDIA(0):      VSyncEnd, VTotal :  909,  934
(II) NVIDIA(0):      H/V Polarity    : -/+
(WW) NVIDIA(0):    Mode is rejected: Mode (1440 x 900) is too large for DFP
(WW) NVIDIA(0):    EDID (Max: 1280 x 1024).


netllama 10-22-06 08:08 PM

Re: [beta driver] DVI EDID problem
 
I've not seen any bug reports for an issue like this (and there are no open bugs for it either). If you want further assistance, please start X with the following command:
startx -- -logverbose 6

and generate and attach an nvidia-bug-report.log


Thanks,
Lonni

romen 10-23-06 01:01 PM

Re: [beta driver] DVI EDID problem
 
1 Attachment(s)
Some posts I just (re-)found:

http://www.nvnews.net/vbulletin/show...1&postcount=50
http://www.nvnews.net/vbulletin/show...5&postcount=52
http://www.nvnews.net/vbulletin/show...1&postcount=56
http://www.nvnews.net/vbulletin/show...4&postcount=61
http://www.nvnews.net/vbulletin/show...1&postcount=64
http://www.nvnews.net/vbulletin/show...9&postcount=65

Yesterday I've found even other similar ones, but I cannot manage to found them again.

Anyway I've send the report to linux-bugs@nvidia.com.

netllama 10-23-06 03:01 PM

Re: [beta driver] DVI EDID problem
 
Does adding the following option have any impact?
Option "ModeValidation" "NoEdidDFPMaxSizeCheck"

Thanks,
Lonni

romen 10-23-06 03:19 PM

Re: [beta driver] DVI EDID problem
 
Yes, it solve the problem temporary. Thank you very much.

Will it be solved in the next release?

Again thank you very much for the great work!!

Nicola

netllama 10-23-06 03:24 PM

Re: [beta driver] DVI EDID problem
 
I'd like to see a bug report against 1.0-8776 where that option isn't needed.

Bloot 10-24-06 02:15 PM

Re: [beta driver] DVI EDID problem
 
Hey many thanks for this!. I added that option to my Monitor Section in the xorg.conf and now I can use my 1440x900 native resolution through the DVI connection, I tried almost anything (use edid false, many modelines, 1440x900 only resolution in subsection display...) but nothing did the trick, nothing but this!.

Again many thanks.

crypticreign 10-26-06 10:39 AM

Re: [beta driver] DVI EDID problem
 
Quote:

Originally Posted by netllama
Does adding the following option have any impact?
Option "ModeValidation" "NoEdidDFPMaxSizeCheck"

This didn't work for me. I have to use the Analog/VGA (instead of DVI) to get my monitor's native resolution (1680x1050). I've tried using Modelines and everything too.

I have a Nvidia GeForce 5600XT w/ Samsung SyncMaster 20.1" 205BW display.

netllama 10-26-06 11:30 AM

Re: [beta driver] DVI EDID problem
 
please start X with the following command:
startx -- -logverbose 6

and generate and attach an nvidia-bug-report.log


Thanks,
Lonni

crypticreign 10-27-06 08:32 PM

Re: [beta driver] DVI EDID problem
 
Received this error

"nvidia-bug-report.log:
Your file of 206.7 KB bytes exceeds the forum's limit of 146.9 KB for this filetype."

So, here -- http://cr.pi.cx/nvidia-bug-report.log

netllama 10-27-06 08:36 PM

Re: [beta driver] DVI EDID problem
 
Here's the problem:
(--) NVIDIA(0): Samsung SyncMaster (DFP-0): 140.4 MHz maximum pixel clock


Your 1680x1050 mode requires a 146.25Mhz pixelclock which your graphics card is unable to provide:
(--) NVIDIA(0): Detailed Timings:
(--) NVIDIA(0): 1680 x 1050 @ 60 Hz
(--) NVIDIA(0): Pixel Clock : 146.25 MHz
(--) NVIDIA(0): HRes, HSyncStart : 1680, 1784
(--) NVIDIA(0): HSyncEnd, HTotal : 1960, 2240
(--) NVIDIA(0): VRes, VSyncStart : 1050, 1053
(--) NVIDIA(0): VSyncEnd, VTotal : 1059,

crypticreign 10-27-06 08:54 PM

Re: [beta driver] DVI EDID problem
 
Quote:

Originally Posted by netllama
Here's the problem:
(--) NVIDIA(0): Samsung SyncMaster (DFP-0): 140.4 MHz maximum pixel clock


Your 1680x1050 mode requires a 146.25Mhz pixelclock which your graphics card is unable to provide:
(--) NVIDIA(0): Detailed Timings:
(--) NVIDIA(0): 1680 x 1050 @ 60 Hz
(--) NVIDIA(0): Pixel Clock : 146.25 MHz
(--) NVIDIA(0): HRes, HSyncStart : 1680, 1784
(--) NVIDIA(0): HSyncEnd, HTotal : 1960, 2240
(--) NVIDIA(0): VRes, VSyncStart : 1050, 1053
(--) NVIDIA(0): VSyncEnd, VTotal : 1059,

I see. Any idea on a cheap video card that will provide that?


All times are GMT -5. The time now is 03:56 AM.

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