Bug 94712 - second xserver has no connected output with radeon DIS
Summary: second xserver has no connected output with radeon DIS
Status: RESOLVED MOVED
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/Radeon (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: xf86-video-ati maintainers
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-03-26 07:16 UTC by jydcome
Modified: 2019-11-19 07:55 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
dmesg (85.86 KB, text/plain)
2016-03-28 08:33 UTC, jydcome
no flags Details
Xorg.1.log (41.71 KB, text/plain)
2016-03-28 08:33 UTC, jydcome
no flags Details

Description jydcome 2016-03-26 07:16:42 UTC
Hi, my notebook thinkpad w500 has two video cards, intel / radeon. When i test some 3d games by wine or some videos by mpv using dri_prime=1 to dynamic enable radeon card, the game/video window always tearing, see bug report https://bugs.freedesktop.org/show_bug.cgi?id=76367.

So i try to start second xserver directly use radeon card, command like this:
$xinit /usr/bin/openbox-session -- :1 -ac -configdir radeon (/etc/X11/Xwrapper.config already changed to allowed_users=anybody)

I put 20-radeon.conf into /etc/X11/radeon, which is:
Section "Device"
Identifier "radeonGPU"
Driver "radeon"
BusID "PCI:1:0:0"
Option "DRI" "3"
EndSection

The basic thouhgts is default xserver using intel+radoen by dri prime that is  nice technique still needs upgrade, start second xsever just using one video cadr(intel or radeon) as needed. 

If i just put 20-intel.conf into /etc/X11/radeon (just use intel IDG), the second xserver runs ok. Just using radeon DIS the second xserver started without any conntected output. run 'DISPLAY=:1 xrandr' could confirm that, all disconnected, so it's black screen on second xserver vtn, and default xserver vt7 still ok.

Am i missing something to config second xserver using radeon DIS, or it's not possible?
Comment 1 Michel Dänzer 2016-03-28 07:55:52 UTC
Please attach the Xorg log and the output of dmesg and xrandr corresponding to the problem.
Comment 2 jydcome 2016-03-28 08:32:42 UTC
(In reply to Michel Dänzer from comment #1)
> Please attach the Xorg log and the output of dmesg and xrandr corresponding
> to the problem.

My basic thouhgts is default xserver using intel+radoen by dri prime, start second xsever just using one video card(intel or radeon) if needed. Both of two xservers using the same physical display, whatever internal or external.

Here is my debug message when second xsever just using radeon card:
  
~$ DISPLAY=:1 xrandr
Screen 0: minimum 320 x 200, current 1024 x 768, maximum 8192 x 8192
DVI-0 disconnected (normal left inverted right x axis y axis)
LVDS-1 disconnected (normal left inverted right x axis y axis)
DisplayPort-1 disconnected (normal left inverted right x axis y axis)
VGA-1 disconnected (normal left inverted right x axis y axis)

~$ xrandr  (intel+radeon dri prime)
Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767
LVDS1 connected (normal left inverted right x axis y axis)
   1920x1200     60.00 +  59.95    49.85  
   (...)
DP1 disconnected (normal left inverted right x axis y axis)
VGA1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 368mm x 207mm
   1920x1080     60.00*+
   (...)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)

And dmesg & Xorg.1.log
Comment 3 jydcome 2016-03-28 08:33:28 UTC
Created attachment 122592 [details]
dmesg
Comment 4 jydcome 2016-03-28 08:33:56 UTC
Created attachment 122593 [details]
Xorg.1.log
Comment 5 Martin Peres 2019-11-19 07:55:49 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/driver/xf86-video-ati/issues/155.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.