nV News Forums

 
 

nV News Forums (http://www.nvnews.net/vbulletin/index.php)
-   NVIDIA Linux (http://www.nvnews.net/vbulletin/forumdisplay.php?f=14)
-   -   7664 and 1600x1200 (maximum pixel clock?) (http://www.nvnews.net/vbulletin/showthread.php?t=51431)

hamsta 06-02-05 06:39 PM

7664 and 1600x1200 (maximum pixel clock?)
 
Hi,

good news: No more crashes since now with 7664 :-)

But now, the bad ones: I cannot star 1600x1200 any longer (worked perfectly with the old driver).

I looked into the logs and found the following lines:

(--) NVIDIA(0): DFP-0: maximum pixel clock: 155 MHz
(--) NVIDIA(0): DFP-0: Internal Single Link TMDS
(II) Loading sub module "ddc"
(II) LoadModule: "ddc"
(II) Loading /usr/X11R6/lib/modules/libddc.a
(II) Module ddc: vendor="X.Org Foundation"
compiled for 6.8.2, module version = 1.0.0
ABI class: X.Org Video Driver, version 0.7
(II) NVIDIA(0): Monitor0: Using default hsync range of 30.00-80.00 kHz
(II) NVIDIA(0): Monitor0: Using default vrefresh range of 56.00-85.00 Hz
(II) NVIDIA(0): Clock range: 12.00 to 155.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 "1280x960" (hsync out of range)
(II) NVIDIA(0): Not using default mode "640x480" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1280x1024" (bad mode clock/interlace/doublescan)
(II) NVIDIA(0): Not using default mode "640x512" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1600x1200" (bad mode clock/interlace/doublescan)

What is kind of strange is the first line: The clock speed was at 350 Mhz with the old driver (I have the old logs). Does anybody has any idea, what is going wrong here? The config is the same as before.

Just if anybody cares: The monitor is an iiyma AU4831D (flatpanel).



CU,

hamsta

hamsta 06-03-05 03:17 AM

Re: 7664 and 1600x1200 (maximum pixel clock?)
 
Hi,

does really nobody has an idea how to fix that? I have already tried a new fresh xorg.conf, but I could not solve the problem. It really looks like a maximum pixel clock related one, which obviously is set to low with the new driver 7664. Some lines above the already quoted lines, you see the problem appearing the first time:

(II) NVIDIA(0): Detected AGP rate: 4X
(--) NVIDIA(0): VideoRAM: 131072 kBytes
(II) NVIDIA(0): Connected display device(s): DFP-0
(--) NVIDIA(0): DFP-0: maximum pixel clock: 155 MHz
(--) NVIDIA(0): DFP-0: Internal Single Link TMD

Should this really be only 155 MHz at this point? Is there any way to influence this?

Looking forward to any help. If you need any more information, just tell me.


Thanks in advance

hamsta

sparkplug 06-03-05 03:26 AM

Re: 7664 and 1600x1200 (maximum pixel clock?)
 
I'm also having the same problem with my system running a viewsonic VP201b monitor. I have currently gone back a release so I can use the 1600x1200. Also I can only get into X when using the DVI socket on the card not the normal analog connection, this is not a problem to me but I thought is was a bit strange.

Dave

My basic system:

AMD 3000+ 64bit 939
MSI K8N Neo4 Platinum
1G Ram
MSI PCIE 6600
Samsung 160G SATA HD
LG DVD RW
Fedora Core 3

Lithorus 06-03-05 03:55 AM

Re: 7664 and 1600x1200 (maximum pixel clock?)
 
Perhaps you could provide the WHOLE log?

hamsta 06-03-05 08:06 AM

Re: 7664 and 1600x1200 (maximum pixel clock?)
 
1 Attachment(s)
The complete log is attached.

Thanks for your help,

hamsta

vwchris 06-03-05 08:32 AM

Re: 7664 and 1600x1200 (maximum pixel clock?)
 
2 Attachment(s)
same problem here. Using VP201S from viewsonic. With all prior drivers, had no problem at 1600x1200. Now I'm getting a "Maximum Pixel Clock" of 155Mhz, and hence the highest resolution I can get at is 1280x1024. This is really frustrating since I was hoping the 7664 drivers would fix stability problems!

Attached are my xorg.conf and Xorg.0.log files.

murray.anderegg 06-03-05 08:50 AM

Re: 7664 and 1600x1200 (maximum pixel clock?)
 
I am having the same problem with my Flat Panel Display.

In my XFree86.0.log it says that 1600x1200 requires a 162MHz clock.
Platform is RHEL3 update 5, kernel is 2.4.21-32.0.1.ELsmp

Lithorus 06-03-05 09:17 AM

Re: 7664 and 1600x1200 (maximum pixel clock?)
 
Try with the
Code:

Option "NoBandWidthTest" "true"

hamsta 06-03-05 09:26 AM

Re: 7664 and 1600x1200 (maximum pixel clock?)
 
Quote:

Originally Posted by Lithorus
Try with the
Code:

Option "NoBandWidthTest" "true"

Done, but it has no effect unfortunately :-(


Thanks for your help,

Jens

jsgf 06-03-05 11:17 AM

Re: 7664 and 1600x1200 (maximum pixel clock?)
 
I'm seeing the same thing. I wonder if it's related to the FAQ in the README:
Q. Why can I not get a resolution of 1600x1200 on the second display device when using a GeForce2 MX?

A. Because the second display device on the GeForce2 MX was designed to be a digital flat panel, the Pixel Clock for the second display device is only 150 MHz. This effectively limits the resolution on the second display device to somewhere around 1280x1024 (for a description of how Pixel Clock frequencies limit the programmable modes, see the XFree86 Video Timings HOWTO). This constraint is not present on GeForce4 or GeForce FX chips -- the maximum pixel clock is the same i on both heads.
It looks to me like it might be mis-applying this test on my Geforce 6600GT.

aritger 06-03-05 02:13 PM

Re: 7664 and 1600x1200 (maximum pixel clock?)
 
The 7664 driver adds more "correct" mode validation checking of the pixel clock (the maximum pixel clock is indeed what is reported in the X log with 7664; the higher number reported in earlier driver versions is incorrect).

However, there is a bug that the mode validation is not properly taking into account reduced blanking, which will be employed when setting the mode. Reduced blanking is a technique for shrinking the blanking regions of a mode, resulting in a lower pixel clock.

This will be addressed in a future driver release, but the work around for 7664 is to add a 1600x1200 modeline with a low enough pixel clock to the Monitor section of your X config file. This one should be sufficient:

Modeline "1600x1200" 145.98 1600 1704 1872 2144 1200 1201 1204 1238 -HSync +Vsync

I apologize for the inconvenience.

hamsta 06-03-05 02:41 PM

Re: 7664 and 1600x1200 (maximum pixel clock?)
 
Quote:

Originally Posted by aritger
Modeline "1600x1200" 145.98 1600 1704 1872 2144 1200 1201 1204 1238 -HSync +Vsync

Thanks a lot for the details and the workarround. Everything is working fine now!

Just a small hint, for anybody else: Don't forget the following Option in your device section, otherwise the Modeline cannot work:
Code:

Option      "IgnoreEDID" "1"
CU and thanks again,

hamsta


All times are GMT -5. The time now is 06:51 PM.

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