Re: [VirtualGL-Users] vglrun not working on FreeBSD

2012-02-28 Thread DRC
On 2/28/12 3:14 AM, 图潘 wrote:
 Another note on PBuffer (pixel buffer).
 
 As I have read the pbuffer is already deprecated and replaced by FBO
 (frame buffer object)
 http://en.wikipedia.org/wiki/Pixel_buffer
 
 I don't know about the differences about linux and freebsd opengl
 implementations. On linux systems are you relying on pbuffer?
 
 Is PBuffer really required to get virtualgl working?


Yes, PBuffers are really required.

Buy an nVidia card and download their proprietary drivers for FreeBSD.
Those should work similarly to the drivers that most of us use on Linux.

FBO's are a fundamentally different beast from Pbuffers.  They are
implemented at the OpenGL level, not the GLX level, so they can't really
substitute for an X window.  You still have to bind an FBO to some
context, which was previously created with some drawable.  That drawable
can't be a window in our case, so what's the other choice?  Well, a
Pbuffer.  But if we're going to bind an FBO to a Pbuffer, why use FBO's
at all?  Why not just use Pbuffers by themselves?  We could possibly
bind an FBO to an unmapped window as well, but I'm not sure of the
ramifications of that, given that a bunch of users are sharing the same
display.  Maybe there are no ramifications, but it would require a lot
of testing to be sure of that.

At minimum, converting VirtualGL to use FBO's is a large effort and not
something I'm prepared to tackle for free, and no one is likely to pay
for it until/unless it becomes absolutely necessary.

--
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
___
VirtualGL-Users mailing list
VirtualGL-Users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/virtualgl-users


Re: [VirtualGL-Users] vglrun not working on FreeBSD

2012-02-28 Thread 图潘
Hmm, looks like my driver does not support pbuffers, so I will get an
nVidia as you recommended.
Thanks

On Tue, Feb 28, 2012 at 10:39 AM, DRC dcomman...@users.sourceforge.net wrote:
 On 2/28/12 3:14 AM, 图潘 wrote:
 Another note on PBuffer (pixel buffer).

 As I have read the pbuffer is already deprecated and replaced by FBO
 (frame buffer object)
 http://en.wikipedia.org/wiki/Pixel_buffer

 I don't know about the differences about linux and freebsd opengl
 implementations. On linux systems are you relying on pbuffer?

 Is PBuffer really required to get virtualgl working?


 Yes, PBuffers are really required.

 Buy an nVidia card and download their proprietary drivers for FreeBSD.
 Those should work similarly to the drivers that most of us use on Linux.

 FBO's are a fundamentally different beast from Pbuffers.  They are
 implemented at the OpenGL level, not the GLX level, so they can't really
 substitute for an X window.  You still have to bind an FBO to some
 context, which was previously created with some drawable.  That drawable
 can't be a window in our case, so what's the other choice?  Well, a
 Pbuffer.  But if we're going to bind an FBO to a Pbuffer, why use FBO's
 at all?  Why not just use Pbuffers by themselves?  We could possibly
 bind an FBO to an unmapped window as well, but I'm not sure of the
 ramifications of that, given that a bunch of users are sharing the same
 display.  Maybe there are no ramifications, but it would require a lot
 of testing to be sure of that.

 At minimum, converting VirtualGL to use FBO's is a large effort and not
 something I'm prepared to tackle for free, and no one is likely to pay
 for it until/unless it becomes absolutely necessary.

 --
 Keep Your Developer Skills Current with LearnDevNow!
 The most comprehensive online learning library for Microsoft developers
 is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
 Metro Style Apps, more. Free future releases when you subscribe now!
 http://p.sf.net/sfu/learndevnow-d2d
 ___
 VirtualGL-Users mailing list
 VirtualGL-Users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/virtualgl-users

--
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
___
VirtualGL-Users mailing list
VirtualGL-Users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/virtualgl-users


Re: [VirtualGL-Users] vglrun not working on FreeBSD

2012-02-28 Thread DRC
On 2/28/12 2:32 AM, 图潘 wrote:
 3D Acceleration works on VirtualBox.
 I can do all the Dirext X 3D tests in a windows virtual machine,
 I have also installed and played Quake III, which runs flawlessly.
 So the drivers are working correctly.
 By the way mine is a ATI X600 RV380 (X600) with 128 MB Ram
 
 So lets forget about VirtualBox for a second, what is the easiest way
 to test VirtualGL that normally always works
 
 Is PBuffer really required to get virtualgl working?

Sorry, this message got spam-filtered, so I didn't see the full content
of it.  ATI adapters should work fine with VirtualGL provided that you
install the ATI Catalyst driver.  Please give that a try:

  http://www2.ati.com/drivers/linux/ati-driver-installer-9-3-x86.x86_64.run

