Comment 2 for bug 610446

I'm also seeing this seg fault, particularly annoying because I would otherwise run Twinview. I've also tried the Nvidia packages

 NVIDIA-Linux-x86-96.43.16-pkg1.run
and
 NVIDIA-Linux-x86-96.43.18-pkg1.run

and also tried with the older kernel

 2.6.32-21-generic

 - no joy, except that, with the Nvidia 96.43.18 package, there is no seg fault, but instead, the log file ends with:

 ...
 (II) NVIDIA(0): Initialized GART.
 (II) NVIDIA(0): kernel module enabled successfully
 (II) NVIDIA(0): Memory mapped
 (EE) NVIDIA(0): Failed to allocate/map the primary surface!

That sort-of sounds like another driver is loaded, but no, there is no other driver loaded. Still, Xorg dmesg has this to say:

 [ 511.284620] Xorg:3820 conflicting memory types e8000000-e8d80000 write-combining<->uncached-minus
 [ 511.284626] reserve_memtype failed 0xe8000000-0xe8d80000, track write-combining, req write-combining

With 2.6.32-21 and 96.43.16, the log ends like this - with similarity to other combinations, "Segmentation fault at address 0xc":

...
(II) NVIDIA(0): Memory mapped
(II) NVIDIA(0): Using built-in logo image.

Backtrace:
0: /usr/bin/X (xorg_backtrace+0x3b) [0x80e937b]
1: /usr/bin/X (0x8048000+0x61c7d) [0x80a9c7d]
2: (vdso) (__kernel_rt_sigreturn+0x0) [0x7ad410]
Segmentation fault at address 0xc

Caught signal 11 (Segmentation fault). Server aborting

This is on an NV11 [GeForce2 MX/MX 400] dual display, with an AMD Sempron processor. I've also tried this same card and software on an older Athlon machine, but same results.