[Bug 94811] ATI radeon driver displays nothing or a client refused to switch message on hybrid graphics - bugzilla-daemon

From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 94811] ATI radeon driver displays nothing or a client refused to switch message on hybrid graphics
Date: Mon, 04 Apr 2016 10:12:11 +0000	[thread overview]
Message-ID: <bug-94811-502@http.bugs.freedesktop.org/> (raw)

[-- Attachment #1.1: Type: text/plain, Size: 2056 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=94811

            Bug ID: 94811
           Summary: ATI radeon driver displays nothing or a client refused
                    to switch message on hybrid graphics
           Product: DRI
           Version: unspecified
          Hardware: Other
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Radeon
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: saurav1.net@gmail.com

Created attachment 122692
  --> https://bugs.freedesktop.org/attachment.cgi?id=122692&action=edit
dmesg output for the radeon driver

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.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 3546 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel