Last Updated:April.11, 2005


Maya 6.5 for Linux Qualification

This 6.5 qual chart is being updated regularly with both new,
and existing graphics cards from the previous Maya 6.0 Qual Chart
Please check back frequently here for updates.

Products Version Software Date
Maya Complete / Unlimited 6.5 200501140033


Operating System
Maya 6.5 is qualified on the following Workstations with Red Hat 9.0 and Enterprise Linux WS 3.0. Please see Notes on Operating Systems. Maya may not run on non Redhat Systems.
Important Note: The Linux operating system is extremely flexible with regards to precise versioning of different components, drivers and libraries. Maya may behave very differently on superficially similar systems and while Alias will do our best to help solve problems that are probably due to operating system configuration issues, we may be unable to explain or determine the cause of a problem.
Internally at Alias we have stabilized on the following configurations. We provide this list for the purpose of aiding our customers, but we can make no guarantees to the reliability, stability or availability of these components. This is not a complete list of Linux configuration choices, but are only the important components that we are aware significantly affect Maya.
Redhat 9.0
  • XFree86 4.3.0
  • 2.4.20-31.9 kernel
  • glibc i686 version (2.3.2-27)
Redhat Enterprise Linux WS 3.0
  • XFree86 4.3.0
  • 2.4.21-27.0.2.EL kernel
  • glibc i686 version (2.3.2-95)
SUSE 9.1
  • XFree86 4.3.99.902-43.28
  • 2.6.5-7.151 kernel
  • glibc 2.3.3-97
Other Useful Maya on Linux Info

Linux Compiler Requirement:
Maya 6.5 was compiled using gcc 3.3.4 on a Redhat 9.0 system. gcc 3.3.4 source code is available from http://gcc.gnu.org/gcc-3.3

The options to build the gcc 3.3.4 compiler used for Maya are:
gcc334 -v
Reading specs from /opt/gcc334/lib/gcc-lib/i686-pc-linux-gnu/3.3.4/specs
Configured with: ../gcc-3.3.4/configure --prefix=/opt/gcc334
--program-suffix=334 --enable-shared --enable-threads=posix
--disable-checking --with-system-zlib --disable-libunwind-exceptions
--enable-__cxa_atexit
Thread model: posix
gcc version 3.3.4

Plugin developers should use the same configuration.

OpenMotif 2.2.3
Maya 6.5 uses OpenMotif 2.2.3 as its GUI framework. The version used is
OpenMotif 2.2.3 from ICS with additional updates from the OpenMotif CVS.
Maya includes the library in its default lib directory, no action is
required to use the proper library.

http://www.motifzone.com/

OpenGL libGLU.so
Maya also depends on a compatible version of libGLU.so, the version that comes with XFree86 is compatible and works with Maya. Some other versions have problems with exception handling within Maya.

OpenGL Visuals
Maya's choice of OpenGL visuals is RGBA 8/8/8/8 double buffer with depth buffer of 24 where applicable. Visuals available from the XServer can be found using the command "glxinfo".

If Maya can not obtain its preferred visual, it will fall back as possible to lower values. A warning will be issued in this case.

Setup the XServer so it is using direct rendering to get as many visuals as possible. Use a depth setting of 24, to enable 8 bits per component.

Non Red Hat systems

Limitation
Maya may not run on systems that do not have a compatible runtime
libraries, including glibc compiled with the __cxa_atexit option. Maya
includes the C++ runtime libraries libstdc++.so.5, and libgcc_s.so.1
within the Maya "lib" directory, as well as the required Motif 2.2.3
runtime library libXm.so.3

Solution

It may be possible to copy selected .so files, however the precise files and locations vary on different versions of Linux and we are unable to provide replacement .so files, precise instructions nor provide Support on how to resolve this.



Intel and AMD 64-bit Compatibility
Please note that qualification on 64-bit capable systems must take into account the mode that the CPU is running as well as the whether the OS is 32-bit or 64-bit.
These combinations were previously described in a way that could be misinterpreted and we apologize for any inconvenience.
Maya 6.5 is currently Qualified on the following:
Opteron: (32-bit mode) Red Hat Enterprise Linux WS 3 (32-bit)
Athlon 64: (32-bit mode) Red Hat Enterprise Linux WS 3 (32-bit)
 
