About the dri support on 5.0.26

[Otacílio]

Dears

Now that dri support was removed from Virtualbox 5.0.26, how will be the
support for OpenGL applications?


[]'s

-Otacilio

_______________________________________________
freebsd-...@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to "freebsd-emulat...@freebsd.org"

[Jung-uk Kim]

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

[Otacílio]

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@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@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@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@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

[Jung-uk Kim]

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

[Kevin Oberman]

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?
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkob...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683

[Jung-uk Kim]

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