I first downloaded 'NVIDIA-Linux-x86-1.0-6629-pkg1.run'.
I run it and the installer starts. But when my kernel module is 100% build, my computer freezes.

This is my nvidia-installer.log:

nvidia-installer log file '/var/log/nvidia-installer.log'
creation time: Tue Nov 23 00:00:44 2004

option status:
license pre-accepted : false
update : false
force update : false
expert : false
uninstall : false
driver info : false
no precompiled interface: false
no ncurses color : false
query latest driver ver : false
OpenGL header files : false
no questions : false
silent : false
no backup : false
kernel module only : false
sanity : false
add this kernel : false
no runlevel check : false
no network : false
no ABI note : false
no RPMs : false
force tls : (not specified)
force compat32 tls : (not specified)
X install prefix : /usr/X11R6
OpenGL install prefix : /usr
compat32 install prefix : (not specified)
installer install prefix: /usr
utility install prefix : /usr
kernel name : (not specified)
kernel include path : (not specified)
kernel source path : (not specified)
kernel output path : (not specified)
kernel install path : (not specified)
proc mount point : /proc
ui : (not specified)
tmpdir : /tmp
ftp mirror : ftp://download.nvidia.com
RPM file list : (not specified)

Using: nvidia-installer ncurses user interface
-> License accepted.
-> There appears to already be a driver installed on your system (version: 1.0-
5336). As part of installing this driver (version: 1.0-6629), the existing
driver will be uninstalled. Are you sure you want to continue? ('no' will a
bort installation) (Answer: Yes)
-> No precompiled kernel interface was found to match your kernel; would you li
ke the installer to attempt to download a kernel interface for your kernel f
rom the NVIDIA ftp site (ftp://download.nvidia.com)? (Answer: Yes)
-> No matching precompiled kernel interface was found on the NVIDIA ftp site;
this means that the installer will need to compile a kernel interface for
your kernel.
-> Kernel source path: '/usr/src/linux'
-> Performing CC test with CC="cc".
-> Performing rivafb check.
-> Performing rivafb module check.
WARNING: Your kernel was configured to include rivafb support as
a loadable kernel module.

The rivafb driver conflicts with the NVIDIA driver; the
NVIDIA kernel module will still be built and installed,
but be aware that the NVIDIA driver will not be able to
function properly if the rivafb module is loaded!
-> Cleaning kernel module build directory.
executing: 'cd ./usr/src/nv; make clean'...
rm -f -f nv.o nv-vm.o os-agp.o os-interface.o os-registry.o nv.o nv-vm.o os-
agp.o os-interface.o os-registry.o nvidia.mod.o
rm -f -f build-in.o nv-linux.o *.d .*.{cmd,flags}
rm -f -f nvidia.{o,ko,mod.{o,c}} nv_compiler.h *~
rm -f -rf .tmp_versions
-> Building kernel module:
executing: 'cd ./usr/src/nv; make module SYSSRC=/usr/src/linux SYSOUT=/usr/s
rc/linux'...
Your kernel was configured to include rivafb support as
a loadable kernel module.

The rivafb driver conflicts with the NVIDIA driver; the
NVIDIA kernel module will still be built and installed,
but be aware that the NVIDIA driver will not be able to
function properly if the rivafb module is loaded!

*** Failed rivafb module sanity check, but continuing! ***


NVIDIA: calling KBUILD...
make CC=cc KBUILD_VERBOSE=1 -C /usr/src/linux SUBDIRS=/tmp/selfgz4451/NVIDI
A-Linux-x86-1.0-6629-pkg1/usr/src/nv modules
CHK include/linux/version.h
*** Warning: Overriding SUBDIRS on the command line can cause
*** inconsistencies
mkdir -p /tmp/selfgz4451/NVIDIA-Linux-x86-1.0-6629-pkg1/usr/src/nv/.tmp_vers
ions
make -f scripts/Makefile.build obj=scripts/basic
make -f scripts/Makefile.build obj=scripts
make -f scripts/Makefile.build obj=scripts/genksyms
make -f scripts/Makefile.build obj=arch/i386/kernel arch/i386/kernel/asm-off
sets.s
cc -Wp,-MD,arch/i386/kernel/.asm-offsets.s.d -nostdinc -iwithprefix includ
e -D__KERNEL__ -Iinclude -D__KERNEL__ -Iinclude -Wall -Wstrict-prototype
s -Wno-trigraphs -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-bo
undary=2 -funit-at-a-time -funit-at-a-time -march=i586 -mregparm=3 -Iinclude
/asm-i386/mach-default -O2 -fomit-frame-pointer -DKBUILD_BASENAME=asm_of
fsets -DKBUILD_MODNAME=asm_offsets -S -o arch/i386/kernel/asm-offsets.s arch
/i386/kernel/asm-offsets.c
CHK include/asm-i386/asm_offsets.h
make -f scripts/Makefile.build obj=/tmp/selfgz4451/NVIDIA-Linux-x86-1.0-6629
-pkg1/usr/src/nv
echo \#define NV_COMPILER \"`cc -v 2>&1 | tail -n 1`\" > /tmp/selfgz4451/NVI
DIA-Linux-x86-1.0-6629-pkg1/usr/src/nv/nv_compiler.h
cc -Wp,-MD,/tmp/selfgz4451/NVIDIA-Linux-x86-1.0-6629-pkg1/usr/src/nv/.nv.o
.d -nostdinc -iwithprefix include -D__KERNEL__ -Iinclude -D__KERNEL__ -Iin
clude -Wall -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-c
ommon -pipe -mpreferred-stack-boundary=2 -funit-at-a-time -funit-at-a-time -
march=i586 -mregparm=3 -Iinclude/asm-i386/mach-defaul
t -O2 -fomit-frame-pointer -I/tmp/selfgz4451/NVIDIA-Linux-x86-1.0-6629-pkg1
/usr/src/nv -Wall -Wimplicit -Wreturn-type -Wswitch -Wformat -Wchar-subscrip
ts -Wparentheses -Wpointer-arith -Wno-multichar -Werror -O -fno-common -MD
-Wno-cast-qual -Wno-error -D_LOOSE_KERNEL_NAMES -D__KERNEL__ -DMODULE -DN
TRM -D_GNU_SOURCE -D_LOOSE_KERNEL_NAMES -D__KERNEL__ -DMODULE -DNV_MAJOR_VE
RSION=1 -DNV_MINOR_VERSION=0 -DNV_PATCHLEVEL=6629 -DNV_UNIX -DNV_LINUX
-DNV_INT64_OK -DNVCPU_X86 -UDEBUG -U_DEBUG -DNDEBUG -DNV_REMAP_PAGE_R
ANGE_5 -DNV_CHANGE_PAGE_ATTR_PRESENT -DNV_PCI_DISABLE_DEVICE_PRESENT -DNV_CL
ASS_SIMPLE_CREATE_PRESENT -DMODULE -DKBUILD_BASENAME=nv -DKBUILD_MODNAME=nv
idia -c -o /tmp/selfgz4451/NVIDIA-Linux-x86-1.0-6629-pkg1/usr/src/nv/.tmp_nv
.o /tmp/selfgz4451/NVIDIA-Linux-x86-1.0-6629-pkg1/usr/src/nv/nv.c


I figured, because it's 100%, that it was done. So I rebooted and made the necessary changes to my XF86config. But when I execute programs, for example DrScheme (an interpreter for the Scheme language), I get the following error multiple times:

Xlib: extension "GLX" missing on display ":0.0".

Is there a good reason you are installing the driver manually and not using YOU (YaST Online Update) to install the nVidia driver? If you open up the update it will install the drive as well as check dependencies, then all you have to do is enable 3D in SaX and restart X, you should be good to go.

Because I was told, it says also so in Yast, that Suse cannot include the Nvidia drivers because of copyright issues.

'XFree86-server-glx - GLX extension and nvidia dummy driver

This is the GLX extension and the nvidia dummy driver for the Xserver'

So because my DVD playback is choppy, I wanted to try installing the official NVIDIA drivers.

The drivers are not included on the disks because of copyright issues, but if you start up YaST Online Update and scroll down to the bottom you will see an option in black text to install nVidia drivers. check it and click OK it will download a SuSE compiled driver after you agree to the nVidia license. Though you may see a slight increase in DVD speeds the nVidia drivers most likely wont help out a whole lot. Most of the jumpyness is because (Last time I checked) the DVD player in Linux, especially when using libdvdcss, copies the DVD to your swapspace on you Hard Drive then then plays the decrypted version from your hard drive. So the slowness is caused by the read/write times of your HDD and your DVD drive as well as your over all system bus speeds. thats why the legality of libdvdcss is questionable because it copies the DVD to your HDD. Unfortunately until someone makes a real DVD program that adhears to the standards and rules set by hollywood the jumpyness is something that we'll just have to deal with. It also means that someone that has a screaming desktop system may not get much jumpyness while someone with a older system or a laptop, where both their DVD and HDD are on the same IDE cable will have poor playback.

Long answer short, use YOU to install nVidia drivers and to get the best playback possible make sure your HDD and DVD are not on the same IDE cable.

Should I first remove or uninstall anything that was installed via the NVIDIA installer?

I think you should, where SuSE has special install instructions for the driver they may place them somewhere different than the nVidia installer does and although it should'nt cause any issues it will be taking up Hard drive space.

Hello,

I think this installation is nicely described in the Suse nvidia installer howto, but there are some little problems maybe not covered.

What I found is the following (if you do it manually)

su

init 3

sh NVidia-istaller.... -q --kernel-source-path=/usr/src/linux (asuming you have the kernel source installed)

then do: depmod -a
modprobe Nvidia

and then: sax2 -m 0=nvidia

that should work

Easy to find out, you should get a splashscreen the next time your Xserver starts. And most likely your virtual terminals are broken, try alt+ctrl+F2 and see what you get, if it is unreadably you may want to change your menu.lst and add the appropriate vga=794 for 1280x1024 24 bit argument to your linux boot entry.

Hope this helps

christoph

Screen 640x480 800x600 1024x768 1280x1024 1600x1200
Colors --------------------------- -------------------------------------------
256 | 769 771 773 775 796
32,768 | 784 787 790 793 797
65,536 | 785 788 791 794 798
16.8M | 786 789 792 795 799

add some blank to this table to get it formatted

You can solve the jumpiness during dvd playback with the following command as root:

hdparm -d1 /dev/hdc

This will work as long as your dvd drive is actually /dev/hdc. It usually is.

Alternatively, use

YaST - Hardware - IDE DMA mode

and turn on DMA for the DVD drive. This does the same thing, with the benefit that it is still there when you reboot. (As has been said earlier in the thread, jumping when viewing DVDs is a problem with data transfer speed, not the video driver. DMA is off by default for CD and DVD drives.)

One very good reason one would not use YOU to install the NVidia drivers is because it does not work for all video cards and systems. Mine is one of those and I must manually install the drivers to get any 3D support. In my opinion you and yast still have a long way to go because it can be considered a good program.