On 07/31/2009 03:09 PM, Roland Scheidegger wrote: > On 31.07.2009 15:35, Terry Barnaby wrote: >> On 07/31/2009 02:15 PM, Roland Scheidegger wrote: >>> On 31.07.2009 10:26, Terry Barnaby wrote: >>>> Hi,I have a problem with the Mesa DRI Radeon 300 driver in that I cannot >>>> use the >>>> blender application as the menus are not displayed correctly. See bug: >>>> https://bugs.freedesktop.org/show_bug.cgi?id=21774 >>>> >>>> I would like to get this fixed as I need to be able to run blender at a >>>> reasonable speed on this system. I am running the latest >>>> DRM/MESA/xf86-video-ati >>>> code from git. Are there any pointers on how to start debugging this ? >>>> For example, can I turn off various hardware acceleration features one by >>>> one >>>> until I find the source of the problem ? >>> This looks like an issue with dri2 and front buffer rendering. Did you >>> try if this still works with dri1? You probably can't just disable dri2, >>> but disabling kms (nomodeset boot param) should force the driver to use >>> dri1 (for radeon cards) I think. >>> >>> Roland >> Thanks for the reply. >> I have tried a lot of user level configuration options such as "nomodeset", >> disabling EXA etc. None of these had any effect on the blender issue. >> Using "nomodeset" on the kernel boot line did appear to change the DRI >> interface >> from DRI2 to DRI1 (at least from the glxinfo report). >> >> Hence my move to trying the latest code from git ... > > Oh so it also happens with DRI1. It would probably be easiest (as others > have suggested) to do a git bisect then. Alternatively, since this > appears to work on r200 but not r300, you could try finding differences > wrt front buffer rendering between those drivers manually - it seems > unlikely this still happens to work with git master on r200 but not r300 > since pretty much all of the code which could affect this issue should > be shared. > > Roland
I have done some "git bisecting" of the mesa source code under Fedora 11 as the base platform and with an ATI M22 [Mobility Radeon X300]. The code at mesa_7_4 is good and works with F11. The code at mesa_7_5 is bad. I have found that the bug seems to appear at: 5340b6dff73a0a23531ce2a5f28fba8303adab6e (Merge commit 'origin/gallium-master-merge') This looks like a major gallium merge into the main trunk ?? The code at: 9fd26daec24f21dbe17afcb2e2ab272667ee9a69 (mesa: remove the unused _mesa_UpdateTexEnvProgram() function) appears to run fine on my system. I have tried to bisect the bug through the ee4c921b65fb76998711f3c40330505cbc49a0e0 (Merge commit 'origin/gallium-0.2' into gallium-master-merge) branch, but it gets difficult here due to dri drivers not being built by default, different drm/dri version requirements and different build systems. I will try a bit more here. Any info on the "origin/gallium-master-merge", it looks like this was separated before mesa_7_0 ? ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Mesa3d-dev mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
