All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 105911] DVI-D monitor connected to DVI-I output not detected (regression from kernel 4.14.32 to kernel 4.16.0 using graphic core)
Date: Thu, 04 Oct 2018 23:09:21 +0000	[thread overview]
Message-ID: <bug-105911-502-ehcs44vUpD@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-105911-502@http.bugs.freedesktop.org/>


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

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

--- Comment #13 from tnmailinglists@gmail.com ---
I now booted with amdgpu.dc_log=1 and found the following in my log when DC is
on (I'm currently on 4.15.0.36):

[    1.479998] [drm] DC: create_links: connectors_num: physical:4, virtual:0
[    1.480001] [drm] Connector[0] description:signal 32
[    1.480029] [drm] Connector[1] description:signal 4
[    1.480031] [drm] dce110_link_encoder_construct: Failed to get
encoder_cap_info from VBIOS with error code 4!
[    1.480046] [drm] Connector[2] description:signal 2
[    1.480048] [drm] dce110_link_encoder_construct: Failed to get
encoder_cap_info from VBIOS with error code 4!
[    1.480064] [drm] Connector[3] description:signal 2
[    1.480066] [drm] dce110_link_encoder_construct: Failed to get
encoder_cap_info from VBIOS with error code 4!
[    1.492083] [drm] Display Core initialized
[    1.492091] [drm] Display Core initialized!
[    1.492427] [drm] link=0, dc_sink_in=          (null) is now Disconnected
[    1.492555] [drm] link=1, dc_sink_in=          (null) is now Disconnected
[    1.492683] [drm] link=2, dc_sink_in=          (null) is now Disconnected
[    1.505440] [drm] SADs count is: -2, don't need to read it
[    1.505453] [drm] [Detect]   [DDVI][ConnIdx:3] EDID goes here
[    1.505455] [drm] dc_link_detect: EDID decoded goes here
[    1.505456] [drm] link=3, dc_sink_in=        (ptrval) is now Connected

This does seem to show that connector 3 is incorrectly identified as dual link
DVI-D, or at least missing/not using the analogue part.

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

[-- Attachment #1.2: Type: text/html, Size: 2599 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

  parent reply	other threads:[~2018-10-04 23:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-105911-502@http.bugs.freedesktop.org/>
2018-04-06  8:09 ` [Bug 105911] DVI-D monitor connected to DVI-I output not detected (regression from kernel 4.14.32 to kernel 4.16.0 using graphic core) bugzilla-daemon
2018-04-06  8:15 ` bugzilla-daemon
2018-04-06  8:34 ` bugzilla-daemon
2018-04-06  8:51 ` bugzilla-daemon
2018-04-06 14:12 ` bugzilla-daemon
2018-04-07 16:49 ` bugzilla-daemon
2018-04-30 14:22 ` bugzilla-daemon
2018-09-27 21:45 ` bugzilla-daemon
2018-10-04 23:09 ` bugzilla-daemon [this message]
2019-11-19  8:35 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-105911-502-ehcs44vUpD@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.