Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Filed from caserun (https://tcms.engineering.redhat.com/run/294277/#caserun_13783570)

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. obtain two screens with different resolution
 2. boot to runlevel 3


 1. after you log in disconnect first monitor and connect the other one
 2. check resolution via monitor menu or fbset (from epel or fedora repo)



Actual results: 
Switching from 1920x1080 to 1920x1200 I get a resolution of 1400x1050 on the 1900x1200 monitor

Expected results:
correct resolution should be set

I think I know exactly what this issue is, it's probably not actually a bug. Basically, in order to make sure that the console can get displayed on both monitors fbcon does the very easy method of choosing a single resolution that both monitors can support. If they're different resolutions, then one of the monitors is always going to be at a lower resolution then the other. Additionally, in your case it's very possible that one of those monitors doesn't support 1080p and thus it goes to a lower resolution for both displays.

Mind showing me the full list of supported modes from both monitors? I should be able to tell pretty easily if this is the case.