About the dri support on 5.0.26

Wed Jul 27 22:14:31 UTC 2016

On 07/27/16 06:03 PM, Kevin Oberman wrote:
> On Wed, Jul 27, 2016 at 11:26 AM, Jung-uk Kim <jkim at freebsd.org
> <mailto:jkim at freebsd.org>> wrote:
> 
>     On 07/27/16 02:10 PM, Otacílio wrote:
>     > Em 27/07/2016 13:40, Jung-uk Kim escreveu:
>     >> On 07/25/16 08:17 PM, Otacílio wrote:
>     >>> Now that dri support was removed from Virtualbox 5.0.26, how
>     will be the
>     >>> support for OpenGL applications?
>     >> Now its own libraries are used, i.e., VBoxOGL.so & VBoxEGL.so replace
>     >> libGL.so & libEGL.so, when OPENGL option is enabled.  It is still
>     work
>     >> in progress but please try r419160 and later.
>     >>
>     >> Jung-uk Kim
>     >>
>     > Dear,
>     >
>     > I have a try and I would like to thank you very much by your support.
>     > This version provides a initial support to OpenGL. If you needs some
>     > help in a manner that I can help you please let me know.
>     >
>     > Only for information. I have installed the 5419160 of
>     > virtualbox-ose-addtions with OpenGL enabled. After that I got this
>     info
>     > from glxinfo -B and glxgears
>     >
>     > [ota at nostromo /usr/home/ota]$ glxinfo -B
>     > name of display: :0.0
>     > display: :0  screen: 0
>     > direct rendering: Yes
>     > OpenGL vendor string: Humper
>     > OpenGL renderer string: Chromium
>     > OpenGL version string: 2.1 Chromium 1.9
>     > OpenGL shading language version string: 4.00 - Build 10.18.10.4276
>     >
>     > [ota at nostromo /usr/home/ota]$ glxgears
>     > 2332 frames in 5.0 seconds = 466.394 FPS
>     > 1292 frames in 5.0 seconds = 258.259 FPS
>     > 1413 frames in 5.0 seconds = 282.587 FPS
>     > 1406 frames in 5.0 seconds = 280.992 FPS
>     > 1412 frames in 5.0 seconds = 282.395 FPS
>     > 1379 frames in 5.0 seconds = 275.709 FPS
>     >
>     >
>     > So, then I have recompiled libGL and I got this info:
>     >
>     > [ota at nostromo /usr/home/ota]$ glxinfo -B
>     > name of display: :0.0
>     > display: :0  screen: 0
>     > direct rendering: Yes
>     > Extended renderer info (GLX_MESA_query_renderer):
>     >     Vendor: VMware, Inc. (0xffffffff)
>     >     Device: llvmpipe (LLVM 3.7, 256 bits) (0xffffffff)
>     >     Version: 11.2.2
>     >     Accelerated: no
>     >     Video memory: 4674MB
>     >     Unified memory: no
>     >     Preferred profile: core (0x1)
>     >     Max core profile version: 3.3
>     >     Max compat profile version: 3.0
>     >     Max GLES1 profile version: 1.1
>     >     Max GLES[23] profile version: 3.0
>     > OpenGL vendor string: VMware, Inc.
>     > OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.7, 256 bits)
>     > OpenGL core profile version string: 3.3 (Core Profile) Mesa 11.2.2
>     > OpenGL core profile shading language version string: 3.30
>     > OpenGL core profile context flags: (none)
>     > OpenGL core profile profile mask: core profile
>     >
>     > OpenGL version string: 3.0 Mesa 11.2.2
>     > OpenGL shading language version string: 1.30
>     > OpenGL context flags: (none)
>     >
>     > OpenGL ES profile version string: OpenGL ES 3.0 Mesa 11.2.2
>     > OpenGL ES profile shading language version string: OpenGL ES GLSL
>     ES 3.00
>     >
>     > [ota at nostromo /usr/home/ota]$ glxgears
>     > 613 frames in 5.0 seconds = 122.536 FPS
>     > 633 frames in 5.0 seconds = 126.534 FPS
>     > 475 frames in 5.0 seconds = 94.839 FPS
>     > 486 frames in 5.0 seconds = 97.098 FPS
>     > 489 frames in 5.0 seconds = 97.690 FPS
>     > 502 frames in 5.0 seconds = 100.340 FPS
>     > 491 frames in 5.0 seconds = 98.122 FPS
>     >
>     > Looks like a incompatibility  between libGL and
>     virtualbox-ose-additions
>     > with OpenGL
> 
>     emulators/virtualbox-ose-additions must be installed *after*
>     graphics/libGL.  In other words, when you reinstall graphics/libGL, you
>     also have to reinstall emulators/virtualbox-ose-additions because
>     libGL.so* and libEGL.so* are overwritten by the last one.  Please note I
>     mimicked x11/nvidia-driver* installation method and it is the only
>     supported multi-libGL mechanism by graphics team AFAICT.
> 
>     Jung-uk Kim
> 
>  
> This really needs to be VERY clearly documented! I'm not sure of the
> best way. I guess the bast that the port can do is include it in
> pkg-message. It would be great if the graphics/libGL port could be
> modified to note the presence of emulators/virtualbox-ose-additions and
> put out a warning. I also worry about keeping things in sync. If MESA is
> updated in the "standard" ports, will the new libdrm play nicely with
> the VirtualBox versions?

graphics/libGL does not play nice with *anything* because it does
"/bin/rm -f ${PREFIX}/lib/libGL.so*" from pkg-deinstall.  Therefore,
it's been always problematic with x11/nvidia-drivers*.

I like to see better multi-libGL handling myself.  If you have better
suggestion, please let us know.

Jung-uk Kim

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://lists.freebsd.org/pipermail/freebsd-emulation/attachments/20160727/4019e7b8/attachment.sig>