Hide Forgot
Filed from caserun (https://tcms.engineering.redhat.com/run/289603/#caserun_13279412) Version-Release number of selected component (if applicable): RHEL-7.3-20160914.1 xorg-x11-server-Xorg-1.17.2-22.el7.x86_64 xorg-x11-drv-ati-7.6.1-3.20160215gitd41fccc.el7.x86_64 kernel-3.10.0-506.el7.x86_64 linux-firmware-20160830-49.git7534e19.el7.noarch package mesa is not installed mesa-dri-drivers-11.2.2-2.20160614.el7.x86_64 package xorg-x11-glamor is not installed Steps to Reproduce: 1. Connect two screens with different native resolutions to you box 1. Check Plymouth 2. Check GDM 3. Check KDE/GNOME Session (you need to set it via system settings and display there) Actual results: If you set the display to Mirror, then revert, and repeat a few times (usually 1-2 interations) the displays stop working. On my setup, with all 3 displays in use, the integrated display stops first, and after a few tries the HDMI display stops working. Running `xrnadr` shows them as normal, modes set, but the target display gets no signal and goes to sleep. Expected results: both screens should be set to some resolution that should fit to both of them Example: Screen 1: 1024x 768 Screen 2: 1280 x 600 both should be set to 1024x600
The 7710 is made of pure evil and cannot be trusted. Please check https://bugzilla.redhat.com/show_bug.cgi?id=1381286#c2 and do that first before I look into this.
More interesting in: RHEL-7.4-20170711.0 xorg-x11-server-Xorg-1.19.3-11.el7.x86_64 xorg-x11-drv-ati-7.7.1-3.20160928git3fc839ff.el7.x86_64 package amdgpu is not installed kernel-3.10.0-693.el7.x86_64 linux-firmware-20170606-56.gitc990aae.el7.noarch package mesa is not installed mesa-dri-drivers-17.0.1-6.20170307.el7.x86_64 package xorg-x11-glamor is not installed libdrm-2.4.74-1.el7.x86_64 Now the built-in display behaves the same, but external displays have a chance to come back on subsequent switches.
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.