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

Newegg Daily Deals

Reply
 
Thread Tools
Old 01-09-06, 07:29 AM   #1
alex31
Registered User
 
Join Date: Dec 2002
Posts: 47
Default not able to drive ibm t221 3840x2400 screen with 81.78 (was ok with 76.76)

have tried to upgrade from 76.76 to 81.78 a box which drive an ibm t221 3840*2400 screen.
Whith 76.76, i had found the modeline to achieve that :

http://www.nvnews.net/vbulletin/show...highlight=t221

But with 81.78, theses modelines no more works : i have in the Xorg.0.log :
Not using default mode "2624x2400" (bad mode clock/interlace/doublescan)

with 76.76 i had theses :
(**) NVIDIA(0): Mode "2624x2400": 211.2 MHz, 73.7 kHz, 59.8 Hz (I)

I have tried to use the get-edid function of the nvidia-settings control panel, it gives me others modelines :

# Monitor preferred modeline (48.0 Hz vsync, 117.8 kHz hsync, ratio 1.09) (bad ratio)
ModeLine "2624x2400" 328 2624 2672 2704 2784 2400 2402 2412 2455 -hsync +vsync

# Monitor preferred modeline (48.0 Hz vsync, 117.8 kHz hsync, ratio 0.51) (bad ratio)
ModeLine "1216x2400" 164 1216 1264 1296 1392 2400 2402 2412 2455 -hsync +vsync

but with 81.78 theses modeline does not works neither, i have the same bad mode clock/interlace/doublescan problem ...

does anyone knows how to drive the t221 with 81.78 ?, i need to upgrade because we use stencil with frame buffer object, and 76.76 is not able to do that.

Thanks
Alexandre
alex31 is offline   Reply With Quote
Old 01-09-06, 08:40 AM   #2
EasyPrey
Registered User
 
Join Date: Dec 2005
Posts: 34
Unhappy Re: not able to drive ibm t221 3840x2400 screen with 81.78 (was ok with 76.76)

nVidia updated their validation routine for the video cards.

It greatly effects the DVI's output clock. My card went down from 400Mhz (DVI clock) to 155MHz DVI clock. Just try to look for "clock" in your Xorg.0.log. I bet it went down below 211.2 MHz (needed to drive your display).

This forum is littered with casualties (from this "bug fix"). Join the club.

I just hope nVidia is going to remove this "feature" soon.

-EasyPrey
EasyPrey is offline   Reply With Quote
Old 01-09-06, 10:25 AM   #3
alex31
Registered User
 
Join Date: Dec 2002
Posts: 47
Default Re: not able to drive ibm t221 3840x2400 screen with 81.78 (was ok with 76.76)

Quote:
Originally Posted by EasyPrey
nVidia updated their validation routine for the video cards.

It greatly effects the DVI's output clock. My card went down from 400Mhz (DVI clock) to 155MHz DVI clock. Just try to look for "clock" in your Xorg.0.log. I bet it went down below 211.2 MHz (needed to drive your display).

This forum is littered with casualties (from this "bug fix"). Join the club.

I just hope nVidia is going to remove this "feature" soon.

-EasyPrey
Oh, ok, and there is no mean to force this badly calculated max dvi clock ?,
like the edid values ?

Why does the validation routine for the video cards is not the same as in the windows drivers, where it just nicely works since ever ?

Alexandre
alex31 is offline   Reply With Quote
Old 01-09-06, 10:29 AM   #4
zander
NVIDIA Corporation
 
zander's Avatar
 
Join Date: Aug 2002
Posts: 3,740
Default Re: not able to drive ibm t221 3840x2400 screen with 81.78 (was ok with 76.76)

@alex31: please generate and post an nvidia-bug-report.log file after starting X with -logverbose 6.

@EasyPrey: the 400 MHz reported were incorrect and actually the RAMDAC's limit.
zander is offline   Reply With Quote
Old 01-09-06, 10:33 AM   #5
alex31
Registered User
 
Join Date: Dec 2002
Posts: 47
Default Re: not able to drive ibm t221 3840x2400 screen with 81.78 (was ok with 76.76)

Quote:
Originally Posted by EasyPrey

Just try to look for "clock" in your Xorg.0.log. I bet it went down below 211.2 MHz (needed to drive your display).

