VMD-L Mailing List
From: Axel Kohlmeyer (akohlmey_at_cmm.chem.upenn.edu)
Date: Mon May 14 2007 - 13:03:49 CDT
- Next message: Adrian Roitberg: "RNA"
- Previous message: John Stone: "Re: An remark on PoV output"
- In reply to: John Stone: "Re: GLSL rendering problems (??)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
On Mon, 14 May 2007, John Stone wrote:
JS>
JS> Hi guys,
JS> It seems that GLSL works on some combinations of 64-bit drivers and
JS> video cards and not on others. Which video card are you using? I've
ok. so i just got lucky?
it worked for me without any trouble for 64-bit and
32-bit applications (just importing the rpms from livna.org
without any modifications), so i thought that had been
sorted out. oh well!
here's the VMD startup message (self compiled):
Info) VMD for LINUXAMD64, version 1.8.6 (May 8, 2007)
Info) http://www.ks.uiuc.edu/Research/vmd/
Info) Email questions and bug reports to vmd_at_ks.uiuc.edu
Info) Please include this reference in published work using VMD:
Info) Humphrey, W., Dalke, A. and Schulten, K., `VMD - Visual
Info) Molecular Dynamics', J. Molec. Graphics 1996, 14.1, 33-38.
Info) -------------------------------------------------------------
Info) Multithreading available, 4 CPUs detected.
Info) Free system memory: 15159MB (94%)
Info) OpenGL renderer: Quadro FX 4500/PCI/SSE2
Info) Features: STENCIL MSAA(16) MDE CVA MTX NPOT PP PS GLSL(OVF)
Info) Full GLSL rendering mode is available.
Info) Textures: 2-D (4096x4096), 3-D (512x512x512), Multitexture (4)
amd here's the glxinfo output
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_texture_from_pixmap, GLX_ARB_multisample,
GLX_NV_float_buffer,
GLX_ARB_fbconfig_float, GLX_NV_swap_group
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_NV_float_buffer, GLX_ARB_fbconfig_float,
GLX_EXT_fbconfig_packed_float, GLX_EXT_texture_from_pixmap,
GLX_EXT_framebuffer_sRGB
GLX version: 1.3
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_texture_from_pixmap, GLX_ARB_multisample,
GLX_NV_float_buffer,
GLX_ARB_fbconfig_float, GLX_NV_swap_group, GLX_ARB_get_proc_address
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: Quadro FX 4500/PCI/SSE2
OpenGL version string: 2.1.0 NVIDIA 97.55
OpenGL extensions:
GL_ARB_color_buffer_float, GL_ARB_depth_texture,
GL_ARB_draw_buffers,
GL_ARB_fragment_program, GL_ARB_fragment_program_shadow,
GL_ARB_fragment_shader, GL_ARB_half_float_pixel, GL_ARB_imaging,
GL_ARB_multisample, GL_ARB_multitexture, GL_ARB_occlusion_query,
GL_ARB_pixel_buffer_object, GL_ARB_point_parameters,
GL_ARB_point_sprite,
GL_ARB_shadow, GL_ARB_shader_objects, GL_ARB_shading_language_100,
GL_ARB_texture_border_clamp, GL_ARB_texture_compression,
GL_ARB_texture_cube_map, GL_ARB_texture_env_add,
GL_ARB_texture_env_combine, GL_ARB_texture_env_dot3,
GL_ARB_texture_float,
GL_ARB_texture_mirrored_repeat, GL_ARB_texture_non_power_of_two,
GL_ARB_texture_rectangle, GL_ARB_transpose_matrix,
GL_ARB_vertex_buffer_object, GL_ARB_vertex_program,
GL_ARB_vertex_shader,
GL_ARB_window_pos, GL_ATI_draw_buffers, GL_ATI_texture_float,
GL_ATI_texture_mirror_once, GL_S3_s3tc, GL_EXT_texture_env_add,
GL_EXT_abgr, GL_EXT_bgra, GL_EXT_blend_color,
GL_EXT_blend_equation_separate, GL_EXT_blend_func_separate,
GL_EXT_blend_minmax, GL_EXT_blend_subtract,
GL_EXT_compiled_vertex_array,
GL_EXT_Cg_shader, GL_EXT_depth_bounds_test,
GL_EXT_draw_range_elements,
GL_EXT_fog_coord, GL_EXT_framebuffer_blit,
GL_EXT_framebuffer_multisample,
GL_EXT_framebuffer_object, GL_EXT_gpu_program_parameters,
GL_EXT_multi_draw_arrays, GL_EXT_packed_depth_stencil,
GL_EXT_packed_pixels, GL_EXT_pixel_buffer_object,
GL_EXT_point_parameters,
GL_EXT_rescale_normal, GL_EXT_secondary_color,
GL_EXT_separate_specular_color, GL_EXT_shadow_funcs,
GL_EXT_stencil_two_side, GL_EXT_stencil_wrap, GL_EXT_texture3D,
GL_EXT_texture_compression_s3tc, GL_EXT_texture_cube_map,
GL_EXT_texture_edge_clamp, GL_EXT_texture_env_combine,
GL_EXT_texture_env_dot3, GL_EXT_texture_filter_anisotropic,
GL_EXT_texture_lod, GL_EXT_texture_lod_bias,
GL_EXT_texture_mirror_clamp,
GL_EXT_texture_object, GL_EXT_texture_sRGB, GL_EXT_timer_query,
GL_EXT_vertex_array, GL_IBM_rasterpos_clip,
GL_IBM_texture_mirrored_repeat, GL_KTX_buffer_region,
GL_NV_blend_square,
GL_NV_copy_depth_to_color, GL_NV_depth_clamp, GL_NV_fence,
GL_NV_float_buffer, GL_NV_fog_distance, GL_NV_fragment_program,
GL_NV_fragment_program_option, GL_NV_fragment_program2,
GL_NV_framebuffer_multisample_coverage, GL_NV_half_float,
GL_NV_light_max_exponent, GL_NV_multisample_filter_hint,
GL_NV_occlusion_query, GL_NV_packed_depth_stencil,
GL_NV_pixel_data_range,
GL_NV_point_sprite, GL_NV_primitive_restart,
GL_NV_register_combiners,
GL_NV_register_combiners2, GL_NV_texgen_reflection,
GL_NV_texture_compression_vtc, GL_NV_texture_env_combine4,
GL_NV_texture_expand_normal, GL_NV_texture_rectangle,
GL_NV_texture_shader, GL_NV_texture_shader2, GL_NV_texture_shader3,
GL_NV_vertex_array_range, GL_NV_vertex_array_range2,
GL_NV_vertex_program,
GL_NV_vertex_program1_1, GL_NV_vertex_program2,
GL_NV_vertex_program2_option, GL_NV_vertex_program3,
GL_NVX_conditional_render, GL_SGIS_generate_mipmap,
GL_SGIS_texture_lod,
GL_SGIX_depth_texture, GL_SGIX_shadow, GL_SUN_slice_accum
JS> had 1.0-9755 on other 64-bit machines and not gotten GLSL, so I'm curious
JS> which card you're using. It may be that only the Quadro cards are enabling
JS> GLSL when run in 64-bit mode. The 32-bit VMD builds will get GLSL on 64-bit
JS> machines for all of the recent cards, but the 64-bit VMD builds
JS> (and this can be seen with glxinfo as well by the way) don't see the GLSL
JS> extensions on all cards. Since I haven't found any vendor documents describing
JS> the hardware and driver combinations in which GLSL is supported via the
JS> 64-bit OpenGL libraries, it seems we're left to anecdotal reports from
JS> people that have seen it work. None of my current Linux test machines
JS> are yielding 64-bit GLSL here in our lab, even with recent drivers,
JS> so needless to say I'd love to know which cards and drivers people
JS> are using that are indeed getting GLSL when running the 64-bit VMD builds...
JS>
JS> Cheers,
JS> John Stone
JS> vmd_at_ks.uiuc.edu
JS>
JS>
JS> On Mon, May 14, 2007 at 12:04:34PM -0400, Axel Kohlmeyer wrote:
JS> > On Mon, 14 May 2007, Dow Hurst DPHURST wrote:
JS> >
JS> > DH> Mario,
JS> > DH> The opteron can run 32bit and 64 bit code so you may be running a 32bit
JS> > DH> nvidia driver. The itanium is not enabled the same way, IIRC. There
JS> > DH> really isn't 64bit GLSL support from Nvidia or ATI yet.
JS> >
JS> > i beg to differ. see:
JS> > http://www.nvidia.com/object/linux_display_amd64_1.0-9755.html
JS> >
JS> > i'm running this on an EM64t machine (dual woodcrest) in 64-bit
JS> > mode and GLSL works nicely when running locally.
JS> >
JS> > the situation is very different on IA64, but for remote display
JS> > this is not so much an issue. the question is more whether
JS> > the local nvidia driver exposes the GLSL infrastructure to a
JS> > remote application via GLX, which is a cat of a different color.
JS> >
JS> > cheers,
JS> > axel.
JS> >
JS> > DH> Dow
JS> > DH>
JS> > DH>
JS> > DH>
JS> > DH> -----owner-vmd-l_at_ks.uiuc.edu wrote: -----
JS> > DH>
JS> > DH> To: John Stone <johns_at_ks.uiuc.edu>, vmd-l_at_ks.uiuc.edu
JS> > DH> From: Mario Valle <mvalle_at_cscs.ch>
JS> > DH> Sent by: owner-vmd-l_at_ks.uiuc.edu
JS> > DH> Date: 04/24/2007 11:44PM
JS> > DH> Subject: Re: vmd-l: GLSL rendering problems (??)
JS> > DH>
JS> > DH>
JS> > DH> > So, at the present time the only option is to get a 64-bit OpenGL
JS> > DH> > driver that supports GLSL. So far as I know, none of the 64-bit
JS> > DH> > drivers from any of the vendors do GLSL yet.
JS> > DH> >
JS> > DH> I disagree, the new HP SVA line (Opteron 64 bits) has GLSL support and
JS> > DH> in fact I'm running VMD with GLSL rendering without trouble. Well, as
JS> > DH> usual, it says my driver is buggy, but it works.
JS> > DH> Ciao!
JS> > DH> mario
JS> > DH> > John Stone
JS> > DH> > vmd_at_ks.uiuc.edu
JS> > DH> >
JS> > DH> > On Tue, Apr 24, 2007 at 05:00:20PM -0400, Nichols A. Romero wrote:
JS> > DH> >
JS> > DH> >> Yes, the machine that I ssh (kerborized) into is an SGI Altix. My local
JS> > DH> >> machine is a laptop, but they appear to have
JS> > DH> >> the same graphics card. In order to get GLSL rendering working on my
JS> > DH> laptop,
JS> > DH> >> I had to update the NVIDIA drivers.
JS> > DH> >>
JS> > DH> >> So, is the problem the SSH or the NVIDIA driver on the Altix?
JS> > DH> >>
JS> > DH> >> On 4/24/07, John Stone <johns_at_ks.uiuc.edu> wrote:
JS> > DH> >>
JS> > DH> >>> Hi,
JS> > DH> >>> The output of glxinfo indicates that your driver isn't exporting
JS> > DH> >>> the GLSL extensions. In fact, the only extra features you're getting
JS> > DH> are
JS> > DH> >>> the multitexture extension and a stencil buffer. It appears that
JS> > DH> you're
JS> > DH> >>> attaching through 'ssh', guessing by your DISPLAY variable being set
JS> > DH> >>> to "localhost:10.0". That combined with the fact that you appear to be
JS> > DH> >>> remote displaying onto a remote laptop may be the reason for problems.
JS> > DH> >>> What happens when you run VMD locally on the laptop? (the machine with
JS> > DH> >>> the Quadro FX Go1400 in it, which I'm assuming is NOT the Altix...)
JS> > DH> >>>
JS> > DH> >>> Cheers,
JS> > DH> >>> John Stone
JS> > DH> >>> vmd_at_ks.uiuc.edu
JS> > DH> >>>
JS> > DH> >>> On Tue, Apr 24, 2007 at 04:40:57PM -0400, Nichols A. Romero wrote:
JS> > DH> >>>
JS> > DH> >>>> Hi,
JS> > DH> >>>>
JS> > DH> >>>> This is on SGI Altix. 16-processors box, using VMD 1.8.5 (I know that
JS> > DH> I
JS> > DH> >>>>
JS> > DH> >>> need
JS> > DH> >>>
JS> > DH> >>>> to upgrade).
JS> > DH> >>>>
JS> > DH> >>>> Receiving following message on start up.
JS> > DH> >>>> Info) Multithreading available, 16 CPUs detected.
JS> > DH> >>>> Xlib: extension "XFree86-DRI" missing on display "localhost:10.0".
JS> > DH> >>>> Info) OpenGL renderer: Quadro FX Go1400/PCI/SSE2
JS> > DH> >>>> Info) Features: STENCIL MTX
JS> > DH> >>>> Info) GLSL rendering mode is NOT available.
JS> > DH> >>>> Info) Textures: 2-D (4096x4096), 3-D (512x512x512), Multitexture (4)
JS> > DH> >>>> Found 1 plugins or data handlers in directory
JS> > DH> >>>> '/usr/people/naromero/vmd-1.8.5/lib/plugins/LINUXIA64/molfile'.
JS> > DH> >>>>
JS> > DH> >>>> Is the lack of GLSL rendering a XFree86 problem or an NVIDIA driver
JS> > DH> >>>>
JS> > DH> >>> problem?
JS> > DH> >>>
JS> > DH> >>>> I attach the glxinfo output.
JS> > DH> >>>>
JS> > DH> >>>> --
JS> > DH> >>>> Nichols A. Romero, Ph.D.
JS> > DH> >>>> 1613 Denise Dr. Apt. D
JS> > DH> >>>> Forest Hill, MD 21050
JS> > DH> >>>> 443-567-8328 (C)
JS> > DH> >>>> 410-306-0709 (O)
JS> > DH> >>>>
JS> > DH> >>>
JS> > DH> >>> --
JS> > DH> >>> NIH Resource for Macromolecular Modeling and Bioinformatics
JS> > DH> >>> Beckman Institute for Advanced Science and Technology
JS> > DH> >>> University of Illinois, 405 N. Mathews Ave, Urbana, IL 61801
JS> > DH> >>> Email: johns_at_ks.uiuc.edu Phone: 217-244-3349
JS> > DH> >>> WWW: http://www.ks.uiuc.edu/~johns/ Fax: 217-244-6078
JS> > DH> >>>
JS> > DH> >>>
JS> > DH> >>
JS> > DH> >> --
JS> > DH> >> Nichols A. Romero, Ph.D.
JS> > DH> >> 1613 Denise Dr. Apt. D
JS> > DH> >> Forest Hill, MD 21050
JS> > DH> >> 443-567-8328 (C)
JS> > DH> >> 410-306-0709 (O)
JS> > DH> >>
JS> > DH> >
JS> > DH> >
JS> > DH>
JS> > DH>
JS> > DH> --
JS> > DH> Ing. Mario Valle
JS> > DH> Visualization Group |
JS> > DH> http://www.cscs.ch/~mvalle
JS> > DH> Swiss National Supercomputing Centre (CSCS) | Tel: +41 (91) 610.82.60
JS> > DH> v. Cantonale Galleria 2, 6928 Manno, Switzerland | Fax: +41 (91) 610.82.82
JS> > DH>
JS> > DH>
JS> > DH>
JS> > DH>
JS> >
JS> > --
JS> > =======================================================================
JS> > Axel Kohlmeyer akohlmey_at_cmm.chem.upenn.edu http://www.cmm.upenn.edu
JS> > Center for Molecular Modeling -- University of Pennsylvania
JS> > Department of Chemistry, 231 S.34th Street, Philadelphia, PA 19104-6323
JS> > tel: 1-215-898-1582, fax: 1-215-573-6233, office-tel: 1-215-898-5425
JS> > =======================================================================
JS> > If you make something idiot-proof, the universe creates a better idiot.
JS>
JS>
-- ======================================================================= Axel Kohlmeyer akohlmey_at_cmm.chem.upenn.edu http://www.cmm.upenn.edu Center for Molecular Modeling -- University of Pennsylvania Department of Chemistry, 231 S.34th Street, Philadelphia, PA 19104-6323 tel: 1-215-898-1582, fax: 1-215-573-6233, office-tel: 1-215-898-5425 ======================================================================= If you make something idiot-proof, the universe creates a better idiot.
- Next message: Adrian Roitberg: "RNA"
- Previous message: John Stone: "Re: An remark on PoV output"
- In reply to: John Stone: "Re: GLSL rendering problems (??)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]