Unable to initialize OpenGL (yes, I read readme)
by Andy · in General Game Discussion · 04/23/2003 (7:44 am) · 13 replies
Yes, I read the readme.txt file.
Here's the message that I see when loading Orbz 2 demo for Linux;
Unable to initialize OpenGL. (Error: Could not load OpenGL library)
appears with a single OK button to exit. Even when adding the -v option for verbose messages (valid in this app?), no additional messages appear.
Details: All other OpenGL programs run at full speed (glxgears reports 827~ FPS). Nvidia drivers: version 4349.
Red Hat 9.0 default kernel. Using nosysinfo at boot time to disable native posix threading.
I'm posting this here FYI as I don't intend to come back to this forum and didn't see any other way to report this.
Suggestions: Ditch the whole login scheme; it is REALLY ANNOYING. I almost didn't report anything here just because of the number of hoops required to jump through. The additional "Markup Lite" is also strange and yet another distraction (though I've seen it used elsewhere); just take HTML and strip out anything that looks suspicious.
Here's the message that I see when loading Orbz 2 demo for Linux;
Unable to initialize OpenGL. (Error: Could not load OpenGL library)
appears with a single OK button to exit. Even when adding the -v option for verbose messages (valid in this app?), no additional messages appear.
Details: All other OpenGL programs run at full speed (glxgears reports 827~ FPS). Nvidia drivers: version 4349.
Red Hat 9.0 default kernel. Using nosysinfo at boot time to disable native posix threading.
I'm posting this here FYI as I don't intend to come back to this forum and didn't see any other way to report this.
Suggestions: Ditch the whole login scheme; it is REALLY ANNOYING. I almost didn't report anything here just because of the number of hoops required to jump through. The additional "Markup Lite" is also strange and yet another distraction (though I've seen it used elsewhere); just take HTML and strip out anything that looks suspicious.
#2
Yes;
# ls -lart /usr/lib/libGL.so.1 /usr/lib/libGL.so
lrwxrwxrwx 1 root root 17 Apr 22 14:59 /usr/lib/libGL.so.1 -> libGL.so.1.0.4349
lrwxrwxrwx 1 root root 10 Apr 22 14:59 /usr/lib/libGL.so -> libGL.so.1
# ls -lart /usr/lib/libGL.so.1.0.4349 /usr/lib/libGL.so.1
-rwxr-xr-x 1 root root 413812 Apr 22 14:59 /usr/lib/libGL.so.1.0.4349
lrwxrwxrwx 1 root root 17 Apr 22 14:59 /usr/lib/libGL.so.1 -> libGL.so.1.0.4349
04/23/2003 (9:42 am)
"Do you have a libGL.so or libGL.so.1 symlink in /usr/lib ? If not, try linking one of those to your libGL library, then run ldconfig -v as root, then try again."Yes;
# ls -lart /usr/lib/libGL.so.1 /usr/lib/libGL.so
lrwxrwxrwx 1 root root 17 Apr 22 14:59 /usr/lib/libGL.so.1 -> libGL.so.1.0.4349
lrwxrwxrwx 1 root root 10 Apr 22 14:59 /usr/lib/libGL.so -> libGL.so.1
# ls -lart /usr/lib/libGL.so.1.0.4349 /usr/lib/libGL.so.1
-rwxr-xr-x 1 root root 413812 Apr 22 14:59 /usr/lib/libGL.so.1.0.4349
lrwxrwxrwx 1 root root 17 Apr 22 14:59 /usr/lib/libGL.so.1 -> libGL.so.1.0.4349
#3
Hmmm, that seems fishy to me. glxgears usually runs in the thousands for me, like 3k, other GL games run though?
04/23/2003 (11:05 am)
Quote:All other OpenGL programs run at full speed (glxgears reports 827~ FPS)
Hmmm, that seems fishy to me. glxgears usually runs in the thousands for me, like 3k, other GL games run though?
#4
I have no complaints, though keep in mind that I'm not commenting on speed only that the game won't start because it (?) doesn't see the OpenGL that's there. (Just checked some of the ReallySlickScreensavers (( /usr/X11R6/bin/lattice -root --computer )) just to be certian...yep, looks like hardware rendering to me.
As for getting thousands of FPS from glxgears, it might be a difference in our vsync settings. With Neverwinter Nights (beta 2) I get no flicker and all options except one water feature are enabled (1024x768).
The card and config is entirely untweaked, and is reported as a "GeForce2 MX/MX 400" (/proc/driver/nvidia/cards/0) with 64MB RAM.
04/23/2003 (12:28 pm)
"Hmmm, that seems fishy to me. glxgears usually runs in the thousands for me, like 3k, other GL games run though?"I have no complaints, though keep in mind that I'm not commenting on speed only that the game won't start because it (?) doesn't see the OpenGL that's there. (Just checked some of the ReallySlickScreensavers (( /usr/X11R6/bin/lattice -root --computer )) just to be certian...yep, looks like hardware rendering to me.
As for getting thousands of FPS from glxgears, it might be a difference in our vsync settings. With Neverwinter Nights (beta 2) I get no flicker and all options except one water feature are enabled (1024x768).
The card and config is entirely untweaked, and is reported as a "GeForce2 MX/MX 400" (/proc/driver/nvidia/cards/0) with 64MB RAM.
#5
Damn Linux bugs...I'm sorry you are having problems, hopefully we can troubleshoot this for you and get it working. If not, talk to Justin/Jeff about a refund.
04/24/2003 (5:48 am)
God that's wierd. Quigman, any ideas? Just for the sake of argument, could you download the Marble Blast demo and see if that runs? If it does, then we can narrow the problem to the Orbz build, if it doesn't than it may be a Torque problem in general. Damn Linux bugs...I'm sorry you are having problems, hopefully we can troubleshoot this for you and get it working. If not, talk to Justin/Jeff about a refund.
#6
strace ./orbz 2> out.txt
Then when you are done, gzip the out.txt and send it to me:
john@lowestplane.org
This will let me determine what errors it is getting when it tries to load your libGL library.
04/24/2003 (8:04 am)
Try running orbz under strace:strace ./orbz 2> out.txt
Then when you are done, gzip the out.txt and send it to me:
john@lowestplane.org
This will let me determine what errors it is getting when it tries to load your libGL library.
#7
Done and emailed. I'll be traveling from now till Monday, though I'll be glad to run other tests when I get back, just let me know.
04/24/2003 (2:15 pm)
"Try running orbz under strace: ..."Done and emailed. I'll be traveling from now till Monday, though I'll be glad to run other tests when I get back, just let me know.
#8
04/26/2003 (3:22 pm)
Ok, Andy mentioned to me in an email that he was using RH9 with the "nosysinfo" option so that native posix thread support is turned off. I just installed RH9 on my box. In the default install, the game works. When I add "nosysinfo" and reboot, I get "Could not load OpenGL library" when I try to start. So it looks like nosysinfo causes the problem.
#9
04/26/2003 (3:43 pm)
Why would that fail to load OGL? Maybe SDL requires that?
#10
04/26/2003 (3:49 pm)
Not sure. It may have to do with the way SDL is compiled (e.g: which thread system it uses). It may help to rename the SDL library distributed with the game in the "lib" folder so that it isn't used. In that case the system library (if installed) will be loaded instead. I'm not in RH9 anymore right now though so I can't test it.
#11
Grrr...that's a first. I put nosysinfo on the kernel line at boot because with native Posix threading enabled other things would break or be unstable. Dammed if you do...
For sure, nosysinfo is a sloppy short-term work around. I didn't expect it to cause any problems beyond slowing the system down in relation to having them on. Since custom and previous kernels don't have native Posix threads, I didn't expect anything to break. If SDL or other libs take advantage of the new threads, it could be a reason. It's something to look out for when a custom kernel on Red Hat 9.0 -- something I was planning to start doing soon.
I'll look at a work around here and post it FYI. For now, I guess the best thing to do is to *not* use nosysinfo at all, allow the broken programs to be found, and use the LD_ASSUME_KERNEL= options (as described in Red Hat's release notes) sparingly.
Along those lines...damn, didn't work. Even while nosysinfo is enabled, neither
LD_ASSUME_KERNEL=2.4.1 ./orbzdemo
LD_ASSUME_KERNEL=2.2.5 ./orbzdemo
work around the problem. It (SDL?) still can't find OpenGL libs. NWN (with no options, nosysinfo or not) still works fine.
I'll have to disable it and reboot to see what happens here.
04/27/2003 (1:44 pm)
"So it looks like nosysinfo causes the problem."Grrr...that's a first. I put nosysinfo on the kernel line at boot because with native Posix threading enabled other things would break or be unstable. Dammed if you do...
For sure, nosysinfo is a sloppy short-term work around. I didn't expect it to cause any problems beyond slowing the system down in relation to having them on. Since custom and previous kernels don't have native Posix threads, I didn't expect anything to break. If SDL or other libs take advantage of the new threads, it could be a reason. It's something to look out for when a custom kernel on Red Hat 9.0 -- something I was planning to start doing soon.
I'll look at a work around here and post it FYI. For now, I guess the best thing to do is to *not* use nosysinfo at all, allow the broken programs to be found, and use the LD_ASSUME_KERNEL= options (as described in Red Hat's release notes) sparingly.
Along those lines...damn, didn't work. Even while nosysinfo is enabled, neither
LD_ASSUME_KERNEL=2.4.1 ./orbzdemo
LD_ASSUME_KERNEL=2.2.5 ./orbzdemo
work around the problem. It (SDL?) still can't find OpenGL libs. NWN (with no options, nosysinfo or not) still works fine.
I'll have to disable it and reboot to see what happens here.
#12
04/27/2003 (2:49 pm)
The difference between nwn and games like orbz, is that nwn is hard-dynamic linked against libGL, while orbz loads it dynamically via SDL. You can see this in the output of ldd on the binary. libGL won't be listed as a dependency on orbz.bin.
Torque Owner John Quigley