Bug 1393022

Summary: External displayport monitor connected through usb-c stays black
Product: [Fedora] Fedora Reporter: Reinout van Schouwen <reinouts>
Component: xorg-x11-drv-intelAssignee: Adam Jackson <ajax>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 24CC: ajax, hdegoede, knutjbj, xgl-maint
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-08 19:10:51 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Reinout van Schouwen 2016-11-08 17:22:28 UTC 
Description of problem:

I have a Dell XPS15 9550 with USB-C (thunderbolt) port.
I have connected a Dell external displayport monitor to the laptop using a StarTech Thunderbolt 3 to Dual Displayport adapter (Part #TB32DP2).

Using any recent kernel (currently Linux localhost.localdomain 4.8.4-200.fc24.x86_64) the external monitor is identified perfectly, however, the screen always stays black.

I have already updated my BIOS to the latest revision.

Version-Release number of selected component (if applicable):
xorg-x11-drv-intel-2.99.917-24.20160712.fc24.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Connect displayport monitor to XPS15 over a usb-c adapter
2.
3.

Actual results:
Black screen

Expected results:
Image on screen

Additional info:
xrandr output:

$ xrandr
Screen 0: minimum 320 x 200, current 5760 x 2160, maximum 8192 x 8192
eDP-1 connected primary 3840x2160+0+0 (normal left inverted right x axis y axis) 346mm x 194mm
   3840x2160     60.00*+
   2048x1536     60.00  
   1920x1440     60.00  
   1856x1392     60.01  
   1792x1344     60.01  
   1600x1200     60.00  
   1400x1050     59.98  
   1280x1024     60.02  
   1280x960      60.00  
   1024x768      60.04    60.00  
   960x720       60.00  
   928x696       60.05  
   896x672       60.01  
   800x600       60.00    60.32    56.25  
   700x525       59.98  
   640x512       60.02  
   640x480       60.00    59.94  
   512x384       60.00  
   400x300       60.32    56.34  
   320x240       60.05  
DP-1 connected 1920x1200+3840+0 (normal left inverted right x axis y axis) 518mm x 324mm
   1920x1200     59.95*+
   1920x1080     60.00  
   1600x1200     60.00  
   1680x1050     59.95  
   1280x1024     60.02  
   1280x960      60.00  
   1024x768      60.00  
   800x600       60.32  
   640x480       59.94  
   720x400       70.08  
HDMI-1 disconnected (normal left inverted right x axis y axis)
DP-2 disconnected (normal left inverted right x axis y axis)
HDMI-2 disconnected (normal left inverted right x axis y axis)

lspci output:
$ sudo lspci
[sudo] wachtwoord voor reinout: 
00:00.0 Host bridge: Intel Corporation Skylake Host Bridge/DRAM Registers (rev 07)
00:01.0 PCI bridge: Intel Corporation Skylake PCIe Controller (x16) (rev 07)
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06)
00:04.0 Signal processing controller: Intel Corporation Skylake Processor Thermal Subsystem (rev 07)
00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller (rev 31)
00:14.2 Signal processing controller: Intel Corporation Sunrise Point-H Thermal subsystem (rev 31)
00:15.0 Signal processing controller: Intel Corporation Sunrise Point-H Serial IO I2C Controller #0 (rev 31)
00:15.1 Signal processing controller: Intel Corporation Sunrise Point-H Serial IO I2C Controller #1 (rev 31)
00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI #1 (rev 31)
00:17.0 RAID bus controller: Intel Corporation 82801 Mobile SATA Controller [RAID mode] (rev 31)
00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #1 (rev f1)
00:1c.1 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #2 (rev f1)
00:1d.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #9 (rev f1)
00:1d.4 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #13 (rev f1)
00:1d.6 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #15 (rev f1)
00:1f.0 ISA bridge: Intel Corporation Sunrise Point-H LPC Controller (rev 31)
00:1f.2 Memory controller: Intel Corporation Sunrise Point-H PMC (rev 31)
00:1f.3 Audio device: Intel Corporation Sunrise Point-H HD Audio (rev 31)
00:1f.4 SMBus: Intel Corporation Sunrise Point-H SMBus (rev 31)
01:00.0 3D controller: NVIDIA Corporation GM107M [GeForce GTX 960M] (rev a2)
02:00.0 Network controller: Broadcom Limited BCM43602 802.11ac Wireless LAN SoC (rev 01)
03:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader (rev 01)
04:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller (rev 01)
06:00.0 PCI bridge: Intel Corporation DSL6340 Thunderbolt 3 Bridge [Alpine Ridge 2C 2015]
07:00.0 PCI bridge: Intel Corporation DSL6340 Thunderbolt 3 Bridge [Alpine Ridge 2C 2015]
07:01.0 PCI bridge: Intel Corporation DSL6340 Thunderbolt 3 Bridge [Alpine Ridge 2C 2015]
07:02.0 PCI bridge: Intel Corporation DSL6340 Thunderbolt 3 Bridge [Alpine Ridge 2C 2015]
08:00.0 System peripheral: Intel Corporation DSL6340 Thunderbolt 3 NHI [Alpine Ridge 2C 2015]
Comment 1 Hans de Goede 2016-11-08 18:54:55 UTC 
Interesting, I did not know until now that USB-C even had an alternative role where both high-speed channel-pairs are used for display-port, but I just checked and it seems that this is standard USB-C and not something custom.

