opensuse@opensuse.org schrieb am 27.12.05 15:50:02:

On Tue, 2005-12-27 at 15:08 +0100, Christian Lange wrote:

...

Hi

I have installed Suse 10.0 this morning. Everything worked fine. My Graphics card is "NVidia GeForce 2 Ti". Since the "nv" driver that is built into Suse doesn´t support 3D, and the nvidia-driver, which I can download using YAST, does not do anything at all (big *slap* for the Suse developers),

And what makes you think it does nothing? Works fine for probably everybody else. Just take a look at the frame rate difference between the two.

I can antivate it for download in YAST, but after downloading, Suse still uses nv, even after a reboot. A friend of mine also hast Suse 10.0 and a NVidia Geforce FX something, and the Suse NVidia drivers are working fine for his card. Just not for mine.

...

I decided to download and install the original NVidia driver. So I got "NVIDIA-Linux-x86-1.0-7174-pkg1.run" (later versions do not support the GeForce2 Ti any more - I don´t know why). "sh NVIDIA-Linux-x86-1.0-7174-pkg1.run -q" installed the driver, a kernel module was built, successful. Afterward, i executed "sax2 -m 0=nvidia" to configure my screen. 3D Support was available at this point and I was happy. :) But after a reboot, the driver didn´t work anymore. I searched the internet and found out that I have to modify the /etc/udev/static-devices.txt and add these lines: nvidia0 c 195 0 666 nvidia1 c 195 1 666 nvidia2 c 195 2 666 nvidia3 c 195 3 666 nvidia4 c 195 4 666 nvidia5 c 195 5 666 nvidia6 c 195 6 666 nvidia7 c 195 7 666 nvidiactl c 195 255 666 Now everything was working fine, event a reboot could not destroy the diver module.

Then, I made an online update using YAST. Since I have done this update, the nvidia driver doesn´t work anymore (I could use "nv" instead, but this does not provide 3D-Support). dmesg told my something about it, and I think the important lines are: nvidia: module not supported by Novell, setting U taint flag. nvidia: module license 'NVIDIA' taints kernel.

This is -not- an unusual occurrence. The VMware modules do the same thing.

...

nvidia: Unknown parameter `NVreg_DeviceFileUID'

What is this? How can the module "taint" the kernel? A new installation of the driver doesn´t solve the problem.

Thanks, Chris

======================== Full dmesg:

It was -NOT- necessary to send the entire dmesg output to only show that the module "taints" the kernel.

...

nvidia: module not supported by Novell, setting U taint flag. nvidia: module license 'NVIDIA' taints kernel. nvidia: Unknown parameter `NVreg_DeviceFileUID'

...

nvidia: module not supported by Novell, setting U taint flag. nvidia: Unknown parameter `NVreg_DeviceFileUID'

...

nvidia: module not supported by Novell, setting U taint flag. nvidia: Unknown parameter `NVreg_DeviceFileUID'

-- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998

--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-help@opensuse.org

__________________________________________________________________ Nur bis 31.12.: 1&1 DSL mit WEB.DE Preisvorteil! Jetzt einsteigen und die Vorteile sichern! http://1und1dsl.web.de/?mc=021130