Maya 6.5 is currently Unsupported on the following systems. Alias is investigating many of these combinations, but cannot currently support them:
Systems capable of running in 32-bit or 64-bit mode, when run in 32-bit mode with a 32-bit OS:  
EM64T: (32-bit mode)  Red Hat Enterprise Linux WS 3 (32-bit)
Systems capable of running in 32-bit or 64-bit mode, when run in 64-bit mode.   
Opteron: (64-bit mode) Red Hat Enterprise Linux WS 3 (64-bit)
Athlon 64: (64-bit mode) Red Hat Enterprise Linux WS 3 (64-bit)
EM64T: (64-bit mode) Red Hat Enterprise Linux WS 3 (64-bit)
64-bit only systems
Itanium2: Red Hat Enterprise Linux WS 3 (64-bit)


Workstations
Company Model Web
HP HP Workstation X1000/X1100/X2000/X2100/X4000 www.hp.com
HP  HP Workstation xw4100, XW5000, XW6000, XW8000 www.hp.com
IBM IBM M Pro 6219, 6230
www.ibm.com
IBM  IBM Z Pro 6221 www.ibm.com
Compaq W6000/W8000 www.compaq.com


Graphics Cards and Driver Versions
Maya is qualified with the following graphics adapters (with the specified driver for the specified operating systems). Alias has tested only drivers listed under each OS. While it may be possible to use Maya successfully on earlier or later drivers, Alias cannot guarantee their performance or behaviour. If you encounter problems with a driver, we strongly suggest that you contact the graphic card vendor to report your problem.
Company Graphics Controller Red Hat 9.0 Red Hat EL WS 3.0* SuSE 9.1
Nvidia Quadro FX 500 71.62 71.62 untested 
Nvidia Quadro FX 1100 71.62 71.62 untested 
Nvidia Quadro FX 1000/2000 71.62 71.62 untested 
Nvidia Quadro FX 3000 71.62 71.62 71.74 
Nvidia Quadro FX 4000 untested  71.62 untested 
Nvidia Quadro FX 330 untested untested untested
Nvidia Quadro FX 540 untested untested untested
Nvidia Quadro FX 1300 untested 71.62 untested
Nvidia Quadro FX 1400 untested untested untested
Nvidia Quadro FX 3400/4400 untested untested untested
ATI1 FireGL X1/Z1 8.8.25 8.8.25 untested 
ATI1 FireGL X2 8.8.25 8.8.25 untested
ATI1 FireGL X3 8.8.25 8.8.25 untested
ATI1 FireGL V3100 untested untested untested
ATI1 FireGL V3200 untested untested untested
ATI1 FireGL V5000 untested untested untested
ATI1 FireGL V5100 untested untested untested
ATI1 FireGL V7100 untested  untested  untested 
[1] We anticipate re-qualifying ATI cards for Maya 6.5 Windows with a future ATI driver, to address the listed Hardware Render Buffer Limitation affecting ATI cards.
*Red Hat Enterprise Linux WS 3.0
see below for important details about each of these graphics cards.
Video Cards without Hardware Overlay Planes
There will be visual differences compared with Hardware overlays that may result in difficulty seeing or manipulating aspects of the scene or Maya interface. Examples of Graphics cards without Hardware overlays include (but are not restricted to):
  • Radeon Family
  • Geforce Series
Although Maya may be used successfully on systems containing these Graphics Cards, only those specifically listed here have been tested. Please review the notes below carefully as some of these cards have limitations which may make them unsuitable for your purposes.
Nvidia Quadro 4 and Quadro FX Family
To set hardware overlay planes on NVIDIA quadro cards you will need to enable "CIOverlay" in the XF86Config file. ex.

Section "Device"

Option "CIOverlay" "on"

Sound

