|
Xlib: extension "GLX" missing on display ":0.0".
Ok. First off a little intro to the problem. I'm running on two machines, one of which is running Fedora Core, and the other runs RedHat 9.0. I am working on a software project that involves using Java3D, which I believe links right into OpenGL. I do not have any root access, as these are machines at work.
With the Fedora machine I am having no problem running the portions of the code that include Java3D. Everything is moving swimmingly. However, with the RedHat machine I am having troubles. Whenever the code attempts to make a call that would perform rendering involving Java3D, (e.g. constructing a Canvas3D object) I get this: Xlib: extension "GLX" missing on display ":0.0". Xlib: extension "GLX" missing on display ":0.0". Xlib: extension "GLX" missing on display ":0.0". Xlib: extension "GLX" missing on display ":0.0". Xlib: extension "GLX" missing on display ":0.0". Xlib: extension "GLX" missing on display ":0.0". ************************************************************************ *** ERROR: Canvas3D constructed with a null GraphicsConfiguration *** This will cause a NullPointerException in a subsequent release ************************************************************************ Xlib: extension "GLX" missing on display ":0.0". Xlib: extension "GLX" missing on display ":0.0". Xlib: extension "GLX" missing on display ":0.0". Xlib: extension "GLX" missing on display ":0.0". Xlib: extension "GLX" missing on display ":0.0". Xlib: extension "GLX" missing on display ":0.0". I did some searching around on these boards, and found a couple of helpful bits. Quote:
direct rendering: Yes Load "glx" Now, on the RedHat machine, the grep for glx in the Config file is the same. "Load 'glx'" is not commented out. However, this is what I got when I typed in "glxinfo | grep rendering": Xlib: extension "GLX" missing on display ":0.0". Xlib: extension "GLX" missing on display ":0.0". Xlib: extension "GLX" missing on display ":0.0". Error: couldn't find RGB GLX visual Xlib: extension "GLX" missing on display ":0.0". Xlib: extension "GLX" missing on display ":0.0". Xlib: extension "GLX" missing on display ":0.0". Xlib: extension "GLX" missing on display ":0.0". Most of the fixes I saw on these posts were along the lines of "uncomment the load glx line", but seeing as how that line is uncommented, I'm kind of at a loss. I am new to Linux, and I do not have root access, so I don't know what other system information to provide right now. Any ideas for fixes? I would be extremely grateful for any assistance. Thanks! -Joe |
I had this sort of problem recently. I had an nVidia card in my machine but I needed to swap it out for a non-nVidia card because it didn't support interlaced modes.
After the swap, I got that Xlib: extension "GLX" missing error whenever trying to run an OpenGL program. Everything else seemed to work normally, but OpenGL wouldn't work at all. I dug around at nVidia's web site and one of the first things I noticed was that my version of nVidia's driver had an UNinstall feature. I ran the uninstall command, and OpenGL started working again! It was only software emulation at that point, but that was a different issue. Anyway, maybe that workstation used to have an nVidia card but it got swapped out for some reason. Possibly there was no uninstall feature in that old nVidia driver, and it's not obvious how to clean things up. |
I think you may be right. I tooled around through the directories, and found two XF86Config files: XF86Config and XF86Config.backup. The backup file has the following under device:
Section "Device" Identifier "Videocard0" Driver "nvidia" VendorName "Videocard vendor" BoardName "NVIDIA Quadro 4 (generic)" EndSection whereas XF86Config has this: Section "Device" Identifier "Videocard0" Driver "nv" VendorName "Videocard vendor" BoardName "NVIDIA Quadro 4 (generic)" EndSection Something happened such that they changed settings on their NVidia driver, changed names, changed driver types, something to that effect. But it seems to have effectively hammered the OpenGL capabilities of the machine. Now, unfortunately since it's Friday and loads o people are taking a long weekend, there are few (if any) here that can get me on another RedHat machine, just for the sake of testing, but it's good to know that it's not specifically a RedHat vs. Fedora thing. Thanks for the help! -Joe |
Okay, "nvidia" is the name of nVidia's official (non-Free) driver. "nv" is the name of the open source nVidia driver.
It looks like someone tried to install the official driver, but it messed things up so he went back to the open source driver. My recommendation is to get the sysadmin to try downloading/installing the latest official nVidia driver. I'm guessing that there's some sysadmin in charge since you say you don't have root access. Right? |
That is indeed the case. And now to talk to our admin guy to fix things up. Thank you muchly for the help.
-Joe |
wow
IsaacKuo, you're right removing the nvidia drivers did the trick. I would have never thought of that
|
| All times are GMT -5. The time now is 03:07 AM. |