Go Back   nV News Forums > Linux Support Forums > NVIDIA Linux

Newegg Daily Deals

Reply
 
Thread Tools
Old 09-18-07, 09:50 PM   #1
cyruspy
Registered User
 
Join Date: Sep 2007
Posts: 10
Default 100.14.19 and XFX 6800XT

Hi, i'm running Suse 10.1@x86_64 with an XFX 6800XT and a LG L203WT. Today updated the nvidia driver with NVIDIA-Linux-x86_64-100.14.19-pkg2.run, and the max resolution was reduced from 1680x1050 to 1280x1024.

Does anybody know how to solve this?
Attached Files
File Type: zip nvidia-bug-report.zip (38.3 KB, 105 views)
cyruspy is offline   Reply With Quote
Old 09-18-07, 10:34 PM   #2
zander
NVIDIA Corporation
 
zander's Avatar
 
Join Date: Aug 2002
Posts: 3,740
Default Re: 100.14.19 and XFX 6800XT

Which driver did you upgrade from? Please run X with -logverbose 6 and generate/attach another nvidia-bug-report.log file.
zander is offline   Reply With Quote
Old 09-18-07, 11:37 PM   #3
cyruspy
Registered User
 
Join Date: Sep 2007
Posts: 10
Default Re: 100.14.19 and XFX 6800XT

When it was working fine, i was using 1.0.8776 from ftp://download.nvidia.com/novell/sle10/x86_64/

Then removed those packages and upgraded to 100.14.11 with the generic installer, got the same issue and tried the 100.14.19 to see if it's corrected there, without luck
Attached Files
File Type: bz2 nvidia-bug-report.log.bz2 (42.0 KB, 111 views)
cyruspy is offline   Reply With Quote
Old 09-19-07, 02:34 PM   #4
AaronP
NVIDIA Corporation
 
AaronP's Avatar
 
Join Date: Mar 2005
Posts: 2,487
Default Re: 100.14.19 and XFX 6800XT

Hi cyruspy,

According to your log file, your flat panel reports 1280x1024 as its native resolution, and the driver is using this information to validate your modes. Unfortunately, there's currently no easy way to tell the driver to work around this particular flat panel quirk. Your best bet is to save the EDID to a file with nvidia-settings, edit it to fix the order of the two detailed timings, and then use the CustomEdid option to override the one read from the panel.

I've filed enhancement request 351824 to get an easier override implemented.
AaronP is offline   Reply With Quote
Old 09-19-07, 02:56 PM   #5
pe1chl
Registered User
 
Join Date: Aug 2003
Posts: 1,026
Default Re: 100.14.19 and XFX 6800XT

Quote:
Originally Posted by AaronP
Hi cyruspy,

According to your log file, your flat panel reports 1280x1024 as its native resolution, .... there's currently no easy way to tell the driver to work around this particular flat panel quirk.
As this is not the first panel that "reports the wrong native resolution", I have tried to find some info about this topic.
There is a document from VESA titled VESA ENHANCED EXTENDED DISPLAY
IDENTIFICATION DATA Implementation Guide, found at http://www.vesa.org/public/EEDIDguideV1.pdf
This document describes the structure of the EDID data.

Studying this, I found before that there is no field in the EDID that gives the native resolution. There are fields that describe usable timings, and even preferred timing. But nowhere it is stated that native resolution can somehow be derived from those values.

Reading it again, I see this paragraph:

4.7.3 Preferred timing does not mean maximum addressability
The preferred timing mode does not necessarily indicate the highest format capability of the display and should not be interpreted as such. This can only be interpreted by examining all the display modes expressed in EDID.


If I interpret this correctly, then NVIDIA's method of determining "native resolution" is not valid at all. This could explain why there are so many panels that exhibits "quirks" in the EDID data. maybe the quirk really is in the driver, that interprets the "preferred timing" as "native resolution" while the VESA document says that this should not be done that way?

In the case of the mentioned LG panel, there is a timing for the native resolution and it is invalidated by the driver. I have seen this same phenomenon in many other bugreports after driver revision somewhere in the 9000 range.

