<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO --- - [945gm regression] GPU hangs on login to Unity" href="https://bugs.freedesktop.org/show_bug.cgi?id=57495#c27">Comment # 27</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO --- - [945gm regression] GPU hangs on login to Unity" href="https://bugs.freedesktop.org/show_bug.cgi?id=57495">bug 57495</a> from <a class="email" href="mailto:kees.bakker@xs4all.nl" title="Kees Bakker <kees.bakker@xs4all.nl>"> Kees Bakker</a> <pre>(In reply to <a href="show_bug.cgi?id=57495#c26">comment #26</a>) > (In reply to <a href="show_bug.cgi?id=57495#c25">comment #25</a>) > > (In reply to <a href="show_bug.cgi?id=57495#c24">comment #24</a>) > > > Any luck Kees? did Daniel's patch help at all with current kernels? > > > > No, I just built a 3.7.0-6.14 kernel (which is the latest in ubuntu-raring), > > and now I wanted to apply the patch but it doesn't apply. I'll have to > > lookup what Daniel means by "the new modeset code". > > Might be a conflict, just add the loop at the end of the modeset_init > functions like the patch does. Patch should apply though on the latest > drm-intel-fixes branch from > > <a href="http://cgit.freedesktop.org/~danvet/drm-intel">http://cgit.freedesktop.org/~danvet/drm-intel</a> No it doesn't. But see below... > > > To summarize my latest findings, the kernel does not oops anymore, but the > > graphics environment does not like 3D (only XFCE and Gnome Classic No > > Effects work). > > That's expected - i945gme is simply too old for glsl and iirc latest unity > requires that now. Or do you mean that 3D in general is busted? No, 3D is not in general, just on my Macbook. By now I know that this hardware simply can't do the 3D stuff. It never could. I was more or less expecting (hoping) that the system would _tell_ me that I can't do 3D, instead of screen corruption and such. And indeed, the Ubuntu folks decided that Unity is 3D only. Thanks guys :-( Now that we know all this, AND the kernel is behaving much better, shouldn't we close this bug? Is it worth the effort to try the patch, and what problem (besides 3D) were we trying to solve?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>