Here I'm going crazy!
I don't understand why the original 1.2 version is working properly, and when I try to start the game after updating it fails with this:
Code:
--------------- R_InitOpenGL ----------------
Initializing SDL subsystem
Loading GL driver 'libGL.so.1' through SDL
SDL_ListModes:
1280x1024 1152x864 1024x768 832x624 800x600 640x480
SDL_ListModes are currently ignored for resolution filtering. Set r_useSDLModes to 1 if you want it
WARNING: SDL_SetVideoMode failed: Couldn't find matching GLX visual
Initializing SDL subsystem
Loading GL driver 'libGL.so.1' through SDL
SDL_ListModes:
1280x1024 1152x864 1024x768 832x624 800x600 640x480
SDL_ListModes are currently ignored for resolution filtering. Set r_useSDLModes to 1 if you want it
WARNING: SDL_SetVideoMode failed: Couldn't find matching GLX visual
--------------- BSE Shutdown ----------------
---------------------------------------------
WARNING: rvServerScanGUI::Clear() - invalid scanGUI
idRenderSystem::Shutdown()
Sys_Error: Unable to initialize OpenGL
I filtered the textures loadind process from the log and you see the last messages, revelant to the OpenGL part. Where it fails.
Also, I tried to link the libSDL-1.2.so.0 to the one present in the 1.3 quake 4 update package. But nothings change.
This is my config:
uname -r : 2.6.15-23-386
glxinfo:
direct rendering: Yes
server glx vendor string: NVIDIA Corporation
server glx version string: 1.4
lspci:
VGA compatible controller: nVidia Corporation NV43 [GeForce 6600/GeForce 6600 GT] (rev a2)
ls /usr/lib/libGL.so.1 -al :
/usr/lib/libGL.so.1 -> libGL.so.1.0.8762
of course the library is present.
ls /usr/lib/libGL.so.1.0.8762 -al :
-rw-r--r-- 1 root root 540136 2006-05-29 14:51 /usr/lib/libGL.so.1.0.8762
I'm lost and I really don't know why it fails. Everywhere you will find on the web that the GLX error is caused by the ColorDepth. You must have 24 bits to get the game running.
Of course I have checked this.
cat /etc/X11/xorg.conf | grep Depth :
DefaultDepth 24
And as I must remind you, quake 1.2 works just fine. So I hope it's not Id software related... I must say I'm the only one facing this yet.