Bug 747392

Summary:	Display port monitor misbehaviour on Quadro 2000
Product:	Red Hat Enterprise Linux 6	Reporter:	Tomas Jamrisko <tjamrisk>
Component:	kernel	Assignee:	Ben Skeggs <bskeggs>
Status:	CLOSED WONTFIX	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.2	CC:	airlied, tpelka
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-12-06 10:59:38 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Tomas Jamrisko 2011-10-19 17:21:38 UTC

Description of problem:
(This card has one DVI and two display ports) Starting with a monitor and later connecting a monitor to the display port doesn't enable the DP monitor as expected

Version-Release number of selected component (if applicable):
RHEL6.2-20111016.n.0

How reproducible:
Always


Steps to Reproduce:
1. Connect a DVI monitor to Quadro 2000
2. Start system
3. Login
4. Connect one DP monitor
  
Actual results:

The display is recognized and turned on (according to gnome-diplay-properties) but the monitor isn't receiving any signal.

Expected results:

The second display powers on

Additional info:

The monitor is question is an Acer B223PW

Comment 2 Tomas Jamrisko 2011-10-20 08:56:22 UTC

Connecting a different monitor (Samsung BX2240) (through DP -> DVI reduction) seems to work as expected.

Comment 3 Tomas Jamrisko 2011-10-20 09:15:59 UTC

The same sort of misbehaviour is with Quadro FX 380. Works properly with Intel HD Graphics.

It seems, that using DP isn't necessary, it didn't work on DVI either.

Comment 4 Ben Skeggs 2011-10-20 09:24:21 UTC

(In reply to comment #3)
> The same sort of misbehaviour is with Quadro FX 380. Works properly with Intel
> HD Graphics.
> 
> It seems, that using DP isn't necessary, it didn't work on DVI either.

I'm confused, the previous comments says DP->DVI works?

In any case, native DP (which includes *any* active DP adaptor) is not supposed to work on nouveau in RHEL6 at this point.  It's fixed upstream, but was deemed to invasive to include at that point in the 6.2 release cycle...

Comment 5 Tomas Jamrisko 2011-10-20 11:33:30 UTC

It seems that this bug is more about multi-monitor setup than DP.

So to make things a little bit clearer -- DP works fine (adaptor or native), the problem is, that the acer monitor isn't properly recognized (by any port) on those mentioned nVidia graphic cards (worked fine on intel) (it is listed in gnome-display-properties, but it's dark -- no signal). Connecting and disconnecting monitors eventually led to corruption of the other one as well.

Also xvinfo tells that there are no adaptors regardless of monitor and port to which it is connected.

Comment 6 Ben Skeggs 2011-10-20 11:47:07 UTC

(In reply to comment #5)
> It seems that this bug is more about multi-monitor setup than DP.
> 
> So to make things a little bit clearer -- DP works fine (adaptor or native),
> the problem is, that the acer monitor isn't properly recognized (by any port)
> on those mentioned nVidia graphic cards (worked fine on intel) (it is listed in
> gnome-display-properties, but it's dark -- no signal). Connecting and
> disconnecting monitors eventually led to corruption of the other one as well.
Yep, sorry, I wasn't clear.  DP *might* work in current 6.2 code, in some circumstances.  What *must* happen is for that display to have been initialised by the VBIOS first, which is why multi-monitor would fail.

You could give the latest F16 updates a try and see how you fare.  The latest F16 kernels have (most) of the DP improvements from upstream.  There's a couple of very recent ones lacking, which *might* effect display switching with DP on some cards.

> 
> Also xvinfo tells that there are no adaptors regardless of monitor and port to
> which it is connected.
Yes, another thing lacking in 6.2 is acceleration support for these chipsets (unless you provide an external firmware image), so you're seeing expected behaviour.  I have no idea of what exact chipset this card has, but it's likely supported in upstream code (and probably will be for 6.3).

Again, testing the latest F16 code will reveal if it'll likely work in 6.3.

Comment 7 Tomas Jamrisko 2011-10-20 12:44:57 UTC

Tried it in Fedora 16. There was a problem when I tried to boot with one monitor in DVI, connecting DP after boot, disconnecting DVI and finally connecting DVI again -- both monitors went black, up until then they worked as expected. It's probably one of those *might* cases.

Comment 8 Dave Airlie 2011-10-21 08:32:25 UTC

fix component.

Comment 9 RHEL Program Management 2011-10-25 05:47:36 UTC

Since RHEL 6.2 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.

Comment 10 Jan Kurik 2017-12-06 10:59:38 UTC

Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/