Hi Timo, Of course I have recompiled the app before running it under feisty...
Most the examples I have tried just give me a black screen, not very high CPU usage though. I get the following printed out: libGL warning: 3D driver claims to not support visual 0x4b libGL warning: 3D driver claims to not support visual 0x4b *********************************WARN_ONCE********************************* File r300_render.c function r300Fallback line 424 Software fallback:ctx->Multisample.Enabled *************************************************************************** Try R300_SPAN_DISABLE_LOCKING env var if this hangs. Then when I exit the problem I get this trace: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 805510928 (LWP 28311)] 0x0de3d750 in ?? () (gdb) bt #0 0x0de3d750 in ?? () #1 0x0f722538 in glXMakeCurrentReadSGI () from /usr/lib/libGL.so.1 #2 0x0f966874 in GemMan::destroyWindow () from ./Gem.pd_linux #3 0x0f967044 in GemMan::render () from ./Gem.pd_linux #4 0x100776b4 in sched_tick () #5 0x1007834c in m_scheduler () #6 0x1007bb90 in sys_main () #7 0x100866c0 in main () Closing the black render window on the other examples always seems to give a similar trace with glXMakeCurrentReadSGI at the top. Note that this is code a lot of other people are using Any suggestions on debugging this further? Thanks, .b. Timo Aaltonen wrote: > b: try rebuilding your on apps. > > rest of you: please test with upcoming feisty herd 5 testrelease if the > mesa-update fixes this for you. > -- 3d rendering performance regression Dapper->Edgy with Radeon 9600 M10 https://launchpad.net/bugs/61607 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
