~ubuntu-branches/ubuntu/hardy/openarena/hardy-backports

This is happening on glibc 2.3 systems such as RedHat 9 and Suze. The text mode installer will crash. If you can do a graphical installation, make sure you have Gtk1 installed and avoid the text installer altogether.

If you are doing a remote installation (such as a dedicated server through ssh), you need to use a newer text mode installer. Run the installer with --keep to extract the files

(look for a setup* directory in the current directory for the extracted setup).

Then replace setup.data/bin/Linux/x86/setup by <a href="http://zerowing.idsoftware.com/linux/setup-RH9/setup">this newer version</a>. Run setup.sh at top level and things should work fine.

Update: Turns out this solution is working for RTCW and ET, but not for Q3 (because the last q3 setup uses an older version of the installer). Will update a specific solution for Q3 'soon'.

<a name="bsd">Installation on

BSD</a><a name="bsd">

</a>

<a name="bsd">The linux binaries will run fine on the BSD family (FreeBSD,

NetBSD and OpenBSD) with the linux binary compatibility software. However

if you are getting the error message ELF binary type "0" not known

while installing or trying to run the binaries, that means you need to run

brandelf on the files.</a>

<a name="bsd">If it's a setup problem, proceed with the following steps:

</a>

<pre><a name="bsd">./linuxq3apoint-1.31.x86.run --keep brandelf -t Linux setup.tmp/setup.data/bin/FreeBSD/x86/setup cd setup.tmp sh ./setup.sh </a></pre>

<a name="bsd">The --keep option will extract the files and leave them

somewhere below your current directory. Depending on the game (Q3 or RTCW)

and the setup version, your mileage may vary (setup.tmp or another directory).</a>

<a name="bsd">The game binaries might need to be brandelf'ed too, with

a command such as</a>

<pre><a name="bsd">brandelf -t Linux /usr/local/games/quake3/quake3.x86 </a></pre>

<a name="bsd"></a><a name="auth">CLIENT_UNKNOWN_TO_AUTH</a>

</a>

<a name="auth">Graeme Devine recently updated his .plan with very

complete </a><a href="http://www.webdog.org/cgi-bin/finger.plm?id=279&time=20011210020942" target="_new">information about CLIENT_UNKNOWN_TO_AUTH errors</a>.

See some additional information from the <a href="http://www.gameadmins.com/modules.php?name=Mail_List">gameadmins.com mailing list</a>:

<pre>If the server you are playing on and the auth server don't see you as the

same IP (for instance you are trying to play on a public internet server

that's on your LAN, and your internet access is using NAT), then it won't

work.

100

It used to work in 1.31, and it doesn't in 1.32. PunkBuster requires

101

reliable auth of the players. What you can do:

102

103

- run a server with sv_strictauth 0 and you'll be able to join your

104

server. This will be the same behaviour as 1.31

105

106

- connect to a server on the internet before you connect to your local

107

server (this will trigger your IP into the cache of the auth server for

108

15mn and let you in to your local server).

109

110

- setup two NATs, one for your client one for your server and make sure

111

your server and Id's auth see the same IP. (this one ain't for network

112

setup newbies)

113

</pre>

114

<a name="pk3">Sys_Error: Couldn't load default.cfg / Sys_Error:

115

FS_FreeFile( NULL )</a>

116

If you get one of these errors after installing Quake III Arena or Return

117

To Castle Wolfenstein, it means that the engine didn't find all the required

118

.pk3 files. Either you didn't copy them, or you copied them to the wrong

119

place. Check the INSTALL instructions for the game for more details, make

120

sure they are in baseq3/ for quake3 (missionpack/ for TA files) and main/

121

for Return To Castle Wolfenstein.

122

