Date: Wed, 27 Jul 2016 18:14:15 -0400 From: Jung-uk Kim <jkim@FreeBSD.org> To: Kevin Oberman <rkoberman@gmail.com> Cc: =?UTF-8?B?T3RhY8OtbGlv?= <otacilio.neto@bsd.com.br>, vbox@freebsd.org Subject: Re: About the dri support on 5.0.26 Message-ID: <43c7702e-ed40-c9d3-5267-838f940a658b@FreeBSD.org> In-Reply-To: <CAN6yY1txnYntmLZNaONOGEYXMKs1N2H9jBxBkuEY4cweqBSyUg@mail.gmail.com> References: <ad954819-f74e-189e-2b41-899ec4b94759@bsd.com.br> <448336e1-2490-7b10-f628-1a53e9ea6a63@FreeBSD.org> <5f5334ef-fca2-8134-a44b-86441b759748@bsd.com.br> <c8d2e63f-8fe3-c178-d823-8fd8a85c6a73@FreeBSD.org> <CAN6yY1txnYntmLZNaONOGEYXMKs1N2H9jBxBkuEY4cweqBSyUg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--3vXAF9Q2xOjUATlWR6qMpAw4067kxqfnI
Content-Type: multipart/mixed; boundary="EhqllmquClIBhfHi0qOX3I8isjUKj1mvk"
From: Jung-uk Kim <jkim@FreeBSD.org>
To: Kevin Oberman <rkoberman@gmail.com>
Cc: =?UTF-8?B?T3RhY8OtbGlv?= <otacilio.neto@bsd.com.br>, vbox@freebsd.org
Message-ID: <43c7702e-ed40-c9d3-5267-838f940a658b@FreeBSD.org>
Subject: Re: About the dri support on 5.0.26
References: <ad954819-f74e-189e-2b41-899ec4b94759@bsd.com.br>
<448336e1-2490-7b10-f628-1a53e9ea6a63@FreeBSD.org>
<5f5334ef-fca2-8134-a44b-86441b759748@bsd.com.br>
<c8d2e63f-8fe3-c178-d823-8fd8a85c6a73@FreeBSD.org>
<CAN6yY1txnYntmLZNaONOGEYXMKs1N2H9jBxBkuEY4cweqBSyUg@mail.gmail.com>
In-Reply-To: <CAN6yY1txnYntmLZNaONOGEYXMKs1N2H9jBxBkuEY4cweqBSyUg@mail.gmail.com>
--EhqllmquClIBhfHi0qOX3I8isjUKj1mvk
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
On 07/27/16 06:03 PM, Kevin Oberman wrote:
> On Wed, Jul 27, 2016 at 11:26 AM, Jung-uk Kim <jkim@freebsd.org
> <mailto:jkim@freebsd.org>> wrote:
>=20
> On 07/27/16 02:10 PM, Otac=C3=ADlio wrote:
> > Em 27/07/2016 13:40, Jung-uk Kim escreveu:
> >> On 07/25/16 08:17 PM, Otac=C3=ADlio 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 re=
place
> >> libGL.so & libEGL.so, when OPENGL option is enabled. It is stil=
l
> 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 supp=
ort.
> > This version provides a initial support to OpenGL. If you needs s=
ome
> > 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 thi=
s
> 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.427=
6
> >
> > [ota@nostromo /usr/home/ota]$ glxgears
> > 2332 frames in 5.0 seconds =3D 466.394 FPS
> > 1292 frames in 5.0 seconds =3D 258.259 FPS
> > 1413 frames in 5.0 seconds =3D 282.587 FPS
> > 1406 frames in 5.0 seconds =3D 280.992 FPS
> > 1412 frames in 5.0 seconds =3D 282.395 FPS
> > 1379 frames in 5.0 seconds =3D 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 bi=
ts)
> > 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 =3D 122.536 FPS
> > 633 frames in 5.0 seconds =3D 126.534 FPS
> > 475 frames in 5.0 seconds =3D 94.839 FPS
> > 486 frames in 5.0 seconds =3D 97.098 FPS
> > 489 frames in 5.0 seconds =3D 97.690 FPS
> > 502 frames in 5.0 seconds =3D 100.340 FPS
> > 491 frames in 5.0 seconds =3D 98.122 FPS
> >
> > Looks like a incompatibility between libGL and
> virtualbox-ose-additions
> > with OpenGL
>=20
> 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 n=
ote I
> mimicked x11/nvidia-driver* installation method and it is the only
> supported multi-libGL mechanism by graphics team AFAICT.
>=20
> Jung-uk Kim
>=20
> =20
> 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 i=
s
> 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
--EhqllmquClIBhfHi0qOX3I8isjUKj1mvk--
--3vXAF9Q2xOjUATlWR6qMpAw4067kxqfnI
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQEcBAEBCAAGBQJXmTI3AAoJEHyflib82/FGErYH/3jkJD5gWPgtOakOPzVj51XK
6heWU174A92E9brKIJhuBfgp0MI/uPxsVqoFcA4hB50ApX2GgmJUv7qZNpZZgoHW
EktWj57AKM9kCDvtsbs0ADabTaZkFinLmqgR7PbYerrS8Is3YBP4REbK59u2YzQg
DMJlS9EspzCpmPziOO0QeWPl8Y9KIijUbbD2ztxOHpoGBz3rFUNu49cPiJMM9Fip
Emsl8V3X7LS76AbmkJE754BQfBvJaeoEyTSW/OFf11G8xL70OTG/Ryw2bu/mmat9
JZRxNUehAT835Su7Cucy2yvKYzetcgxnMEtCbMJTwd6mMmKWF6MBNnbE1VZmBOs=
=gAut
-----END PGP SIGNATURE-----
--3vXAF9Q2xOjUATlWR6qMpAw4067kxqfnI--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?43c7702e-ed40-c9d3-5267-838f940a658b>