Go Back   nV News Forums > Linux Support Forums > NVIDIA Linux

Newegg Daily Deals

Reply
 
Thread Tools
Old 11-07-10, 02:46 PM   #13
ariekenb
Registered User
 
Join Date: Oct 2010
Posts: 10
Default Re: 260.xx drivers break Java2D OpenGL pipeline

danix/others - any updates on this issue? Has a bug been filed for this problem? Thanks!
ariekenb is offline   Reply With Quote
Old 11-24-10, 04:34 PM   #14
ariekenb
Registered User
 
Join Date: Oct 2010
Posts: 10
Default Re: 260.xx drivers break Java2D OpenGL pipeline

I tried the latest 260.19.21 drivers. With these the crashing-on-exit problem seems to be fixed. However the original problem with -Dsun.java2d.opengl=true still exists:

1. If I just set -Dsun.java2d.opengl=true, I see all swing frames are empty - no widgets are drawn (see empty_java2d_opengl_window).

2. If I set -Dsun.java2d.opengl=true and -Dsun.java2d.opengl.fbobject=false (disable frame buffer objects) this works around problem #1 and widgets are displayed (although this has known performance impacts)
ariekenb is offline   Reply With Quote
Old 12-16-10, 07:59 AM   #15
KDE
Registered User
 
Join Date: Nov 2007
Posts: 50
Default Re: 260.xx drivers break Java2D OpenGL pipeline

Swing apps like Netbeans have still empty windows with 260.19.29
KDE is offline   Reply With Quote
Old 12-30-10, 12:29 PM   #16
ariekenb
Registered User
 
Join Date: Oct 2010
Posts: 10
Default Re: 260.xx drivers break Java2D OpenGL pipeline

I can also confirm this bug still exists with the 260.19.29 drivers on 64-bit linux:

1. If I just set -Dsun.java2d.opengl=true, I see all swing frames are empty - no widgets are drawn (see empty_java2d_opengl_window).

2. If I set -Dsun.java2d.opengl=true and -Dsun.java2d.opengl.fbobject=false (disable frame buffer objects) this works around problem #1 and widgets are displayed (although this has known performance
impacts)
ariekenb is offline   Reply With Quote
Old 12-31-10, 03:07 PM   #17
naib
Registered User
 
Join Date: Nov 2004
Posts: 8
Default Re: 260.xx drivers break Java2D OpenGL pipeline

Ill add my 2cents

The latest 260.19.29 are an improvement from when the 260.x line 1st come out BUT 3D applications still crash for me
I am also 64bit so I wonder if something went amiss in the 64bit build
naib is offline   Reply With Quote
Old 01-01-11, 12:49 PM   #18
mdeggers
Registered User
 
Join Date: Apr 2003
Posts: 17
Default Re: 260.xx drivers break Java2D OpenGL pipeline

I can confirm this on a 32 bit system.

Environment (old system):

Fedora 14: 2.6.35.10-74.fc14.i686
JDK/JRE: 1.6.0_23
NetBeans: 6.9.1
Video: 7600 GS
Driver: 260.19.29

Run NetBeans with -J-Dsun.java2d.opengl=true and just an empty frame is displayed.

Run NetBeans with -J-Dsun.java2d.opengl=true -J-Dsun.java2d.opengl.fbobject=false and everything works as expected (but with an obvious performance impact).
mdeggers is offline   Reply With Quote
Old 02-22-11, 02:45 AM   #19
oyvind
Registered User
 
Join Date: May 2004
Location: Norway
Posts: 117
Default Re: 260.xx drivers break Java2D OpenGL pipeline

Still missing widgets with nvidia 270.26, JDK 1.6u24 x86-64 when using Java2D OpenGL-pipeline.
oyvind is offline   Reply With Quote
Old 05-14-11, 01:43 AM   #20
Lauwenmark78
Registered User
 
Join Date: Mar 2005
Posts: 33
Default Re: 260.xx drivers break Java2D OpenGL pipeline

The problem is still present in 270.41 with JDK 1.6u25 on an x86-64 system.
__________________
CPU: AMD Athlon 3500+, MB: Asus A8N-SLI Deluxe (BIOS rev.1014), GFX:: Point-of-View 6600GT 128MB, Mem: 2x512MB DDR400 Kingston CL2.5, HDDs: 2x80GB Maxtor DiamondMax SATA + 1x160GB Hitachi/IBM SATA, OS:Windows Xp Pro Sp2 fr/ForceWare 78.05, Debian Linux AMD64 Sid/NVIDIA-7676
Lauwenmark78 is offline   Reply With Quote