I misunderstood and didn't realize you had an ATI board.

The easiest way to test VirtualGL is to just log into the machine
locally and run:

  export VGL_LOGO=1
  vglrun /opt/VirtualGL/bin/glxspheres

Assuming the application launches properly, you should see a VGL logo
in the bottom corner of the window, which lets you verify that VirtualGL
is in fact active and that the app is using it rather than displaying
directly to the X server.  Once it works locally, then the next step is
to go through the procedure in the User's Guide for configuring gdm or
kdm so that VGL can access the 3D X server when it's sitting at the
login prompt.  Then you can test the same thing remotely.  Then, and
only then, should you try running VirtualBox in VirtualGL.

--
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
___
VirtualGL-Users mailing list
VirtualGL-Users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/virtualgl-users


Re: [VirtualGL-Users] vglrun not working on FreeBSD

2012-02-28 Thread 图潘
 export VGL_LOGO=1
 vglrun /opt/VirtualGL/bin/glxspheres
Polygons in scene: 62464
ERROR (593): could not obtain RGB visual with requested properties.

So it looks like it is not working with my card :-(

Anyway, thanks for the help

On Tue, Feb 28, 2012 at 5:34 PM, 图潘 patula...@gmail.com wrote:
 On Tue, Feb 28, 2012 at 5:05 PM, DRC dcomman...@users.sourceforge.net wrote:

 Sorry, this message got spam-filtered, so I didn't see the full content
 of it.  ATI adapters should work fine with VirtualGL provided that you
 install the ATI Catalyst driver.  Please give that a try:

  http://www2.ati.com/drivers/linux/ati-driver-installer-9-3-x86.x86_64.run
 This is not going to work. I am running FreeBSD ;-) using an open
 source ati driver.
 The card is fully recognized except the pbuffer thing is not supported
 by the driver (as it looks)


 The easiest way to test VirtualGL is to just log into the machine
 locally and run:

  export VGL_LOGO=1
  vglrun /opt/VirtualGL/bin/glxspheres

 Thanks, I will try this when I get home and let you know.

--
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
___
VirtualGL-Users mailing list
VirtualGL-Users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/virtualgl-users


Re: [VirtualGL-Users] vglrun not working on FreeBSD

2012-02-28 Thread DRC
On 2/28/12 10:34 AM, 图潘 wrote:
 This is not going to work. I am running FreeBSD ;-) using an open
 source ati driver.
 The card is fully recognized except the pbuffer thing is not supported
 by the driver (as it looks)

Duh.  I knew that.  Sorry for my momentary confusion.


  export VGL_LOGO=1
  vglrun /opt/VirtualGL/bin/glxspheres
 
 Thanks, I will try this when I get home and let you know.

I meant to try it once you know that you have Pbuffers working.  There's
no way it will work until glxinfo shows Pbuffer-enabled FB configs.

So yeah, I guess buy an nVidia board, since they seem to have the only
Pbuffer-enabled FreeBSD driver support.

--
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
___
VirtualGL-Users mailing list
VirtualGL-Users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/virtualgl-users


Re: [VirtualGL-Users] vglrun not working on FreeBSD

2012-02-27 Thread 图潘
I did the steps in configuring the system.
Just to be 100% accurate I have even installed gdm, as I normally
started it with 'startx'

 /opt/VirtualGL/bin/vglserver_config
# I have answered everything with no in order to avoid all possible
mistakes at the beginning


So no I am testing the 3D X Server acces
 /opt/VirtualGL/bin/glxinfo -display :0 -c
You should also examine the output of glxinfo to ensure that at least
one of the visuals is 24-bit or 32-bit TrueColor and has Pbuffer
support
This is not the case, but 3D drivers are working

Here is the output
 /opt/VirtualGL/bin/glxinfo -display :0 -c

name of display: :0
display: :0  screen: 0
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.2
server glx extensions:
GLX_ARB_multisample, GLX_EXT_visual_info, GLX_EXT_visual_rating,
GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_OML_swap_method,
GLX_SGI_make_current_read, GLX_SGIS_multisample, GLX_SGIX_hyperpipe,
GLX_SGIX_swap_barrier, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer,
GLX_MESA_copy_sub_buffer
client glx vendor string: 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_allocate_memory,
GLX_MESA_copy_sub_buffer, GLX_MESA_swap_control,
GLX_MESA_swap_frame_usage, 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 version: 1.2
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_MESA_swap_frame_usage, GLX_OML_swap_method,
GLX_SGI_make_current_read, GLX_SGI_video_sync, GLX_SGIS_multisample,
GLX_SGIX_fbconfig
OpenGL vendor string: DRI R300 Project
OpenGL renderer string: Mesa DRI R300 20060815 TCL
OpenGL version string: 1.3 Mesa 7.4.4
OpenGL extensions:
GL_ARB_depth_texture, GL_ARB_fragment_program, GL_ARB_imaging,
GL_ARB_multisample, GL_ARB_multitexture, GL_ARB_point_parameters,
GL_ARB_shadow, GL_ARB_shadow_ambient, 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_crossbar, GL_ARB_texture_env_dot3,
GL_MESAX_texture_float, GL_ARB_texture_mirrored_repeat,
GL_ARB_texture_rectangle, GL_ARB_transpose_matrix,
GL_ARB_vertex_buffer_object, GL_ARB_vertex_program, GL_ARB_window_pos,
GL_EXT_abgr, GL_EXT_bgra, GL_EXT_blend_color,
GL_EXT_blend_equation_separate, GL_EXT_blend_func_separate,
GL_EXT_blend_logic_op, GL_EXT_blend_minmax, GL_EXT_blend_subtract,
GL_EXT_clip_volume_hint, GL_EXT_compiled_vertex_array, GL_EXT_convolution,
GL_EXT_copy_texture, GL_EXT_draw_range_elements,
GL_EXT_gpu_program_parameters, GL_EXT_histogram, GL_EXT_multi_draw_arrays,
GL_EXT_packed_pixels, GL_EXT_point_parameters, GL_EXT_polygon_offset,
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_subtexture,
GL_EXT_texture, GL_EXT_texture3D, GL_EXT_texture_edge_clamp,
GL_EXT_texture_env_add, GL_EXT_texture_env_combine,
GL_EXT_texture_env_dot3, GL_EXT_texture_filter_anisotropic,
GL_EXT_texture_lod_bias, GL_EXT_texture_mirror_clamp,
GL_EXT_texture_object, GL_EXT_texture_rectangle, GL_EXT_vertex_array,
GL_APPLE_packed_pixels, GL_ATI_blend_equation_separate,
GL_ATI_texture_env_combine3, GL_ATI_texture_mirror_once,
GL_IBM_rasterpos_clip, GL_IBM_texture_mirrored_repeat,
GL_INGR_blend_func_separate, GL_MESA_pack_invert, GL_MESA_ycbcr_texture,
GL_MESA_window_pos, GL_NV_blend_square, GL_NV_light_max_exponent,
GL_NV_texture_rectangle, GL_NV_texgen_reflection, GL_NV_vertex_program,
GL_OES_read_format, GL_SGI_color_matrix, GL_SGI_color_table,
GL_SGIS_generate_mipmap, GL_SGIS_texture_border_clamp,
GL_SGIS_texture_edge_clamp, GL_SGIS_texture_lod, GL_SGIX_depth_texture,
GL_SGIX_shadow_ambient, GL_SUN_multi_draw_arrays

16 GLXFBConfigs:
   visual  x  bf lv rg d st colorbuffer ax dp st accumbuffer  ms  cav  drw
 id dep cl sp sz l  ci b ro  r  g  b  a bf th cl  r  g  b  a ns b eat  typ
--
0xa3  0 tc  0 32  0 r  .  .  8  8  8  8  0 24  0  0  0  0  0  0 0 None .XW
0xa4  0 tc  0 32  0 r  .  .  8  8  8  8  0 24  0 16 16 16 16  0 0 Slow .XW
0xa5  0 tc  0 32  0 r  y  .  8  8  8  8  0 24  0  0  0  0  0  0 0 None .XW
0xa6  0 tc  0 32  0 r  y  .  8  8  8  8  0 24  0 16 16 16 16  0 0 Slow .XW
0xa7  0 tc  0 32  0 r  .  .  8  8  8  8  0 24  8  0  0  0  0  0 0 None .XW
0xa8  0 tc  0 32  0 r  .  .  8  8  8  8  0 24  8 16 16 16 16  0 

Re: [VirtualGL-Users] vglrun not working on FreeBSD

2012-02-27 Thread DRC
On 2/27/12 4:39 PM, 图潘 wrote:
 /opt/VirtualGL/bin/glxinfo -display :0 -c
 You should also examine the output of glxinfo to ensure that at least
 one of the visuals is 24-bit or 32-bit TrueColor and has Pbuffer
 support
 This is not the case, but 3D drivers are working

Currently, the only types of 3D adapters that are known to work with
VirtualGL on the server end are ATI and nVidia, and you have to install
the proprietary vendor-supplied drivers to get Pbuffer support.

Also, have you first verified that 3D acceleration works with VirtualBox
on your system running locally (without VirtualGL)?  That is a necessary
prerequisite to this whole process.

--
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2
___
VirtualGL-Users mailing list
VirtualGL-Users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/virtualgl-users