Fedora 11/12 – Nvidia – Maya 7/2009

Recent updates of Fedora 11 and 12 seems to make Nvidia driver not usable in Maya 7 and 2009 in two of our test machine at my client.  I usually use the driver provided by RPM Fusion but this time round, Maya kept reporting Signal 11 error just as it was about to finish starting up.  Using Maya’s Crash Reporting environment variable which kept pointing to libc and TWindow, I thought at first it could be a glibc incompatibility issue.  However rolling back glibc does not seem to solve the problem.  Finally, just out of gut feeling, I removed kmod-nvidia and install the driver (190.53) provided by Nvidia and voila!! Problem solve.

On a different machine, we have i7core with 6GiB of RAM and an NVidia GTX275 with 896MiB of Video RAM. An error along the line of “/dev/nvidia0 input/output error” kept preventing the machine from starting up X window.  After searching on Google for two weeks, a not so obvious answer emerges. I don’t understand the solution but it has something to do with the kernel allocating virtual memory.  The default is 128MiB and for reasons unknown to me, its not enough to get GTX275 started even though it was not a problem previously on Fedora 10.  The solution is to increase the “vmalloc” for the kernel via keying in the value in the kernel parameters in grub.conf.  After I added “vmalloc=256M”, X-Window started up in its full glory!!

Advertisements

4 responses to “Fedora 11/12 – Nvidia – Maya 7/2009

  1. Great blog!
    So, I had Maya2008 working fine in FC12, but wanted to use the Nvidia driver for my FX1700
    graphics card so after much hassle installed Nvidia driver for my quadcore 64-bit box: now Maya won’t run:

    maya encountered a fatal error

    Signal: 11 (Unknown Signal)
    Here’s the debug Stack trace:
    /lib64/libc.so.6() [0x3f1fc32730]
    TinputDeviceManager::deviceByIndex(short) const
    Twindow::unStow(Tevent const&)
    TstartupWnd::unStow(Tevent const&)
    /usr/autodesk/maya2008-x64/bin/maya.bin() [0x4149dd]
    /usr/autodesk/maya2008-x64/bin/maya.bin() [0x4118d9]
    /usr/autodesk/maya2008-x64/bin/maya.bin() [0x40ffd5]
    /usr/autodesk/maya2008-x64/bin/maya.bin() [0x41d10b]
    __libc_start_main
    __gxx_personality_v0

    ran apcw routine and it said (not including the good entries):
    libpcwsupport.so => not found
    But if you check the directory it IS there. Did try reinstalling Maya but no luck. Also extracted the .rpm and copied the libpcwsupport.so to the maya lib directory, checked my xorg.conf and Xinerama on or off doesn’t help, also Composite is disabled and the kmod-nvidia driver is not installed.
    Any ideas? I’m just smart enough to get myself in a lot of trouble…
    Thanks!

    • In my experience, if you have installed kmod-nvidia or official-nvidia first but later decide otherwise and try the other then you must re-install Fedora again. Its a hassle but that’s what happen to me since Fedora Core 4.

  2. Hey xray0. I too am getting into the same prob with maya . any idea as to why?
    Stack trace: /lib/libc.so.6 [0x7fa6fad133a0] TinputDeviceManager::deviceByIndex(short) const Twindow::unStow(Tevent const&)
    TstartupWnd::unStow(Tevent const&)
    /usr/autodesk/maya2009-x64/bin/maya.bin [0x414f2d]
    /usr/autodesk/maya2009-x64/bin/maya.bin [0x412ec2]
    /usr/autodesk/maya2009-x64/bin/maya.bin [0x41058a]
    /usr/autodesk/maya2009-x64/bin/maya.bin [0x41e93b]
    __libc_start_main
    __gxx_personality_v0

    • Assuming you are running Fedora12 with the latest update to kernel 2.6.32.11-99, the nvidia from both kmod and official website works in the X environment except when running maya. My guess is that there is something in the latest kernel that prevents maya from doing its mojo. On the i7core that my client is using, I have to roll back the kernel to 2.6.30 in order to use maya without it crashing. With this episode, I pretty much conclude the top most version to run maya2009 is Fedora 11.

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s