FBConfig error
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.)

Any help I can get would be GREATLY appreciated.
Thanks in advance.
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.)



Any help I can get would be GREATLY appreciated.

Thanks in advance.

#1
Posted 08/15/2011 10:10 PM   
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.

[code]server glx vendor string: NVIDIA Corporation
server glx version string: 1.4
server glx extensions:
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_SGIX_fbconfig,
GLX_SGIX_pbuffer, GLX_SGI_video_sync, GLX_SGI_swap_control,
GLX_EXT_swap_control, GLX_EXT_texture_from_pixmap, GLX_ARB_create_context,
GLX_ARB_create_context_profile, GLX_EXT_create_context_es2_profile,
GLX_ARB_create_context_robustness, GLX_ARB_multisample,
GLX_NV_float_buffer, GLX_ARB_fbconfig_float, GLX_EXT_framebuffer_sRGB
client glx vendor string: Mesa Project and SGI
client glx version string: 1.4
client glx extensions:
GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context,
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_copy_sub_buffer,
GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control,
GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync,
GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer,
GLX_SGIX_visual_select_group, GLX_EXT_texture_from_pixmap,
GLX_INTEL_swap_event

[/code]

So i think the problem depends more on a driver conflict between mesa and the nvidia driver.
Maybe thats your problem too and maybe you've found a solution?

cheers Vasilie
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.



server glx vendor string: NVIDIA Corporation

server glx version string: 1.4

server glx extensions:

GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_SGIX_fbconfig,

GLX_SGIX_pbuffer, GLX_SGI_video_sync, GLX_SGI_swap_control,

GLX_EXT_swap_control, GLX_EXT_texture_from_pixmap, GLX_ARB_create_context,

GLX_ARB_create_context_profile, GLX_EXT_create_context_es2_profile,

GLX_ARB_create_context_robustness, GLX_ARB_multisample,

GLX_NV_float_buffer, GLX_ARB_fbconfig_float, GLX_EXT_framebuffer_sRGB

client glx vendor string: Mesa Project and SGI

client glx version string: 1.4

client glx extensions:

GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context,

GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_copy_sub_buffer,

GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control,

GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync,

GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer,

GLX_SGIX_visual_select_group, GLX_EXT_texture_from_pixmap,

GLX_INTEL_swap_event






So i think the problem depends more on a driver conflict between mesa and the nvidia driver.

Maybe thats your problem too and maybe you've found a solution?



cheers Vasilie

#2
Posted 08/29/2011 03:13 PM   
So, finally i solved the problem.
The actual Nvidia driver package in the fedora repository wasn't the correct one for my graphics adapter.
So I've downloaded the latest drivers for my graphics card from Nvidia's site, removed the complete NVidia driver section ( inclusive all Mesa stuff ) and installed the downloaded one.

After this odyssey glxinfo show me the correct configuration:

[code]name of display: :0.0
display: :0 screen: 0
direct rendering: Yes
server glx vendor string: NVIDIA Corporation
server glx version string: 1.4
server glx extensions:
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_SGIX_fbconfig,
GLX_SGIX_pbuffer, GLX_SGI_video_sync, GLX_SGI_swap_control,
GLX_EXT_swap_control, GLX_EXT_texture_from_pixmap, GLX_ARB_create_context,
GLX_ARB_create_context_profile, GLX_EXT_create_context_es2_profile,
GLX_ARB_create_context_robustness, GLX_ARB_multisample,
GLX_NV_float_buffer, GLX_ARB_fbconfig_float, GLX_EXT_framebuffer_sRGB
client glx vendor string: NVIDIA Corporation
client glx version string: 1.4
client glx extensions:
GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_visual_info,
GLX_EXT_visual_rating, GLX_EXT_import_context, GLX_SGI_video_sync,
GLX_NV_swap_group, GLX_NV_video_out, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer,
GLX_SGI_swap_control, GLX_EXT_swap_control, GLX_ARB_create_context,
GLX_ARB_create_context_profile, GLX_NV_float_buffer,
GLX_ARB_fbconfig_float, GLX_EXT_fbconfig_packed_float,
GLX_EXT_texture_from_pixmap, GLX_EXT_framebuffer_sRGB,
GLX_NV_present_video, GLX_NV_copy_image, GLX_NV_multisample_coverage,
GLX_NV_video_capture, GLX_EXT_create_context_es2_profile,
GLX_ARB_create_context_robustness
GLX version: 1.4
GLX extensions:
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_SGIX_fbconfig,
GLX_SGIX_pbuffer, GLX_SGI_video_sync, GLX_SGI_swap_control,
GLX_EXT_swap_control, GLX_EXT_texture_from_pixmap, GLX_ARB_create_context,
GLX_ARB_create_context_profile, GLX_EXT_create_context_es2_profile,
GLX_ARB_create_context_robustness, GLX_ARB_multisample,
GLX_NV_float_buffer, GLX_ARB_fbconfig_float, GLX_EXT_framebuffer_sRGB,
GLX_ARB_get_proc_address
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce GT 330M/PCI/SSE2
OpenGL version string: 3.3.0 NVIDIA 280.13
OpenGL shading language version string: 3.30 NVIDIA via Cg compiler
OpenGL extensions:
[/code]

