Radeon (TM) 7500 Graphics Support for HP Tru64 UNIX
Tru64 UNIX Version 5.1B
© Copyright 2004 Hewlett-Packard Development Company, L.P.
The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.
Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.
This document contains the release notes for the ATI RADEON 7500 Graphics Support for Tru64 UNIX kit. Release notes are supplied in HTML format and are located in the following location after the kit is installed:
This guide is intended for anyone who has purchased Version 1.3 of the ATI RADEON 7500 Graphics Support for Tru64 UNIX kit. Knowledge of Tru64 UNIX installation is recommended. For more information on future releases or updates, please refer to the Tru64 UNIX software products section of the following web site: /index.html.
The RADEON 7500 Graphics Support kit contains all 2D and 3D drivers required to support the RADEON 7500 AGP and RADEON 7500 PCI graphics cards. The kit supercedes the RADEON 7500 support included with the Tru64 UNIX V5.1B base operating system.
For 2D, the RADEON 7500 Graphics Support kit provides improved 2D rendering, support for dual-screen mode with a single card, and support for multiple cards.
For 3D, the kit contains support for the RADEON 7500 TCL hardware, hardware alpha and stencil planes, 3D multitexturing, 3D cube map textures, hardware-accelerated indirect rendering, dual-screen mode with a single card, and support for OpenGL V1.2 and GLX V1.2.
The RADEON 7500 Graphics Support kit contains the following components:
- Device-dependent libraries for the X server.
- Kernel device driver for the RADEON 7500.
- Configures the Tru64 UNIX system to run the RADEON 7500.
- OpenGL graphics support libraries.
The RADEON 7500 Graphics Support kit requires Tru64 UNIX V5.1B with Patch Kit 1 or later. Tru64 UNIX patch kits are available for download at http://www.itrc.hp.com/service/patch/mainPage.do.
Before installing the RADEON 7500 Graphics Support kit, check whether an updated kit is available for download at /index.html under Tru64 UNIX software products.
If there is an earlier version of the RADEON 7500 Graphics Support kit installed on your system, you must remove it before installing the latest kit. For example:
# /usr/sbin/setld -i | /usr/bin/grep RADEON
# /usr/sbin/setld -d RADCONFIG542 RADDEVICE542 RADGLBASE542
If your system has more than one RADEON 7500 card, see Section 3.1.3 Removing the RADEON 7500 Graphics Support Kit to avoid problems with this procedure.
The RADEON 7500 supports a variety of video modes. It is recommended that you set your refresh rate to the highest value supported by both the RADEON 7500 and your monitor. Table 2-1 lists which video modes are supported by the RADEON 7500. All video modes are supported at 8, 16, and 24 bits per pixel. Note that OpenGL rendering is supported only at 24 bits per pixel.
Table 2-1: Supported Video Modes
To change the default video mode, edit the X server's configuration file, /usr/var/X11/Xserver.conf. Before attempting to change your resolution, make sure that the attached monitor will support the new video mode.
For example, to switch to 1280x1024 at 85Hz add the following X server command line arguments to the "args<>" section of /usr/var/X11/Xserver.conf:
-screen 1280x1024 -vsync 85
After updating the file, you must restart the X server. For example, when logged in remotely, enter the following command:
# /usr/sbin/init.d/xlogin restart
The RADEON 7500 card has three built-in connectors:
An analog VGA connector (labeled CRT)
- Accepts CRT monitors and flat panel monitors with an analog VGA connector.
A DVI-I connector (labeled DVI)
- Can be connected to an analog monitor by using the DVI-I to VGA adapter supplied with the RADEON 7500. Digital output is not supported.
An S-Video connector (labeled VID OUT)
- Not supported.
To use the DVI-I port, a monitor must be connected via the DVI-I to VGA adapter to the RADEON 7500 when you power cycle the machine or when you initialize from the system console. If a monitor is not connected to the DVI-I connector during console initialization, the DVI-I port is disabled.
2.3.1 OPEN3D License PAK
To use the 3D features of the RADEON 7500, an OPEN3D license product authorization key (QL-6ZRA9-AA) must be registered in the license database on the system. A license product authorization key is not required for 2D.
2.3.2 OpenGL Subsets
To use the 3D features of the RADEON 7500, the OpenGL Runtime subset from the Tru64 UNIX operating system (OSFOPENGLxxx) and the OpenGL subset from the RADEON 7500 Graphics Support kit (RADGLBASExxx) must be installed.
2.3.3 tty Group
Use of a direct-rendered OpenGL rendering context (direct rendering) requires that either the user running the OpenGL application be a member of the "tty" group or that the executable for the OpenGL application be owned by group "tty" and have the set-group-ID bit set. To do the latter to the OpenGL application "myglprog", issue the following commands:
% chgrp tty myglprog
% chmod g+s myglprog
On a non-clustered system, the OpenGL software for the RADEON 7500 uses direct rendering whenever the OpenGL client requests connection to the local X server (for example, by specifying a display of ":0" or "node:0" where "node" is the same system that the client is running on).
On a cluster, a display of ":0" will use direct rendering, but a display of "node:0" where "node" is the same system that the client is running on will use indirect rendering. To change this behavior so that direct rendering is used in this case, the cluster administrator should remove the "out_alias" attribute from the "Xserver" line in /etc/clua_services and then run "cluamgr -f" on each cluster member to make the change take effect. See clua_services(4) for more information about the "out_alias" attribute.
To force indirect rendering even when connecting to a local X server, define the following environment variable for the OpenGL client:
% setenv LIBGL_ALWAYS_INDIRECT 1
The OpenGL driver for the RADEON 7500 contains support for the on-board transformation, clipping, and lighting (TCL) hardware of the RADEON 7500 for increased primitive rendering performance.
The RADEON 7500 OpenGL driver is thread-safe.
By default, the RADEON 7500 appears as a single-head device with identical video signals coming out of the DVI-I and VGA ports. If desired, you can enable dual-screen mode in which a single RADEON 7500 card drives two independent screens with the signal of the first screen (display :0.0) coming out of the VGA port and the signal of the second screen (display :0.1) coming out of the DVI-I port.
To enable dual-screen mode, create a temporary file containing the following:
RADEON_DUAL_SCREEN = 1
Assuming that the name of the temporary file is "myconfig", as the root user, issue the following command:
# sysconfigdb -a -f myconfig radeon
Then reboot for the change to take effect.
To return to single-screen mode, as the root user, issue the following command and reboot:
# sysconfigdb -r -f myconfig radeon
When in dual-screen mode, you can run each screen at a different refresh rate. You can also run each screen at different resolutions if you are not running the X server's PanoramiX extension. Running each screen at a different bit depth is not supported. If you are in PseudoColor mode, you can load different color maps on the two screens if you are not running PanoramiX.
3D rendering is available in dual-screen mode when the resolutions on both screens are set to 1280x1024 or lower. Note that in dual-screen mode there will only be about half as much graphics memory available for texture storage, so texture-intensive applications may not perform as well as they do in single-screen mode.
If there is more than one RADEON 7500 card in a system, dual-screen mode is only available on the primary card.
Up to four RADEON 7500 AGP and/or RADEON 7500 PCI cards can be installed in one of the supported configurations. Prior to plugging in more than one RADEON 7500 card, you must make sure that your installed SRM console revision level is 6.4-12 or above for AlphaServer GS1280, ES80, and ES47 systems, and 6.4 or above for all other systems. When the driver detects more than one RADEON 7500 card, 3D and DMA are automatically disabled. In addition, the DVI-I port on cards other than the primary card will not be useable and dual-screen mode will only be available on the primary card. The SRM console determines which card is the primary card.
3.1.1 Not Supported by Base Operating System
The RADEON 7500 support provided with the Tru64 UNIX V5.1B base operating system only supports a single RADEON 7500 card. Before Tru64 UNIX V5.1B Patch Kit 3 (BL24), the system may crash when the X server starts if there is more than one RADEON 7500 card in the system. Beginning with Patch Kit 3, the X server will run successfully on systems with more than one RADEON 7500 card, but only the primary card will be enabled. You must install the RADEON 7500 Graphics Support kit to use more than one RADEON 7500 card.
When performing a fresh installation of Tru64 UNIX V5.1B on a system with more than one RADEON 7500 card, use the Tru64 UNIX NHD 7 kit. That kit includes the changes from Patch Kit 3 and will install correctly on systems with more than one RADEON 7500 card.
3.1.2 Booting genvmunix
If you have the RADEON 7500 Graphics Support kit installed on a system with more than one RADEON 7500 card and you boot the generic kernel (genvmunix), only the primary card will be enabled. If you have changed the default screen order (by specifying the -screenOrder argument in the X server configuration file, /var/X11/Xserver.conf), the primary card may be a different card than the card you specified as screen 0.
3.1.3 Removing the RADEON 7500 Graphics Support Kit
Before upgrading to a new version of the RADEON 7500 Graphics Support kit, you must remove the previous version. On systems with more than one RADEON 7500 card, the X server may fail to start if you reboot the system or restart the X server after removing the previous version. To avoid this problem, remove the previous version and install the new version without rebooting or restarting the X server in between. If it is necessary to reboot, boot the generic kernel (genvmunix) from Patch Kit 3 or later.
3.1.4 2D Only
Only 2D rendering is available when there is more than one RADEON 7500 card in a system. 3D and DMA are disabled when multiple cards are detected. Note, however, that 3D rendering on two screens is available with a single RADEON 7500 in dual-screen mode.
The RADEON 7500 Graphics Support kit only supports connection to monitors with analog interfaces, including flat panel displays with analog interfaces. Monitors with digital-only interfaces are not supported. The DVI-I to VGA adapter supplied with the RADEON 7500 can be used to connect a monitor's analog interface to the DVI-I port of the card for dual-screen mode. If you use the DVI-I port, a monitor must be connected when the system is powered up or when the system is initialized from the system console. Otherwise, the DVI-I port is disabled.
The RADEON 7500 graphics controller supports only one hardware colormap per screen. Keep this in mind if you change to the 8-bit color depth, where the default visual is PseudoColor. Attempting to use more than one PseudoColor colormap at a time causes colormap flashing. Applications should not install or uninstall colormaps themselves. The window manager should perform these actions. However, the application is responsible for providing the window manager with hints about which colormaps to install or uninstall. You provide this information using the Xlib function XSetWMColormapWindows(). This function sets the WM_COLORMAP_WINDOWS property for a given window.
With the RADEON 7500, all windows created on a particular screen must have the same bit depth. The RADEON 7500 supports bit depths of 8, 16, and 24 bits per pixel on any screen, but once the X server establishes a bit depth on a particular screen, only windows or visuals with that bit depth can be created on that screen.
Hardware overlay planes are not supported on the RADEON 7500.
Stereo is not supported on the RADEON 7500.
The X server PanoramiX extension which allows multiple physical screens to be treated as one large logical screen is supported on the RADEON 7500 for 2D, but not for 3D.
The implementation of backing store and save unders in the RADEON 7500 X server does not support 3D windows. The RADEON 7500 installation procedure will disable backing store and save unders by adding the X server command line arguments "-bs -su" to the X server configuration file. If you wish to run only 2D programs and have backing store and save unders enabled, edit /usr/var/X11/Xserver.conf and remove the "-bs -su" command line arguments.
8-bit visuals (color index mode) are supported for 2D rendering when the X server is started with a color depth of 8. 3D rendering is not supported on 8-bit visuals.
The RADEON 7500 X server exports double buffered visuals only. For single buffering, users will need to use a double buffered visual with a call to glDrawBuffer(GL_FRONT_BUFFER) in their application.
When the RADEON 7500 Graphics Support kit is installed on a cluster, the RADEON 7500 must be the only type of 3D graphics card installed on the cluster. There can be other 2D graphics cards installed.
If you encounter memory allocation errors when running an OpenGL application which uses large display lists, try increasing the maximum size of the data region for the application. For example, using the C shell:
% limit datasize unlimited
4.1.1 System Hangs Fixed
Occasionally during periods of high graphics activity, the RADEON 7500 would hang the bus causing the system to be unresponsive. This problem has been fixed.
4.1.2 Transparent Stipples Fixed
Sometimes when drawing with a graphics context fill style of FillStippled, the drawing would actually be done as if the fill style were FillOpaqueStippled with a background pixel value of white. This problem has been fixed.
4.2.1 New URL for Tru64 UNIX Graphics Information
Information about Tru64 UNIX graphics support kits is now available at /index.html under Tru64 UNIX software products.
4.2.2 Additional Video Modes Supported
Support has been added for the following video modes:
1920x1080 at 60 Hz
1920x1200 at 60 Hz
4.2.3 XAABitBlt() Segmentation Fault Fixed
The X server would fail with a segmentation fault when drawing certain figures. The stack trace in the core file would include the routine XAABitBlt(). This problem has been fixed.
4.2.4 Dashed Line GC Function Fixed
Sometimes, when drawing dashed lines, the graphics context function would be ignored and the drawing would be done as if the graphics context function were GXcopy. This problem has been fixed.
4.2.5 DECterm Character Fragments Fixed
Sometimes, when deleting characters in a DECterm terminal emulator (dxterm) window, fragments of the deleted characters would be left on the screen. This problem has been fixed.
4.2.6 "Cannot Resolve All Symbols" Segmentation Fault Fixed
If 3D rendering was disabled and an application did a QueryExtension call on the GLX extension, the X server would display "Cannot resolve all symbols" messages in its log file (/var/dt/Xerrors), and later, when the user logged out of the desktop session, the X server would fail with a segmentation fault. This problem has been fixed.
4.2.7 Extra Point on Line Segments Fixed
When drawing zero-width horizontal or vertical line segments or when drawing zero-width segments that consisted of only a single point with a graphics context cap style of CapButt, CapRound, or CapProjecting, an extra point would be drawn at the end of the segments. This problem has been fixed.
4.2.8 fbPolyLine() Segmentation Fault Fixed
The X server would fail with a segmentation fault when drawing certain figures. The stack trace in the core file would include the routine fbPolyLine(). This problem has been fixed.