Doom3/opengl problem

[veritas366]

I installed, correctly as far as I can tell, the nvidia drivers to my geforce video card. Tuxracer works, for example, and the nvidia splash screen comes up at boot.

 

I installed the linux doom3 demo to see if it would work and it does not. This isn't that surprising, but the reason it didn't was surprising. The errors are about locating opengl....Here is the actual output:

 

Code:

Running in restricted demo mode.

----- Initializing Decls -----
------------------------------
------- Initializing renderSystem --------
using ARB renderSystem
renderSystem initialized.
--------------------------------------
5151 strings read from strings/english.lang
Couldn't open journal files
couldn't exec editor.cfg
execing default.cfg
couldn't exec DoomConfig.cfg
couldn't exec autoexec.cfg
5151 strings read from strings/english.lang
----- Initializing Sound System ------
sound system initialized.
--------------------------------------
----- R_InitOpenGL -----
Setup X display connection
dlopen(libGL.so.1)
Initializing OpenGL display
Using XFree86-VidModeExtension Version 2.2
DGA DirectVideo Mouse (Version 2.0) initialized
Free86-VidModeExtension Activated at 640x480
Couldn't get a visual
dlopen(libGL.so.1)
Initializing OpenGL display
Using XFree86-VidModeExtension Version 2.2
DGA DirectVideo Mouse (Version 2.0) initialized
Free86-VidModeExtension Activated at 640x480
Couldn't get a visual
idRenderSystem::Shutdown()
Fatal X Error:
Major opcode of failed request: 105
Minor opcode of failed request: 0
Serial number of failed request: 39
BadValue (integer parameter out of range for operation)
Fatal X Error:
Major opcode of failed request: 2
Minor opcode of failed request: 0
Serial number of failed request: 43
BadWindow (invalid Window parameter)
Fatal X Error:
Major opcode of failed request: 4
Minor opcode of failed request: 0
Serial number of failed request: 44
BadWindow (invalid Window parameter)
Sys_Error: Unable to initialize OpenGL

 

I'm trying to sort out if the error is with the driver or with the game. If it is with the game...oh well, but if this indicates I'm having nvidia driver problems still....I'd like to sort it out.

 

I note that when I installed the drivers and did the "modprobe nvidia" command, it returned the driver information, but now modprobe nvidia only gets me another command prompt. (Yes, I entered su - before trying it, otherwise it won't even recognize the command.)

 

Does that indicate that somehow linux (fc3 in my case) can't FIND the module again?

 

Tux racer still works, which was my way of testing if the driver was installed. Tux racer would not play very well at all before the driver was installed.

 

Appreciate any clues!

[anyweb]

does the game run as root, if so the nvidia permissions are likely to be incorrect,

 

check the nvidia howto for fedora core release 3 right here

 

cheers

 

anyweb

[veritas366]

does the game run as root, if so the nvidia permissions are likely to be incorrect, 

 

anyweb

<{POST_SNAPBACK}>

 

A good suggestion, but now, I changed the ownership during the nvidia install. In my experience Tuxracer has been a good benchmark as it does not run well (like 1 fps) when the drivers aren't installed.

 

IN addition, I can't run the game in root mode either.

 

I'd love some other suggestions. I can live without playing Doom 3 but I'd really like to know what's up with opengl.