Installing Unreal Tournament GOTY Edition in Linux

Note: Content on this page is old and may no longer applicable, use with this is mind. The original artiles can be found here and here at Princess Leia's website. Special thanks to Elizabeth for allowing me to repost this artilce here on I have deleted many of the links as they were mostly dead. However, in some cases replacement articles exist at other sites, for instance the opengl renderer's faq's section on the very bottom. If you would like to contribute and rewrite this page, it would be appreciated.

Installing Unreal Tournament GOTY Edition in Debian and Gentoo Linux

At one time, I spend at least an hour every day playing UT, I found the need to look down every possible avenue to get it to run in linux. I knew it was possible but I think I was a little lazy and a little scared of linux at the time to try. So I just booted into windows everytime I wanted to play. SO when I finally got it to run in Linux it was a big, totally cool step %) In an effort to put together a complete instruction guide for the total installation of UT, I depended on the current developers and my boyfriend Michael. Together we made a complete installation guide, from putting your GOTY Edition installation cd into the drive, to installing the umod packs, to starting UT for the first time. For any of these installs you will need the GOTY edition cds (or game data somewhere on your system)


Installing UT on Debian Linux isn't too hard, the worst part about it is finding good places to download everything that is needed, and we've taken care of that for you. We have instructions for Debian and Gentoo.

Debian Install

What you will need for the Debian install:

Unreal Tournament Bonus Packs (BONUS & MAP PACKS), which you can find on the official Unreal Tournament site by clicking here (make sure to "save link target as" rather than just clicking this)

Now follow the debian instuctions located here:2.README.Debian

Gentoo Install

This install is very simple! At the time of writing this (06-22-04) the UT packages in portage are hard masked, so that's the only tricky part of this install. Everything you will need to download is in portage. So just follow these gentoo directions: 2.README.Gentoo

After recieiving an email from James Teague III about this How-To, he offered to write up some instructions for Redhat and Slackware. Those are located here: Installing Unreal Tournament GOTY Edition On Red Hat and Slackware Linux (this does not include info about installing umod packs)

Official Links

Other links you might find helpful

Unreal Tournament FAQ - This includes a great deal of great information about UT GOTY edition in linux.
Unreal Tournament Tweak Guide - Interesting tweaks for UT, not linux specific.
Gaming Tips and Tricks - Includes UT tips, benchmarks, and cheat codes.


I must give credit where it is due...

Thanks to Epic Games, for the creation of UT, the best FPSG ever, and the bonus umod packs that they gave out to their faithful users.

Thanks so much to Loki for putting so much effort into the development of the linux installation program, etc, for UT.

Thanks to the developers working with who created the UmodPack installation program.

Thanks to Michael for the grueling work of writing the instructions, something I had been dreading.

Thanks to the wonderful Gimp program that was used to make the original Tux, and which I used to make my UT tux.

Thanks to James Teague for putting together the list of "other links you might find helpful." And bringing to my attention the fact that people still do visit this site and I should fix my links!

And thanks to my friends and acquaintances that I play UT with all the time, I wouldnt be into UT if it werent for the fun we have playing together! I couldn't have made this page without all these people.


Content on this page is old and may no longer applicable, use with this is mind

Installing Unreal Tournament GOTY Edition On Red Hat and Slackware Linux

Written by James Teague III

(UT directions for Debian and Gentoo here)

Installations of GOTY on Red Hat and Slackware are similiar and fairly straightforward. This howto is intended for linux newbies who have played GOTY in the past on other operating systems. I say in the past because Unreal Tournament has been around since 1999 and GOTY (which simply included a second disc with the ChaosUT and Rocket Arena mods) since 2000. These days UT noobs are few and far between, although it is amazing how many people are still playing. In 2001-2 there were peaks of 8000 or so players (at the same time) in the "Populated Servers" tab in the UT Server browser. Yesterday (Memorial Day 2004) afternoon there were still 5600 players fragging away. Amazing. Anyway, the file you need to start fragging in Linux is: 

Download this file and cd into the directory where you put it. A .run file is a basically a compressed archive with a pre-appended shell script that runs/uses it, an idea that Loki Entertainment came up with. Fairly clever, too bad Loki is now defunct. When you download this file don't use a download accelerator or anything, as the .run format is rarely used and these apps will corrupt the archive. Also, it can confuse browsers, which will try to display it as text. Right click on the file link proper and do a "Save As" or "Save Link As" to download it properly. 
Red Hat 9.0 
1. Insert GOTY disc1

2. Close the Nautilus window that pops up (RH automounts/displays cdrom contents)

