OpenGL pipeline on a linux platform bombs out when enabled.

Can anybody test the openGL pipeline enabling on linux (I’m using fedora Core 6) running

javaws http://www.java.net/download/javadesktop/blogs/campbell/2006.10.12/PhotoCube-OGL.jnlp

I’m still getting a JVM crash and when I post on the NVIDIA formns (http://www.nvnews.net/vbulletin/showthread.php?p=1260045#post1260045) they told me:

[QUOTE=netllama]I’m not able to reproduce this here. I should also note that no one else has reported this problem, and SUN typically alerts us to Java OpenGL bugs in our driver (and has not for this issue).
[/quote]
It sounds like there done with me, and I have a presentation in the next 3 weeks for my application that would be so UNCOOL if it had to work without the pipeline enabled. I need to know if its me or if its the rest of the world that’s out to get me :frowning:

The hardware I’ve tried it on is GeForce 5200 and GeForce 7950 on Ferdora Core 6 (2.6.20-1.2948.fc6) with the 9755, and 100.14.03 drivers. Am I the only one who can’t seem to get the pipeline to work on linux.

It’s working fine on my Solaris/x86 workstation with a Quadro FX 1100 and NVidia’s 97.55 drivers for Solaris/x86.

Thanks Ken. Anybody running fedora or another linux distro who reads this page, can you try the link http://www.java.net/download/javadesktop/blogs/campbell/2006.10.12/PhotoCube-OGL.jnlp and let me know if it works or not. I need to know if I’m that different from everybody.

Hi, for me it worked after I downloaded the .jnlp file and commented out the following line:

without that it would crash in libGL.so.1 (crash dump attached).

Therefore when the OpenGL pipeline is enabled it dosen’t work for you. What is your video hardware hardware and OS architecture?

OK. I see from the attached crash dump that its Fedora Core 6 2.6.20-1.2948_1.fc6 with the NVIDIA 9755 drivers. Just like me. If there is anybody who is reading this and has this platform and it works, please add somethine here. Also if there is any other linux distro that has it working I would be extremely greatful. I’m loosing too much sleep over this. :frowning:

I’m not sure whether this may be a known issue in NVidia’s drivers. Have you tried also specifying -Dsun.java2d.opengl.fbobject=false and seeing whether that works around the crash?

Yes. Ive tried this and it has no effect where the crash is concerned. What wories me is that netllama from NVIDIA who replied to me on the NVIDIA forum said that no one has reported this problem from SUN, and they usually tell them when there is an issue. Sounds to me like he figures that this is my problem and not the drivers. So I’m trying to find out how many people have this problem and if it is platform related.

The other possibility is that I use the GLCanvas and not GLJPanel. However I need the overlay windowing infrastructure via JDesktoppane and JInternalFrame that allow me to overlay regular windows ontop of a OpenGL canvas. Does anybody know of a descent opensource OpenGL windowing package that I could use to get MDI windows similar in function to JInternalFrames.

Hi

javaws PhotoCube-OGL.jnlp works for me. Note that I had to download and edit the .jnlp to point to http://download.java.net/media/jogl/builds/archive/jsr-231-1.0.0/jogl.jnlp to work around the known glibc 2.3 incompatibility.

Debian Etch, Nvidia 8776 drivers.

Andrew

What known glibc2.3 incompatibility What is not compatible.

They’re talking about the problem described here which hopefully should now be resolved.

So it sounds like the pipeline works on the Debian distribution. Is there another Debian user who can verify this. If there are any other linux distro users (Ubuntu, Suse, etal) who can try the link and say whether it works or not, this would be helpful to see if it is a Fedora problem.

Not to bother you SUN guys too much but netlama over at NVIDIA suggested I ask you all if there is any light that you can throw on the matter.

What I was asking them was how I could go about finding out the real problem.

It runs (slowly) when I set sun.java2d.opengl to false.
It crashes for me when the sun.java2d.opengl property is set to true in the jnlp.

It prints:

Could not enable OpenGL pipeline for default config on screen 0

and then segfaults in the ATI driver.

SIGSEGV (0xb) at pc=0xb4fc5529, pid=27812, tid=2987170704

Java VM: Java HotSpot™ Client VM (1.6.0-b105 mixed mode, sharing)

Problematic frame:

C [atiogl_a_dri.so+0x1d3529] glEnable+0x19

I don’t know if this is the same problem you have or my own different problem.

I am running FC6 on with an old ATI R200 series chip and (somewhat old) fglrx drivers from AMD.

Sounds to me like this is a driver issue. Your problem occurs in the atiogl_a_dri.so library, while my problem lies in the libGL.so.1 library. Have you tried upgrading your drivers.

The demo doesn’t show the cube on my PC (Ubuntu 7.04, Java 1.6.0, ATI X1600 with the proprietary driver xorg-driver-fglrx 7.1.0-8.34.8). The other tests I did were with windows PCs and the demo-apps that come with the JDK - with the pipeline enabled, either the rotating cubes didn’t show at all, or the screen flashed white the whole time. It seems that it is extremely important to have the right graphics card and the right drivers. It doesn’t look like the pipline could be a stable solution yet.

It doesn’t work at all :
Mandriva Linux 2007
2 GB DDRAM
ATI 9250 Pro with Xorg driver

I have only a gray window

I have no problems whatsoever.
ubuntu 7.04
java 1.6.0
nvidia GeForce4 MX 4000

Sorry to bump this post up, but I want to report my experience with the java.opengl pipeline.

When I enable it in my development environment(intellij idea) with the -D flag it bombs out. When I try the various examples on the web which have the opengl pipeline enabled it only displays part of which what should be displayed. And more importantly it doesnt even throw an exception. Like with the photocube it only shows the 2d text on the foreground and the background but not the photocube(I know what is meant to be displayed since it displays fine on our windows machine).

In our company we run linux(slackware 11.0/12.0), with java 1.6.0.2 and the latest jogl build. In three of our computers we have ati cards and in one we have an nvidia card. I’ve tried running the java webstart example photocube on all of them. For none of these computers the pipeline works(the nvidia one doesnt even startup, it just shows the loader then closes). Jogl doesnt reside in the jdk directory.

JOGL/Java2D integration enabled
OpenGL pipeline enabled for default config on screen 0
Starting initialization of J2D FBO share context
Ending initialization of J2D FBO share context
GLCanvas.addNotify()
#
# An unexpected error has been detected by Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0xb4a48d00, pid=602, tid=2748619696
#
# Java VM: Java HotSpot(TM) Client VM (1.6.0_02-b05 mixed mode, sharing)
# Problematic frame:
# C  [fglrx_dri.so+0x2d9d00]
#
# An error report file with more information is saved as hs_err_pid602.log
#
# If you would like to submit a bug report, please visit:
#   http://java.sun.com/webapps/bugreport/crash.jsp
#

Process finished with exit code 134


Do you have any idea when this will be fixed?

P.S. I wanted to send the log file with this post, but it said that the upload folder is full. If you still want it I could send it to you through email or other means.

Both ATI and Nvidia’s OpenGL drivers have been in a state of flux lately, and there have been driver regressions in (at least) the FBO codepath that affect the OpenGL-based Java2D pipeline and the Java2D/JOGL bridge. Those companies run an automated testsuite provided by Sun that exercises these codepaths, but unfortunately it still seems that regression bugs have crept through. We’re continuing to work with those driver teams to address these issues, but we don’t know yet when those fixes will appear in production.

If running via the command line, you can try passing -Dsun.java2d.opengl.fbobject=false in addition to the usual -Dsun.java2d.opengl=True and see if that helps.

Also, could you post the driver versions with which you’ve had trouble?

Thanks,
Chris