Probably your enhancement request would better be rewritten as a request to modify the logic that determines the native resolution. It looks like it is flawed.
pe1chl is offline   Reply With Quote
Old 09-20-07, 10:01 AM   #6
cyruspy
Registered User
 
Join Date: Sep 2007
Posts: 10
Default Re: 100.14.19 and XFX 6800XT

Quote:
Originally Posted by AaronP
Hi cyruspy,

According to your log file, your flat panel reports 1280x1024 as its native resolution, and the driver is using this information to validate your modes. Unfortunately, there's currently no easy way to tell the driver to work around this particular flat panel quirk. Your best bet is to save the EDID to a file with nvidia-settings, edit it to fix the order of the two detailed timings, and then use the CustomEdid option to override the one read from the panel.

I've filed enhancement request 351824 to get an easier override implemented.
Got a edid.bin file using nvidia-settings. How should i edit it?, it's a binary file...
cyruspy is offline   Reply With Quote
Old 09-20-07, 10:06 AM   #7
cyruspy
Registered User
 
Join Date: Sep 2007
Posts: 10
Default Re: 100.14.19 and XFX 6800XT

Quote:
Originally Posted by pe1chl
As this is not the first panel that "reports the wrong native resolution", I have tried to find some info about this topic.
There is a document from VESA titled VESA ENHANCED EXTENDED DISPLAY
IDENTIFICATION DATA Implementation Guide, found at http://www.vesa.org/public/EEDIDguideV1.pdf
This document describes the structure of the EDID data.

Studying this, I found before that there is no field in the EDID that gives the native resolution. There are fields that describe usable timings, and even preferred timing. But nowhere it is stated that native resolution can somehow be derived from those values.

Reading it again, I see this paragraph:

4.7.3 Preferred timing does not mean maximum addressability
The preferred timing mode does not necessarily indicate the highest format capability of the display and should not be interpreted as such. This can only be interpreted by examining all the display modes expressed in EDID.


If I interpret this correctly, then NVIDIA's method of determining "native resolution" is not valid at all. This could explain why there are so many panels that exhibits "quirks" in the EDID data. maybe the quirk really is in the driver, that interprets the "preferred timing" as "native resolution" while the VESA document says that this should not be done that way?

In the case of the mentioned LG panel, there is a timing for the native resolution and it is invalidated by the driver. I have seen this same phenomenon in many other bugreports after driver revision somewhere in the 9000 range.

Probably your enhancement request would better be rewritten as a request to modify the logic that determines the native resolution. It looks like it is flawed.
Well, obviously something changed in the detection procedure, taking a look at a old log file from July (using the old driver), i get:
Code:
(II) NVIDIA(0): Detected PCI Express Link width: 16X
(--) NVIDIA(0): Interlaced video modes are supported on this GPU
(--) NVIDIA(0): Connected display device(s) on GeForce 6800 XT at PCI:2:0:0:
(--) NVIDIA(0):     LG L203WT (DFP-1)
(--) NVIDIA(0): LG L203WT (DFP-1): 155.0 MHz maximum pixel clock
(--) NVIDIA(0): LG L203WT (DFP-1): Internal Single Link TMDS
(II) NVIDIA(0): Assigned Display Device: DFP-1
(WW) NVIDIA(0): No valid modes for "1600x1000"; removing.
(WW) NVIDIA(0): No valid modes for "1440x900"; removing.
(WW) NVIDIA(0): No valid modes for "1366x768"; removing.
(WW) NVIDIA(0): No valid modes for "1280x800"; removing.
(WW) NVIDIA(0): No valid modes for "1280x768"; removing.
(WW) NVIDIA(0): No valid modes for "1280x600"; removing.
(WW) NVIDIA(0): No valid modes for "1024x600"; removing.
(WW) NVIDIA(0): No valid modes for "768x576"; removing.
(II) NVIDIA(0): Validated modes:
(II) NVIDIA(0):     "1680x1050"
(II) NVIDIA(0):     "1600x1024"
(II) NVIDIA(0):     "1400x1050"
(II) NVIDIA(0):     "1280x1024"
(II) NVIDIA(0):     "1280x960"
(II) NVIDIA(0):     "1152x864"
(II) NVIDIA(0):     "1024x768"
(II) NVIDIA(0):     "800x600"
(II) NVIDIA(0):     "640x480"
(II) NVIDIA(0): Virtual screen size determined to be 1680 x 1050
(--) NVIDIA(0): DPI set to (75, 96); computed from "UseEdidDpi" X config option
Attached Files
File Type: log Xorg.2.log (31.5 KB, 90 views)
cyruspy is offline   Reply With Quote
Old 09-20-07, 09:12 PM   #8
cyruspy
Registered User
 