3. Open a terminal (Start -> System ->....Terminal) 

4. user@computer~> su


5. root@computer~> sh

6. The UT GOTY Installer GUI will come up. The paths should be /usr/games/ut for the install path and /usr/bin for the link path. If not then make it so. Click Install. The first disc will copy over. Then a dialogue box will appear, asking to insert disc 2 to contine. If the cdrom will eject then change discs and click ok. If the cdrom will not eject then: 

6a. Open a second terminal window and su to root as in step 4. 

6b. root@computer~> eject /mnt/cdrom

6c. Inset disc 2, close the Nautilus window that comes up, and then select ok. 

7. Sit back and chill, as this part takes the longest, copying disc 2 and then uncompressing all the files. The installer finishes and asks if you want to play or exit. Go ahead and exit at this point, since it was installed as root if you play now all the preferences will apply to the /root user. 

8. Close the second terminal window.

9. In the first terminal: 

root@computer~> exit

user@computer~> ut 
Red Hat 7.2
Install for 7.2 pretty much follows that of 9.0, in my case I did not even need the second terminal to get the cdrom to eject. However, 7.2 has a well-known bug that sometimes prevents a cdrom from being read, giving the error:

mount /dev/cdrom is not a valid block device

If you're getting this error then do this to fix it:

/sbin/depmod -ae

I had a little trouble running GOTY because of X problems, whereas RH9 looks at the XF86Config file to run X, 7.2 uses XF86Config-4. This is important if you are using an nvidia graphics chipset and are compiling your own driver modules. 
Slackware 9.0
The Slackware GOTY install is the easiest - open a command prompt, change directory to where the ut install script is, su to root and type: 


Unlike (for me) in Red Hat, the script will unmount the cdrom (thus allowing you to eject disc 1) when it comes time to insert disc 2. If it does get stuck then do the Red Hat thingy to fix it. 

After X starts KDE (on my system, anyway) a little desktop sound is played. Opening a command prompt and starting ut straight away results in the game starting but no sound, and sure enough there is a warning message in the prompt that the sound device, /dev/dsp, is busy or in use. The problem is that the desktop sound process (artsd) takes a few seconds to release the device. Before firing up ut you can see if anything is using your sound device with this command: 

lsof | grep dsp 

On my system it generally takes about 30 seconds or so for artsd to release the sound card. Also, in the sound-system menu in the Control Center you can uncheck the option that starts artsd when KDE starts. 





UT FAQ (Printer-friendly)

Unreal Tournament FAQ 

Last Updated on: 2000-09-16 01:43:52

This is where you will find useful information about Unreal Tournament for Linux. The following are answers to some frequently asked questions about this game. Please read these before e-mailing Loki Technical Support - Chances are your question is answered here too!