and every opengl code is compiled correctly.
I think this is the solution for you're cuda problem also because you have a mobile version of the nvidia graphics adapter.

cheers Vasilie
So, finally i solved the problem.

The actual Nvidia driver package in the fedora repository wasn't the correct one for my graphics adapter.

So I've downloaded the latest drivers for my graphics card from Nvidia's site, removed the complete NVidia driver section ( inclusive all Mesa stuff ) and installed the downloaded one.



After this odyssey glxinfo show me the correct configuration:



name of display: :0.0

display: :0 screen: 0

direct rendering: Yes

server glx vendor string: NVIDIA Corporation

server glx version string: 1.4

server glx extensions:

GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_SGIX_fbconfig,

GLX_SGIX_pbuffer, GLX_SGI_video_sync, GLX_SGI_swap_control,

GLX_EXT_swap_control, GLX_EXT_texture_from_pixmap, GLX_ARB_create_context,

GLX_ARB_create_context_profile, GLX_EXT_create_context_es2_profile,

GLX_ARB_create_context_robustness, GLX_ARB_multisample,

GLX_NV_float_buffer, GLX_ARB_fbconfig_float, GLX_EXT_framebuffer_sRGB

client glx vendor string: NVIDIA Corporation

client glx version string: 1.4

client glx extensions:

GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_visual_info,

GLX_EXT_visual_rating, GLX_EXT_import_context, GLX_SGI_video_sync,

GLX_NV_swap_group, GLX_NV_video_out, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer,

GLX_SGI_swap_control, GLX_EXT_swap_control, GLX_ARB_create_context,

GLX_ARB_create_context_profile, GLX_NV_float_buffer,

GLX_ARB_fbconfig_float, GLX_EXT_fbconfig_packed_float,

GLX_EXT_texture_from_pixmap, GLX_EXT_framebuffer_sRGB,

GLX_NV_present_video, GLX_NV_copy_image, GLX_NV_multisample_coverage,

GLX_NV_video_capture, GLX_EXT_create_context_es2_profile,

GLX_ARB_create_context_robustness

GLX version: 1.4

GLX extensions:

GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_SGIX_fbconfig,

GLX_SGIX_pbuffer, GLX_SGI_video_sync, GLX_SGI_swap_control,

GLX_EXT_swap_control, GLX_EXT_texture_from_pixmap, GLX_ARB_create_context,

GLX_ARB_create_context_profile, GLX_EXT_create_context_es2_profile,

GLX_ARB_create_context_robustness, GLX_ARB_multisample,

GLX_NV_float_buffer, GLX_ARB_fbconfig_float, GLX_EXT_framebuffer_sRGB,

GLX_ARB_get_proc_address

OpenGL vendor string: NVIDIA Corporation

OpenGL renderer string: GeForce GT 330M/PCI/SSE2

OpenGL version string: 3.3.0 NVIDIA 280.13

OpenGL shading language version string: 3.30 NVIDIA via Cg compiler

OpenGL extensions:




and every opengl code is compiled correctly.

I think this is the solution for you're cuda problem also because you have a mobile version of the nvidia graphics adapter.



cheers Vasilie

#3
Posted 08/30/2011 01:12 PM   
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.

Thanks for your input.

JGibson
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.



Thanks for your input.



JGibson

#4
Posted 08/30/2011 10:44 PM   
Scroll To Top