[Bug 103618] New: Reverse Prime with intel/amdgpu leaves Intel monitor blank
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Wed Nov 8 11:43:25 UTC 2017
https://bugs.freedesktop.org/show_bug.cgi?id=103618
Bug ID: 103618
Summary: Reverse Prime with intel/amdgpu leaves Intel monitor
blank
Product: DRI
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Intel
Assignee: intel-gfx-bugs at lists.freedesktop.org
Reporter: EoD at xmw.de
QA Contact: intel-gfx-bugs at lists.freedesktop.org
CC: intel-gfx-bugs at lists.freedesktop.org
Depends on: 103613
I have a primary discrete AMD card (Tonga) using amdgpu and an Intel iGPU
(Skylake/HD530) using the intel driver.
I enabled DRI3 on both devices, but xrandr only shows the outputs/monitors of
the AMD card.
The main monitor (connected to the AMD Tonga) is active and shows a screen,
while the 2nd monitor (connected to the Intel iGPU) is already active but has
only a blank screen.
When I use "xrandr --setprovideroutputsource 1 0" it flickers a bit and xrandr
shows now all outputs/monitors.
When I try to enable the monitor connected to the iGPU via "xrandr --output
HDMI3 --auto" the 2nd monitor stays active but blank.
When I "extend" my desktop to the 2nd monitor I can leave the desktop with the
mouse, but the monitor is still just blank.
When I use modesetting on the intel card instead, everything works.
Here are further details, including the Xorg.log and the used configs:
https://gist.github.com/EoD/c1c4f2b4afde2d0523e9ea8bb1567452
Referenced Bugs:
https://bugs.freedesktop.org/show_bug.cgi?id=103613
[Bug 103613] Reverse Prime with intel/amdgpu causes segfault in
glamor_block_handler when enabling monitor
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20171108/2f0aeed0/attachment.html>
More information about the intel-gfx-bugs
mailing list