-EasyPrey
I have reinstalled 81.78 to see, and in fact the log report that
(II) NVIDIA(0): Connected display device(s): DFP-0, DFP-1
(--) NVIDIA(0): DFP-0: maximum pixel clock: 310 MHz
(--) NVIDIA(0): DFP-0: Internal Dual Link TMDS
(--) NVIDIA(0): DFP-1: maximum pixel clock: 310 MHz
(--) NVIDIA(0): DFP-1: Internal Single Link TMDS
(II) NVIDIA(0): Frequency information for DFP-0:
(II) NVIDIA(0): HorizSync : 29.000-117.000 kHz
(II) NVIDIA(0): VertRefresh : 12.000-85.000 Hz
(II) NVIDIA(0): (HorizSync from EDID)
(II) NVIDIA(0): (VertRefresh from EDID)
(II) NVIDIA(0): Adding EDID-provided mode "3840x2400" for DFP-0.
(II) NVIDIA(0): Adding EDID-provided mode "2624x2400" for DFP-0.
(II) NVIDIA(0): Adding EDID-provided mode "1216x2400" for DFP-0.
(II) NVIDIA(0): Adding EDID-provided mode "1920x1200" for DFP-0.


But the driver in unable to use the edid provided mode neither the custom provided mode.

Alexandre
alex31 is offline   Reply With Quote
Old 01-09-06, 10:39 AM   #6
alex31
Registered User
 
Join Date: Dec 2002
Posts: 47
Default Re: not able to drive ibm t221 3840x2400 screen with 81.78 (was ok with 76.76)

Quote:
Originally Posted by zander
@alex31: please generate and post an nvidia-bug-report.log file after starting X with -logverbose 6.
Here is the log

Thanks by advance for any help !

Alexandre
Attached Files
File Type: zip nvidia-bug-report.log.zip (24.3 KB, 115 views)
alex31 is offline   Reply With Quote
Old 01-09-06, 10:54 AM   #7
alex31
Registered User
 
Join Date: Dec 2002
Posts: 47
Default Re: not able to drive ibm t221 3840x2400 screen with 81.78 (was ok with 76.76)

Quote:
Originally Posted by alex31
Here is the log

Thanks by advance for any help !

Alexandre
Hum, the same, but with X really launched with -verbose-level 6

sorry !

Alexandre
Attached Files
File Type: zip nvidia-bug-report.log.zip (25.7 KB, 115 views)
alex31 is offline   Reply With Quote
Old 01-30-06, 02:59 AM   #8
alex31
Registered User
 
Join Date: Dec 2002
Posts: 47
Default Re: not able to drive ibm t221 3840x2400 screen with 81.78 (was ok with 76.76)

[quote=zander]@alex31: please generate and post an nvidia-bug-report.log file after starting X with -logverbose 6.

I have posted the log some time ago now, does this log has permitted to the nvidia team to see if there is possible work around with current driver, or does i have to wait for next release ?


Alexandre
alex31 is offline   Reply With Quote

Old 01-30-06, 03:53 PM   #9
netllama
NVIDIA Corporation
 
Join Date: Dec 2004
Posts: 8,763
Default Re: not able to drive ibm t221 3840x2400 screen with 81.78 (was ok with 76.76)

Based on your bug report, X is doing exactly what you've configured it to do. You're requesting 1216x2400 on DFP-0, not 3840x2400. DFP-1 is on a single link TMDS controller, and is therefore incapable of doing the 2624x2400 mode that you've specified in your Metamodes.

Perhaps what you meant is that you were getting a total of 3840x2400 across both DFPs in 1.0-7676?

Thanks,
Lonni
netllama is offline   Reply With Quote
Old 01-31-06, 08:06 AM   #10
alex31
Registered User
 
Join Date: Dec 2002
Posts: 47
Default Re: not able to drive ibm t221 3840x2400 screen with 81.78 (was ok with 76.76)

In fact, the ibm t221 screen has two dvi entries, one dual link which addresses 2/3 of the screen (2624x2400) and one single link which addresses 1/3 oh the screen (1216x2400), so from the graphic card it is seen as two screens.

In fact it's a litte more complex, you can adresses all the screen (3840x2400) with just one double dvi link, but in this case you are limited @ 24hz. If you want to use the screen at his top freq (48hz) you need to use the 2 dvi entries.

Since it do not work anymore with 8x.xx drivers, i have done several trials, and the last time i have tried, i have, like you have detected, inverted the 2624 entry and the 1216 one, putting the 2624 on the single link side.

I hace corrected this error and lauched again with -logverbose 6

