Bug 1624607

Summary:	amdgpu.dc=1 triggers graphic card not recognizing native screen resolution
Product:	[Fedora] Fedora	Reporter:	Germano Massullo (Thetra) <germano.massullo>
Component:	xorg-x11-drv-amdgpu	Assignee:	Christopher Atherton <cjatherton>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	28	CC:	cjatherton, germano.massullo
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-05-28 19:24:53 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:
Embargoed:

Description Germano Massullo (Thetra) 2018-09-02 09:16:32 UTC

Clone of upstream bugreport:https://bugs.freedesktop.org/show_bug.cgi?id=107465
Attachments are on upstream bugzilla

Videocard: RX480
OS: Fedora 28 KDE
Kernel 4.17.9-200.fc28.x86_64

Sometimes when I poweroff the screen, then after some time I turn on it again, the system cannot recognize native screen resolution, and sets it to a weird one. In Plasma system settings, the monitor name is unknown and the native resolution is missing (1600x1050), other resolutions are available instead.. After playing with some resolutions, suddendly the screen name (ViewSonic etc.) returns back.

MrCooper user in #radeon Freenode chat, suggested me to start the system with amdgpu.dc=0 flag. 24 hours of testing seems to confirm that such flag fixes the problem.

I attach dmesg and xorg.0.log of system experiencing the problem

Comment 1 Germano Massullo (Thetra) 2018-09-02 09:26:01 UTC

Just a clarification: title "amdgpu.dc=1" is not meant as having amdgpu.dc=1 as setted boot parameter, the situation is:
no boot parameter = problem triggered
amdgpu.dc=0 = no problem

Comment 2 Ben Cotton 2019-05-02 20:59:58 UTC

This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. 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 '28'.

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 28 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 3 Germano Massullo (Thetra) 2019-05-03 07:46:28 UTC

At the moment I cannot access to the affected machine, so if in the future I will experience it again, I will reopen the bugreport

Comment 4 Ben Cotton 2019-05-28 19:24:53 UTC

Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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.