1. Introduction

  • 1.1 How to use this FAQ
  • 2. Requirements

  • 2.1 What are the system requirements for this game?
  • 2.2 Which Linux platforms does UT run on?
  • 3. Demo

  • 3.1 Where can I get the Unreal Tournament demo version?
  • 3.2 Does the demo support anything other than Glide?
  • 4. Installation

  • 4.1 How do I install the game?
  • 4.2 Which installer should I use?
  • 4.3 Can I specify the CD directory?
  • 4.4 Even after specifying the CD path, it still won't install, because it can't find the CD!
  • 4.5 Does the installer work under FreeBSD?
  • 4.6 How can I install umod files into the Linux version of UT?
  • 4.7 After installing, I can't run the game. It always exits with a SIGIOT.
  • 4.8 The game complains about a missing Where can I get that?
  • 5. Display

  • 5.1 The intro and sound are really choppy, and the game crashes when I hit ESC.
  • 5.2 The game crashed and I can't switch back to my normal resolution using
    CTRL-ALT- +/-
  • 5.3 I'm not getting any fog with the OpenGL renderer!
  • 5.4 Can I fix the menu corruption/black boxes instead of text in the menus?
  • 5.5 In OpenGL, the whole screen turns white whenever I'm hit, and I can't see anything!
  • 5.6 The 428 patch has really slowed the GL version down.
  • 5.7 UT crashes on my (G200/G400/Voodoo) when I hit ESC to exit the opening movie.
  • 5.8 UT 428a gives me "Glide: Colorbuffers (2,3) failed, failing back ..." when I try to launch.
  • 5.9 What does "The file '../System/Core' contains unrecognizable data" mean?
  • 5.10 The game displays very slowly/choppily, almost as if running in Mesa software mode, on my TNT/TNT2/GeForce.
  • 5.11 How can I change the display resolution of the game?
  • 6. Networking

  • 7. Input

  • 8. Sound

  • 9. Renderer

  • 9.1 I installed the Glide[OpenGL, Software] Renderer as default but now want to use the OpenGL[Glide, Software] renderer.
  • 9.2 How can I specify my OpenGL library?
  • 9.3 I am using XF 4.0 with my 3dfx card and the textures look really
    weird. When I exit the game I can see a "No space for texture"
    error message.
  • 9.4 The towers seem to flicker in CTF-FACE.
  • 9.5 The game segfaults when trying to use windowed mode with the Glide renderer.
  • 9.6 There used to be an OpenGL renderer for Windows, but it's no longer there!
  • 10. Administration

  • 10.1 The web admin won't run!
  • 10.2 My changes to UnrealTournament.ini on the server aren't taking effect.
  • 10.3 I can't get ngWorldStats working. Can you help?
  • 11. Miscellaneous

  • 12. Contact

  • 12.1 How do I report a bug?

  • 1. Introduction

      • This FAQ allows you to navigate through the answers by category, or individually, or to view the entire FAQ at once. The full view is also suitable for printing.

        This FAQ is modelled on the Linux HOWTO documents for consistency and ease of navigation.

      • The maintainers of the FAQ can be reached by e-mailing Please send all correspondance directly related to the FAQlist tool to that address.

    2. Requirements

      • Minimum system requirements:
        Linux kernel version 2.2.X

        Pentium II with 3D caccelerator card

        64 RAM required (128 MB recommended)

        Video card capable of 640x480 resolution
        XFree86 3.3.5 or newer at 16bpp

        OSS compatible sound card

        Hard disk with at least 550 MB of space

      • Unreal Tournament currently only runs on the x86 version of Linux. There is not a version for PPC, SPARC, Alpha, or any non-x86-compatible processor at this time.

      • Unreal Tournament is known to run under the Linux emulator included with FreeBSD. Success has been reported with the Linux emulator under OpenBSD.

        We provide Unreal Tournament for (x86) Linux, and that is the platform on which it is primarily tested. We are not familiar with any Linux-emulation capabilities of other Unix platforms (Solaris, AIX, etc.) and we do not provide a version specific to these other platforms.

    3. Demo

    4. Installation

      • First, download the appropriate update patch from

        If this is the first time you are installing Unreal Tournament, or if you are doing a complete re-install, you will need to download a patch named (or for the Game of the Year edition, The XXX will indicate the version of UT (425, 428, 436, etc.).

        If, however, you have the previous version installed (e.g. 425 when 428 came out, or 428 when 436 came out), you can download the patch to the previous install ( NOTE: we do not provide patches for versions prior to 425 -- if you have an existing 400, 400a, 402, or 413 install, you will need to re-install from scratch.

        Once you have the patch downloaded:
        [ From the README: ]

        Before starting the installation process with "sh"
        you must have your Unreal Tournament CDROM in your CDROM drive and have
        it mounted. For example:
        $ mount /mnt/cdrom

        $ sh

      • There are three possible files:
        Use if you are doing a new installation from a UT retail CD (blue jewel case, blue CD).

        Use if you are updating a UT 428 retail installation. This does NOT work on UT versions prior to 428. Do a new install instead.

        Use if you are doing a new installation using a Game of the Year CD (red jewel case, red CD).

        Loki does not presently offer support for other UT packages ("Best of Infogrames", "Totally Unreal").

      • (Beginning with UT 428)
        From the README:

        If you want to install Unreal Tournament remotely you can use the
        SETUP_CDROM environment variable to point to your CDROM drive.
        For example: $export SETUP_CDROM=/path/to/cdrom $sh ut-install

      • Please make certain that Joliet extensions are enabled in your kernel, since the UT CD was burned using Joliet extensions for the long filenames, and that you are using the correct installer for your CD. More information about the specific installers can be found here.

        A quick test is to mount the UT CD and list the files on it. If the filenames are all 8 characters or less, and contain tildes (~), then you do not have Joliet extensions enabled.

        Please re-build your kernel and modules after enabling Joliet extensions under the iso9660/cd-rom file system. Refer to your distribution's documentation (or the Linux Documentation Project at for instructions on re-compiling and installing your kernel.

        If you are running SuperMount or an auto-mounter, you may need to manually un-mount and re-mount the CD prior to pressing "Retry". You may also need to kill the associated daemons, in order to prevent them from confusing the CD detection.

      • Yes. You may need to either specify the CD directory (see the question "Can I specify the CD directory?"), or you may need to make certain that Joliet CD-ROM extensions are available. The original UT CD uses the Joliet extensions for the long file names, and the files will not be detected, copied, and patched if they cannot be found.

        You may also need to use the version of bash from /compat/linux/bin in order for the script itself to run.

      • Please use the UModPack set of utilities, which is available from

      • There are several possible SIGIOT problems/solutions.

        First, if the SIGIOT occurs shortly after a line indicating an fread error, the UT data files did not install correctly.
        If you have one available, please try installing from a different CD-ROM drive. Not all drives can correctly handle the copy protection on the CD. You should also check the md5sums of your CD against one of the lists at: If the md5sums do not match, your drive is not reading the CD correctly. (ut-cd1.txt is for the original UT retail release, ut-goty-cd1.txt and ut-goty-cd2.txt are for the CDs of the Game of the Year edition.)

        Second, if the SIGIOT occurs after an audio initilization, or if you upgraded UT from a previous install, you will need to rename your ~/.loki/ut/UnrealTournament.ini (if you want to carry over any customizations) and allow UT to re-create its own default UnrealTournament.ini.

        Third, if you are trying to run the OpenGL renderer but you have not configured the drivers yourself, you will need to either configure your own OpenGL drivers (see our FAQs on the subject) or you will need to switch to the software renderer.

        Finally, if you are installing using a Game of the Year CD, please make sure that you are using the correct installer. The retail release (blue CD, blue CD jewel case inserts) uses, and the GOTY release (red CD, red CD jewel case inserts) uses

      • is part of EsounD. You can download the project's files from You do not have to have the esd service running to play the game, but the library does need to be present in order to run the game.

      • Under some circumstances (such as using an unsupported CD), the maps are not uncompressed during the installation. The opening screen of Unreal Tournament is actually a map, called "Entry", which should be named /usr/local/games/ut/Maps/Entry.unr If this file is missing, the installation was not successful and you should make sure you are using the correct installer for your CD.

        If, however, the file is present but is called, it is still compressed. Since the maps were not shipped on the retail Unreal Tournament in a compressed format, you are either trying to use a GOTY CD (or one of the other, currently unsupported, Unreal Tournament releases) with the regular installer, or the uncompression step failed.

        If you have a number of .uz files in your Maps/ directory, you will need to uncompress them after the installation. A description for doing so (particularly with non-GOTY compressed CDs, such as the "Totally Unreal" and "Best of Infogrames" packages) can be found at

        See also
        for information regarding which CDs are currently supported.

    5. Display

      • You are running in software OpenGL mode via Mesa. You will need to either install the correct OpenGL drivers for your video card, use Glide if you have a Voodoo card, or switch to the built-in UT software renderer.

      • After running "xvidtune -unlock" you can change resolutions normally.

      • This is a known issue with UT 425 and has been fixed in 428.

      • This appears to occur with some OpenGL implementations.

        In ~/.loki/ut/System/UnrealTournament.ini, change the value of UsePalette from 1 to 0, like so:


      • Some of the Utah-GLX supported cards exhibit this behavior. The work-around is to set a variable in your ~/.loki/ut/System/UnrealTournament.ini. Look for the section [SDLDrv.SDLClient], and the variable ScreenFlashes. Change it to:

      • [The correct solution is to upgrade to UT 428a or UT 436, as the fix is included with that patch. Please reference 5.10 for more information.]

        [deprecated answer, left for maintenance reasons - do NOT use]:
        Please download the following file: and place it into your /usr/local/games/ut/System directory (or the System directory under your install directory if different from the default). This will clear up GL issues on several cards, including the G200, G400, and GeForce-based cards.

      • Try setting the environment variable SDL_VIDEO_X11_DGAMOUSE to 0 prior to launching UT.

      • If, for some reason, UT decides to segfault, it will often dump a core file. This file ends up in the System directory. The next time you start the game, UT will see this core file and attempt to load it, resulting in the "unrecognizable data" message, and a subsequent crash. To fix this, simply remove the core file from '/path/to/your/install/directory/System/', and all should be fine.

      • From the UT 428a README.PATCH.428a:

        UseTNT // workaround for TNT/TNT2 cards
        t this to one if you experience problem with your TNT/ TNT2 cards

        This answer also applies to 436 and 436-GOTY. Note that as of 436, all nVidia-based users should be using OpenGL instead of SDLGL. You will need to edit your UnrealTournament.ini for this to take effect. See 9.1 for information about selecting the correct renderer.

      • Normally, this is done from within the game using the Options menu. However, for some video card/driver combinations, this may not work correctly. In those cases, you may edit your ~/.loki/ut/System/UnrealTournament.ini file (and possibly the /usr/local/games/ut/System/UnrealTournament.ini file to make the global change for future users). You will need to change some variables (WindowedViewportX, WindowedViewportY, FullscreenViewportX, FullscreenViewportY), in the [SDLDrv.SDLClient] section of the file. So, for instance, if you wanted to run UT at 800x600, that portion of the file would look like:

        0 FullscreenViewportY=6
        Note that not all cards support all possible resolutions.

      • You will need to use the OpenGL renderer rather than the SDLGL renderer. The default OpenGL setting is the SDLGL, which is supported on all OpenGL cards, but the UseS3TC=1 setting does not necessarily work.

        The preferred renderer for nVidia GeForce cards is the OpenGLDrive, which can be configured by editing ~/.loki/ut/System/UnrealTournament.ini, by changing the lines:

        to the following:

        Note that the new OpenGL renderer has a separate configuration section (OpenGLDrv.OpenGLRenderDevice) from the default SDLGL renderer (SDLGLDrv.SDLGLRenderDevice). This means that you may need to re-set your UseTNT and UseS3TC settings in the new section.

    6. Networking

    7. Input

    8. Sound

      • First, you need to be using the new drivers from, rather than the older drivers from These drivers are much more complete.

        Second, it has recently come to our attention that the 1.1.2 release of the drivers are no longer compatible with UT and/or OpenAL. The 1.1.1 drivers are known to work correctly with UT, so you should drop back to 1.1.1 in order to run the game with sound.

        From a fenris suggestion, for dealing with 2.4.x:

        * Check out the cvs repository from sourceforge for the aureal driver with a -D
        (date) tag of: '2000-09-09 04:14:42'. This fetches the file versions that most
        ions). * Edit the Makefile to point to the kernel include tree. * make * in
        closely resembel the original aureal source with fixes for 2.4.x (non-testX ver
        sstall -o root -g root -m 444 au8830.o


    9. Renderer

      • ** Edit the following lines in either




        To use the SDLGL renderer reccomended for DRI users (non-nVidia XFree86):

        To use the OpenGL renderer reccomended for nVidia cards:

        To use the Glide renderer used with voodoo cards on XFree86 version 3 only:

        To use the Software renderer (no hardware acceleration required):

        ** Global settings are made in (INSTALL_PATH)/... and local ones in your home directory. When you first run Unreal Tournament it will copy the version of UnrealTournament.ini from (INSTALL_PATH)/... to your home directory and from there on only use the one in your home directory.

      • You can choose the OpenGL library Unreal Tournament tries to use by specifying the path to it in your UnrealTournament.ini:


        (If you are using the OpenGL renderer, you will need to make the change in the [OpenGLDrv.OpenGLRenderDevice] section.)

      • This is a bug in DRI that got fixed recently (07/31/00). You have to use the CVS version of DRI.

      • If you have a 3dfx card please choose the Glide renderer. Otherwise try to use 32 bit renderering which should resolve the issues you are seeing and also will enhance the display quality.

      • Glide doesn't support rendering in a window.

      • Daniel Vogel developed and hosted a replacement OpenGL renderer while he was at Loki. He is now employed by Epic, and his renderer is available from the Unreal Technology site ( UPDATE! For years now the place to go is here

      • Since the Glide renderer was written to glide2, and XFree86 4.x uses glide3, this renderer is not supported under XFree86 4.x.

    10. Administration

      • You can edit ~/.loki/ut/UnrealTournament.ini, and change the section under [UWeb.WebServer] from:
        ImageServer ApplicationPaths[1]=images to:
        T Applications[0]=UTServerAdmin.UTServerAdmin
        ApplicationPaths[0]=/ServerAdmin Applicatio
        n ApplicationPaths[1]=/images

      • One change introduced by the new patch is that the configuration files are now read from and stored in ~/.loki/ut/. This can cause conflicts with servers configured with previous patches.

        To work around this and restore the old behavior, launch Unreal Tournament as follows:

        ut -nohomedir

        This works with UT, starting with 425b.

      • There is an installation help page at which can help you configure ngWorldStats correctly on your machine.

      • Visit for information on how to get the Linux dedicated server package. You nust sign up for the utservers list in order to get access to the current, Loki-maintained package.

    11. Miscellaneous


  • Unreal Tournament - Game of the Year Edition
    SteelSeries Ikari Optical Mouse
    Unreal Tournament 2004

    User login

    Sign in using Facebook