Red Hat Bugzilla – Bug 154538
r200_dri with maya
Last modified: 2007-11-30 17:11:03 EST
Description of problem:
Just tried a valid maya 6.5 license on FC4-devel for testing purpose.
Computer: laptop with ATI R250 (firegl 9000) - xorg radeon/r200_dri drivers and
dri enabled -> Maya hangs on startup.
dri disabled -> Maya GL is slow but runs fine
Why I post here:
Maya also runs fine on the last ubuntu distro with xorg 6.8.2 and r200_dri
drivers - dri enabled
Version-Release number of selected component (if applicable):
every time beeing a normal user as well as beeing root
Steps to Reproduce:
1. Lauch Maya 6.5
As soon as the GL interface part is drawn, maya hangs. Tracing with gdb, it
seems to be messed up in the r200_dri.
Working r200_dri GL
works at least on ubuntu hoary with same xorg version - dri enabled.
Please report this issue to X.Org developers, in the X.Org bug tracker
located at http://bugs.freedesktop.org in the "xorg" component.
Once you've filed your bug report to X.Org, if you paste the new
bug URL here, Red Hat will continue to track the issue in the
centralized X.Org bug tracker, and will review any bug fixes
that become available for consideration in future updates.
Setting status to "NEEDINFO", awaiting X.Org bug report URL for tracking
You mention it doesn't occur in Ubuntu, which means that it is either
a bug in stock X.org and Ubuntu has a patch that fixes it, or it is
a bug in stock X.Org that for some other reason does not trigger
under Ubuntu (perhaps kernel related), or it could be something else.
We do not have Maya available to be able to investigate this problem
directly, and there have not been any responses in this bug report
for over a month now.
If the problem still exists in the latest updates for Fedora Core,
file a bug report in X.Org bugzilla as requested above and Red Hat
will continue to track the issue in the X.org bugzilla.
If someone can provide a reproduceable test case that doesn't require
having a legally licensed copy of Maya, or can provide enough
debugging information in the X.Org bug report once it is filed,
which can help developers to diagnose the cause of the problem,
then someone can probably fix the issue in X.Org directly (perhaps
Ubuntu can submit their patch if they have one), and all distributions
can obtain the centralized fix for the issue.
Setting status to "ERRATA", assuming bug is fixed in current updates
due to lack of response.