Operating System

Redhat 7.3

• XFree86 4.2.0
• 2.4.18-17.7x kernel
• glibc i686 version (glibc-2.2.5-43)

Redhat 8.0

• XFree86 4.2.0
• 2.4.18-18.8.0 kernel
• glibc i686 version (glibc-2.2.93-5)

Redhat 9.0

• XFree86 4.3.0
• 2.4.20-28.9 kernel
• glibc i686 version (2.3.2-27)

Redhat Enterprise Linux WS 3.0

• XFree86 4.3.0
• 2.4.21-9.EL kernel
• glibc i686 version (2.3.2-95)

Other Useful Maya on Linux Info 

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

Plugin developers should use the same configuration.

OpenMotif 2.1
Maya uses OpenMotif 2.1 as its GUI framework. The version used is OpenMotif 2.1.30 from ICS. Maya includes the library in its default lib directory, so no action is required to use the proper library. The runtime rpm is included for reference on the CD in the support directory.

OpenMotif 2.2.x is not binary compatible with OM 2.1.30, development of Motif plugins can not use the default OM 2.2.x libraries supplied with RedHat 7.3/8.0, one needs to install the 2.1.30 versions of the runtime and development rpms:
    openmotif-2.1.30-2_ICS.i386.rpm openmotif-devel-2_1_30-2_ICS_i386.rpm
    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.1 runtime library libXm.so.2

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.

Computer Models

Graphics

Additional information regarding Maya Hardware Rendering

Video Cards without Hardware Overlay Planes

• VR3
• Quadro line of cards

Sound

General Configuration

• A three button mouse is required.
• At least 256 MB of RAM is required and 512 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.
• Where Graphics Controllers are configurable, you must have at least 16MB of texture memory (TRAM). Due to the differences in the manner in which hardware vendors approach display memory, we suggest that you consult your hardware vendor to ensure that your configuration will support your required resolution.
• 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.