------------------------------------------------------------------------------
  Graphics Accelerators:
    ATI Radeon 8500, 9100, 9200, 9500, 9600, 9700, 9800, M9, M9+, M10
    ATI FireGL 8700, 8800, E1, E2, X1, X2, Z1
  Video Driver for Linux:
    Driver Version 4.1.0-3.2.5
    Driver Version 4.2.0-3.2.5
    Driver Version 4.3.0-3.2.5
------------------------------------------------------------------------------

  Please read the entire contents of this document. Information in this
  file may not appear in printed documentation or online help.

  This READ-ME file contains the following information:

      1.      GENERAL INFORMATION
      1.1     Requirements
      1.2     List of Download files

      2.      INSTALLING THE VIDEO DRIVER
      2.1     How to get the correct binary distribution package
      2.2     Installing the driver using the rpm utility program
      2.3     Generating a kernel with ISSE support (Kernel 2.2.x)
      2.4     Generating a customized kernel module
      2.5     Enabling AGP support

      3.      MONITOR CONFIGURATION
      3.1     Changing the monitor configuration

      4.      CONFIGURATION FEATURES AND INFORMATION

      5.      USING THE CONTROL PANEL APPLICATION
      5.1     How to Launch the Control Panel Application
      5.2     --- spare ---
      5.3     Gamma Correction Adjustment

      6.      NOTES, TROUBLESHOOTING AND LIMITATIONS

      7.      LIST OF SUPPORTED MODES

      8.      SERVICE, SUPPORT AND SOFTWARE UPDATES


