Red Hat Bugzilla – Bug 1033908
Test case failure: Multihead - Large Desktop on Radeon HD 7850 [1002:6819]
Last modified: 2015-11-19 15:00:33 EST
Filed from caserun https://tcms.engineering.redhat.com/run/99313/#caserun_3816187 Version-Release number of selected component (if applicable): Build : RHEL-7.0-20131111.1 xorg-x11-server-Xorg-1.14.99.901-5.20131101.el7.x86_64 xorg-x11-drv-ati-7.2.0-6.20131023gitf1dc677.el7.x86_64 kernel-3.10.0-48.el7.x86_64 Steps to Reproduce: 1. obtain a card that is capable to connect 4 screens and 4 monitors 2. plug everything together and start GNOME 1. go into Control Center -> Display 2. Create 4x1 setup with all displays set to the same resolution 3. Create 2x2 setup 4. Create 1x4 setup with all displays set to different resolution Actual results: Hotplugging monitors results in hang. Booting with four already plugged is more interesting. They appear to be set to 800x600 or or maybe even smaller and are all mirroring the top left corner of a large desktop (probably the full resolution of the first monitor). Definitely something new. Oh, and you can use the desktop tool to rearrange them as the case describes, but then three monitors go to sleep and one now displays a small res desktop surrounded by a thick black border. I'm really curious how it ends up going down _that_ codepath. Expected results: you should be able to move cursor from one screen to another flawlessly in all setups. In different resolution setup there should be borders where you cannot pass to another screen accordingly
You need linux-firmware >= 20131106-0.1.git7d0c7a8
This need to be retested but here i can not reproduce with : linux-firmware-20140102-0.2.git52d77db.el7.noarch kernel-3.10.0-89 mesa-dri-drivers-9.2.5 xorg-x11-drv-ati-7.2.0-8.20140113git3213df1 xorg-x11-glamor-0.5.1-4.20140115gitfb4d046c
We believe this is already fixed but moving to 7.1
This is fixed in Build : RHEL-7.0-20140214.0 However a different bug is now present: https://bugzilla.redhat.com/show_bug.cgi?id=1076774
This should already work in 7.0 but reassigning to kernel as if it is an issue than it is a kernel issue.
*** Bug 1076770 has been marked as a duplicate of this bug. ***
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHSA-2015-2152.html