I'm not sure I am on the correct forum, but I'll start here. I'm very new on the forum, so please take it a little easy on me.

I have an ASUS G73SW-BST6. It came with an Intel Core I7-2630QM, 8 GB memory and a GEForce GTX 460M/1 GB dedicated graphics. The machine has been set up to run Redhat 6.0 Linux. We installed the Nvidia driver 270.41.19. I downloaded the cudatoolkit_4.0.17_linux_64_rhel6.0.run. I also installed freeglut. When I try to run fluidsGL in the SDK (or any other GL application) I get the following error:
"freeglut (./fluidsGL): ERROR: Internal error <FBConfig with necessary capabilities not found> in function fgOpenWindow. X Error of failed request: BadWindow (invalid window parameter) major opcode of failed request: 4 (X_DestroyWindow) Resource id in failed request :0x0 Serial number of failed request; 24 Current serial number in output stream: 27"

However, note that the freeglut demos work...it's only the ones that also use CUDA (or is that nvcc?) that are failing.

I have searched on line and found a few posts on Nvidia's CUDA on Linux forum (but I posted here, because I read somewhere here that laptop problems should be addressed to this forum). I found a few posts ("Error freeglut" on 4/4/11, "Problems with Cuda 3.0,devdriver195.36.5 on Ubuntu 10.04" on 6/14/10 and "CUDA SDK GLX dependent examples will not run (Help)" on 5/13/10. I'm not seeing any responses that are helping me. There is mention that if Mesa is in the first line of the /usr/include/GL/gl.h file that the driver needs to be reinstalled. I have a desktop machine that is running the same o/s and one version older of the nvidia driver and freeglut and that file says Mesa and everything runs fine.

What am I doing wrong? If I need to post to a different forum please let me know. Can a person post the same question to more than one forum? (I told you I was green.)

I'm not sure I am on the correct forum, but I'll start here. I'm very new on the forum, so please take it a little easy on me.

I have an ASUS G73SW-BST6. It came with an Intel Core I7-2630QM, 8 GB memory and a GEForce GTX 460M/1 GB dedicated graphics. The machine has been set up to run Redhat 6.0 Linux. We installed the Nvidia driver 270.41.19. I downloaded the cudatoolkit_4.0.17_linux_64_rhel6.0.run. I also installed freeglut. When I try to run fluidsGL in the SDK (or any other GL application) I get the following error:

However, note that the freeglut demos work...it's only the ones that also use CUDA (or is that nvcc?) that are failing.

I have searched on line and found a few posts on Nvidia's CUDA on Linux forum (but I posted here, because I read somewhere here that laptop problems should be addressed to this forum). I found a few posts ("Error freeglut" on 4/4/11, "Problems with Cuda 3.0,devdriver195.36.5 on Ubuntu 10.04" on 6/14/10 and "CUDA SDK GLX dependent examples will not run (Help)" on 5/13/10. I'm not seeing any responses that are helping me. There is mention that if Mesa is in the first line of the /usr/include/GL/gl.h file that the driver needs to be reinstalled. I have a desktop machine that is running the same o/s and one version older of the nvidia driver and freeglut and that file says Mesa and everything runs fine.

What am I doing wrong? If I need to post to a different forum please let me know. Can a person post the same question to more than one forum? (I told you I was green.)

I have an equal problem with Fedora 14 on my Notebook which is a Customized Quad core (Hyperthreaded) with 4 Gb Ram and GeForce GT 330M!
I think the problem you have is not depending on cuda!
The error says nothing else than opengl can't create a window/subwindow! (fgOpenWindow is called by the glutCreateWindow(String) function.

glxinfo tells me that my server glx vendor is set to NVIDIA but the client glx is Mesa.

I found that updating to the latest NVIDIA driver (280.13 ? sorry but the machine isn't here with me so I can't be sure of the driver version) from the NVIDIA site, took care of this problem...although it appears to have introduced others...but that's a different question.

I found that updating to the latest NVIDIA driver (280.13 ? sorry but the machine isn't here with me so I can't be sure of the driver version) from the NVIDIA site, took care of this problem...although it appears to have introduced others...but that's a different question.

I know this is an ancient thread but in case this info is useful to anyone, I wanted to note that I can across this same error on Linux without nVidia hardware and this line was the problem:
glutInitDisplayMode (GLUT_SINGLE | GLUT_INDEX);
GLUT_INDEX was not supported. Changing it to use GLUT_RGB made things happy.

I know this is an ancient thread but in case this info is useful to anyone, I wanted to note that I can across this same error on Linux without nVidia hardware and this line was the problem:
glutInitDisplayMode (GLUT_SINGLE | GLUT_INDEX);
GLUT_INDEX was not supported. Changing it to use GLUT_RGB made things happy.