Little big problem with nvidia-kernel : Building modules, stage 2. make -rR -f /usr/src/linux-2.6.16.2/scripts/Makefile.modpost scripts/mod/modpost -i /usr/src/linux-2.6.16.2/Module.symvers -I /var/tmp/portage/nvidia-kernel-1.0.8762-r1/work/NVIDIA-Linux-x86-1.0-8762-pkg1/usr/src/nv/Modules.symvers -o /var/tmp/portage/nvidia-kernel-1.0.8762-r1/work/NVIDIA-Linux-x86-1.0-8762-pkg1/usr/src/nv/Modules.symvers vmlinux /var/tmp/portage/nvidia-kernel-1.0.8762-r1/work/NVIDIA-Linux-x86-1.0-8762-pkg1/usr/src/nv/nvidia.o FATAL: modpost: GPL-incompatible module nvidia.ko uses GPL-only symbol 'lockdep_init_map' make[3]: *** [__modpost] Erreur 1 make[2]: *** [modules] Erreur 2 NVIDIA: left KBUILD. nvidia.ko failed to build! make[1]: *** [mdl] Erreur 1 make: *** [module] Erreur 2 !!! ERROR: media-video/nvidia-kernel-1.0.8762-r1 failed. Call stack: ebuild.sh, line 1545: Called dyn_compile ebuild.sh, line 940: Called src_compile ebuild.sh, line 1254: Called linux-mod_src_compile linux-mod.eclass, line 515: Called die !!! Unable to make IGNORE_CC_MISMATCH=yes V=1 SYSSRC=/usr/src/linux SYSOUT=/usr/src/linux clean module. the error " FATAL: modpost: GPL-incompatible module nvidia.ko uses GPL-only symbol 'lockdep_init_map' " is strange ... I have 2.6.18-rc1 kernel (uname -r saays that), but my kernel sources are in /usr/src/linux-2.6.16.2/ ....
I've found this patch, give it a try. ;) http://dev.gentoo.org/~kingtaco/patch-2.6.18-rc1-no-zealot-gpl-checks.diff
That patch will not help, it will still fail to load at runtime. The solution is to not build lockdep into your kernel. Some directionless discussion here: http://lkml.org/lkml/2006/7/4/247
done use my patch, it will fail at runtime. instead, make sure that CONFIG_PROVE_LOCKING is turned off. package maintainers should probably add a check for this and die() if the code makes it's way into 2.6.18
Did the code make it into 2.6.18?
nvidia-drivers emerges just fine here w/ 2.6.18 (1.0.8774 and 1.0.9625) so this can be closed.
I have no clue what code to use... so how about FIXED? ;]
(In reply to comment #5) > nvidia-drivers emerges just fine here w/ 2.6.18 (1.0.8774 and 1.0.9625) so this > can be closed. > The bug only ever manifested itself if you enabled lockdep in the kernel config. But yes, let's close this unless there are further reports.
# zgrep LOCKDEP /proc/config.gz CONFIG_LOCKDEP_SUPPORT=y Either the kernel changed, or nVidia worked around this.
CONFIG_PROVE_LOCKING was the item in question.. LOCKDEP_SUPPORT is unconditionally enabled on all architectures which can possibly support lock dependency checking