Segfault: RHEL 3 / 1.0-8756 driver

[hijinx]

Hardware:
Quadro FX3000 (AGP, VBIOS 04.35.20.23.08, VMEM, 256Mb)
Dual CPU Intel Xeon 2.40GHz

Original working configuration:
OS: Red Hat Enterprise Linux 3
Kernel: 2.4.20-6 (with SMP)
Video Driver: 1.0-5341

Goal:
Update graphics driver to latest version (1.0-8756)

Problem:
X11 segfaults (sig11) on start up.

Attached are two files. The first, 'startx.log' is the redirected output of the startx command. The second, 'XFree86.0.log' is of course the start log generated by X.

Any help in regards to the segfault problem would be greatly appreciated. I'd be happy to provide more information as its requested.

-----
edit: attached the nvidia-bug-report.log (zipped)

[netllama]

Please generate and post an nvidia-bug-report.log. Additionally, please verify that your RHEL3 installation is up to date.

Thanks,
Lonni

[hijinx]

Lonni,

I've posted the nvidia-bug-report.log (zipped as it exceed 100kb). Much to my chagrin, keeping these RHEL3 boxes up to date is almost impossible for political reasons. They operate in a lab that has a platform consistency requirement. Given the choice I'd be using a modern distribution, and an up to date kernel, but that currently isn't my call.

[netllama]

Looking at your bug report, this isn't RHEL3 you're running but RH9.

I'm guessing that if you comment out the glx module in your X configuration, then X will start?

You can also try to (re)install the driver with the --force-tls option set to new or classic and see if that has any impact.

Thanks,
Lonni

[hijinx]

Indeed, you are correct, it is a RH9 box. I was mistaken.

Reinstalling with either of the "--force-tls" options elicits the same behavior as if the option hadn't been specified.

With glx disabled, X will start, but no GL applications will run. Leaving glx enabled, a starting X gives me:
"XIO: fatal IO error 104 (Connection reset by peer) on X server ":0.0" after 0 requests (0 known processed) with 0 events remaining.

[netllama]

I'm not able to reproduce this in a RH9 installation that I have here, so I suspect something in your environment is causing the problem.

Its expected that OpenGL applications will fail to work without the glx module.

[hijinx]

Originally Posted by netllama

I'm not able to reproduce this in a RH9 installation that I have here, so I suspect something in your environment is causing the problem.

Could it be a result of the installation not being at all updated?

Originally Posted by netllama

Its expected that OpenGL applications will fail to work without the glx module.

I figured :]

[netllama]

My RH9 installation is not updated and isn't experiencing this problem. I'm not sure why its failing on your system. Is the environment customized in any way from a fresh RH9 installation?

-Lonni

[hijinx]

Unfortunately, I inherited this machine so I'll have a tough time ever confirming what (if anything) might have changed the system. Personally, I've installed a number of small apps (firefox, gaim, etc) as well as the software thats being developed on this machine. Its a OpenGL based app that shouldn't ever change the core of the installation in any way. I've also updated module-init-tools, but I've had the same trouble with the NV drivers prior to their update.

Additionally I've been told that no drivers newer than 1.0-5341 have ever worked on these machines. (Dell 650, RH9)