But even with the good combination, it still fail.
(--) NVIDIA(0): DFP-0: maximum pixel clock: 310 MHz
(--) NVIDIA(0): DFP-0: Internal Dual Link TMDS
(II) NVIDIA(0): Mapping display device 1 (DFP-1) to CRTC 1
(--) NVIDIA(0): DFP-1: maximum pixel clock: 310 MHz
(--) NVIDIA(0): DFP-1: Internal Single Link TMDS


(II) NVIDIA(0): Adding EDID-provided mode "3840x2400" for DFP-0.
(II) NVIDIA(0): Adding EDID-provided mode "2624x2400" for DFP-0.
(II) NVIDIA(0): Adding EDID-provided mode "1216x2400" for DFP-0.
(II) NVIDIA(0): Adding EDID-provided mode "1920x1200" for DFP-0.
(II) NVIDIA(0): Frequency information for DFP-1:
(II) NVIDIA(0): HorizSync : 31.500-160.000 kHz
(II) NVIDIA(0): VertRefresh : 19.000-62.000 Hz
(II) NVIDIA(0): (HorizSync from SecondMonitorHorizSync X Config Option)
(II) NVIDIA(0): (VertRefresh from SecondMonitorVertRefresh X Config
(II) NVIDIA(0): Option)
(II) NVIDIA(0): Adding EDID-provided mode "3840x2400" for DFP-1.
(II) NVIDIA(0): Adding EDID-provided mode "2624x2400" for DFP-1.
(II) NVIDIA(0): Adding EDID-provided mode "1216x2400" for DFP-1.
(II) NVIDIA(0): Adding EDID-provided mode "1920x1200" for DFP-1.
(II) NVIDIA(0): Parsed 1 valid MetaMode(s)
(II) NVIDIA(0): MetaMode [0]; display [0]; name : "2624x2400"
(II) NVIDIA(0): MetaMode [0]; display [1]; name : "1216x2400"

At this stage each screen is correctly detected,a and EDID mode are read.

(II) NVIDIA(0): Clock range: 12.00 to 310.00 MHz
(II) NVIDIA(0): Not using default mode "1024x768" (vrefresh out of range)
(II) NVIDIA(0): Not using default mode "512x384" (vrefresh out of range)
(II) NVIDIA(0): Not using default mode "1920x1440" (bad mode clock/interlace/doublescan)
(II) NVIDIA(0): Not using default mode "960x720" (hsync out of range)
(II) NVIDIA(0): Not using default mode "2048x1536" (bad mode clock/interlace/doublescan)
(II) NVIDIA(0): Not using default mode "1024x768" (hsync out of range)
(II) NVIDIA(0): Not using default mode "2048x1536" (bad mode clock/interlace/doublescan)
(II) NVIDIA(0): Not using default mode "1024x768" (hsync out of range)
(II) NVIDIA(0): Not using mode "2624x2400" (bad mode clock/interlace/doublescan)
(II) NVIDIA(0): Not using mode "" (bad mode clock/interlace/doublescan)

But here, 2624x2400 mode is rejected by 8x.xx driver, in the 7x.xx serie of driver this mode was accepted.
I join the entire nvidia-bug-report.log.zip

As usual, thanks for any help !
Alexandre
Attached Files
File Type: zip nvidia-bug-report.log.zip (25.6 KB, 103 views)
alex31 is offline   Reply With Quote
Old 01-31-06, 09:32 AM   #11
alex31
Registered User
 
Join Date: Dec 2002
Posts: 47
Default Re: not able to drive ibm t221 3840x2400 screen with 81.78 (was ok with 76.76)

here is the log, with logverbose=6 with 7676 driver, whan it works, it could perhaps be useful to compare with the 8178 log.

Alexandre
Attached Files
File Type: zip nvidia-bug-report_7676-ok.log.zip (21.0 KB, 114 views)
alex31 is offline   Reply With Quote
Old 02-03-06, 05:09 PM   #12
netllama
NVIDIA Corporation
 
Join Date: Dec 2004
Posts: 8,763
Default Re: not able to drive ibm t221 3840x2400 screen with 81.78 (was ok with 76.76)

Alexandre,
I've reproduced a problem similar to this with the IBM T221 that we have here, and have opened bug 209711 for the issue.

Thanks,
Lonni
netllama 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


Similar Threads
Thread Thread Starter Forum Replies Last Post
IBM drive sometimes making noises. Fluke General Hardware 5 10-15-02 07:13 AM

All times are GMT -5. The time now is 11:54 AM.


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