Bug 58840

Please attach your xorg log and dmesg output.

(In reply to comment #1)
> Please attach your xorg log and dmesg output.

The same as the ones at bug 58839

Created attachment 72400 [details]
neverball.png

The frames of Neverball are ok most of the time, but it flashes to garbage like in the attachment several times per second. The other applications I tried are sauerbraten and kde-window-manager, those are permanently garbage.

Now I tried again with updated mesa (git-8ed6b14). Now glxgears, sauerbraten, ut2004 (32bit), fgfs (when did 3d clouds become such a performance killer?) are fine. Neverball still flashes garbage. Nexuiz is 3fps with AA. Etqw (32bit) and team fortress 2 (32bit, wine) cause gpu lockup even without AA (I'll bisect later). Alien-arena with AA dies with
r600_texture.c:776:r600_texture_transfer_map: Assertion `rtex->resource.b.b.nr_samples <= 1' failed.

In all cases I had to use the env var, even games that support setting AA cannot do it themselves.

Cogs also works, sort of. It has to be started with the __GL_FSAA_MODE=4 env var *and* antialias must be enabled in the options menu to see AA. However, it cannot start this way, it says
Couldn't set 1280x960 OpenGL video mode: Couldn't find matching GLX visual
on the next startup. The antialias has to be reset to 0 in ~/.local/share/Cogs/cogs.ini, and re-enabled in the menu. Additionally, there is a 90% chance of segfault on startup and on changing the antialias setting.

(In reply to comment #5)
> Couldn't set 1280x960 OpenGL video mode: Couldn't find matching GLX visual
> on the next startup.

If you want MSAA GLX visuals, you must *install* the gallium driver and restart the X server for it to pick up the visuals.

(In reply to comment #6)
> (In reply to comment #5)
> > Couldn't set 1280x960 OpenGL video mode: Couldn't find matching GLX visual
> > on the next startup.
> 
> If you want MSAA GLX visuals, you must *install* the gallium driver and
> restart the X server for it to pick up the visuals.

I know, but the last time I tried to install it, the whole screen became noise, like I said in the initial report.

Now I tested things again, and I only see rendering errors with neverball.

I don't know if it is expected, but some games completely slow down to a few fps with msaa enabled (etqw, nexuiz), while others slow down only when lots of geometry is seen (sauerbraten). I still can't install the msaa-capable r600_dri.so, because of the kde-window-manager slowdown bug discussed at bug 55998, so I used the __GL_FSAA_MODE=4 env var for the tests.

(In reply to comment #8)
> Now I tested things again, and I only see rendering errors with neverball.
> 
> I don't know if it is expected, but some games completely slow down to a few
> fps with msaa enabled (etqw, nexuiz), while others slow down only when lots
> of geometry is seen (sauerbraten). I still can't install the msaa-capable
> r600_dri.so, because of the kde-window-manager slowdown bug discussed at bug
> 55998, so I used the __GL_FSAA_MODE=4 env var for the tests.

Does the slowdown happen with the latest kernel from Linus Torvalds's git?

(In reply to comment #9)
> 
> Does the slowdown happen with the latest kernel from Linus Torvalds's git?

Currently I use 3.6.4. I plan to upgrade to 3.7.4 this weekend. How stable is the git version? How do I check it out? Is 3.8-rc4 enough?

The latest kernel may be more stable for your graphics card. You can get it from:

git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git

I happened to check out the git exactly at the tag 3.8-rc5 as HEAD. With that the preformance issues in etqw and nexuiz are gone. The neverball problem is still there though.

With Mesa 10.1.1 and kernel 3.12 Neverball runs perfectly even with __GL_FSAA_MODE=4. Closing.