[Bug 105891] New: miniDP to external monitor with DVI-D via miniDP to HDMI/DVI-D/DP adapter : DP dual mode HDMI ID: (err -6) and blank screen

[bugzilla-daemon at freedesktop.org]

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

            Bug ID: 105891
           Summary: miniDP to external monitor with DVI-D via miniDP to
                    HDMI/DVI-D/DP adapter : DP dual mode HDMI ID:  (err
                    -6) and blank screen
           Product: DRI
           Version: XOrg git
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: genpur at o2.pl
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

Created attachment 138602
  --> https://bugs.freedesktop.org/attachment.cgi?id=138602&action=edit
dmesg_kernel-4.13.0-38-generic.log

Overview :
Connection from miniDP port (Intel HD Graphics 3000) to DVI-D input of external
monitor (iiyama ProLite E1900S) via miniDP to HDMI/DVI/DP adapter (LogiLink
CV0045A).

Laptop specification:
Dell XPS L502x with Optimus combo

lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core
Processor Family Integrated Graphics Controller (rev 09)
01:00.0 VGA compatible controller: NVIDIA Corporation GF108M [GeForce GT 525M]
(rev ff)

Operating system:
Lubuntu 17.10 64-bit with latest kernels :
a) 4.13.0-38-generic - from official ubuntu repositories (sudo apt-get
dist-upgrade)
b) 4.16.0-041600-generic - from
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16/

Steps to Reproduce:
1) connect like described above in overview

2a) start laptop with kernel (4.13.0-38-generic) with parameters :
    drm.debug=14 video=HDMI-A-1:1280x1024-16 at 75D
drm_kms_helper.edid_firmware=HDMI-A-1:edid/monitor.bin

OR

2b) start laptop with kernel (4.16.0-041600-generic) with parameters :
    drm.debug=14 video=HDMI-A-1:1280x1024-16 at 75D
drm.edid_firmware=HDMI-A-1:edid/monitor.bin


Actual Results:
1) Blank display of external monitor
2) error : [drm:drm_dp_dual_mode_detect [drm_kms_helper]] DP dual mode HDMI ID:
 (err -6)

Expected Results:
Display activated

Additional Information:
When X server has started, I checked some parameters :

cat /sys/class/drm/card1-HDMI-A-1/enabled
enabled

cat /sys/class/drm/card1-HDMI-A-1/status
connected

cat /sys/class/drm/card1-HDMI-A-1/modes
1280x1024
1280x1024
1280x960
1152x864
1024x768
1024x768
1024x768
832x624
800x600
800x600
800x600
800x600
640x480
640x480
640x480
640x480
720x400

------

Before I tried to connect iiyama monitor, I have tried to connect Panasonic-TV
via the same adapter without any extra kernel parameters(just normal launch)
and TV was working correctly. I have got :
[drm:drm_dp_dual_mode_detect [drm_kms_helper]] DP dual mode HDMI ID: DP-HDMI
ADAPTOR\004 (err 0)
instead of
[drm:drm_dp_dual_mode_detect [drm_kms_helper]] DP dual mode HDMI ID:  (err -6)

This is only difference I saw, when display was activated (err 0) and not
activated (err -6).

I supposed that problem might be that EDID is not read corectly from iiyama
monitor via miniDP/HDMI adapter.
So, I saved EDID from this monitor when I have connected to another computer. I
saved EDID of Panasonic-TV, too. I verified both of them and checksum was
correct.
Next I have stored EDID into initramfs. I played with kernel parameters
(drm.edid_firmware=... , video=... ) on connection with Panasonic TV just to be
sure, that I'm using EDID builded-in initram. Display of Panasonic TV seems to
work according to those parameters.

Finally, I have connected iiyama monitor and I tried to force state "on" of
HDMI-A-1 connector but display was not activated.

-- 
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/20180404/d3c2c059/attachment-0001.html>