Join Date: Sep 2007
Posts: 10
Default Re: 100.14.19 and XFX 6800XT

Quote:
Originally Posted by cyruspy
Got a edid.bin file using nvidia-settings. How should i edit it?, it's a binary file...
Anyone?
cyruspy is offline   Reply With Quote

Old 09-21-07, 02:32 AM   #9
firewalker
Registered User
 
Join Date: Mar 2005
Location: Ellas
Posts: 32
Default Re: 100.14.19 and XFX 6800XT

With a hex editor ? E.g. ghex2 in gnome.

In any case I have a 6800GS and a LG204WT and it works at 1680x1050.
firewalker is offline   Reply With Quote
Old 09-24-07, 09:53 PM   #10
cyruspy
Registered User
 
Join Date: Sep 2007
Posts: 10
Default Re: 100.14.19 and XFX 6800XT

Quote:
Originally Posted by firewalker
With a hex editor ? E.g. ghex2 in gnome.
I know, but what should be modified exactly?

0000000000 000 377 377 377 377 377 377 000 036 155 076 116 011 153 000 000 ...m>N.k..
0000000016 014 020 001 003 356 053 033 170 352 306 005 243 127 112 235 045 ....+.x.WJ.%
0000000032 022 120 124 247 153 200 201 200 161 117 001 001 001 001 001 001 .PTk...qO......
0000000048 001 001 001 001 001 001 060 052 000 230 121 000 052 100 060 160 ......0*..Q.*@0p
0000000064 023 000 262 016 021 000 000 036 174 056 220 240 140 032 036 100 .......|.. `..@
0000000080 060 040 066 000 262 016 021 000 000 000 000 000 000 375 000 070 0 6..........8
0000000096 125 034 123 016 000 012 040 040 040 040 040 040 000 000 000 374 U.S... ...
0000000112 000 114 062 060 063 127 124 012 040 040 040 040 040 040 000 144 .L203WT. .d
0000000128


Quote:
Originally Posted by firewalker
In any case I have a 6800GS and a LG204WT and it works at 1680x1050.
With the latest driver?
cyruspy is offline   Reply With Quote
Old 09-25-07, 01:49 AM   #11
firewalker
Registered User
 
Join Date: Mar 2005
Location: Ellas
Posts: 32
Default Re: 100.14.19 and XFX 6800XT

Quote:
Originally Posted by cyruspy
I know, but what should be modified exactly?
Sorry I cant help you with this. You could look at the driver cd if there
is an EDID file or search the forum.

Find attached the L204WT monitor EDID file in case it helps.
WARNING please note this is for L204WT and there might be a chance damaging your monitor if you use this edid.

Quote:
Originally Posted by cyruspy
With the latest driver?
Yes.
Attached Files
File Type: zip L204WT.zip (267 Bytes, 291 views)
firewalker is offline   Reply With Quote
Old 09-29-07, 05:00 PM   #12
cyruspy
Registered User
 
Join Date: Sep 2007
Posts: 10
Default Re: 100.14.19 and XFX 6800XT

Thanks, but i'll give the nvidia folks some more time, maybe they can get this fixed (or rolled back as it was working on old versions)
cyruspy is offline   Reply With Quote
Reply


Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


All times are GMT -5. The time now is 10:17 PM.


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