<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Flickering screen with Intel graphics from specific kernel version onwards (4.2)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=106017#c21">Comment # 21</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Flickering screen with Intel graphics from specific kernel version onwards (4.2)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=106017">bug 106017</a>
from <span class="vcard"><a class="email" href="mailto:udippel@gmail.com" title="Uwe Dippel <udippel@gmail.com>"> <span class="fn">Uwe Dippel</span></a>
</span></b>
<pre>@Lakshmi,
I run into another problem with Intel drivers, this time 5300 on lenovo Helix
2.
Please refer to
<a href="https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817944">https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817944</a>
Here, if you check the logs, it's another clear case of 'giving up'. In this
case however, it seems to wait for EDID, and after showing the screen for some
time, it starts by looking not synchronized, and in the end I'm stuck with a
black display.
Remarkable the output of xrandr, which tried hard, successfully in the
beginning, shows some ridiculous results later, and finally considers the
display 'not connected'; while I don't do anything, don't touch anything. Some
time later it starts trying again.
I wonder if I should file this as a bug here under Freedesktop as well?
(Yes, I do know I should try with the most recent kernel version, too. I will
do so in one of the next days, after having read up (again) how I did it last
time. I do take bets, however, that it doesn't make any difference. I rather
think some bug will be found one day that explains all those unexplained
'giving up's, while the W10 driver on just the other half of the hard disk
performs properly after a reboot.)</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 QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>