Bug 1323645

Summary: ATI radeon driver displays nothing or a client refused to switch message on hybrid graphics
Product: [Fedora] Fedora Reporter: Saurav <sengupta01.saurav>
Component: xorg-x11-drv-atiAssignee: X/OpenGL Maintenance List <xgl-maint>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 23CC: massi.ergosum, xgl-maint
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-12-20 19:47:18 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:
Attachments:
Description Flags
dmesg output for the radeon driver
none
Sample XOrg configuration for the radeon driver
none
XOrg log for the radeon driver none

Description Saurav 2016-04-04 10:37:18 UTC 
Created attachment 1143301 [details]
dmesg output for the radeon driver

Description of problem:
On a Lenovo G50-80 with Intel HD Graphics 5500 (Broadwell GT2) and Advanced Micro Devices [AMD/ATI] Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330] using vgaswitcheroo with echo DDIS > /sys/kernel/debug/vgaswitcheroo/switch results in a blank screen on logging out or in a message that client 0 refused to switch and a reversion to the login screen (depending on the display manager in use) on logging out and trying to log back in. The computer can be powered off normally using the power button or the options in the login screen if visible or by switching to a different VT. Trying to use the radeon driver with an XOrg configuration file like the one attached results in the display manager not starting (other VTs remain operational). The XOrg log (attached) shows that the radeon driver fails to find a screen to its liking, 
> (EE) RADEON(0): No modes.
> (EE) Screen(s) found, but none have a usable configuration.
and then gives up altogether:-
> (EE) no screens found(EE)

The message "radeon 0000:04:00.0: VCE init error (-22)." appears during boot; the dmesg output for radeon is attached.

The problem occurs irrespective of whether the module parameter radeon.runpm = 0 or not.

The radeon configuration attached is adapted from the one used by Ubuntu 15.10 for fglrx. fglrx works properly on Ubuntu 15.10.

Version-Release number of selected component (if applicable):
7.6.1-3.20160215gitd41fccc

I have reported this upstream.
Comment 1 Saurav 2016-04-04 10:37:56 UTC 
Created attachment 1143302 [details]
Sample XOrg configuration for the radeon driver
Comment 2 Saurav 2016-04-04 10:38:31 UTC 
Created attachment 1143303 [details]
XOrg log for the radeon driver
Comment 3 Saurav 2016-04-06 22:39:37 UTC 
From what I've read in comments upstream, apparently the radeon driver does not automatically offload the discrete GPU's content to the integrated GPU's buffer on systems with offloading GPUs that aren't connected to a display unit directly (where the discrete GPU's content is copied to the integrated one's buffer and then rendered by the latter). The GPU can be activated by setting the DRI_PRIME environment value to 1 for the program that needs to be run via the discrete GPU. So this works in a way, but is inconvenient if we want to run the entire session through the discrete GPU (I'm guessing that we would have to run the display manager itself, GDM, LightDM, etc., using DRI_PRIME). Being able to automatically select the GPU, e.g., the way fglrx does on (pre-16.04) Ubuntu using an XOrg configuration file, would be helpful.
Comment 4 Fedora End Of Life 2016-11-25 07:14:48 UTC 
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. 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 '23'.

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 23 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 5 Fedora End Of Life 2016-12-20 19:47:18 UTC 
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.