Bug 105971 - DVI port is not detecting connected monitor with 4.16.0+ kernel and amdgpu.dc=1 set
Summary: DVI port is not detecting connected monitor with 4.16.0+ kernel and amdgpu.dc...
Status: RESOLVED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/AMDgpu (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-04-10 12:50 UTC by Joel Sass
Modified: 2018-05-07 18:53 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
dmesg output from amdgpu.dc=0 switch (164.48 KB, text/plain)
2018-04-10 12:50 UTC, Joel Sass
no flags Details
Xorg.0.log with amdgpu.dc=0 (61.71 KB, text/plain)
2018-04-10 12:51 UTC, Joel Sass
no flags Details
xrandr with amdgpu.dc=0 (2.14 KB, text/plain)
2018-04-10 12:52 UTC, Joel Sass
no flags Details
lshw output (64.81 KB, text/plain)
2018-04-10 12:53 UTC, Joel Sass
no flags Details
Xorg.0.log with amdgpu.dc=1 (70.28 KB, text/plain)
2018-04-10 13:14 UTC, Joel Sass
no flags Details
dmesg output with amdgpu.dc=1 switch (87.02 KB, text/plain)
2018-04-10 13:15 UTC, Joel Sass
no flags Details
xrandr with amdgpu.dc=1 switch (3.30 KB, text/plain)
2018-04-10 13:15 UTC, Joel Sass
no flags Details

Description Joel Sass 2018-04-10 12:50:12 UTC
Created attachment 138731 [details]
dmesg output from amdgpu.dc=0 switch

Hello. I'm trying to get 4 monitors working on the same desktop. Video card is a Radeon RX560.

root@nope:/tmp# lsb_release -a
LSB Version:	core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch
Distributor ID:	Ubuntu
Description:	Ubuntu 16.04.4 LTS
Release:	16.04
Codename:	xenial

root@nope:/tmp# uname -a
Linux nope 4.16.0+ #1 SMP Mon Apr 2 15:52:14 CEST 2018 x86_64 x86_64 x86_64 GNU/Linux

With kernel switch amdgpu.dc=1, DVI port doesn't detected connected monitor, but displayport MST is detected and utilized properly, allowing me to output video to three monitors from a single displayport.

With kernel switch amdgpu.dc=0, DVI port properly detects connected monitor, but displayport MST is not detected. Instead, displayport MST acts as a single output, and video output is mirrored to all three connected monitors.

This appears to be a kernel issue. Kernel was retrieved from git repo github.com/M-Bab/linux-kernel-amdgpu-binaries

I'm running the AMDGPU.UBUNTU kernel on that repo.

I'll attach dmesg, xrandr and Xorg.0.log output from both kernel switches. 

I'm running amdgpu.dc_log=1 kernel switch for verbose logging.
Comment 1 Joel Sass 2018-04-10 12:51:49 UTC
Created attachment 138732 [details]
Xorg.0.log with amdgpu.dc=0
Comment 2 Joel Sass 2018-04-10 12:52:50 UTC
Created attachment 138733 [details]
xrandr with amdgpu.dc=0
Comment 3 Joel Sass 2018-04-10 12:53:17 UTC
Created attachment 138734 [details]
lshw output
Comment 4 Joel Sass 2018-04-10 13:14:44 UTC
Created attachment 138735 [details]
Xorg.0.log with amdgpu.dc=1
Comment 5 Joel Sass 2018-04-10 13:15:15 UTC
Created attachment 138736 [details]
dmesg output with amdgpu.dc=1 switch
Comment 6 Joel Sass 2018-04-10 13:15:32 UTC
Created attachment 138737 [details]
xrandr with amdgpu.dc=1 switch
Comment 7 Joel Sass 2018-04-10 13:18:48 UTC
A note about the Xorg.0.log with amdgpu.dc=0,

I see that the amdgpu module doesn't appear to be loaded. X came up just fine without the driver being loaded, and GPU desktop acceleration still worked just fine with compiz in gnome-flashback.
Comment 8 Joel Sass 2018-05-07 18:53:57 UTC
Update:

looks like the DVI output detection of the monitor has been fixed in drm-fixes-4.17 from agd5f here: https://cgit.freedesktop.org/~agd5f/linux/?h=drm-fixes-4.17

had to compile it myself, but works relatively well. When plugging in a new monitor, the size was not properly detected, but it's better than freezing.

Thanks!


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.