<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - mesa-18.1: regression with TFP on intel"
href="https://bugs.freedesktop.org/show_bug.cgi?id=107117#c16">Comment # 16</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - mesa-18.1: regression with TFP on intel"
href="https://bugs.freedesktop.org/show_bug.cgi?id=107117">bug 107117</a>
from <span class="vcard"><a class="email" href="mailto:fourdan@xfce.org" title="Olivier Fourdan <fourdan@xfce.org>"> <span class="fn">Olivier Fourdan</span></a>
</span></b>
<pre>(In reply to Denis from <a href="show_bug.cgi?id=107117#c15">comment #15</a>)
<span class="quote">> Olivier, could you please advice, how to verify the driver in use?</span >
The DDX can be seen in the Xorg logs, either in
"~/.local/share/xorg/Xorg.*.log" or in "/var/log/Xorg.*.log" depending on your
system.
There, you should see either "modeset" or "intel" depending on which DDX you've
selected in your xorg.conf (or xorg.conf.d/).
e.g. for modesetting:
(II) modesetting: Driver for Modesetting Kernel Drivers: kms
(II) modeset(0): using drv /dev/dri/card0
for intel:
(II) intel: Driver for Intel(R) Iris(TM) Graphics
(II) intel: Driver for Intel(R) Iris(TM) Pro Graphics
(II) intel(0): Using Kernel Mode Setting driver: i915, version 1.6.0
20180308
(--) intel(0): Integrated Graphics Chipset: Intel(R) HD Graphics 4400
Point is, something has changed in Mesa 18.1 which causes <span class=""><a href="attachment.cgi?id=140540" name="attach_140540" title="Simple reproducer">attachment 140540</a> <a href="attachment.cgi?id=140540&action=edit" title="Simple reproducer">[details]</a></span> to
render a white window with the Xorg modesetting driver with glamor but not with
the intel DDX, at least on my hardware (using Fedora 28 here with
xserver-1.20)... Many distributions have switched to the modesetting driver by
default with Intel hardware.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>