Hide Forgot
Filed from caserun (https://tcms.engineering.redhat.com/run/289603/#caserun_13279407) 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. execute xrandr and check your native resolution (marked with +) 1. change resolution: $ xrandr --output LVDS1 --mode 640x480 2. change resolution back to native via xrandr command Actual results: Technically no bug as dictated by our test case but the interpolation is awful for this whole range of resolutions: 1680x1050 1400x1050 1280x1024 1440x900 1280x960 1280x854 1280x800 1280x720 <-- If you have to pick one, this is the worst. 1152x768 For example black-on-white text has horizontal white lines running through it. This may be an issue with the prototype HW we have for testing - I don't know since I've never seen this issue. If interpolation is up to the display then I guess this is definitely not a bug. Expected results: screen should be changed to 640x480 and back to native resolution
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.
Still horrendous on: 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 (In reply to Lyude from comment #2) > 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. I'll bring it to Boston office for you. =)
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.