nV News Forums

 
 

nV News Forums (http://www.nvnews.net/vbulletin/index.php)
-   NVIDIA Linux (http://www.nvnews.net/vbulletin/forumdisplay.php?f=14)
-   -   Twinview widscreen problem (http://www.nvnews.net/vbulletin/showthread.php?t=85658)

krisnilsen 02-03-07 07:03 PM

Twinview widscreen problem
 
Hey everyone,

I have just got my self a new 22" acer widscreen monitor.
I have it setup in twinview with a 17" LCD.
I am trying to get th 22" to work at its natural 1680x1050 res with my 17" running at 1280x1024.
For some reason the monitor turns off when i try this combo of res. I can get each monitor to work individually at these res.

Here is some of the xorg.conf
Option "TwinView"
Option "SecondMonitorHorizSync" "31.5 - 60.7"
Option "SecondMonitorVertRefresh" "60 - 75"
Option "TwinViewOrientation" "RightOf"
Option "MetaModes" "1280x1024, 1680x1050"

I have had twinview with 2 17" LCD working fine in the past.
At he moment I have it running at "1280x1024,1024x768", it will let me do that.
PS(i have got it to work in windows)
thanks

netllama 02-03-07 07:17 PM

Re: Twinview widscreen problem
 
Please start X with the following command:
startx -- -logverbose 6

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

Thanks,
Lonni

krisnilsen 02-05-07 05:22 AM

Re: Twinview widscreen problem
 
ok I have done the log but it was to big to attach

I think i found the problem in the log though

(II) NVIDIA(0): Validating Mode "1680x1050":
(II) NVIDIA(0): 1680 x 1050 @ 60 Hz
(II) NVIDIA(0): Mode Source: X Server
(II) NVIDIA(0): Pixel Clock : 147.14 MHz
(II) NVIDIA(0): HRes, HSyncStart : 1680, 1784
(II) NVIDIA(0): HSyncEnd, HTotal : 1968, 2256
(II) NVIDIA(0): VRes, VSyncStart : 1050, 1051
(II) NVIDIA(0): VSyncEnd, VTotal : 1054, 1087
(II) NVIDIA(0): H/V Polarity : +/+
(WW) NVIDIA(0): Mode is rejected: PixelClock (147.1 MHz) too high for EDID
(WW) NVIDIA(0): (EDID Max: 135.0 MHz).

THis is not right. The monitor can go to ~160 Mz

krisnilsen 02-05-07 06:14 AM

Re: Twinview widscreen problem
 
In another section it finds the pixel clock to have a max of 165 MHz
so I am a little misterfied.

(II) Setting vga for screen 0.
(**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
(==) NVIDIA(0): RGB weight 888
(==) NVIDIA(0): Default visual is TrueColor
(==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
(**) NVIDIA(0): Option "NvAGP" "1"
(**) NVIDIA(0): Option "UseEdidFreqs" "True"
(**) NVIDIA(0): Option "TwinView" "True"
(**) NVIDIA(0): Option "TwinViewOrientation" "RightOf"
(**) NVIDIA(0): Option "SecondMonitorHorizSync" "31.5 - 60.7"
(**) NVIDIA(0): Option "SecondMonitorVertRefresh" "56 - 75"
(**) NVIDIA(0): Option "MetaModes" "1280x1024, 1680x1050"
(**) NVIDIA(0): Enabling RENDER acceleration
(**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID has been
(**) NVIDIA(0): enabled on all display devices.
(**) NVIDIA(0): TwinView enabled
(**) NVIDIA(0): Use of NVIDIA internal AGP requested
(II) NVIDIA(0): NVIDIA GPU GeForce FX 5900XT at PCI:3:0:0
(--) NVIDIA(0): VideoRAM: 131072 kBytes
(--) NVIDIA(0): VideoBIOS: 04.35.20.32.00
(--) NVIDIA(0): Interlaced video modes are supported on this GPU
(--) NVIDIA(0): Connected display device(s) on GeForce FX 5900XT at
(--) NVIDIA(0): PCI:3:0:0:
(--) NVIDIA(0): IQT Q17 Analog (CRT-0)
(--) NVIDIA(0): Acer AL2216W (DFP-0)
(--) NVIDIA(0): IQT Q17 Analog (CRT-0): 400.0 MHz maximum pixel clock
(--) NVIDIA(0): Acer AL2216W (DFP-0): 165.0 MHz maximum pixel clock
(--) NVIDIA(0): Acer AL2216W (DFP-0): External Single Link TMDS
(II) NVIDIA(0): Assigned Display Devices: CRT-0, DFP-0
(II) NVIDIA(0): Validated modes:
(II) NVIDIA(0): "1280x1024,1680x1050"
(II) NVIDIA(0): Virtual screen size determined to be 1280 x 1024
(++) NVIDIA(0): DPI set to (100, 100); computed from -dpi X commandline option
(--) Depth 24 pixmap format is 32 bpp
(II) do I need RAC? No, I don't.

krisnilsen 02-05-07 06:17 AM

Re: Twinview widscreen problem
 
Ok I tried adding in
Option "ModeValidation" "NoMaxPClkCheck"
to xorg.conf
and I tried manually setting the virtual screen size with no luck for either

netllama 02-05-07 10:37 AM

Re: Twinview widscreen problem
 
Please start X with the following command:
startx -- -logverbose 6

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

Thanks,
Lonni

mooninite 02-05-07 11:07 AM

Re: Twinview widscreen problem
 
Ah, yet another EDID bug that nVidia claims doesn't exist.

Maybe if they fix this then HDTV sets will work without custom modelines. Good luck though.

P.S. Load up Windows and watch it magically work. netllama, please stress EDID still has issues.

netllama 02-05-07 11:21 AM

Re: Twinview widscreen problem
 
mooninite,
I'm not really clear on what you're referring to here as no one from NVIDIA has commented at all on the content of this thread.

Thanks,
Lonni

AaronP 02-05-07 11:56 AM

Re: Twinview widscreen problem
 
krisnilsen,

It sounds like the GPU is reporting a hardware pclk limit of 165 MHz, but the flat panel is reporting its own (incorrect) limit of 135 MHz. Accordingly, you'll need the NoEdidMaxPClkCheck override, rather than the NoMaxPClkCheck one, which overrides the GPU limit.

krisnilsen 02-06-07 01:48 AM

Re: Twinview widscreen problem
 
Hey everyone I have fixed it.

I found this in the log

(II) NVIDIA(0): Validating Mode "1680x1050":
(II) NVIDIA(0): 1680 x 1050 @ 60 Hz
(II) NVIDIA(0): Mode Source: X Server
(II) NVIDIA(0): Pixel Clock : 147.14 MHz
(II) NVIDIA(0): HRes, HSyncStart : 1680, 1784
(II) NVIDIA(0): HSyncEnd, HTotal : 1968, 2256
(II) NVIDIA(0): VRes, VSyncStart : 1050, 1051
(II) NVIDIA(0): VSyncEnd, VTotal : 1054, 1087
(II) NVIDIA(0): H/V Polarity : +/+
(WW) NVIDIA(0): Mode is rejected: HorizSync (65.2 kHz) out of range
(WW) NVIDIA(0): (31.500-60.700 kHz).

Then noticed that i had manually set the second monitor HSync and VSync
Commented them out and hay presto worked
Thanks for your help everyone (stupid me)


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

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