Bug 80187 - [hsw mst] MST required for HP UltraSlim Dock 2013
Summary: [hsw mst] MST required for HP UltraSlim Dock 2013
Status: CLOSED DUPLICATE of bug 72795
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-06-18 14:04 UTC by Steffen Weber
Modified: 2017-07-24 22:53 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
xrandr --verbose (8.70 KB, text/plain)
2014-06-18 14:05 UTC, Steffen Weber
no flags Details
dmesg (54.20 KB, text/plain)
2014-06-18 14:05 UTC, Steffen Weber
no flags Details
X.Org log (46.91 KB, text/plain)
2014-06-18 14:05 UTC, Steffen Weber
no flags Details
Linux kernel config (85.56 KB, text/plain)
2014-06-18 14:06 UTC, Steffen Weber
no flags Details
dmesg drm.debug=0xe (140.16 KB, text/plain)
2014-06-18 14:16 UTC, Steffen Weber
no flags Details

Description Steffen Weber 2014-06-18 14:04:48 UTC
Notebook: HP EliteBook 840 G1 (Core i7-4600U, HD Graphics 4000)
Docking station: HP UltraSlim Dock 2013
Monitors: 2x Dell U2414H (1920x1080, DisplayPort)
Software: Linux 3.15.1, X.Org 1.15.99.903, xf86-video-intel 2.99.912

The docking station has two DisplayPort connectors. Both are connected to an external Dell U2414H monitor. But GNOME and xrandr only see DP1 but not DP2. (And for some reason the first external monitor is mirrored on the second external monitor.)

# xrandr 
Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767
eDP1 connected (normal left inverted right x axis y axis)
    [...]
DP1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 527mm x 296mm
    [...]
HDMI1 disconnected (normal left inverted right x axis y axis)
DP2 disconnected (normal left inverted right x axis y axis)
HDMI2 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)
Comment 1 Steffen Weber 2014-06-18 14:05:14 UTC
Created attachment 101300 [details]
xrandr --verbose
Comment 2 Steffen Weber 2014-06-18 14:05:28 UTC
Created attachment 101301 [details]
dmesg
Comment 3 Daniel Vetter 2014-06-18 14:05:55 UTC
Please boot with drm.debug=0xe, reproduce the issue and then attach dmesg for everything.

Also, is this a regression?
Comment 4 Steffen Weber 2014-06-18 14:05:55 UTC
Created attachment 101302 [details]
X.Org log
Comment 5 Steffen Weber 2014-06-18 14:06:35 UTC
Created attachment 101303 [details]
Linux kernel config
Comment 6 Steffen Weber 2014-06-18 14:16:23 UTC
Created attachment 101305 [details]
dmesg drm.debug=0xe

Thank you for the quick reply. I've booted with drm.debug=0xe and attached the dmesg output.

I've never used external monitors before and therefore at the moment cannot say whether this is a regression or not. Would it help if I tried to reproduce this problem with a) old Linux Kernel b) old X.Org or c) old xf86-video-intel?

(Btw, both external displays are independently recognized in Windows 7. So this is not a hardware issue.)
Comment 7 Steffen Weber 2014-06-18 14:17:45 UTC
(In reply to comment #0)
> Notebook: HP EliteBook 840 G1 (Core i7-4600U, HD Graphics 4000)

Just noticed a typo. Must be "HD Graphics 4400".
Comment 8 Steffen Weber 2014-06-18 16:58:22 UTC
Good news: David Airlie's "drm-i915-mst-support" branch (http://cgit.freedesktop.org/~airlied/linux/log/?h=drm-i915-mst-support) has solved the problem! :)

Will those patches be part of Linux 3.16?
Comment 9 Jani Nikula 2014-06-23 11:23:10 UTC
(In reply to comment #8)
> Good news: David Airlie's "drm-i915-mst-support" branch
> (http://cgit.freedesktop.org/~airlied/linux/log/?h=drm-i915-mst-support) has
> solved the problem! :)
> 
> Will those patches be part of Linux 3.16?

No. Not sure about 3.17 either.

*** This bug has been marked as a duplicate of bug 72795 ***


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.