Next
Previous
Contents
A new site with community forums is
LinuxQuake.Org.
Other trouble-shooting resources can be found at:
Jörgen's GLQuake Site,
the
old version of this how-to, and
Linux Gamers FAQ.
Often, using an alternative game engine such as
TyrQuake,
EzQuake and
Darkplaces will fix mouse and sound related problems.
"bash: ./glquake.glx: Permission denied"
- The binary may not have the executable bit set.
Type chmod +x glquake.glx to fix this.
- If the program is located on a windows partition, it is possible it has
been mounted with the noexec option.
Type (as root): mount -o remount,exec /mnt/windows
"bash: glquake.glx: command not found"
- Bash may not be including the current directory in it's path. Type:
"export PATH=$PATH:."
This is not good, but some simple options to try are:
- - use -nosound to test if sound is the problem.
Sound problems are covered in detail below.
- - use -noudp if network is unconfigured.
- - use -nocdaudio if cdrom is absent.
- - use -height, -width and
-fullscreen command line options to select a screen
mode you know is properly configured.
e.g. glquake.glx -width 800 -height 600 -fullscreen -nosound
Files not lowercased or Data files missing.
Linux Quake requires (most) filenames to be in lowercase. If you get an error
similar to "Error: W_LoadWadFile: couldn't load gfx.wad" it means the game
can't find the data files, possibly because they are not all lowercase.
Missing libraries: "error while loading shared libraries: libGL.so.1: cannot open shared object file"
A message similar to this means the program cannot run because it can't find a system file it needs.
Perhaps:
- File is not installed - Just check with your package manager and install the correct package.
- Links aren't properly set-up. If you have (say) /usr/lib/libGL.so.1.2, but get the above message, you should be able to remedy this with ln -s /usr/lib/libGL.so.1.2 /usr/lib/libGL.so.1
Dynamic libraries (or DLLs as they are known to Windows users) can be quite
complex. For more information try the ldd and ldconfig man
pages.
"Memory overwrite in Sys_Printf"
- This error means you need to edit file sys_linux.c,
procedure Sys_Printf, and change text[1024] to
text[4096] and recompile.
Many versions of Quake have what appear to be two versions of this
procedure, but one is always commented out. Obviously you'll need to change
the value in the correct procedure.
Problems with GCC 4
- If you're experiencing core dumps and are using version 4.x of the GNU
compiler, see
Compilation Issues below.
- Many mods require extra memory. Use the -mem 64 option
to allocate 64 meg of memory for the heap.
- In some cases, this problem can be sound related. Try some of the tips
in the sound section.
- A few newer mods just won't work with standard GLQuake, and need an
enhanced
game engine.
Darkplaces has the best large map support under Linux, but some
are even too big for it, and are unsupported under Linux.
For more information see the
drivers section.
An error such as: "/dev/dsp: Device or resource busy" indicates some program is
already using your sound card, and you will have to halt this program to get
Quake sound effects.
- From the Linux command line, type killall artsd
or killall esd to terminate either of these popular sound daemons.
- Alternatively, to run Quake through the KDE sound daemon, type
artsdsp glquake.glx ...
"Quake engine games exit, and I see an error about mmap!"
- The
Linux Gamers FAQ
recommends "Your sound card/driver doesn't support this needed feature.
However, if you use KDE/arts you may be able to bypass this with the -m switch
to the artsdsp wrapper".
Make sure the artsd program is running
by typing ps -A | grep artsd and checking that this command returns
at least one non-empty line. Then type artsdsp -m glquake.glx.
- Try alternative sound drivers as outlined in the
Sound Drivers section.
Sound stutters or is not very good.