Bug 1390387 - Screen not recognized after kernel update (wrong resolution, low performance)
Summary: Screen not recognized after kernel update (wrong resolution, low performance)
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-ati
Version: 24
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-31 22:50 UTC by Dylan B.
Modified: 2017-08-08 19:05 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1374385
Environment:
Last Closed: 2017-08-08 19:05:02 UTC
Type: Bug


Attachments (Terms of Use)
Unknown Display (995.38 KB, image/png)
2016-10-31 22:50 UTC, Dylan B.
no flags Details

Description Dylan B. 2016-10-31 22:50:35 UTC
Created attachment 1215939 [details]
Unknown Display

+++ This bug was initially created as a clone of Bug #1374385 +++

Description of problem:
After kernel upgrade, my screen is unrecognized. It is marked as "Unknown display" in Settings, the resolution is wrong and the graphic performance is very low.

There are only two available resolutions by now :
- 1024x768 (4:3)
- 800x600 (4:3)
Before this upgrade, there were plenty other resolutions, including the ideal one for my screen which is 1366x768, now unavailable.

As mentioned before, my graphic performance is now very low. As an example, Minecraft used to run at ~60FPS, but now only runs at ~6FPS.

Version-Release number of selected component (if applicable): the bug appeared first when I upgraded to kernel-4.6.7-300.fc24.x86_64 and is still present in kernel-4.7.2-201.fc24.x86_64.

The last kernel without this bug is kernel-4.5.5-300.fc24.x86_64, which I'll keep installed and use as my default kernel until the problem is resolved.

Additional info:
My graphic card is an ATI Radeon HD 7670M.
In "lspci", it is named "01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7500M/7600M Series]".
Result of "uname -a" with the last kernel with this bug : "Linux fedora-l850-15z 4.7.2-201.fc24.x86_64 #1 SMP Fri Aug 26 15:58:40 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux".

I also attached a screenshot of the display settings.

Comment 1 Fedora End Of Life 2017-07-25 23:42:30 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '24'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 2 Fedora End Of Life 2017-08-08 19:05:02 UTC
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.