nV News Forums

 
 

nV News Forums (http://www.nvnews.net/vbulletin/index.php)
-   NVIDIA Linux (http://www.nvnews.net/vbulletin/forumdisplay.php?f=14)
-   -   9629 & glxinfo segfault (http://www.nvnews.net/vbulletin/showthread.php?t=79703)

Hannibal 11-07-06 02:09 PM

9629 & glxinfo segfault
 
1 Attachment(s)
Upgrade to 9629 cause glxinfo to segfault on Ti4200. On this same machine with 6600 it works. I've attach strace info.

netllama 11-07-06 02:40 PM

Re: 9629 & glxinfo segfault
 
Please generate and post an nvidia-bug-report.log.

Thanks,
Lonni

Hannibal 11-07-06 02:45 PM

Re: 9629 & glxinfo segfault
 
1 Attachment(s)
As you wish :)

PS. Glxgears and other opengl apps also crash

netllama 11-07-06 03:11 PM

Re: 9629 & glxinfo segfault
 
Does this problem persist if you're not using the Composite extension?

Hannibal 11-07-06 03:27 PM

Re: 9629 & glxinfo segfault
 
Yes

piotrq__ 11-07-06 03:33 PM

Re: 9629 & glxinfo segfault
 
1 Attachment(s)
Same here :(
Running SuSE 10.1 + X.Org 7.1 on a GF3 and getting segfault with beryl/glxinfo/glxgears...
Bug-report attached.

netllama 11-07-06 04:15 PM

Re: 9629 & glxinfo segfault
 
I've reproduced this problem, and opened bug 266033.

Thanks,
Lonni

reggaemanu 11-07-06 04:23 PM

Re: 9629 & glxinfo segfault
 
1 Attachment(s)
Same card, same problem...
Driver 9626 worked perfectly.

ook4mi 11-08-06 08:46 AM

Re: 9629 & glxinfo segfault
 
1 Attachment(s)
Same problem here on a GeForce Ti4800SE, worked fine on 9625.

netllama 11-08-06 10:59 AM

Re: 9629 & glxinfo segfault
 
This bug is specific to graphics cards with NV2x GPUs. It will be fixed in a future driver release. The current recommended workaround is to downgrade to 1.0-9626 or 1.0-8776.

Thanks,
Lonni

reggaemanu 11-08-06 04:59 PM

Re: 9629 & glxinfo segfault
 
is it fixed in 9742 ?

piotrq__ 11-08-06 06:52 PM

Re: 9629 & glxinfo segfault
 
I think that the only change in that 9742 release was G80 support so there's no point in installing them. Besides there were no significiant changes/improvements/fixes since 9626 (at least I don't know about anything revelant), so I think we can stick with 9626, we won't loose anything important.


All times are GMT -5. The time now is 11:50 AM.

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