<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 - [i915][BYT] Blank screen on MIPI panel"
href="https://bugs.freedesktop.org/show_bug.cgi?id=101205">101205</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>[i915][BYT] Blank screen on MIPI panel
</td>
</tr>
<tr>
<th>Product</th>
<td>DRI
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Hardware</th>
<td>x86-64 (AMD64)
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux (All)
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</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>dimitry@cos.flag.org
</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>Created <span class=""><a href="attachment.cgi?id=131526" name="attach_131526" title="Syslog for the faulty Pipo X8 (Z3735F) unit">attachment 131526</a> <a href="attachment.cgi?id=131526&action=edit" title="Syslog for the faulty Pipo X8 (Z3735F) unit">[details]</a></span>
Syslog for the faulty Pipo X8 (Z3735F) unit
I have two very similar Baytrail devices: Pipo X8 and Pipo X8S.
The former (X8) is based on Z3736F and runs fine. The latter (X8S) is based on
Z3735F and gets a blank screen once the i915 driver is loaded.
Both units run identical set up software-wise:
distro: Gentoo
kernel: drm-tip branch (713f8e of 16 May)
xorg: 1.19.2
xf86-video-intel: 2.99.917_p20170216
Comparing the logs I can see the faulty unit seems to be missing some MIPI
initialization commands. Here is the diff of the logs between the good unit
(left) and the faulty one (right):
<a href="https://www.diffchecker.com/tv4c7jTl">https://www.diffchecker.com/tv4c7jTl</a>
The HDMI output on the faulty unit works fine. Attached are the logs for both
the good and the faulty units with drm.debug=0x1e</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>