Old 05-14-11, 05:56 PM   #21
mdeggers
Registered User
 
Join Date: Apr 2003
Posts: 17
Default Re: 260.xx drivers break Java2D OpenGL pipeline

Still broken with 260.19.44 / JDK 1.6.0_24 / NetBeans 6.9.1.

Launching with -J-Dsun.java2d.opengl=true results in an empty frame.
mdeggers is offline   Reply With Quote
Old 05-21-11, 03:31 PM   #22
DeiF
Registered User
 
Join Date: Oct 2008
Posts: 114
Default Re: 260.xx drivers break Java2D OpenGL pipeline

I don't know if this is the same bug, but I've tested 275.09 with JOSM, with these command lines:

Code:
java -jar josm-tested.jar
No problems, but slow (see first screenshot).


Code:
java -Dsun.java2d.opengl=True -Dsun.java2d.opengl.fbobject=false -jar josm-tested.jar
and
Code:
java -Dsun.java2d.opengl=True -jar josm-tested.jar
Both produce a window with no icons or text (see 2nd screenshot attached).
In the command line I see this additional message "OpenGL pipeline enabled for default config on screen 1".
On closing the app I see this error too: "Inconsistency detected by ld.so: dl-close.c: 741: _dl_close: Assertion `map->l_init_called' failed!"
Attached Thumbnails
Click image for larger version

Name:	josm-software-rendering.png
Views:	84
Size:	51.3 KB
ID:	42811  Click image for larger version

Name:	josm-opengl.png
Views:	87
Size:	28.4 KB
ID:	42812  
Attached Files
File Type: gz nvidia-bug-report.log.gz (63.4 KB, 60 views)
DeiF is offline   Reply With Quote
Old 06-03-11, 02:47 AM   #23
Lauwenmark78
Registered User
 
Join Date: Mar 2005
Posts: 33
Default Re: 260.xx drivers break Java2D OpenGL pipeline

Quote:
Originally Posted by DeiF View Post
I don't know if this is the same bug, (...)On closing the app I see this error too: "Inconsistency detected by ld.so: dl-close.c: 741: _dl_close: Assertion `map->l_init_called' failed!"
The "Assertion failed" part is not - I don't get that one. However, the window redrawing issue is.

FBO support in the Nvidia driver has been buggy in regards to the Java2D pipeline at least since 2006, so I wouldn't count on seeing a fix for this in short or medium-term, seeing the very active returns we get on this issue from the Nvidia developers...
__________________
CPU: AMD Athlon 3500+, MB: Asus A8N-SLI Deluxe (BIOS rev.1014), GFX:: Point-of-View 6600GT 128MB, Mem: 2x512MB DDR400 Kingston CL2.5, HDDs: 2x80GB Maxtor DiamondMax SATA + 1x160GB Hitachi/IBM SATA, OS:Windows Xp Pro Sp2 fr/ForceWare 78.05, Debian Linux AMD64 Sid/NVIDIA-7676
Lauwenmark78 is offline   Reply With Quote
Old 06-12-11, 12:50 PM   #24
mdeggers
Registered User
 
Join Date: Apr 2003
Posts: 17
Default Re: 260.xx drivers break Java2D OpenGL pipeline

Quote:
Originally Posted by ariekenb View Post
I can also confirm this bug still exists with the 260.19.29 drivers on 64-bit linux:

1. If I just set -Dsun.java2d.opengl=true, I see all swing frames are empty - no widgets are drawn (see empty_java2d_opengl_window).

2. If I set -Dsun.java2d.opengl=true and -Dsun.java2d.opengl.fbobject=false (disable frame buffer objects) this works around problem #1 and widgets are displayed (although this has known performance
impacts)
This seems to be fixed for me.

Environment
--------------
Hardware: 7600 GS (overclocked)
Driver: 275.09.04 (beta)
OS: Fedora 15
Windowing System: KDE 4.6.3
JDK: 1.6.0_24

I tested NetBeans 6.9.1 with the default metal theme, Nimbus theme, and GTK theme by running:

/opt/netbeans-6.9.1/bin/netbeans --laf <look-and-feel-abbreviation> \
-J-Dsun.java2d.opengl=true

I've not tried Gnome 3 or WindowMaker yet, but I don't expect any differences.

. . . . just my two cents.

/mde/
mdeggers is offline   Reply With Quote
Reply


Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


All times are GMT -5. The time now is 10:27 PM.


Powered by vBulletin® Version 3.7.1
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Copyright 1998 - 2014, nV News.