I have a Tesla C870 board installed on a Linux RHEL 4.5 64-bit system Intel system.
I’ve installed the latest CUDA 1.1 driver, Toolkit and SDK.
When I run non-graphics SDK samples like deviceQuery, matrixMul, bandwidthTest etc., they work fine however when I run some OpenGL samples like fluidGL or particles there is an error “GLX extension is not supported by the display :0.0”
I have an on-board Intel 945 chipset and the monitor is connected to this onboard videoout.
Also after installing the driver, when i configure the X settings using the nvidia-xconfig and try to run startX, the X windows do not start and I get a Fatal error. ‘XIO Fatal IO error 104 (connection reset by peer) on X Server:0.0’
The X however runs fine with the default Intel 945 chipset.
I have attached a couple of logs, in case it helps.
Let me know if some one has come across a similar problem and has found a solution to this.
(II) LoadModule: “glx”
(II) Loading /usr/X11R6/lib64/modules/extensions/libglx.so
(II) Module glx: vendor=“NVIDIA Corporation” <------------------------------
compiled for 4.0.2, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 0.1
(II) NVIDIA GLX Module 169.09 Fri Jan 11 14:46:52 PST 2008
(II) Loading extension GLX
and it results in an error later on:
(EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not found)
Try to get the integrated graphic adapter to work with glxgears. Once you got it to work, install the NVIDIA driver but skip the Xconfig and do the entries in /dev plus load the nvidia kernel module.
If you want to run the SDK samples on the Tesla C870 GPUs then you’ll need to configure X to run on the C870 in addition to configuring X to use the integrated Intel GPU. Once you have X working on the Intel integrated GPU, for the C870, you should run the following as root:
nvidia-xconfig --virtual=800x600 --use-display-device=none
and then restart X.
At this point you will still need to set the DISPLAY environment variable to point to the X screen that is running (headless) on the the C870 if you wish to run fluidGL (or any other sample which requires X). You can do so as follows:
At this point you should be able to run fluidGL on the C870, however if you wish to see the rendering, you would need to take a screenshot of the X screen running on the C870. This can be accomplished with the ‘import’ utility which ships with the ImageMagick package(which ships with RHEL-4.5):
import -window root screenshot.jpg
Please note that you will not be able to run any of the samples on the Intel X screen as the NVIDIA display driver overwrites the GLX (Mesa) X module that the Intel X driver requires with a new one that the nvidia X driver requires.
If you have further questions please generate and attach an nvidia-bug-report.log (as root by running nvidia-bug-report.sh).
Ok I was able to run glxgears with the Nvidia driver and other software in place. Engineers from Nvidia (pune) helped to ensure that the correct lib64 files are used while running glxgears.
However the fluidsGL and similar applications were still not running and I was getting the following error : “ERROR: Support for necessary OpenGL extensions missing.”
The engineers asked me to get the latest Mesa, which I did and installed the latest Mesa7.0.2 Demos, GLUT and Lib. The latest Mesa demos like gears, gloss, teapot work fine. However when I try to invoke fluidsGL etc samples I get the same error as above.
One observation while running an applications called fslight from Mesa, I got the following message
This program requires OpenGL 2.x, found 1.3 Mesa 6.2.1
Also I had copied the files from Lib64 directory of Mesa to the /usr/X11R6/lib64.
(the lib64.txt has the list of files I copied)
Also I checked (ldd fluidsGL, lddsimpleTexture etc) if the same files were being looked at. I’ve attached the logs fyi.
What additional OpenGL files are required to run these samples ?
The OpenGL headers that ship with Mesa are mutually exclusive of the OpenGL headers that ship with the NVIDIA X driver. You cannot use them both, and installing/updating Mesa after installing the NVIDIA X driver will result in all OpenGL support from the nvidia X driver being removed.
Thus, its entirely expected that glxgears would run (falling back to the software Mesa OpenGL) and any apps which require hardware acceleration via the nvidia driver to fail.