<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - Upgrade to FC 27 broke support for DisplayPort 1.2 three port adapter"
href="https://bugs.freedesktop.org/show_bug.cgi?id=105199">105199</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>Upgrade to FC 27 broke support for DisplayPort 1.2 three port adapter
</td>
</tr>
<tr>
<th>Product</th>
<td>DRI
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Hardware</th>
<td>Other
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux (All)
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>major
</td>
</tr>
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Component</th>
<td>DRM/Intel
</td>
</tr>
<tr>
<th>Assignee</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>david283@gmail.com
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>CC</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr></table>
<p>
<div>
<pre>NOTE: I received an email from Ian Pilcher through
<a href="mailto:users@lists.fedoraproject.org">users@lists.fedoraproject.org</a>
saying =
Intel broke multi-stream transport in 4.15/4.14.4:
<a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - [KBL] Dell TB16 external displays blank in kernel 4.14.4+"
href="show_bug.cgi?id=104425">https://bugs.freedesktop.org/show_bug.cgi?id=104425</a>
<a class="bz_bug_link
bz_status_NEW "
title="NEW - [CFL] black screen with DP MST"
href="show_bug.cgi?id=104158">https://bugs.freedesktop.org/show_bug.cgi?id=104158</a>
------
My original issue/bug =
I had a working Fedora 24 box for almost 2 years that I decided to
upgrade to FC 27. I have 3 monitors and used a 3 way adapter from
StarTech to adapt the single display port from my Intel NUC to support
my 3 displays. Again this worked fine for years. After the upgrade
this setup stopped working.
My system has an encrypted root and home partition, and an
un-encrypted boot partition. When I power on the computer with the 3
way adapter I get bios screens and the grub menu. If I select the old
FC24 kernel to boot, the system proceeds to the password screen where
I unlock my root partition, and then to the user login screen for
fedora. But if I select one of the new FC 27 kernels on the grub menu
I get a black screen only, no password screen to un-encrypt. If I use
a straight through DisplayPort cable to power only one screen, the new
Kernels work fine and I can unlock and login.
Also, adding *nomodeset* to the kernel boot options will allow the new
kernels to work with the adapter, but all 3 screens mirror and
performance is way down. I think this option doesn't use Intel's
drivers?
I looked at Xorg vs Wayland as a possible cause, but the option to
select that is on the user login screen, would that have any effect on
the un-encrypt password screen just after grub?
My graphics are Intel Iris 6100. My hardware is an Intel NUC with i7
processor. Video card is on chip.
So I am stuck. Please help?
*****
I made sure my Intel drivers where fully updated =
$ sudo dnf install
<a href="https://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-$(rpm">https://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-$(rpm</a>
-E %fedora).noarch.rpm
Last metadata expiration check: 0:59:03 ago on Tue 16 Jan 2018 09:22:40 PM CST.
rpmfusion-free-release-27.noarch.rpm 24 kB/s | 20 kB 00:00
Package rpmfusion-free-release-27-1.noarch is already installed, skipping.
Dependencies resolved.
Nothing to do.
Complete!
$ sudo dnf install intel-gpu-tools libva-intel-driver libva-utils
libva mesa-libOSMesa cairo-gobject cairo mesa-dri-drivers
mesa-filesystem mesa-libEGL mesa-libGL mesa-libGLES mesa-libgbm
mesa-libglapi mesa-libwayland-egl mesa-libxatracker
Last metadata expiration check: 0:59:23 ago on Tue 16 Jan 2018 09:22:40 PM CST.
Package intel-gpu-tools-2.99.917-31.20171025.fc27.x86_64 is already
installed, skipping.
Package libva-intel-driver-1.8.3-2.fc27.x86_64 is already installed, skipping.
Package libva-intel-driver-1.8.3-2.fc27.i686 is already installed, skipping.
Package libva-utils-1.8.3-4.fc27.x86_64 is already installed, skipping.
Package libva-1.8.3-3.fc27.x86_64 is already installed, skipping.
Package libva-1.8.3-3.fc27.i686 is already installed, skipping.
Package mesa-libOSMesa-17.2.4-2.fc27.x86_64 is already installed, skipping.
Package mesa-libOSMesa-17.2.4-2.fc27.i686 is already installed, skipping.
Package cairo-gobject-1.15.10-1.fc27.x86_64 is already installed, skipping.
Package cairo-gobject-1.15.10-1.fc27.i686 is already installed, skipping.
Package cairo-1.15.10-1.fc27.x86_64 is already installed, skipping.
Package cairo-1.15.10-1.fc27.i686 is already installed, skipping.
Package mesa-dri-drivers-17.2.4-2.fc27.x86_64 is already installed, skipping.
Package mesa-dri-drivers-17.2.4-2.fc27.i686 is already installed, skipping.
Package mesa-filesystem-17.2.4-2.fc27.x86_64 is already installed, skipping.
Package mesa-filesystem-17.2.4-2.fc27.i686 is already installed, skipping.
Package mesa-libEGL-17.2.4-2.fc27.x86_64 is already installed, skipping.
Package mesa-libEGL-17.2.4-2.fc27.i686 is already installed, skipping.
Package mesa-libGL-17.2.4-2.fc27.x86_64 is already installed, skipping.
Package mesa-libGL-17.2.4-2.fc27.i686 is already installed, skipping.
Package mesa-libGLES-17.2.4-2.fc27.x86_64 is already installed, skipping.
Package mesa-libgbm-17.2.4-2.fc27.x86_64 is already installed, skipping.
Package mesa-libgbm-17.2.4-2.fc27.i686 is already installed, skipping.
Package mesa-libglapi-17.2.4-2.fc27.x86_64 is already installed, skipping.
Package mesa-libglapi-17.2.4-2.fc27.i686 is already installed, skipping.
Package mesa-libwayland-egl-17.2.4-2.fc27.x86_64 is already installed,
skipping.
Package mesa-libwayland-egl-17.2.4-2.fc27.i686 is already installed, skipping.
Package mesa-libxatracker-17.2.4-2.fc27.x86_64 is already installed, skipping.
Dependencies resolved.
Nothing to do.
Complete!</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
<li>You are the assignee for the bug.</li>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>