Alias is aware that sound reproduction inside Maya (scrubbing and playback) doesn't work on many sound cards on Linux. At this time we must caution you that sound reproduction may not be adequate for your purposes. Sound playback does behave correctly on some cards and some on-board/built-in sound devices, and we are currently attempting to identify specific sound cards that provide better performance.
Soundblaster Live cards are currently known to provide inadequate performance for interactive sound playback - particularly scrubbing.
We are also aware that sound will not work on some sounds cards (e.g. Soundblaster 16) when another application is already using the sound system.

ALSA

ALSA stands for Advanced Linux Sound Architecture.  It is a complete replacement for the existing sound architecture in Linux. It is geared toward high performance applications and is better suited to SMP machines.  It has emulation for the older OSS sound system that is standard in RedHat Linux.  Maya uses the OSS compatibility layer. If you are experiencing sound problems under linux, we recommend installing ALSA drivers.

You may find more information at http://www.alsa-project.org/ .


General Configuration
  • A three button mouse is required. At least 512 MB of RAM is required and 1024 MB or more is strongly recommended.Customers intending to license their Alias software based on an external network card should be aware that Alias does not support the use of these devices and cannot guarantee that software will operate correctly when licensed in this way.It may be possible to successfully use Maya with a non-qualified or partially qualified configuration, but support and maintenance programs will be subject to the Alias Support services guidelines.The configurations shown are subject to change, and additional qualified configurations may be added after qualification testing has been carried out.The graphics drivers specified in this table are the drivers that were used for the qualification process. While it may be possible to use Maya successfully on earlier or later drivers, Alias cannot guarantee their performance or behaviour.We do not recommend saving data directly from Maya to NFS or other remote mounted file systems. We strongly recommend that you save the files locally and then copy the data to the mounted storage system.When texture images are stored on systems remote from the rendering process; depending on network speed, specifications and load it is possible that the renderer may be unable to access a texture file on demand and may 'drop' individual textures on a frame by frame basis. To reduce this occurrence store textures on a system local to the rendering process.
  • Be aware that with ALL dual monitor setups you will experience problems with window positioning - windows/menus not displaying on 2nd monitor, flipping back to the main monitor, etc. Dual Monitor use is therefore not recommended or supported at this time.
  • KDE klipper is known to have focusing issues with Maya, which may contribute to application instability. We recommend removing the applet from the panel and editing the config file, ( ~/.kde/share/config/klipperrcv), to disable KDE klipper.
    --
    [$Version]
    update_info=klipperrc.upd:25082001,klipperrc.upd:kde3.1

    [General]
    AutoStart=false

Notes on Operating Systems
Redhat 9.0 Limitations and Solutions
Limitation When using Maya Live, the startTrack initial image may appear very small, and the playblast may appear with no image. Sometimes the files are created correctly even though they do not play back with fcheck manually.
Solution None
Limitation While many NFS issues with Irix file servers were fixed in Redhat 7.2, issues are still occurring on Redhat 7.2 and 7.3 when exporting to 64-bit file systems (e.g. IRIX).
Solution Exporting with the ,32bitclients attribute sometimes helps.
Check your /etc/exports file and append ,
32bitclients on each line that exports to a 64-bit file system. E.g;
/var -access=hosts,32bitclients
Note: with this setting you will not be able to access files larger than 2GB.

Non Redhat Systems Limitations and Solutions
Limitation

Maya may not run on systems that do not have a compatible runtime libraries, including glibc compiled with the __cxa_atexit option. Maya includes the C++ runtime libraries libstdc++.so.5, and libgcc_s.so.1 within the Maya "lib" directory, as well as the required Motif 2.2.3 runtime library libXm.so.3

Solution It is possible to copy selected .so files, however the precise files and locations vary on different versions of Linux and we are unable to provide replacement .so files, precise instructions nor provide Support on how to resolve this.


Detailed Driver Notes and Settings:


ATI FireGL X1/Z1
Model Version Driver Settings

ATI FireGL X1/Z1

Red Hat Linux :
8.8.25
Application Profile->Maya
Limitations and Solutions
Limitation Shaders using HardwareTexturing-> TextureFilter-> MipmapNearest, MipmapLinear, MipmapBilinear or MipmapTrilinear, will display incorrectly in the Hardware Render Buffer.
Solution Set TextureFilter to either Nearest(Unfiltered) or Bilinear, per shader



