Bug 559068

Summary:	energy saving mode does not work when using DisplayPort-cable
Product:	Gentoo Linux	Reporter:	Mario Bachmann <grafgrimm77>
Component:	[OLD] Unspecified	Assignee:	Gentoo Linux bug wranglers <bug-wranglers>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	alex_y_xu
Priority:	Normal
Version:	unspecified
Hardware:	AMD64
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Mario Bachmann 2015-08-29 08:46:41 UTC

I iiyama_ProLite_XB2776QShave absolutely no idea for that behaviour. 

I have to following combination:
iiyama ProLite XB2776QS
MSI GeForce GTX 980 Gaming 4G (GM204)
nvidia driver 355.06

When I use DVI-cable, that the display goes into energy saving mode after a while.

When I use a DisplayPort-cable, the display is always in on-mode. When triggering suspend mode with "xset dpms force suspend", the display shows a black screen. 

I check the mode of the display with its power indicator (LED): blue means on, orange means power saving mode. 



Reproducible: Always

Steps to Reproduce:
1. use a DisplayPort cable instead of DVI
2. try getting display into power saving mode


Expected Results:  
Energy Saving modes (suspand, standby, ...) should work with all kind of digital cable connection. 

Modern graphic cards tend to offer more and more DisplayPorts (or Mini) only. I a multi monitor setup I could use my working DVI, but for the second display I have to use DisplayPort. HDMI ist no real Option, because combination of resolution and refresh rate seems to be limited to FullHD/60Hz.

Comment 1 Alex Xu (Hello71) 2015-09-20 16:05:39 UTC

guessing source to be nvidia-drivers.

Comment 2 Alex Xu (Hello71) 2015-09-20 19:08:21 UTC

jer: what info exactly is required?

Comment 3 Mario Bachmann 2015-09-20 19:32:25 UTC

What does the status "RESOLVED NEEDINFO" mean? Sounds like a joke. 

Do you even own a nvidia graphics card? Did You try the the described steps to reproduce the bug? 

This was my last bug report. Greetings.

Comment 4 Alex Xu (Hello71) 2015-09-26 20:54:17 UTC


*** This bug has been marked as a duplicate of bug 560774 ***