Posted by
Sven Gothel on
Jan 14, 2012; 12:21am
URL: https://forum.jogamp.org/Ubuntu-11-10-64bit-and-AWT-vs-NEWT-tp3654908p3658068.html
On Saturday, January 14, 2012 12:12:46 AM Martin Hegedus [via jogamp] wrote:
>
> Sorry, I'm new to this Ubuntu Unity thing. And it's been a while since I've
> dug into system admin. My core skills are aerodynamics, computational fluid
> dynamics (CFD), and user interface programing using java. I'm happy when I
> can go a year without really touching my machines. :)
>
> Ubuntu's System Info tells me I'm using Gallium 0.4 on NV86 and glxinfo
> (which was installed from Ubuntu Software Center) tells me "OpenGL render
> string: Gallium 0.4 on NV86" So I guess that's my driver. Here is the
> output from glxinfo
http://www.hegedusaero.com/jogl/glxinfo.out.txt>
> The JOGL_test.java program I attached exhibits the same problem as the
> TestGears one. So I'm focusing on that since it is easier for me to wrap my
> head around.
>
> At the moment I'm focusing on the following as my issues because of the
> runaway cpu in glXMakeContextCurrent
> 1) Driver
> 2) Mesa
>
> This is not to say that some unexpected feedback between JOGL, Java, Mesa,
> and Drivers is not causing the problem. But, I would like to build
> confidence in the driver first.
I will test your test-app tomorrow.
Most likely it's a driver bug .. confused w/ our multithreading context use,
at least this was always the case in the past.
You can verify it by just using Mesa3D's pure software driver w/o gallium.
BTW .. 'Gallium on NV86' means NVidia ? In this case we may talk about the
reengineered Novum (?) driver (sorry, not sure about the name).
If so .. you really should avoid it for a stable development platform
and use NVidia's proprietory closed source driver.
With the latter - it will just work.
~Sven