I know that display-port over USB-C works on the XPS9550 when using a more standard USB-C to single display-port adapter. Have you tried using the other displayport on the adapter?
Comment 2 Hans de Goede 2016-11-08 18:55:49 UTC 
Also have you tried upgrading the thunderbolt controller firmware ? (AFAIK this can only be done from Windows)
Comment 3 Reinout van Schouwen 2016-11-09 10:47:59 UTC 
(In reply to Hans de Goede from comment #1)

> I know that display-port over USB-C works on the XPS9550 when using a more
> standard USB-C to single display-port adapter. Have you tried using the
> other displayport on the adapter?

Yes. Now, every 10 seconds or so my desktop is shortly shown on the monitor, a little distorted it seems, and then disappears again!

> Also have you tried upgrading the thunderbolt controller firmware ? (AFAIK this  > can only be done from Windows)

I don't have Windows on the machine any more, so no. Should it be possible using FreeDOS? Maybe I should talk to our IT department to see whether we can temporarily swap the harddisk or something...
Comment 4 Hans de Goede 2016-11-09 11:48:18 UTC 
(In reply to Reinout van Schouwen from comment #3)
> (In reply to Hans de Goede from comment #1)
> 
> > I know that display-port over USB-C works on the XPS9550 when using a more
> > standard USB-C to single display-port adapter. Have you tried using the
> > other displayport on the adapter?
> 
> Yes. Now, every 10 seconds or so my desktop is shortly shown on the monitor,
> a little distorted it seems, and then disappears again!

Well that is progress (in some way). Note that there have been some displayport related fixes for skylake GPUs recently, can you try kernel 4.8.6 please? From here: http://koji.fedoraproject.org/koji/buildinfo?buildID=814667

Download both the kernel-core and kernel-modules x86_64 rpms and put them together in a directory, then from that directory run:

sudo rpm -ivh "kernel*.rpm"

Note "-ivh' rather then the standard "-Uvh" so that you keep your current kernel and can always select it in the bootloader in case 4.8.6 fails to boot for you for some reason.

Then reboot and see how things go.

If that does not work, one thing you can try is getting a simple USB-C to displayport adapter like I'm using, these are not that expensive, e.g. : https://www.aliexpress.com/item/CY-Gold-Color-USB-C-Type-C-USB-3-1-Male-to-DisplayPort-DP-1080P-Monitor/32439890556.html?

If you wait one day with ordering you even get an extra discount for the 11.11 sale.

> > Also have you tried upgrading the thunderbolt controller firmware ? (AFAIK this  > can only be done from Windows)
> 
> I don't have Windows on the machine any more, so no. Should it be possible
> using FreeDOS? Maybe I should talk to our IT department to see whether we
> can temporarily swap the harddisk or something...

I think you can only do the upgrade under Windows, I have not tried myself yet.
Comment 5 Fedora End Of Life 2017-07-25 23:48:39 UTC 
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '24'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Comment 6 Fedora End Of Life 2017-08-08 19:10:51 UTC 
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.