path: root/xc/programs/Xserver/hw/xfree86/doc/README.DRIcomp

                            DRI Compilation Guide

          VA Linux Systems, Inc. Professional Services - Graphics.

                                8 August 2000

1.  Preamble

1.1  Copyright

Copyright © 2000 by VA Linux Systems, Inc.  All Rights Reserved.

Permission is granted to make and distribute verbatim copies of this document
provided the copyright notice and this permission notice are preserved on all
copies.

1.2  Trademarks

OpenGL is a registered trademark and SGI is a trademark of Silicon Graphics,
Inc.  Unix is a registered trademark of The Open Group.  The `X' device and X
Window System are trademarks of The Open Group.  XFree86 is a trademark of
The XFree86 Project.  Linux is a registered trademark of Linus Torvalds.
Intel is a registered trademark of Intel Corporation.  3Dlabs, GLINT, and
Oxygen are either registered trademarks or trademarks of 3Dlabs Inc. Ltd.
3dfx, Voodoo3, Voodoo4, and Voodoo5 are registered trademarks of 3dfx Inter-
active, Incorporated.  Matrox is a registered trademark of Matrox Electronic
Systems Ltd.  ATI Rage is a registered trademark of ATI Technologies, Inc.
All other trademarks mentioned are the property of their respective owners.

2.  Introduction

This document describes how to download, compile and install the DRI project.
This information is intended for experienced Linux developers.  Beginners are
probably better off installing precompiled packages.

Edits, corrections and updates to this document may be mailed to brianp@val-
inux.com.

3.  Prerequisites

You'll need the following:

   o At least 400MB of free disk space.  More is needed if you want to build
     with debugging information or keep several build trees.

   o A fast system.  Using a PIII-550 it takes about 1/2 hour to build every-
     thing.

   o GCC compiler and related tools.

   o ssh (secure shell) for registered developer downloading of the DRI
     source tree

For 3dfx Voodoo3 hardware, you'll also need:

   o Glide3x headers and runtime library if you want to use the 3dfx driver.
     These can be obtained from linux.3dfx.com.

   o Linux kernel 2.2.x.  The DRI developers have been using stock RedHat 6.1
     systems (kernel 2.2.12-20).  Later kernel versions will be supported in
     the future.

For Matrox G200/G400 hardware, you'll also need:

   o Linux kernel 2.3.51.  Older kernel versions will not work.

For Intel i810 hardware, you'll also need:

   o Linux kernel 2.3.99-pre6.  Older kernel versions will not work.

For ATI Rage hardware, you'll also need:

   o Linux kernel 2.3.51.  Other kernel versions may work but this one is
     known to work.

4.  Kernel preparation

You may have to upgrade your Linux kernel in order to use the DRI.  This is
because you need a kernel version which supports AGP.  Building a new Linux
kernel can be difficult for beginners but there are resources on the Internet
to help.  This document assumes experience with configuring, building and
installing Linux kernels.

Linux kernels can be downloaded from www.kernel.org

Download the needed kernel and put it in /usr/src.  Create a directory for
the source and unpack it.  For example:

                 cd /usr/src
              rm -f linux
                 mkdir linux-2.3.51
                 ln -s linux-2.3.51 linux
                 bzcat linux-2.3.51.tar.bz2 | tar xf -

Now configure your kernel.  You might, for example, use make menuconfig and
do the following:

   o Go to Code maturity level options

   o Enable Prompt for development and/or incomplete code/drivers

   o hit ESC

   o Go to Character devices

   o Disable Direct Rendering Manager (XFree86 DRI support) since we'll use
     the DRI module from the XFree86/DRI tree.

   o Go to /dev/agpgart (AGP Support) (EXPERIMENTAL) (NEW)

   o Hit SPACE twice

   o Enable all chipsets' support for AGP

It's recommended that you turn on MTRRs under Processor type and Features,
but not required.

Configure the rest of the kernel as required for your system (i.e. Ethernet,
SCSI, etc)

Exit, saving your kernel configuration.

Edit your /etc/lilo.conf file.  Make sure you have an image entry as follows
(or similar):

                 image=/boot/vmlinuz
                       label=linux.2.3.51
                       read-only
                       root=/dev/hda1

The important part is that you have /boot/vmlinuz without a trailing version
number.  If this is the first entry in your /etc/lilo.conf AND you haven't
set a default, then this will be your default kernel.

Now compile the new kernel:

                 cd /usr/src/linux-2.3.51
                 make dep ; make bzImage
                 make modules ; make modules_install
                 make install

Note that the final part, make install, will automatically run lilo for you.

Now reboot to use this new kernel.

5.  Downloading the XFree86/DRI CVS Sources

The DRI project is hosted by VA Linux Systems' SourceForge.  The DRI source
code, which is a subset of the XFree86 source tree, is kept in a CVS reposi-
tory there.

The DRI CVS sources may be accessed either anonymously or as a registered
SourceForge user.  It's recommended that you become a registered SourceForge
user so that you may submit non-anonymous bug reports and can participate in
the mailing lists.

5.1  Anonymous CVS download:

  1.  Create a directory to store the CVS files:

                       cd ~
                       mkdir DRI-CVS

      You could put your CVS directory in a different place but we'll use
      ~/DRI-CVS/ here.

  2.  Check out the CVS sources:

                       cd ~/DRI-CVS
                       cvs -d:pserver:anonymous@cvs.dri.sourceforge.net:/cvsroot/dri login
                         (hit ENTER when prompted for a password)
                       cvs -z3 -d:pserver:anonymous@cvs.dri.sourceforge.net:/cvsroot/dri co xc

      The -z3 flag causes compression to be used in order to reduce the down-
      load time.

5.2  Registered CVS download:

  1.  Create a directory to store the CVS files:

                       cd ~
                       mkdir DRI-CVS

      You could put your CVS directory in a different place but we'll use
      ~/DRI-CVS/ here.

  2.  Set the CVS_RSH environment variable:

                       setenv CVS_RSH ssh      // if using csh or tcsh
                       export CVS_RSH=ssh      // if using sh or bash

  3.  Check out the CVS sources:

                       cd ~/DRI-CVS
                       cvs -z3 -dYOURID@cvs.dri.sourceforge.net:/cvsroot/dri co xc

      Replace YOURID with your CVS login name.  You'll be prompted to enter
      your sourceforge password.

      The -z3 flag causes compression to be used in order to reduce the down-
      load time.

5.3  Updating your CVS sources

In the future you'll want to occasionally update your local copy of the DRI
source code to get the latest changes.  This can be done with:

                cd ~/DRI-CVS
                cvs -z3 update -dA xc

The -d flag causes any new subdirectories to be created and -A causes most
recent trunk sources to be fetched, not branch sources.

6.  Mesa

Most of the DRI 3D drivers are based on Mesa (the free implementation of the
OpenGL API).  The relevant files from Mesa are already included in the
XFree86/DRI source tree.  There is no need to download or install the Mesa
source files separately.

Sometimes a newer version of Mesa will be available than the version included
in XFree86/DRI.  Upgrading Mesa within XFree86/DRI is not always straightfor-
ward.  It can be an error-prone undertaking, especially for beginners, and is
not generally recommended.  The DRI developers will upgrade Mesa when appro-
priate.

7.  Compiling the XFree86/DRI tree

7.1  Make a build tree

Rather than placing object files and library files right in the source tree,
they're instead put into a parallel build tree.  The build tree is made with
the lndir command:

                 cd ~/DRI-CVS
                 ln -s xc XFree40
                 mkdir build
                 cd build
                 lndir -silent -ignorelinks ../XFree40

The build tree will be populated with symbolic links which point back into
the CVS source tree.

Advanced users may have several build trees for compiling and testing with
different options.

7.2  Edit the host.def file

The ~/DRI-CVS/build/xc/config/cf/host.def file is used to configure the
XFree86 build process.  You can change it to customize your build options or
make adjustments for your particular system configuration

The default host.def file will look something like this:

                 #define DefaultCCOptions -Wall
                 #define DefaultGcc2i386Opt -O2
                 #define LibraryCDebugFlags -O2
                 #define BuildServersOnly YES
                 #define XF86CardDrivers vga tdfx mga r128 i810
                 #define LinuxDistribution LinuxRedHat
                 #define DefaultCCOptions -ansi GccWarningOptions -pipe
                 #define BuildXF86DRI YES
                 #define HasGlide3 YES
                 /* Optionally turn these on for debugging */
                 /* #define GlxBuiltInTdfx YES */
                 /* #define GlxBuiltInMga YES */
                 /* #define GlxBuiltInR128 YES */
                 /* #define DoLoadableServer NO */
                 #define SharedLibFont NO

The ProjectRoot variable specifies where the XFree86 files will be installed.
You probably don't want to use /usr/X11R6/ because that would overwrite your
default X files.  The following is recommended:

                 #define ProjectRoot /usr/X11R6-DRI

Especially note the XF86CardDrivers line to be sure your driver is listed.

If you have 3dfx hardware be sure that the Glide 3x headers are installed in
/usr/include/glide3/ and that the Glide 3x library is installed at
/usr/lib/libglide3x.so.

If you do not have 3dfx hardware comment out the HasGlide3 line in host.def.

7.3  Compilation

To compile the complete DRI tree:

                 cd ~/DRI-CVS/build/xc/
                 make World >& World.LOG

Or if you want to watch the compilation progress:

                 cd ~/DRI-CVS/build/xc/
                 make World >& World.LOG &
                 tail -f World.LOG

With the default compilation flags it's normal to get a lot of warnings dur-
ing compilation.

Building will take some time so you may want to go check your email or visit
slashdot.

WARNING: do not use the -j option with make.  It's reported that it does not
work with XFree86/DRI.

7.4  Check for compilation errors

Using your text editor, examine World.LOG for errors by searching for the
pattern ***.

Verify that the DRI kernel module(s) for your system were built:

               cd ~/DRI-CVS/build/xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel
               ls

For the 3dfx Voodoo, you should see tdfx.o.  For the Matrox G200/G400, you
should see mga.o.  For the ATI Rage 128, you should see r128.o.  For the
Intel i810, you should see i810.o.

If the DRI kernel module(s) failed to build you should verify that you're
using the right version of the Linux kernel.  The most recent kernels are not
always supported.

If your build machine is running a different version of the kernel than your
target machine (i.e. 2.2.12-20 vs. 2.3.99-pre6), make will select the wrong
kernel headers. This can be fixed by explicitly setting the value of TREE.
If the path to your kernel source is /bigdisk/linux-2.3.99-pre6,

               cd ~/DRI-CVS/build/xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel
               make TREE=/bigdisk/linux-2.3.99-pre6

or alternatively, edit Makefile to include this change.

After fixing the errors, run make World again.  Later, you might just compile
parts of the source tree but it's important that the whole tree will build
first.

8.  Normal Installation and Configuration

Most users will want to install the new X server and use it instead of the
original X server.  This section explains how to do that.  We assume that the
user is upgrading from XFree86 3.3.x.

Developers, on the other hand, may just want to test the X server without
actually installing it as their default server.  If you want to do that, skip
to the next section.

8.1  X Installation

You'll need to run as root to do the following commands:

                su

As mentioned above, the installation directory is specified by the Project-
Root variable in the host.def file.  Create that directory now if it doesn't
already exist, then run the install commands:

                mkdir /usr/X11R6-DRI
                cd ~/DRI-CVS/build/xc
                make install

8.2  Linker configuration

Edit your /etc/ld.so.conf file and put /usr/X11R6-DRI/lib as the first line.
Then run:

                ldconfig

This will ensure that you use the new X libraries when you run X programs.

8.3  Update Locale Information

To update your X locale information do the following:

                  cd ~/DRI-CVS/build/xc/nls
                  xmkmf -a
                  make
                  make install

This will prevent a locale error message from being printed when you run Xlib
programs.

8.4  Setup Miscellaneous Files

Issue the following commands:

                  cd /usr/X11R6-DRI/lib/X11
                  ln -s /usr/X11R6/lib/X11/rgb.txt .
                  ln -s /usr/X11R6/lib/X11/fonts .
                  ln -s /usr/X11R6/lib/X11/app-defaults .

This will allow applications to use the fonts and resources that they used in
the past.

8.5  Disable the Old X Server and Enable the New One

Assuming that an installation of XFree86 3.3.x is present, we need to disable
the old 3.3.x X server and enable the new 4.0.x X server.

Issue the following commands:

                  cd /usr/X11R6/bin
                  mv Xwrapper Xwrapper.old
                  rm X
                  ln -s /usr/X11R6-4.0.1/lib/X11/XFree86  X

This will cause the new X server to be used instead of the original one.

8.6  Create the XF86Config File

Configuration files for XFree86 3.3.x will not work with XFree86 4.0.x.

The new 4.0.x server can generate a basic configuration file itself.  Simply
do this:

                  cd /usr/X11R6-DRI/bin
                  ./XFree86 -configure

A file named /root/XF86Config.new will be created.  It should allow you to
try your X server but you'll almost certainly have to edit it.  For example,
you should add HorizSync and VertRefresh options to the Monitor section and
Modes options to the Screen section.  Also, the ModulePath option in the
Files section should be set to /usr/X11R6-DRI/lib/modules.

On the DRI web site, in the resources section, you'll find example XF86Config
files for a number of graphics cards.  These configuration files also setup
DRI options so it's highly recommended that you look at these examples.

In any case, your new XF86Config file should be placed in /etc/X11/XF86Con-
fig-4.  This configuration file will be recognized by the 4.0.x server but
not by 3.3.x servers.  You can instead name it /etc/X11/XF86Config but
that'll overwrite your old config file, which you may want to preserve.

8.7  Start the New X Server

The new X server should be ready to use now.  Start your X server in your
usual manner.  Typically, the startx command is used:

                  startx

9.  Testing the Server Without Installing It

As mentioned at the start of section 8, developers may want to simply run the
X server without installing it.  This can save some time and allow you to
keep a number of X servers available for testing.

9.1  Configuration

As described in the preceding section, you'll need to create a configuration
file for the new server.  Put the XF86Config file in your ~/DRI-
CVS/build/xc/programs/Xserver directory.

Be sure the ModulePath option is set correctly.

9.2  A Startup Script

A simple shell script can be used to start the X server.  Here's an example.

             #!/bin/sh
             export DISPLAY=:0
             ./XFree86 -xf86config XF86Config & \
             sleep 2
             fvwm2 &
             xset b off
             xmodmap -e "clear mod4"
             xsetroot -solid "#00306f"
             xterm -geometry 80x40+0+0

You might name this script start-dri.  Put it in your ~/DRI-CVS/build/xc/pro-
grams/Xserver directory.

To test the server run the script:

                  cd ~/DRI-CVS/build/xc/programs/Xserver
                  ./start-dri

For debugging, you may also want to capture the log messages printed by the
server in a file.  If you're using the C-shell:

                  ./start-dri >& log

10.  Where To Go From Here

At this point your X server should be up and running with hardware-acceler-
ated direct rendering.  Please read the DRI User Guide for information about
trouble shooting and how to use the DRI-enabled X server for 3D applications.

     Generated from XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/DRIcomp.sgml,v 1.5 2000/08/28 18:24:15 dawes Exp $


$XFree86$