Trying to run Q3A...

[augy]

when I try to run Q3A, I get this message printed out:

...loading libGL.so.1: Initializing OpenGL display
...setting mode 3: 640 480
Using XFree86-VidModeExtension Version 2.1
Xlib: extension "XFree86-DGA" missing on display ":0.0".
Failed to detect XF86DGA Mouse
XFree86-VidModeExtension Activated at 640x480
Using 8/8/8 Color bits, 16 depth, 0 stencil display.
Received signal 11, exiting...

It's the failure to detect the mouse that's bugging the **** out of me. The mouse works fine. I've tried killing gpm, and the mouse still won't detect. What could be wrong?

Slackware 8.1
1.8 P4
G4 Ti4600 nv
latest binarys from ftp.idsoftware.com (32b)

Where is it looking for the Xf86DGA mouse? I can't find the string anywhere in XF86Config, nor in libvga.config. C'mon guys, if I can get quake 3 working in linux then I can uninstall windows and fulfill my new year's resolution =]


Thanks a bunch,


augy.

[root.veg]

Wouldn't you have to change your Quake3 config file so it does / doesn't use the DGA mouse handling (to your preference)? I have no idea what will work for you, but shouldn't editing

/home/yourname/.q3a/baseq3/q3config.cfg

do the trick? I would check my own file and post it, but I'm not near my own computer.

[bwkaz]

In your XF86Config, you should have a line in the Modules section that says SubSection "extmod".

Right now, you either don't have extmod listed at all, or you have an Omit "XFree86-DGA" in that SubSection. Get RID of that Omit line (or add the SubSection if you don't have it) to get DGA support.

[augy]

Thanks bwkaz, that worked for me.

But I still can't get the game started. The mouse initializes fine now, but Q3 still quits out w/ signal 11 at the same spot.

Thoughts?


augy.

[bwkaz]

Do you have the nVidia drivers installed?

You might be able to run the game under gdb, as well. Go into wherever the executable is and gdb ./quake3 (or whatever). Type run to start it, and do whatever it takes to get the sig 11. At that point, the game will freeze (you will want to run it windowed if you can, because otherwise this freeze will take over your display), and gdb will give you a prompt back. Type in bt and hit return to get a stack backtrace, to see which function the segfault is happening in.

Not having the source for Q3 or the nVidia drivers is going to make it difficult to diagnose, but there's a chance.

[augy]

"no debugging symbols found."

crud.
Is there a resource out there which matches exit values with errors?
And yes, I do have the latest nVidia drivers installed.

thanks for your time,


augy

[bwkaz]

What do you mean by "exit values"?

Signal 11 is SIGSEGV, which means the program (or a library function it called) tried to access memory that it didn't have permission to. The different signals are listed by kill -l, but their meaning is not; for that, see man 7 signal.

You could also try searching Google (not G4L) for "quake 3 segfault" or something similar, to see if there are any known issues.

[quietguy47]

have you downloaded the latest update(1.32) from idsoftware?