ATI FireGL X2
Model Version Driver Settings

ATI FireGL X2

Red Hat Linux:
8.8.25
Application Profile->Maya
Limitations and Solutions
Limitation Shaders using HardwareTexturing-> TextureFilter-> MipmapNearest, MipmapLinear, MipmapBilinear or MipmapTrilinear, will display incorrectly in the Hardware Render Buffer.
Solution Set TextureFilter to either Nearest(Unfiltered) or Bilinear, per shader



ATI FireGL X3
Model Version Driver Settings

ATI FireGL X3

Red Hat Linux:
8.8.25
Application Profile->Maya
Limitations and Solutions
Limitation Shaders using HardwareTexturing-> TextureFilter-> MipmapNearest, MipmapLinear, MipmapBilinear or MipmapTrilinear, will display incorrectly in the Hardware Render Buffer.
Solution Set TextureFilter to either Nearest(Unfiltered) or Bilinear, per shader



ATI FireGLV3100
Model Version Driver Settings

ATI FireGL V3100

Red Hat Linux:
8.8.25
Application Profile->Maya
Limitations and Solutions
Limitation Shaders using HardwareTexturing-> TextureFilter-> MipmapNearest, MipmapLinear, MipmapBilinear or MipmapTrilinear, will display incorrectly in the Hardware Render Buffer.
Solution Set TextureFilter to either Nearest(Unfiltered) or Bilinear, per shader



ATI FireGLV3200
Model Version Driver Settings

ATI FireGL V3200

Red Hat Linux:
8.8.25
Application Profile->Maya
Limitations and Solutions
Limitation Shaders using HardwareTexturing-> TextureFilter-> MipmapNearest, MipmapLinear, MipmapBilinear or MipmapTrilinear, will display incorrectly in the Hardware Render Buffer.
Solution Set TextureFilter to either Nearest(Unfiltered) or Bilinear, per shader



ATI FireGLV5000
Model Version Driver Settings

ATI FireGL V5000

Red Hat Linux:
8.8.25
Application Profile->Maya
Limitations and Solutions
Limitation Shaders using HardwareTexturing-> TextureFilter-> MipmapNearest, MipmapLinear, MipmapBilinear or MipmapTrilinear, will display incorrectly in the Hardware Render Buffer.
Solution Set TextureFilter to either Nearest(Unfiltered) or Bilinear, per shader



ATI FireGLV5100
Model Version Driver Settings

ATI FireGL V5100

Red Hat Linux:
8.8.25
Application Profile->Maya
Limitations and Solutions
Limitation Shaders using HardwareTexturing-> TextureFilter-> MipmapNearest, MipmapLinear, MipmapBilinear or MipmapTrilinear, will display incorrectly in the Hardware Render Buffer.
Solution Set TextureFilter to either Nearest(Unfiltered) or Bilinear, per shader



ATI FireGLV7100
Model Version Driver Settings

ATI FireGL V7100

Red Hat Linux:
8.8.25
Application Profile->Maya
Limitations and Solutions
Limitation Shaders using HardwareTexturing-> TextureFilter-> MipmapNearest, MipmapLinear, MipmapBilinear or MipmapTrilinear, will display incorrectly in the Hardware Render Buffer.
Solution Set TextureFilter to either Nearest(Unfiltered) or Bilinear, per shader


Quadro FX 1000/2000
Model Version Driver Settings    
Quadro FX 500/1000/2000 (NVIDIA) Red Hat 9
1.0-7162
default settings
         
Limitations and Solutions
Limitation Changing the contents of a panel several times consecutively (e.g. Panels->Panel->Visor) may cause Maya to crash
Solution None

Quadro FX 1100/1000/2000/3000/4000/1300
Model Version Driver Settings    

Quadro FX 500/1100/1000/2000/3000/4000/1300 (NVIDIA)

Red Hat 9 | Red Hat EL WS 3.0
1.0-7162
default settings
         
Limitations and Solutions
Limitation Alpha and luminance are not displayed in correctly in imageplanes.
Solution None