nV News Forums

 
 

nV News Forums (http://www.nvnews.net/vbulletin/index.php)
-   NVIDIA Linux (http://www.nvnews.net/vbulletin/forumdisplay.php?f=14)
-   -   DisplayPort Powersave Help (http://www.nvnews.net/vbulletin/showthread.php?t=135751)

dillzz 07-14-09 11:18 AM

DisplayPort Powersave Help
 
Just recently purchased Quadro NVS 450 and (2) Dell 3008wfp. Currently using driver 185.18.14 on RHEL 5.2 64bit.

These monitors are connected via native DisplayPort each running at a resolution of 2560x1600. Everything works perfect except when the monitors enter powersave mode. Moving mouse/touching keyboard does not wake them up. Only way to wake up is unplug a monitor and plug back in OR reboot. Tried connecting with DisplayPort to DVI adaptors but only reach a resolution of 1920x1200, but the wake up works fine.

We are looking at a replacement for the 440's as they are EOL. There will be roughly 300 of these cards ordered. Any ideas so we can proceed? Works fine in windows so it is not hardware related. . .

dillzz 07-15-09 08:36 PM

Re: DisplayPort Powersave Help
 
No updates? Has no one ever experienced such an issue. We posted a bug report to nvidia weeks ago and have not heard a thing.

bobn 07-18-09 08:11 PM

Re: DisplayPort Powersave Help
 
I'm seeing the same symptoms as dilzz, but am able to get the monitor to wake up if I switch away from vt7 and switch back again using Ctrl-Alt-F1, Ctrl-Alt-F7.

My hardware is an Apple early 2009 Mac mini that is driving an Apple 30" LCD monitor via an Apple DisplayPort to dual DVI adapter.

But for the lack of wake-up on mouse or keyboard activity, everything looks good at 2560x1600.

This hardware is running Debian Lennny 5.0 (stable) with the following nvidia-specific packages:

ii nvidia-glx 185.18.14-2 NVIDIA binary
ii nvidia-kernel-2.6.26-2-amd64 185.18.14-2+2.6.26-17 NVIDIA binary
ii nvidia-kernel-common 20080825+1 NVIDIA binary
ii nvidia-kernel-source 185.18.14-2 NVIDIA binary

Note that nvidia-kernel-2.6.26-2-amd64 is built using module-assistant from nvidia-kernel-source/unstable and that nvidia-glx is also from unstable.

I'm running with the following xorg.conf:

Section "Device"
Identifier "Video"
Driver "nvidia"
BusID "PCI:2:0:0"
EndSection


grep -i nvidia /var/log/Xorg.0.log:

(--) PCI:*(2:0:0) nVidia Corporation unknown chipset (0x0861) rev 177, Mem @ 0xd2000000/24, 0xc0000000/28, 0xd0000000/25, I/O @ 0x1000/7, BIOS @ 0xd3000000/17
(II) Module glx: vendor="NVIDIA Corporation"
(II) NVIDIA GLX Module 185.18.14 Wed May 27 01:53:56 PDT 2009
(II) LoadModule: "nvidia"
(II) Loading /usr/lib/xorg/modules/drivers//nvidia_drv.so
(II) Module nvidia: vendor="NVIDIA Corporation"
(II) NVIDIA dlloader X Driver 185.18.14 Wed May 27 01:30:19 PDT 2009
(II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
(WW) NVIDIA: No matching Device section for instance (BusID PCI:0:3:5) found
(--) Chipset NVIDIA GPU found
(II) NVIDIA(0): Creating default Display subsection in Screen section
(==) 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.
(II) NVIDIA(0): NVIDIA GPU GeForce 9400 (C79) at PCI:2:0:0 (GPU-0)
(--) NVIDIA(0): Memory: 524288 kBytes
(--) NVIDIA(0): VideoBIOS: 62.79.4e.00.01
(--) NVIDIA(0): Interlaced video modes are supported on this GPU
(--) NVIDIA(0): Connected display device(s) on GeForce 9400 at PCI:2:0:0:
(--) NVIDIA(0): Apple Cinema HD (DFP-2)
(--) NVIDIA(0): Apple Cinema HD (DFP-2): 330.0 MHz maximum pixel clock
(--) NVIDIA(0): Apple Cinema HD (DFP-2): Internal DisplayPort
(II) NVIDIA(0): Assigned Display Device: DFP-2
(==) NVIDIA(0):
(==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
(==) NVIDIA(0): will be used as the requested mode.
(==) NVIDIA(0):
(II) NVIDIA(0): Validated modes:
(II) NVIDIA(0): "nvidia-auto-select"
(II) NVIDIA(0): Virtual screen size determined to be 2560 x 1600
(--) NVIDIA(0): DPI set to (101, 101); computed from "UseEdidDpi" X config
(--) NVIDIA(0): option
(==) NVIDIA(0): Enabling 32-bit ARGB GLX visuals.
(II) NVIDIA(0): Initialized GPU GART.
(II) NVIDIA(0): Setting mode "nvidia-auto-select"
(II) NVIDIA(0): NVIDIA 3D Acceleration Architecture Initialized
(==) NVIDIA(0): Disabling shared memory pixmaps
(II) NVIDIA(0): Using the NVIDIA 2D acceleration architecture
(==) NVIDIA(0): Backing store disabled
(==) NVIDIA(0): Silken mouse enabled
(II) NVIDIA(0): DPMS enabled
(II) NVIDIA(0): Setting mode "nvidia-auto-select"

bobn 07-18-09 11:05 PM

Re: DisplayPort Powersave Help
 
1 Attachment(s)
Here's nvidia-bug-report.log.gz

dillzz 07-20-09 01:45 PM

Re: DisplayPort Powersave Help
 
1 Attachment(s)
bobn,

Thank you for the information. Here is my bug report of course!

Thanks,

Dillzz

dillzz 07-23-09 10:21 AM

Re: DisplayPort Powersave Help
 
Bump

kdgassiot 07-27-09 01:32 PM

Re: DisplayPort Powersave Help
 
1 Attachment(s)
I am seeing the same thing with a machine using the DisplayPort to DVI adapter driving 2 Dell 21 inch LCD displays. When the screensaver puts the monitors to sleep, there are intermittent problems with the monitors waking up. At first, we had 1 monitor connected via the DVI port and 1 monitor connected via an HP DisplayPort to DVI adapter. User reported that it was always the monitor connected via the DisplayPort to DVI adapter. Then connected both monitors using a DisplayPort to DVI adapter, and can (intermittently) recreate the problems on both monitors using the any of the following xset commands...

xset dpms force off
xset dpms force standby
xset dpms force suspend

Environment is RHEL 5.3 64-bit, Nvidia driver 185.18.14

dillzz 07-28-09 11:53 AM

Re: DisplayPort Powersave Help
 
Tried release "Current beta release: 190.18 (x86 / x86_64)" and am still seeing the issue

bobn 11-14-09 08:15 AM

Re: DisplayPort Powersave Help
 
Thanks, dillzz, for looking at 190.

AaronP 11-16-09 01:07 AM

Re: DisplayPort Powersave Help
 
This is a known issue that should be resolved in the first 195.* release.


All times are GMT -5. The time now is 11:26 PM.

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