Created attachment 41227 [details] bad_indirect.png See screenshot of teapot demo with indirect rendering: LIBGL_ALWAYS_INDIRECT=1 LIBGL_DRIVERS_PATH=$HOME/mesa/lib/gallium LIBGL_ALWAYS_INDIRECT=1 ./teapot $ LIBGL_ALWAYS_INDIRECT=1 glxinfo|grep OpenGL OpenGL vendor string: Advanced Micro Devices, Inc. OpenGL renderer string: Mesa DRI R600 (RV730 9498) 20090101 TCL DRI2 OpenGL version string: 1.4 (2.0 Mesa 7.8.2) OpenGL extensions: vs direct rendering: ./teapot $ glxinfo|grep OpenGL OpenGL vendor string: Advanced Micro Devices, Inc. OpenGL renderer string: Mesa DRI R600 (RV730 9498) 20090101 TCL DRI2 OpenGL version string: 2.1 Mesa 7.10-devel OpenGL shading language version string: 1.20 OpenGL extensions:
Created attachment 41228 [details] good_direct.png
Created attachment 41229 [details] Xorg.0.log
Here are screenshots with matching Mesa versions in Xorg and client: LIBGL_ALWAYS_INDIRECT=1 glxinfo|grep OpenGL OpenGL vendor string: X.Org OpenGL renderer string: Gallium 0.4 on AMD RV730 OpenGL version string: 1.4 (2.1 Mesa 7.10-devel) OpenGL extensions: glxinfo|grep OpenGL OpenGL vendor string: X.Org OpenGL renderer string: Gallium 0.4 on AMD RV730 OpenGL version string: 2.1 Mesa 7.10-devel OpenGL shading language version string: 1.20 OpenGL extensions:
Created attachment 41230 [details] bad indirect rendering with matching versions
https://bugs.freedesktop.org/attachment.cgi?id=41230 ^text is missing, teapot not seen in its entirety either.
Can you bisect?
(In reply to comment #6) > Can you bisect? I initially thought this was a regression, but it is not. It is due to indirect rendering, something I never tested in the past, and just accidentally triggered now (I used a relative LIBGL_DRIVERS_PATH instead of an absolute one, it couldn't find the drivers and falled back to indirect). Do you know of a past version of Mesa that worked with indirect rendering and r600?
Is this still an issue with lastest mesa and r600g ?
Closing
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.