New 256MB 6600GT, AMD 64x2 - Display hangs
I have a new system with the following configuration:
ASUS A8N-SLI motherboard Dell 2001FP Monitor AMD-Athlon 64x2 (Manchester) CPU eVGA 256MB 6600GT Video card (This is new model with 2xDVI, part number P2-N420-FX) Suse 10.0 I'm currently running on NVIDIA driver rev 7676 as that appears to be the only one that partially works. For this version, I have to startx. The display goes blank and then the green connect light on the monitor goes yellow indicating a loss of connection. The system does boot into X however as I can hear the boot music in the background. I have to ctl-alt-f2 into another screen just to get in. I then have to kill the xserver. If I do this, I can then give a startx command and it boots into X correctly. I've tried to upgrade to driver version 8178 and also tried the new patch on 8178. These are a disaster, the xserver never finishes booting and everything is hung. I have another system with an Nvidia 5700 and from that card I know the mode lines I'm using for this display are correct as I've been using it for more than a year. I've looked at the Xorg.0.log's and there is nothing obvious. Here is a diff on a good boot (after x-restart) vs the first attempt. 82][root@bigt log]# diff Xorg.0.log Xorg.0.log.old 14c14 < (==) Log file: "/var/log/Xorg.0.log", Time: Sun Mar 5 06:33:15 2006 --- > (==) Log file: "/var/log/Xorg.0.log", Time: Sun Mar 5 06:32:01 2006 452a453 > (==) NVIDIA(0): Removed MMIO write-combining range (0xc0000000,0x10000000) 454,456c455,456 < (II) NVIDIA(0): Connected display device(s): DFP-1 < (--) NVIDIA(0): DFP-1: maximum pixel clock: 310 MHz < (--) NVIDIA(0): DFP-1: Internal Dual Link TMDS --- > (II) NVIDIA(0): Connected display device(s): CRT-0 > (--) NVIDIA(0): CRT-0: maximum pixel clock: 400 MHz 462a463 > (WW) NVIDIA(0): Failure reading EDID parameters for display device CRT-0 465,467c466 < (II) NVIDIA(0): Clock range: 12.00 to 310.00 MHz < (WW) (1600x1200,Monitor[0]) mode clock 162MHz exceeds DDC maximum 160MHz < (WW) (1600x1000,Monitor[0]) mode clock 166.71MHz exceeds DDC maximum 160MHz --- > (II) NVIDIA(0): Clock range: 12.00 to 400.00 MHz 494c493 < (II) NVIDIA(0): Not using default mode "1920x1440" (bad mode clock/interlace/doublescan) --- > (II) NVIDIA(0): Not using default mode "1920x1440" (hsync out of range) 497,498c496,497 < (II) NVIDIA(0): Not using default mode "2048x1536" (bad mode clock/interlace/doublescan) < (II) NVIDIA(0): Not using default mode "2048x1536" (bad mode clock/interlace/doublescan) --- > (II) NVIDIA(0): Not using default mode "2048x1536" (hsync out of range) > (II) NVIDIA(0): Not using default mode "2048x1536" (hsync out of range) 503c502 < (**) NVIDIA(0): Validated modes for display device DFP-1: --- > (**) NVIDIA(0): Validated modes for display device CRT-0: PS - When I use the 8178 driver the last 4 lines in the Xorg.0.log are: [50] 0 0 0x000003c0 - 0x000003df (0x20) IS[b](OprU) (II) NVIDIA(0): Setting mode "1600x1200" (WW) NVIDIA(0): WAIT (0, 1, 0x8000, 0x000005d4, 0x000005d4, 0) (II) Loading extension NV-GLX It tries to load NV-GLX and just never comes back. |
Fixed it. Here's the fix if anyone else has this issue. Add the following line
under: Section "Device" Option "ConnectedMonitor" "DFP-0" The problem was that the driver was coming up in CRT mode first. The above line forces DFP mode. |
All times are GMT -5. The time now is 02:25 PM. |