<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - [865G] Intel OpenGL rendering not starting"
href="https://bugs.freedesktop.org/show_bug.cgi?id=88275#c7">Comment # 7</a>
on <a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - [865G] Intel OpenGL rendering not starting"
href="https://bugs.freedesktop.org/show_bug.cgi?id=88275">bug 88275</a>
from <span class="vcard"><a class="email" href="mailto:jason@jlekstrand.net" title="Jason Ekstrand <jason@jlekstrand.net>"> <span class="fn">Jason Ekstrand</span></a>
</span></b>
<pre>(In reply to Chris Wilson from <a href="show_bug.cgi?id=88275#c6">comment #6</a>)
<span class="quote">> (In reply to Jason Ekstrand from <a href="show_bug.cgi?id=88275#c4">comment #4</a>)
> > Looks like your X server isn't built with present support and the intel
> > driver is requiring it. This is either a problem with your build or an
> > intel DDX bug. In any case, it's not a mesa bug.
>
> Wrong, very wrong.
>
> [ 5295.161] (EE) AIGLX error: Calling driver entry point failed
> [ 5295.161] (EE) AIGLX: reverting to software rendering</span >
Sorry, I missed that. I saw the first error and didn't notice the others.
<span class="quote">> __glXDRIscreenProbe()
> screen->driScreen =
> (*screen->dri2->createNewScreen) (pScreen->myNum,
> screen->fd,
> loader_extensions,
> &screen->driConfigs, screen);
>
> if (screen->driScreen == NULL) {
> LogMessage(X_ERROR, "AIGLX error: Calling driver entry point
> failed\n");
> goto handle_error;
> }
>
> A mesa provided function (createNewScreen) is reporting a failure.</span >
That seems odd.
Eugene, Did this recently start happening? Does it work with an older mesa?
Unfortunately, those logs aren't telling me much about what actually happened.</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>