RH8.0 + GeForce3 + AMD Athlon = Segmentation fault

[thot]

Hi Guys,

I've installed the following drivers on my machine:
NVIDIA_kernel-1.0-3123.src.rpm
NVIDIA_GLX-1.0-3123.src.rpm

I've followed all the steps and guidelines, and it is working quite nicely, except....

... except when I am trying to use OpenGL in my programs. Then, it is always the same, it ends up with a segmentation fault saying

Program received signal SIGSEGV, Segmentation fault.
0x407712c4 in __nvsym14770 () from /usr/lib/libGLcore.so.1.0.3123

So apparently there is a problem in this libGL library which is the result of the corresponding driver 3123.

Anyone has an idea?

Just to let you know that this is not the program's fault, I did exactly the same thing on my IBM/intel laptop equipped with an ATI card, and it worked without complaining.

Thank you for your help

Thot

[bwkaz]

libGLcore.so is a part of the NVIDIA_GLX package.

See if changing driver versions helps. What are you doing in the programs that causes this? i.e. which program line is the segfault happening on? What do you get on a gdb backtrace?

[thot]

:confused:
What do you mean by changing driver version?
There is no newer version of the rpms which are available for my machine (AMD Athlon + GeForce).
The latest drivers given by nvidia website are the 4180, and they don't work on my system.
Should I go back in time to older versions?
Where can I get them?

As for the gdb backtrace, this is exactly what I gave you in the last post. I am using gdb to debug it, and there is no other information that I can backtrace.

The process ends in __nvsym14770 () from /usr/lib/libGLcore.so.1.0.3123

Just to give you a possible clue about what is going on, this happens when I try to represent a (not so) huge number of triangles. But I cannot send images on this forum.

Anyway, thank you for your interest.

Thot

[bwkaz]

DON'T use 4180!!

4191 is the latest version (and is 11 builds later than 4180 in any case... ;)). But 4180 isn't even for your processor; it's for the AMD Hammer 64-bit processors that haven't even been released yet.

Yes, I was thinking try an older (version 3123) driver.

How many triangles can you get on the screen before it segfaults? Any specific number?