1. GENERAL INFORMATION
----------------------

  This driver is based on the xfree86 version mentioned in the document header.
  (see http://www.xfree86.org/4.0/ for documentation)
  You must install this version of xfree86 before installing the drivers for
  the ATI FireGL 8700/8800.

  If your Linux distribution does not provide the XFree86 version that is
  supported by the current driver version, you must download and install 
  the respective xfree86 binaries from
      'ftp://ftp.xfree86.org/pub/XFree86/4.1.0/binaries/'
  or from
      'ftp://ftp.xfree86.org/pub/XFree86/4.2.0/binaries/'.
  or from
      'ftp://ftp.xfree86.org/pub/XFree86/4.3.0/binaries/'.


1.1 Requirements
----------------

  1. Any Linux/x86 system that does provide a glibc 2.2 (=libc 6.2) compatible
     environment is supported. If your system does have a glibc 2.3 then this
     condition is nicley fullfiled due to the lib's backward compatibility.

  2. XFree86 Version 4.1.0, 4.2.0 or X4.3.0 must be installed beforehand.

  3. The OpenGL implementation that comes with the driver can
     of use the ISSE commandset extensions of some current x86 cpus.
     So you should run a Linux kernel that can handle the respective 
     register extensions at the task switches to make use of them.

     (ISSE: Internet Streaming Single-Instruction, Multiple-Data Extensions;
     an extension of the IA-32 instruction set in the Intel Pentium III, the
     Intel Pentium 4 and recent AMD Athlon processors.)

     Most current Linux distributions do already support ISSE and provide
     an i686-optimized version of kernel 2.4.xx as systems base.
     
     You can add ISSE support to your Linux
     kernel, if required follows:     
         - apply a patch to the kernel (see 2.3)
         - recompile the kernel
         - install the recompiled kernel.

     NOTE: The OpenGL driver can use AMD 3DNow! enhanced opcodes as well
           and - due to design - does not need a kernel patch for AMD 3DNow!.

  4. To generate your own kernel modules for your local workstation where
     the modules match your kernel setup, you need a full tree of configured
     kernel sources on your local workstation.

  
1.2 List of Download files
--------------------------

  fileinfo.txt  - Download and quickstart installation guide.
  Check.sh      - Helper script for determining libc and XFree86 version.
  readme.txt    - This document.
  fglrx-glc22-4.1.0-1.2.0.i586.rpm
                - Driver package for ix86 systems with libc6.2 (=glibc2.2)
                  and XFree86 4.1.0 in rpm format.
  fglrx-glc22-4.2.0-1.2.0.i586.rpm
                - Driver package for ix86 systems with libc6.2 (=glibc2.2)
                  and XFree86 4.2.0 in rpm format.
  fglrx-glc22-4.3.0-1.2.0.i586.rpm
                - Driver package for ix86 systems with libc6.2 (=glibc2.2)
                  and XFree86 4.3.0 in rpm format.


2. INSTALLING THE VIDEO DRIVER
------------------------------


2.1 How to get the correct binary distribution package
------------------------------------------------------

  Determine which binary distribution you need for your system:
  Download the script 'Install.sh' or 'Check.sh' and run it like this:
      sh Install.sh -check
  or
      sh Check.sh

  This will provide information on suitable binary distributions for
  your system. 
  NOTE: Getting the correct binary distribution information may prevent
  you from wasting time by downloading the wrong distribution.


2.2 Installing the driver using the rpm utility program
-------------------------------------------------------

  Download the rpm that fits to your system and store the package
  to a temporary folder where you can create, delete, and modify files
  and directories. You'll need at least 5 MB of diskspace available.
  Get super user (root) privileges and change (cd) to this directory.

  Start the rpm program:

      rpm -Uhv <package_name>.rpm

  In case you do spot any problems try this command line:

      rpm -i --force <ati_package_name>.rpm

  Since the rpm program does check any sort of dependencies to system
  libraries you might observe that you are requested to install certain
  revisions (or compatible versions) of other packages in order to install
  the driver package. Advanced administrators can decide to override
  specific dependencies by the "--nodeps" switch as described in the RPM
  manual pages, but in general those dependencies should be fullfilled.

  E.g. you might be prompted for QT 2.x.x in order to install the
  driver. In this case you just have to install the appropiate version
  of the lib and then repeat the installation. If you dont have or
  dont want to install that particular version of QT lib, you can
  override this by adding "--nodeps" to your commandline. Since the
  QT lib is only required for the FGL panels the panels will just
  not launch. You can instead compile the panels from the provided
  sources against your QT lib version or install the QT libs later.

  Note for RedHat 8.0 users:
    RedHat 8.0 installations often include a specific version of the 
    libGL component. (For example, provided by the rpm package 
    XFree86-Mesa-libGL-4.2.0-72). Installing the ATI Linux driver package
    causes a conflict because the ATI Linux drivers include a custom-built 
    libGL version providing extra pbuffer support. The ATI libGL is backward
    compatible to the respective XFree86 libGL version.

    Install the ATI Linux driver package and replace the existing libGL 
    installation as follows:

    - Force RPM to use the replacement file of the ATI driver package:
        rpm -i --force <ati_package_name>.rpm
       NOTE: This includes overriding the rpm warning

    or

   - Remove the existing libGL installation and then install the new libGL 
     with the ATI driver installation. 
     For example:

      rpm -e --nodeps XFree86-Mesa-libGL-4.2.0-72
      rpm -Uhv <ati_package_name>.rpm

     NOTES:
        (1) Ensure that no OpenGL program is running during installation
        (2) You need the "--nodeps" option because some screen savers, qt-3, 
            and some parts of XFree86 might depend on the libGL presence.
            Installing the new libgl from the ATI package will restore the 
            required libGL presence.

  Perform the following steps after you have installed the driver files:
  - Run fglrxconfig to configure your XFree86 installation.
  - Respond to the questions of the fglrxconfig program
  - Save the settings to  /etc/X11/XF86Config-4.

  Some notes for debian users:

  The debian Linux distribution in most cases does not come with the 
  ability to handle rpm packages with the rpm tool. But there is a
  tool called "alien" which allows you to convert rpm files into the
  debian supported *.deb package format. Please consult your debian
  documentation on how to operate this tool. 

  A typcial debian installation commandline will look like this:

      dpkg -i <ati_package_name>.deb 

  In order to override complaints (which might be caused by an already
  installed package "xlibmesa3" that also provides the file libGL.so.1.2)
  please use this installation command line:

      dpkg -i --force-overwrite <ati_package_name>.deb 


2.3 Generating a Kernel with ISSE Support (Kernel 2.2.x)
--------------------------------------------------------

  Note: You may skip the information in this section in the following cases:
  (1) You have Kernel 2.4.xx: Kernel 2.4.xx and most current distributions
      come with ISSE support built-in,
  (2) Your CPU does not have ISSE support at all. 

  If your kernel does not have Pentium III ISSE support, you need a kernel 
  patch to benefit from the Pentium III ISSE instruction set.

  The patches on 'http://people.redhat.com/mingo/mmx-patches/' may be useful.
  Please note that these patches represent preliminary 'alpha' or 'beta' 
  code. Version "mmx-2.2.14-A0" has been tested with quite positive results.

  You must use the exactly matching kernel source from www.kernel.org.
  A distribution-specific kernel, e.g. 2.2.14-5.0 from RedHat or 2.2.14.SuSE
  may not work.
  +++ It is highly recommended to backup the old kernel sources before applying
      the patch! +++

  Extract the kernel sources to a directory of your choice, typically in
      /usr/src.
  Make sure that the new linux kernel sources are referenced by a symbolic link
  called /usr/src/linux before continuing.

  Copy the patch file to /usr/src and extract it from there:
 
      - for a gzip-packed patch use

            'zcat piii.gz | patch -p0 -E' 
  
      - for unpacked patches use 
  
            'cat piii | patch -p0 -E' 
  
  No queries or errors are displayed if your kernel matches 
  exactly the kernel the patch was designed for.

  Change to '/usr/src/linux' and type 'make menuconfig' to start the kernel
  configuration program. 
  Enter "Processor type and features". Select "PIII/Xeon/Deschutes" as
  Processor family to display ISSE or MMX2 menu items. For a fully working,
  ISSE-capable kernel select the following options:

      - Processor type and features
            (PIII/Xeon/Deschutes) Processor Family
            - [*] Enable CPU Specific (MMX/MMX2) Optimization Functions
            - [*] MTRR (Memory Type Range Register) support

      - Loadable Module Support 
            - [*] Enable loadable module support
            - [*] Kernel module loader support

  Save your settings and leave the menuconfig program.
  Build your kernel. See the documentation of your distribution vendor for 
  details.
  Install the newly compiled kernel and test it.
  +++ Keep your previous kernel bootable in case you experience problems. +++

  In case of doubt or trouble please check the files /var/log/XFree86.0.log and
  /var/log/messages for hints on possible failures.

  After you have successfully compiled and installed the new, patched kernel, 
  reboot your system with the new kernel.

  Install the driver for a second time. Use the Install.sh script again.
  Remember, you must be logged in with super user (root) privileges. 
  Now the necessary kernel driver module and client driver will be installed.

  You may use the 'cpu_check'software tool for checking the system CPU and
  the kernel patch.


2.4 Generating a customized kernel module
-----------------------------------------

  The FireGL 8700/8800 uses the performance capacity of your workstation
  intensively. A precisely tailored kernel module is needed to support some
  features, for example, AGP support, busmaster DMA transfers, or memory
  mapping. Such a module is loaded at boot time or when the x-server starts
  up and remains present for usage with the driver all the time. 

  Note: 
    If the module is missing, you do not have hardware-accelerated 
    3D-support and the 2D driver might abort while loading. See
    the console outputs of X11 and /var/log/XFree86.0.log for results.
  
  You are in need to start the kernel module build manually
  - if you spot having no hardware 3D support (run fglrxinfo to check)
  - if you have done any important system changes, e.g. a changed kernel
  - if you were adviced so whilst the driver installation
 
  The binary package provides fully working kernel modules for a few
  distributions and kernel versions. So, for some cases, you don't need
  to build a kernel module yourself. The installer will notify you if
  installation of provided modules did succeed.
  
  The FireGL provided kernel modules will not fit your needs, for example,
  - if you have a new or customized Linux kernel, or
  - if you have kernel symbols versioning enabled.
  
  In these cases you must build the configured sources of your kernel
  at /usr/src/linux - this is allowed to be a symlink.
  To build a customized kernel module you need administrator privileges.
  You must manually start two shell scripts to build a customized kernel 
  module.

  Perform the following steps:
      - get the matching Linux kernel source
      - run "make distclean"
      - setup that kernel source with the config file matching your kernel
      - run "make dep" on the kernel source tree
      - go to "/lib/module/fglrx/build_mod" and enter "./make.sh"
      - go to "/lib/module/fglrx" and enter "./make_install.sh"
  
  Enter /lib/module/fglrx/build_mod and enter (as root) "./make.sh".
  Thus you will create a new customer-specific kernel module.
  If the creation fails, look up for the reason in the
  shell and in the related logfile "make.log".
  
  Note: Ignore the following warning that may turn up in some configurations:
  
      compiling...
      /tmp/ccOWu6AI.s: Assembler messages:
      /tmp/ccOWu6AI.s:9: Warning: Ignoring changed section attributes 
          for .modinfo

  A specific combination of Linux kernel sources and C compiler triggers this 
  warning. Similar messages turn up if you build your own Linux kernel. This 
  is a widely known Linux issue that does not affect your builds.

  There are some kernel sources arround that produce further warnings about
  some sort of pointer conversion. You can ignore this warnings as well.
  
  To set up a kernel module build you need Linux kernel headers that match
  exactly the kernel you are running.   
  If your kernel is configured SMP with P-III support and agpgart enabled, 
  you must have a kernel source that is configured exactly the same way.
  
  If your kernel was built by your Linux distribution and supplied as binary:
  - Get the related source RPM file 
  - Extract the matching configuration settings contained there.
    (RedHat Linux files may reside in the subdir "configs".
    SuSE Linux: find the files in the SRPMs.
    Latest SuSE versions will present /proc/config.gz for the running kernel.)
  - Set up your kernel source with these settings:
    (1) copy the config file to /usr/src/linux<your-extension>/.config
        (For SuSE config.gz first apply "gunzip config.gz" at a temp location.)
    (2) run "make oldconfig" for exact importing
  - Run "make dependencies" ("make dep").

  Note:
    If you want to build multiple modules for multiple kernel configurations,
    run "make distclean" after each cycle and setup the config file again.
  
  If you cannot build the matching kernel headers
  (1) build a new kernel from scratch that is optimally customized to
      your machine,
  (2) install the new kernel and boot it
  (3) continue with setup - if the kernel runs. 
  
  Perform the final step on each customized kernel module build:
  - Go to /lib/modules/fglrx
  - Start ./make_install.sh
  This copies the matching kernel module into the loadable modules tree of your
  running kernel. The script also updates the module loader dependency list.
  
  On machines that use identical kernels and kernel configuration the results
  of the kernel module build are interchangeable. Copy the module into
    /lib/modules/fglrx
  and setup the new module for usage by running the script
    ./make_install.sh
  that you can find in the same directory.
  

2.5 Enabling AGP Support
------------------------

  Several up-to-date distributions, for example, SuSE 7.0 or RedHat 7.0, 
  come with a matching and possibly activated AGP support. This is provided
  by the so called 'agpgart' kernel module.

  If the graphics driver's kernel module detects the presence of this feature,
  it tries to connect to the supplied AGP/GART module. 

  To verify if the related AGP module is already loaded run 'lsmod' as root. 
  With the XServer running and the connection established, the usage count 
  of the agpgart module has to be different from zero.
  
  Note:
    The modules dependency list does not list agpgart as a requirement for
    the fglrx kernel module - agpgart is not a 'hard dependency' for module 
    operation. So the system's administrator has maximum control of what he 
    wants to run on a specific machine.

  The latest version of the driver's kernel module is shipped with 'built-in' 
  agp support. If your distribution's kernel setup does not provide agpgart 
  compatible services, the FireGL built-in agpgart module will be used.


3. MONITOR CONFIGURATION
------------------------


  NOTES:
  (1) Full overlay functionality is available in Single Head mode only.
  (2) A connected digital display is always the primary display
  (3) Primary/Secondary head definition (if two display devices are connected):
  (4) Quad Buffer Stereo ("Active Stereo") is available in Single Head mode 
      only.
  
        - Primary Head:
          the bottom DVI port on X1, LCD output on M9, the only DVI port on 
          other cards (The connected display on this head is the first 
          string in MonitorLayout option).

        - Secondary Head:
          the top DVI port on X1, VGA port on all other cards (The connected 
          display on this head is the second string in MonitorLayout option).


  The driver supports the following monitor configurations.

    - Single Head: Single monitor operation only. If a second monitor is 
      connected, it remains dark. 
      This is the only available display mode setting if you have only one 
      monitor connected.
      This is further the only mode Quad Buffer Stereo ("Active Stereo") is 
      working.

    - Clone: The contents of the primary monitor are duplicated on the second 
      monitor. If one monitor cannot display the selected resolution, a lower
      resolution is automatically selected for this monitor. The original 
      resolution is used then as it was specified as the virtual resolution.
      This means the second screen will do panning when the mouse moves ahead.

    - Big Desktop. There is a single big framebuffer that gets split either
      horizontally or vertically and each half is sent to a single monitor.
      
      Availabel selections:
        - Big Desktop Horizontal: left section of your display on the 
          primary monitor and the right section on the second monitor.
        - Big Desktop Vertical: upper section of your display on the 
          primary monitor and the lower section on the second monitor.
         
      NOTES: 
      (1) There is only a single frame buffer and only one window manager.
      (2) Both monitors have to operate with the same video mode settings.
      (3) The mode information in 'Section Screen, Subsection Display, Modes' 
          (in XF86Config-4) does apply to both monitors.
      (4) The maximum resolution for OpenGL operation are: 
          - R200 family (Radeon 8500-9000 Pro, Fire GL 8700/8800/E1): 2048x2048
          - R300 family (Radeon 9500-9700 Pro, Fire GL X1/Z1):        2560x2560
      (5) Option "ScreenOverlap" (Type OPTV_INTEGER):
          - This option is intended to allow image overlapping with e.g. two 
            video projectors.
          - This option only applys to "Big Desktop" mode.
          - When this option is set to a value greater than zero then the a full
            heighted rectangualar region along the aligned edge will get 
            displayed on both screens.
          - The option value specifies the width in pixels of the rectangular 
            region.
          - The final virtual screen width (unless a higher virtual screen was
            specified) is the sum of the width of both screens minus the given 
            screen overlap value.
         - The monitor resolutions and timings from the config file remain
           unaltered.

    - Dual Head: Separate framebuffer, independent displays and video modes
       for each monitor (two window managers possible).


3.1 Changing the monitor configuration
--------------------------------------

  IMPORTANT: To rebuild the XF86Config-4 file, only use the fglrxconfig tool.

  NOTE: To rebuild the XF86Config-4 file you must know the type of monitor,
    keyboard, and mouse of your system. See the existing config file first.
  
  WARNING: Do not specify monitor timings that do exceed the performance
    scope of your monitor. Wrong monitor settings can damage your monitor! 
    
  To change the monitor configuration, you have to execute these steps:

  1. Log on with root privileges.
 
  2. Run the FireGL 8700/8800/E1/X1/Z1 configuration program again.
     Enter:

       fglrxconfig

  3. Answer the questions of the fglrxconfig program and save
     the settings to /etc/X11/XF86Config-4.

  4. Restart the XServer.


4. CONFIGURATION FEATURES AND INFORMATION
-----------------------------------------

  1. To check, if 3D acceleration is working properly, use the
     'fglrxinfo' program installed together with the FireGL 8700/8800 driver.

     To run the test program enter:

         fglrxinfo

     Typical output information (3D acceleration is working properly)
     may read like this:

         OpenGL vendor string: ATI
         OpenGL renderer string: FireGL 8700/8800
         OpenGL version string: 1.2.1234 (1.2.3)

  2. Some tools, for example, from the XFree86 group may also
     provide useful information, e.g. xdpyinfo or glxinfo.

  3. For information on the CPU support of your running system 
     run the application "cpu_check". (This program might only
     be present if you have also installed the FireGL 1 - 4 drivers.)

  4. Dual Head Configuration
     The driver is multi-load capable, i.e. a second screen with a 
     different window manager can be created for the second output
     connector. Use configuration tool "fglrxconfig" to enable dual 
     head mode. To get control of the second screen, just move your 
     mouse to it.

     Notes:
     - Xinerama and DRI are mutual exclusive. Because of this Xinerama
       can not be enabled.

  5. Video Overlay
     All graphics boards supported by this driver are Video Overlay capable.
     When you are using the fglrxconfig tool to generate a XF86Config-4 file,
     Video Overlay is enabled.

     Notes:
      - Video Overlay, OpenGL Overlay and Quad Buffer Stereo ("Active Stereo")
        are mutual excluding each other.

  6. Quad Buffer Stereo ("Active Stereo")
     The FireGL X1 is Quad Buffer Stereo ("Active Stereo") capable. To enable 
     Stereo mode add
        'Option "Stereo" "on"'
     to the XF86Config-4 file and disable both, VideoOverlay and OpenGLOverlay.
     Use at least 100 Hz (better 120Hz) modes for Stereo. Find appropriate mode 
     lines in the XF86Config-4 file generated by fglrxconfig.

     Notes:
     - For stereoscopic viewing you need shutter glasses that are not included 
       in delivery. Connected to the stereo output connector of the graphics 
       card, the shutter glasses alternately open the view for the left or right
       eye.

  7. Full Scene Anti Aliasing (FSAA) 
     The FireGL X1 uses a multi-sampling technique to implement anti-aliasing.
     To set/enable/disable FSAA use
        Option "FSAAScale" (Type OPTV_INTEGER).
     Possible values for "FSAAScale":
     - "1" (disables FSAA)
     - "2" (2 multi sample points)
     - "4" (4 multi sample points)
     - "6" (6 multi sample points).

     Notes:
     (1) By default FSAA gamma is set to "2.2." (Typical for CRT display 
         devices). To disable FSAA gamma (i.e. set it to "1.0") use
            'Option "FSAADisableGamma" "yes"' (Type OPTV_BOOLEAN)
     (2) If you want to customize the sample points set 
            'Option "FSAACustomizeMSPos" "yes"' (Type OPTV_BOOLEAN)
     (3) To set ...
         ... the first point use
            Option "FSAAMSPosX0" (Type OPTV_DOUBLE)
            Option "FSAAMSPosY0" (Type OPTV_DOUBLE)
         ... the 2nd point use
            Option "FSAAMSPosX1" (Type OPTV_DOUBLE)
            Option "FSAAMSPosY1" (Type OPTV_DOUBLE)
         ... the 3rd point use
            Option "FSAAMSPosX2" (Type OPTV_DOUBLE)
            Option "FSAAMSPosY2" (Type OPTV_DOUBLE)
         ... the 4th point use
            Option "FSAAMSPosX3" (Type OPTV_DOUBLE)
            Option "FSAAMSPosY3" (Type OPTV_DOUBLE)
         ... the 5th point use
            Option "FSAAMSPosX4" (Type OPTV_DOUBLE)
            Option "FSAAMSPosY4" (Type OPTV_DOUBLE)
         ... the 6th point use
            Option "FSAAMSPosX5" (Type OPTV_DOUBLE)
            Option "FSAAMSPosY5" (Type OPTV_DOUBLE)
         For FSAA "2" you have to set 2 points, for FSAA "4" you have to set 4
         points, for FSAA "6" you have to set all 6 points.
     (4) Range. Pixel size is 1x1, so the range is
            (0 <= (X position) <= 1) and (0 <= (Y position) <= 1).
     (5) FSAA applies only to OpenGL.

  8. Center Mode
     Center Mode allows 'real' screen display in non-"panel native modes": one 
     pixel of the frame buffer is one pixel on the screen. The display is 
     centered on the screen and the surrounding screen area remains black.

     NOTES: 
     - By default a Mobility FireGL automatically expands the display in 
       non-"panel native modes" to fullscreen size.
     - Non-"panel native modes": For example, 1280x1024 resolution on a 
       1600x1200 (= panel native mode) LCD.
     - Some panels may not work in Center Mode, screen remains black then.

     How to enable the Center Mode function?
     - Open the XF86Config-4 file
     - Go to the Driver Device section
     - Insert the Option  "CenterMode" "on" 
     - Restart the X server


5. USING THE CONTROL PANEL APPLICATION
--------------------------------------

  The current drivers come with an easy-to-use set of panels
  that integrate into the two most common window managers.

  So you can easily retrieve information about the adapter
  and its setup. You can also select several
  variations of single or dual screen setups and the adjustment
  of the screen color gamma factors.

  Notes:
  - The panel application is based upon the QT Toolkit for Linux
    from Trolltech. Since not all Linux platforms may have the respective
    libs installed, we provide the panel application in two versions:
    - statically linked and 
    - dynamically linked
    By default the dynamically linked version is used. 

    If you do not have the appropriate version of the QT libraries available
    in your system then the installer will redirect to the statically linked
    version of the panel application which is also available with this name: 
      /usr/X11R6/bin/fireglcontrol.static
    This binary comes with the matching QT libs inside. This version of the
    application has a significantly bigger file size and memory footprint.

    The statically linked version should match with your the major compiler
    version in order to get any c++ mangled names correct. If that does not
    match you might see several unresolved symbols reported when the panel
    apllication is started vom an X11 based terminal. In this case only a
    rebuild of the panesl from the provides sources will help. This task
    should be doable by any average system administrator with c knowledge.

    The finally unused version will only be present as a bzip2 compressd
    archive in the /usr/X11R6/bin directory to minimize space consumption.

  - For GPL and QPL license reasons (copies are provided with the driver
    package) the sources of the panel application are included in the driver
    package. If you are interested in these files then please find find them
    (bundled as an archive) after driver installation on your system at:
      /usr/src/fglrx_panel_sorce.tgz

    NOTE:
    RedHat 8.0 users do need to install the qt-devel package in order to
    compile this source package if they target for panel recompiliation.
    This package provides some needed source components and symbolic links.


5.1 How to Launch the Control Panel Application
------------------------------------------------

  To launch the control panel application:

  - If you are using RedHat 8.0 then go to:
      Main Menu ("RedHat symbol") => Extras => Other => ATI Control

  - If you are using the GNOME Desktop Environment then go to:
      Main Menu ("gnome footprint") => Programs => ATI Control

  - If you are using the KDE Desktop Environment then go to:
      Main Menu ("K icon") => ATI Control

  - If you are using another window manager you will find the
    FireGL 8700/8800 control panel at:
      /usr/X11R6/bin/fireglcontrol

    If you do have set a path to this location then can just enter
      fireglcontrol
    for launching the panels application from inside an xterm window.


5.2 --- spare ---
-----------------

5.3 Gamma Correction Adjustment
-------------------------------

  To adjust the gamma correction factor 
  
  The Gamma Correction Adjustment settings are individual for each monitor.

  - In the ATI FireGL 8700/8800 control panel select the appropriate monitor
    tag for the monitor you want to correct:
      Monitor tab 1 is for the monitor connected to the VGA connector,
      Monitor tab 2 is for the monitor connected to the DVI connector.
  - select the Adjustment tab for the desired monitor 
  
  Adjust the monitor's gamma correction to your needs with the red, green
  and blue slider bars. The applied changes will show immediately on
  the respective monitor. The effect of display gamma is to darken or lighten
  the midtones of the framebuffer data.

  The gamma correction affects the entire display of the respective monitor. 
  The slider settings range is 0.1 - 10.0 (among X). The default is 1.0.
  With "Link sliders" selected, the three sliders move together as you drag any
  individual slider. With the "Link sliders" unchecked, you can adjust colors
  individually by dragging each of the applicable slider separately.

  Click the ">1<" button - if not linked then for each color separately - to 
  reset the respective gamma correction value back to the default value of 1.0.

  Click the Apply or OK button to confirm your adjustments.

  Notes:
  - The gamma values are adjusted by applying an exponential translation 
    function that matches each of the 256 possible input values of R, G and B 
    to a numeric output value. This value is transmitted to the monitor driving 
    units. 

    When adjusted with the panels 
    - An input value of zero is always matched to the darkest output value.
    - An input value of 255 is always matched to the lightest output value.

  - Since the source of the panel application is provided, advanced programmers 
    can customize the gamma function, e.g. to address special needs like gamma 
    offsets or clamping.

  - Caution: Different gamma correction applications may not work as described 
    here. Please check with the application-related instructions. 


6. NOTES, TROBULESHOOTING AND LIMITATIONS
-----------------------------------------

  1. The FireGL 8700/8800 allows graphical Linux installation in VGA and VESA 
     modes. On distributions that come with pre-packaged drivers for the 
     graphics board a native graphics mode install will work.

  2. For SuSE systems with XFree86 4 and higher the following might apply:
     If you do spot warnings about wrong, incomplete or missing GLX support
     when running any opengl related software (or the SuSE script 3Ddiag)
     then you might be in need for doing what is described below.

     SuSE is providing XFree86 3.3.6 for legacy hardware where drivers are
     not yet ported to current XFree86. For this reason you might have a
     look into the SuSE installation guide for OpenGL (chapter 6 on SuSE 7.3)
     for a few more details on the subject.

     In short, you require the installation of the xf86_glx-4.*.i386.rpm
     package on your machine. If you have selected the checkbox for
         "3D hardware support"
     whilst running the system installation program then you might already
     have this package.

     After this you have to run the following two scripts
         /usr/X11R6/bin/switch2xf86-4
         /usr/X11R6/bin/switch2xf86_glx
     which sets up the executeables of X4.x.x as the default and further
     installs the DRI libraries for X11 compliant OpenGL support. There
     are other methods of OpenGL support like "mesasoft" or some third
     party hw specific set of OpenGL libraries that wont accellerate or
     even work with the FireGL series of adapters.

     The installer of the FireGL driver package tries to care and solve
     for the mentioned requirement, but might not always succeed in it,
     especially when the required rpm package is just not present. Further
     this setup might get corrupted if other third party graphics hardware
     was installed in the system for some reasons.

  3. If you do spot interference with grafical console emulations in
     form of textmode screen corruption, hangs on console switching
     or sudden stops on XServer shutdown, then try replacing kernel
     parameters like "vga=<nnn>" or "vga=ask" by "vga=normal".
     This will possibly apply to SuSE 8.0, but check with your system.
     
     If you are using the lilo boot loader then you will find this
     parameter most likely in the file /etc/lilo.conf. The "vga=..."
     statement will typically appear on its own line. After modifying
     this file you must start "lilo" once to update the boot block data.

     If you are using the grub boot loader then you will find this
     parameter possibly in the file /boot/grub/menu.lst. The "vga=..."
     entry will typically appear in a line that starts with the keyword
     "kernel". After modifying this file you can simply reboot because
     "grub" is auto configuring.

     The files and actions will differ if you are using a different loader.

  4. Xv support
     Video and other media playback via the Xv software system is currently
     in an early stage and therefore some visualisation problems might occure. 
     If you really have problems with that functionality we recommend you to
     try out the program "mplayer" and set its VideoOut option to "GL" for best
     overall quality and performance.

  5. Limitations
     - Systems with libc 6.0 trough libc 6.1 are not supported.
     - Panning/scrolling does not work in the "big desktop" display mode.

  6. For further information on programming OpenGL Applications, DRI, DRM
     please refer to the file README.DRI located at /usr/X11R6/lib/X11/doc.

  7. Other OpenGL implementations
     - Your system may have installed other OpenGL-compatible libraries (e.g.
       MesaGL) with higher priority than the hardware supported libraries.
     - Your applications may link to other GL libs than those provided with the
       FireGL 8700/8800 - and therefore do not use the provided hardware 
       accelera