<a name="setupbug29h">I get ./setup.sh {: ==: binary

123

operator expected when running the setup?</a><a name="setupbug29h">

124

</a>

125

<a name="setupbug29h">This is a known issue to 1.29h setups and prior.

126

It happens on systems with bash version < 2.*. There are several solutions:

127

- Upgrade bash to something more recent and run the setup again - Run the

128

setup with the --keep option. It will fail but it will leave a setup-full

129

directory. You can then copy the files manually from that dir. - Once you

130

used the --keep option above, you can edit setup.sh and replace occurences

131

of == by =. Then run setup.sh and the installer will execute.</a>

132

<a name="setupbug29h"></a><a name="hints">The game doesn't

133

start, I have performance problems, etc.</a>

134

The first thing to do is to check on the forums and various FAQs (this

135

one, but there are others. See the <a href="#links">links</a>). The Quake3World

136

forums have a great search function.

137

Before reporting the problem to <a href="mailto:ttimo@idsoftware.com">me</a>

138

make sure it's an issue with the game, and not an issue with your OS/OpenGL/sound

139

configuration. Common OS issues are listed in this FAQ. You should make sure

140

you have OpenGL configured correctly (by checking if gearsis running

141

for instance, and how well it runs). And see if non-Id linux games are running

142

fine too.

143

When you are going to report a bug, first make sure you are using the

144

latest version of the game. Include the game version in your report.

145

Include general information about your OS:

146

147

<ul>

148

<li>Motherboard brand, CPU type, RAM</li>

149

<li>distribution name and version</li>

150

<li>kernel / OS info (from uname -a)</li>

151

<li>libc version (ls -l /lib/libc.so.*)

152

please specify if you can if the libc is your distribution's standard

153

version, or if you compiled yourself, and what binary target was used (x86,

154

or AMD, i686 etc.)</li>

155

</ul>

156

If it's a problem with the client, send the output of glxinfo.

157

If you have an nvidia board, send the output of cat /proc/nv/card0

158

159

Send output of the run:

160

run the game with +set developer 1 option, and send the output. You

161

can do something like quake3 +set developer 1 &>q3run.log.

162

If it's a crash, you can send a backtrace of the game running through

163

gdb.

164

You can also send a log of the game running with strace:

165

<pre>cd /usr/local/games/quake3 strace -o ~/strace.log ./quake3.x86 </pre>

166

NOTE: please avoid sending me the strace of /usr/local/games/quake3/quake3,

167

which is a shell script wrapper and probably no interest to your problem.

168

169

<a name="aureal">Aureal sound drivers</a><a name="aureal">

170

</a>

171

<a name="aureal">It seems that some versions of the Aureal sound drivers

172

don't work right with Q3. Last I heard, a kernel upgrade to 2.4.17 + Aureal

173

1.1.3, and/or using the old 1.1.1 drivers from </a><a href="http://aureal.sourceforge.net/" target="_new">Aureal's website</a>fixed

174

the problem.

175

If you need to know more about this, have a look at this <a href="http://www.quake3world.com/ubb/Forum15/HTML/001348.html" target="_new">Q3W forum thread</a>.

176

<a name="nosound">The sound doesn't work / sound crashes</a>

177

The first thing to check is that it is actually a sound related. Run

178

the game with +set s_initsound 0 and see what happens. All problems

179

reported so far about sound turned out to be OS/drivers. Listed below:

180

On some Mandrake distributions:

181

Check if you are running the enlightenment sound daemon (esd). With ps

182

aux | grep esdfor instance. It is a multiplexer for /dev/dsp, and might

183

block use of /dev/dsp by Quake III Arena. You can disable esd with esdctl

184

stop (as root).

185

<a href="http://www.linux-mandrake.com/">Mandrake 8</a>'s default

186

sound drivers seem broken, installing the <a href="http://www.alsa-project.org/" target="_new">Alsa drivers</a> or the

187

<a href="http://www.opensound.com/">http://www.opensound.com</a> drivers

188

fixes the problem.

189

Some beta <a href="http://www.alsa-project.org/" target="_new">Alsa drivers</a>

190

have been reported to crash with Q3. Non-beta ones are fine.

191

VIA chipset and AC97 driver:

192

This combination is known to have various issues. They have been fixed in

193

recent drivers (thanks to Arne Schmitz for the heads up):

194

195

<pre>http://sourceforge.net/projects/gkernel has got the up to date version of the AC97 kernel driver. The current version can be found here: http://prdownloads.sourceforge.net/gkernel/via82cxxx-1.1.15.tar.gz It has working mmap sound, so Q3 shouldn't be a problem any more. </pre>

196

(thanks to Arne Schmitz for the heads up)

197

198

<a name="discuss">Where can I report bugs and discuss about linux Quake III

199

Arena?</a><a name="discuss">

200

</a>

201

<a name="discuss">Reports bugs to </a><a href="mailto:bugs@idsoftware.com">bugs@idsoftware.com</a>. If you are pretty

202

sure this is a linux-only issue, you can shorten the loop by emailing <a href="mailto:ttimo@idsoftware.com">ttimo@idsoftware.com</a> directly.

203

You will find the discussion forums for linux Quake III Arena on <a href="http://www.quake3world.com/cgi-bin/forumdisplay.cgi?action=topics&forum=*nix+Discussion&number=15&DaysPrune=30&LastLogin=">

204

Quake3World forums</a>. There is for sure a lot of other places to talk about

205

linux Quake III Arena, but this is the one we read regularly to track bugs

206

and common issues.

207

<a name="gameso">The *.so files are not in the setups?

208

(cgamei386.so qagamei386.so uii386.so)</a><a name="gameso">

209

</a>

210

<a name="gameso">If you still have baseq3/*.so and missionpack/*.so

211

files, then those come from the earlier 1.27g beta installation and you should

212

REMOVE them. They were provided in 1.27g to go around a bug in the VM code,

213

which made win32 VMs incompatible with linux. This problem has been fixed

214

and the two files are no longer required.</a>

215

<a name="gameso">If you are upgrading from 1.27g, it is likely that your

216

q3config.cfg files are set to use the native libraries (*.so files)

217

instead of the bytecode. Run quake3 with the following options to set things

218

right:

219

quake3 +set vm_game 2 +set vm_cgame 2 +set vm_ui 2</a>

220

<a name="gameso"></a><a name="vm_game">I get Sys_Error:

221

Sys_LoadDll(..) failed dlopen() completely!when running quake3?</a><a name="vm_game">

222

</a>

223

<a name="vm_game">Try running quake3 with the following options:

224

quake3 +set vm_game 2 +set vm_cgame 2 +set vm_ui 2

225

You should also read the </a><a href="#gameso">above answer</a>.

226

<a name="3dnow">I have an AMD CPU and a kernel 2.4.*,

227

Quake III Arena is slowing down to a complete stop after a while?</a>

228

It seems the 3DNow! copy routines have issues with the southbridge chip

229

in the KT133A, this results in performances degrading while playing for a

230

while. Re-compile your kernel without 3DNow! instructions to avoid the problem,

231

and wait for newer kernels with better support for 3DNow! / KT133A.

232

<a name="gamma">How do I set up the gamma correction?</a>

233

Starting with 1.29h, you can set the gamma correction with the brightness

234

slider in the graphical menu (under setup). On some older systems which don't

235

have the appropriate XFree86 extensions, you might have to set r_gamma

236

manually from the console, and issue a vid_restart command.

237

<a name="browser">Servers don't show up in the ingame

238

browser</a>

239

The reason for this has not been clearly identified yet, seems to be related

240

to upgrade from older versions. Deleting ~/.q3a/baseq3/q3config.cfg fixes

241

the problem (you will have to reconfigure your bindings)

242

<a name="libsafe">Detected an attempt to write across

243

stack boundary</a>

244

If Quake III Arena exits with the error "Detected an attempt to write

245

across stack boundary", this probably means that you are running libsafe

246

on this system. Quake III Arena is compiled with some options that confuse

247

libsafe, you should disable it before running. See <a href="http://www.mudos.org/?faq" target="_new">this page</a> for more details.

248

249

<a name="libmesa">libMesaVoodooGL.so</a>

250

The GL driver for Voodoo cards (libMesaVoodoGL.so) used to be distributed

251

in older Q3 setups. This is no longer the case. If you have this .so

252

in your Quake III Arena directory (/usr/local/games/quake3), you should

253

remove it. Any recent/decent linux distribution should support your Voodoo

254

card out of the box, otherwise it is recommended that you setup XFree 4.*

255

and the correct DRI infrastructure for it.

256

<a name="UDPwide">Running a LAN dedicated server with

257

multiple network interfaces</a>

258

A LAN dedicated server will use the net_ip cvar to identify the

259

NIC it is going to use (default is "localhost"). As it only opens one socket,

260

it is not possible to have a server broadcast it's packets on all the NICs.

261

This can be a problem if the server is serving games for a LAN and runs several

262

NICs to access the various sub networks.

263

264

The following Linux kernel patch (2.4.19) was provided by Rogier Mulhujzen

265

and John Tobin, it will force broadcasts to be emitted on all interfaces:

266

<a href="http://zerowing.idsoftware.com/linux/q3a/udp_wide_broadcast.patch">udp_wide_broadcast.patch</a>

267

<a href="http://zerowing.idsoftware.com/linux/q3a/udp_wide_README.txt">udp_wide_README.txt</a>

268

The equivalent <a href="http://www.bsdchicks.com/patches/">patch for FreeBSD</a>

269

is available too.

270

271

<a name="64bits">Setup and execution on 64 bits CPUs</a>

272

If you are running Linux on a 64 bit CPU (such as AMD's Opteron), and if your system is backwards compatible so that it can execute 32 bits x86 binaries, then the regular Quake III Arena binaries should work (your mileage may vary).

273

It's likely that the installer scripts will get confused though, and will refuse to install giving you an error: "This installation doesn't support glibc-2.1 on Linux / unknown". You will have to extract the game files manually by passing --keep on the command line when running the setup script. Once the files are unpacked, you will need to copy them manually to /usr/local/games. You probably want to have a working installation to refer to while doing this. This also applies to RTCW and ET

274

<a name="links">Links</a>

275

The <a href="http://www.icculus.org/lgfaq" target="_new">Linux Gamer's

276

faq</a> is a very good resource for general Linux Gaming topics.

277

Also at <a href="http://www.icculus.org/" target="_new">icculus.org</a>,

278

the <a href="http://www.icculus.org/lgfaq/loki/q3faq.html" target="_new">old

279

Q3 FAQ from Loki Software</a>.

280

<a href="http://www.quake3world.com/ubb/Forum15/HTML/000529.html">Quake3World's

281

linux FAQ</a>

282

283

</body></html>

Older »