<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED NOTOURBUG - DRM backend does not search for i915_dri.so"
href="https://bugs.freedesktop.org/show_bug.cgi?id=94476#c4">Comment # 4</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED NOTOURBUG - DRM backend does not search for i915_dri.so"
href="https://bugs.freedesktop.org/show_bug.cgi?id=94476">bug 94476</a>
from <span class="vcard"><a class="email" href="mailto:gobogowoli@dlemail.ru" title="gobogowoli@dlemail.ru">gobogowoli@dlemail.ru</a>
</span></b>
<pre>Sorry for the erroneous bug report. When it comes to the Linux graphics stack,
I still only know just enough to be dangerous. I did look into libgbm since the
error was labeled, but I couldn't readily find any documentation about it. I
don't quite know where the lines are drawn between Weston, Mesa, DRI/DRM, etc.
Weston, Mesa, and at least all of their direct dependencies are installed via
Gentoo Portage, so in theory they should be coherent with one another. However,
I have to do some more testing to figure out why Mesa is installing modules in
/usr/lib64/mesa and libgbm is searching for them in /usr/lib/dri. It's likely
that I messed something up along the way, but if not it's a bug for the Gentoo
(or perhaps Mesa) people I suppose. I only did the symlinks as a quickfix; I'm
more concerned about libgbm searching for i965_dri.so instead of i915_dri.so,
regardless of the parent directories.
Since libgbm is part of Mesa (which I didn't know until now), I'll look for
some more documentation on it and see if there's some way to force libgbm to
choose i915_dri.so specifically. I'll submit a bug report to Mesa also if
necessary.
As for which driver is actually being loaded, I'm assuming its swrast_dri.so,
since that's the only other one in /usr/lib64/mesa, and it would explain the
slowness. I attached the log in case anyone is interested.
So thanks for the explanation. I'll look into libgbm some more and see if I can
find a workaround or submit a bug report to Mesa.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>