On Fri, Dec 19, 2003 at 07:44:49PM -0500, Matt Price wrote: > Hey Folks, > > now that there are patches for the nvidia non-free drivers > (http://home.comcast.net/~andrex/nvidia-2.6-Debian/) I used this method, but had to "export KERNDIR=/usr/src/linux-2.6.0" to successfully compile the nvidia kernel. By the way, after installing 2.6.0 kernel and nvidia-kernel and rebooting, I found that loading the nvidia kernel resulted in thousands of messages in /var/log/kern.log and /var/log/messages such as: Dec 20 21:25:30 alph kernel: Badness in pci_find_subsys at drivers/pci/search.c:132 Dec 20 21:25:30 alph kernel: Call Trace: Dec 20 21:25:30 alph kernel: [pci_find_subsys+199/208] pci_find_subsys+0xc7/0xd0 Dec 20 21:25:30 alph kernel: [pci_find_device+47/64] pci_find_device+0x2f/0x40 Dec 20 21:25:30 alph kernel: [pci_find_slot+40/80] pci_find_slot+0x28/0x50 Dec 20 21:25:30 alph kernel: [__crc_enable_lapic_nmi_watchdog+4242015/8192632] os_pci_init_handle+0x39/0x70 [nvidia] Dec 20 21:25:30 alph kernel: [__crc_enable_lapic_nmi_watchdog+3017093/8192632] __nvsym00057+0x1f/0x24 [nvidia] Dec 20 21:25:30 alph kernel: [__crc_enable_lapic_nmi_watchdog+3886145/8192632] __nvsym04236+0x1f/0x24 [nvidia] After a few minutes of this, I calculate that loading the nvidia kernel will generate about 1.4G of log messages per day. I haven't figured out a solution to this yet. > I'm trying to > upgrade to 2.6.0 on my workstation. The instructions at the above > link are quite clear and helpful, but I'm having trouble compiling > the NVIDIA drivers nonetheless. I've apt-getted all the necessary > nvidia-related packages, applied the patches as instructed, and run > > make-kpkg clean && make-kpkg --append-to-version=-nondebian1 kernel-image > > without any evident problems (there are some minor error messages, and > I think there may be some problems with the kernel; until I get the > nvidia drivers to compile, I don't want to try it out, as X won't work > without them). > > Anyway, then I run: > make-kpkg --append-to-version=-nondebian1 modules-image > > and get the following response: > > You appear to be compiling the NVIDIA kernel module with > a compiler different from the one that was used to compile > the running kernel. We are going to use the compiler that > were used to build the kernel with the specified headers. > (if specified in KSRC/include/linux/compile.h) > Using compiler gcc > touch /usr/src/modules/nvidia-kernel/nv/gcc-check > IGNORE_CC_MISMATCH=1 CC=gcc /usr/bin/make -C > /usr/src/modules/nvidia-kernel/nv > SYSINCLUDE=/usr/src/linux-2.6.0/include module > cat: /lib/modules/2.4.18-586-demudi/build/Makefile: No such file or > directory > cat: /lib/modules/2.4.18-586-demudi/build/Makefile: No such file or > directory > cat: /lib/modules/2.4.18-586-demudi/build/Makefile: No such file or > directory > make[2]: Entering directory `/usr/src/modules/nvidia-kernel/nv' > make: *** /lib/modules/2.4.18-586-demudi/build: No such file or > directory. Stop. > make: Entering an unknown directorymake: Leaving an unknown > directorynvidia.ko failed to build! > make[2]: *** [module] Error 1 > make[2]: Leaving directory `/usr/src/modules/nvidia-kernel/nv' > make[1]: *** [build-stamp] Error 2 > make[1]: Leaving directory `/usr/src/modules/nvidia-kernel' > Module /usr/src/modules/nvidia-kernel failed. > > 2.4.18-586-demudi is my currently-running kernel. For some reason the > nvidia sources want to access something from the running kernel! > anyone know how to make them NOT do that? > > Anyway, thanks much for your help. > > best, > > matt > > > -- > To UNSUBSCRIBE, email to debian-user-request@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org > -- Jerome
Attachment:
pgp7NZgnpde1p.pgp
Description: PGP signature