Hide Forgot
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.
Please attach the output from 'intel_reg_dumper' from the affected setup. This command is available in the intel-gpu-tools package.
Do you still see this with 6.3?
This appears to correspond to the following commit in upstream DRM: === commit 0c14c7f957e70c3cb100e3fd6553b0ebea557571 Author: Paulo Zanoni <paulo.r.zanoni> Date: Mon May 28 16:42:49 2012 -0300 drm/i915: properly alternate between DVI and HDMI This solves problems that happen when you alternate between HDMI and DVI on the same port. I can reproduce these problems using DP->HDMI and DP->DVI adapters on a DP port. When you first plug HDMI and then plug DVI, you need to stop sending DIPs, even if the port is in DVI mode (see the HDMI register spec). If you don't stop sending DIPs, you'll see a pink vertical line on the left side of the screen, some modes will give you a black screen, some modes won't work correctly. [...] === This change is included in the DRM rebase series posted to rhkernel.
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux release for currently deployed products. This request is not yet committed for inclusion in a release.
Lukas, please attach the output from 'xrandr --properties' with the affected monitor connected.
(In reply to Adam Jackson from comment #22) > Lukas, please attach the output from 'xrandr --properties' with the affected > monitor connected. I still can't proceed without this.
(In reply to Adam Jackson from comment #22) > Lukas, please attach the output from 'xrandr --properties' with the affected > monitor connected. That was a year ago, this must not be urgent. Closing. Please do retest this scenario with RHEL 6.6 and 7.0 so we can either verify that this has been fixed, or create a bug to fix it.