GeForce6600 + NVIDIA-x86_64-1.0-8756 + 2.6.16-1.2069_FC4 + twinview = kernel crash

[chopperboy]

Hi,

I am trying to get the 8756 twinview version running on the 2.6.16-1.2069-FC4 kernel, with not much success. The driver compiles and installs fine, but the machine hangs on X server startup. I'm attaching the pertinent log files. If anyone has a solution, I would greatly appreciate the help.

Thanks,
--MK

[netllama]

Are you able to test with analog, instead of digital (DVI) connections?

Thanks,
Lonni

[chopperboy]

Thank you for the prompt reply. Interesting suggestion, but, no, I can't bypass the DVI outputs. The graphics card is dual-DVI only. No analog VGA outputs.

[netllama]

The card itself doesn't need to have VGA outputs as long as your displays have them, and you have a DVI->VGA adapter. If so, then the nvidia driver will treat it as an analog CRT.

Thanks,
Lonni

[chopperboy]

Yeah, I have the adapters for both monitors. I'll give it a try later today, when I'm done working for the day. Is there something you expect to see in the trace that would help zero in on the problem, or is your suggestion more of a permanent workaround (if it works)? If it's the latter, it would be sad, because the reason I went with this card/chipset is to use the DVI with both screens...

Just for reference, the combination of 2.6.15-1.1833_FC4 kernel and the NVIDIA-Linux-x86_64-1.0-8178 driver works fine with my dual-DVI configuration. (That's what I downgraded back to now.) The NVIDIA-Linux-x86_64-1.0-8756 fails on both the 2.6.15 and the 2.6.16 series kernels in the same way, and the NVIDIA-Linux-x86_64-1.0-8178 driver does not install on the 2.6.16 kernel.

Thanks,
Maciek K

[netllama]

Analog would be a temporary workaround.

Thanks,
Lonni

[chopperboy]

If this is a workaround, rather than a step towards finding and fixing the bug, I'll temporaily stay with the 2.6.15-1.1833_FC4 kernel and the NVIDIA-Linux-x86_64-1.0-8178 driver, because the dual DVI screens are so much sharper and easier on the eyes than analog.

Is the problem that I'm having a known issue by now? I browsed the forums earlier, and did not find a match for the issue I'm seeing, so I thought that maybe I could help expose something new that would lead to a fix. But, if this is a known issue, then I appreciate your workaround suggestion, and I look forward to a fix sometime.

Best,
Maciek K

[netllama]

If switching to analog fixes the problem, then yes, this is a known issue. If switching to analog does not fix the problem, then this isn't a known issue.

Thanks,
Lonni