| Summary: | Test case failure: Screen - Resolution Change on Dell Precision 7710 - Amethyst XT [Radeon R9 M295X] [1002:6921] | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Vasiliy Sharapov <vsharapo> |
| Component: | xorg-x11-drv-ati | Assignee: | Lyude <lyude> |
| Status: | CLOSED WONTFIX | QA Contact: | Desktop QE <desktop-qa-list> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 7.5 | CC: | lyude, tpelka |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-12-15 07:46:49 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Vasiliy Sharapov
2016-10-04 06:08:40 UTC
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. |