NVS 295 + DP->VGA + 185.18.14 -> problems

Jean Tourrilhes · 07-17-09, 06:11 PM

Hi,

I'm a quite seasoned user of X-Window. I installed a new HP xw4600 with a NVS 295 (I've got other xw400 working fine with NVS 280 and FX 570). The NVS 295 is a card with a DisplayPort, and as my KVMs are VGA, I bought a DisplayPort to VGA adapter. I downloaded the latest binary driver (185.18.14). I tried kernel 2.6.27.24 and 2.6.30.1 on Debian Lenny. I tried two monitors, a HP LP2035 (LCD 1600x1200) and a HP f2105 (1680x1050).
In both cases, I get only 640x480 resolution.
And the Xorg.0.log report some suspicious errors...

I suspect that somehow the DisplayPort to VGA adapter is not recognised and prevent the card to talk properly to the monitor.

This is a quick extract of the log for the LP2035 and the f2105 :

---------------------------------
(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): Enabling RENDER acceleration
(II) NVIDIA(0): Support for GLX with the Damage and Composite X extensions is
(II) NVIDIA(0): enabled.
(WW) NVIDIA(GPU-0): Unable to read EDID for display device DFP-2
(II) NVIDIA(0): NVIDIA GPU Quadro NVS 295 (G98GL) at PCI:1:0:0 (GPU-0)
(--) NVIDIA(0): Memory: 262144 kBytes
(--) NVIDIA(0): VideoBIOS: 62.98.5f.00.08
(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 Quadro NVS 295 at PCI:1:0:0:
(--) NVIDIA(0): DFP-2
(--) NVIDIA(0): DFP-2: 330.0 MHz maximum pixel clock
(--) NVIDIA(0): DFP-2: Internal DisplayPort
(II) NVIDIA(0): Assigned Display Device: DFP-2
(WW) NVIDIA(0): No valid modes for "1600x1200"; removing.
(WW) NVIDIA(0): No valid modes for "1280x1024"; removing.
(WW) NVIDIA(0): No valid modes for "1024x768"; removing.
(WW) NVIDIA(0): No valid modes for "800x600"; removing.
(II) NVIDIA(0): Validated modes:
(II) NVIDIA(0): "640x480"
(II) NVIDIA(0): Virtual screen size determined to be 640 x 480
(WW) NVIDIA(0): Unable to get display device DFP-2's EDID; cannot compute DPI
(WW) NVIDIA(0): from DFP-2's EDID.
(==) NVIDIA(0): DPI set to (75, 75); computed from built-in default
(==) NVIDIA(0): Enabling 32-bit ARGB GLX visuals.
---------------------------------

-----------------------------------------------------
(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): Enabling RENDER acceleration
(II) NVIDIA(0): Support for GLX with the Damage and Composite X extensions is
(II) NVIDIA(0): enabled.
(WW) NVIDIA(GPU-0): Unable to read EDID for display device DFP-2
(II) NVIDIA(0): NVIDIA GPU Quadro NVS 295 (G98GL) at PCI:1:0:0 (GPU-0)
(--) NVIDIA(0): Memory: 262144 kBytes
(--) NVIDIA(0): VideoBIOS: 62.98.5f.00.08
(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 Quadro NVS 295 at PCI:1:0:0:
(--) NVIDIA(0): DFP-2
(--) NVIDIA(0): DFP-2: 330.0 MHz maximum pixel clock
(--) NVIDIA(0): DFP-2: Internal DisplayPort
(II) NVIDIA(0): Assigned Display Device: DFP-2
(WW) NVIDIA(0): No valid modes for "1680x1050"; removing.
(WW) NVIDIA(0): No valid modes for "1440x900"; removing.
(WW) NVIDIA(0): No valid modes for "1024x768"; removing.
(WW) NVIDIA(0): No valid modes for "800x600"; removing.
(II) NVIDIA(0): Validated modes:
(II) NVIDIA(0): "640x480"
(II) NVIDIA(0): Virtual screen size determined to be 640 x 480
(WW) NVIDIA(0): Unable to get display device DFP-2's EDID; cannot compute DPI
(WW) NVIDIA(0): from DFP-2's EDID.
(==) NVIDIA(0): DPI set to (75, 75); computed from built-in default
(==) NVIDIA(0): Enabling 32-bit ARGB GLX visuals.
(--) Depth 24 pixmap format is 32 bpp
-----------------------------------------------------

I assume that it's just that the hardware is too new. Good luck figuring that one out ;-)

Jean

lanyao · 07-19-09, 10:28 PM

Same scenario here and met the similar issue: with nvs295 we want to use VGA KVM under RHEL5U3.

The screen display is messed while using DisplayPort to VGA adapter on NVS295, with DVI it'll be OK. "messed" means that the screen is like a wringing watercolor painting...

pgquiles · 07-21-09, 06:12 AM

Try 185.19 (available in the FTP). It fixes this kind of issues.

lanyao · 07-28-09, 01:28 AM

Quote:

Originally Posted by pgquiles

Try 185.19 (available in the FTP). It fixes this kind of issues.

Hi, I tried that, same issue still

lanyao · 07-28-09, 01:35 AM

Quote:

Originally Posted by Jean Tourrilhes

Hi,

I'm a quite seasoned user of X-Window. I installed a new HP xw4600 with a NVS 295 (I've got other xw400 working fine with NVS 280 and FX 570). The NVS 295 is a card with a DisplayPort, and as my KVMs are VGA, I bought a DisplayPort to VGA adapter. I downloaded the latest binary driver (185.18.14). I tried kernel 2.6.27.24 and 2.6.30.1 on Debian Lenny. I tried two monitors, a HP LP2035 (LCD 1600x1200) and a HP f2105 (1680x1050).
In both cases, I get only 640x480 resolution.
And the Xorg.0.log report some suspicious errors...

I suspect that somehow the DisplayPort to VGA adapter is not recognised and prevent the card to talk properly to the monitor.

I assume that it's just that the hardware is too new. Good luck figuring that one out ;-)

Jean

Hello Jean, have you ever tried to manually set HorizSync and VertRefresh value for your monitor? Maybe add one line like Modes "1600x1200" under "Display" SubSection?

lanyao · 08-04-09, 01:20 AM

One update:
I've tried the new version 185.18.31, still the same issue.

DP=>DVI is OK, DP=>VGA is messed

Jean Tourrilhes · 12-21-09, 07:00 PM

Hi,

Sorry for resurrecting an old thread. Today I was upgraded the PC to kernel 2.6.31.9, and I've put 190.53. The changelog for 190.53 made me hopeful. However, at first glance, I got the same issue, it is still stuck on 640x480 with the same message in the log.
Regards,

Jean

lanyao · 01-13-10, 01:19 AM

Hi Jean,

I met the same issue while connecting with HP LP1965 monitor, but after changing to a LP2065, that issue goes away, Xorg log shows that it can read the EDID info then.
So the resolution issue only happens on specified monitor models?

BTW, 190.53 fixed the massed display issue via DP=>VGA.

07-21-09, 06:12 AM	#3
pgquiles Registered User Join Date: Jul 2009 Posts: 3	Re: NVS 295 + DP->VGA + 185.18.14 -> problems Try 185.19 (available in the FTP). It fixes this kind of issues.

08-04-09, 01:20 AM	#6
lanyao Registered User Join Date: Apr 2006 Posts: 5	Re: NVS 295 + DP->VGA + 185.18.14 -> problems One update: I've tried the new version 185.18.31, still the same issue. DP=>DVI is OK, DP=>VGA is messed

12-21-09, 07:00 PM	#7
Jean Tourrilhes Registered User Join Date: Jul 2009 Posts: 2	Re: NVS 295 + DP->VGA + 185.18.14 -> problems Hi, Sorry for resurrecting an old thread. Today I was upgraded the PC to kernel 2.6.31.9, and I've put 190.53. The changelog for 190.53 made me hopeful. However, at first glance, I got the same issue, it is still stuck on 640x480 with the same message in the log. Regards, Jean

01-13-10, 01:19 AM	#8
lanyao Registered User Join Date: Apr 2006 Posts: 5	Re: NVS 295 + DP->VGA + 185.18.14 -> problems Hi Jean, I met the same issue while connecting with HP LP1965 monitor, but after changing to a LP2065, that issue goes away, Xorg log shows that it can read the EDID info then. So the resolution issue only happens on specified monitor models? BTW, 190.53 fixed the massed display issue via DP=>VGA.