Bug 1628530 - monitor NEC MultiSync E233WM powered off via DP to dock of X1 Carbon 4th gen
Summary: monitor NEC MultiSync E233WM powered off via DP to dock of X1 Carbon 4th gen
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: xorg-x11-drv-intel
Version: 7.6
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Adam Jackson
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-09-13 11:19 UTC by Tomas Hudziec
Modified: 2021-02-15 07:42 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-02-15 07:42:37 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Tomas Hudziec 2018-09-13 11:19:21 UTC
Description of problem:
Monitor NEC MultiSync E233WM does not power on when connected through DisplayPort to OneLink+ dock station of laptop Lenovo X1 Carbon 4th generation. The monitor is recognized by system and present in monitors layout, but powered off.

Version-Release number of selected component (if applicable):
xorg-x11-drv-intel-2.99.917-28.20180530.el7.x86_64
kernel-3.10.0-948.el7.x86_64

How reproducible:
always

Steps to Reproduce:
1. have laptop Lenovo X1 Carbon 4th generation connected to OneLink+ dock station
2. power on the machine and proceed to graphical desktop environment
3. connect monitor NEC MultiSync E233WM to dock station via DisplayPort cable

Actual results:
system recognizes the monitor, but it is powered off

Expected results:
the monitor should be powered on and show graphics

Additional info:
00:02.0 VGA compatible controller [0300]: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07)
Tried also to connect to mini-DP on laptop with the same result. (Also to HDMI on laptop, but there was no reaction at all, maybe hw restriction.)
DVI-D output of the monitor connected to dock via DVI-to-DP cable reduction works fine.

Comment 4 RHEL Program Management 2021-02-15 07:42:37 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.


Note You need to log in before you can comment on or make changes to this bug.