check Additional Information Reproducible: Always Steps to Reproduce: 1.emerge =nvidia-kernel-1.0.6629 2.modprobe nvidia 3. Actual Results: /lib/modules/2.4.28/video/nvidia.o: /lib/modules/2.4.28/video/nvidia.o: unresolv ed symbol preempt_disable /lib/modules/2.4.28/video/nvidia.o: /lib/modules/2.4.28/video/nvidia.o: unresolv ed symbol preempt_enable /lib/modules/2.4.28/video/nvidia.o: Hint: You are trying to load a module without a GPL compatible license and it has unresolved symbols. The module may be trying to access GPLONLY symbols but the problem is more likely to be a coding or user error. Contact the module supplier for assistance, only they can help you. /lib/modules/2.4.28/video/nvidia.o: insmod /lib/modules/2.4.28/video/nvidia.o fa iled /lib/modules/2.4.28/video/nvidia.o: insmod nvidia failed 2.4.2x users should just comment some epatch lines in ebuild, probably just the preempt one #epatch ${FILESDIR}/${PV}/conftest_koutput_includes.patch # Fix pgd_offset() -> pml4_pgd_offset() for >=2.6.10-rc1-mm3 #epatch ${FILESDIR}/${PV}/nv-pgd_offset.patch # Speedup driver for 2.6 kernel to be on par with 2.4 kernel #epatch ${FILESDIR}/${PV}/nv-pgprot-speedup.patch # Fix the vm_flags to only have VM_IO, and not VM_LOCKED as well #epatch ${FILESDIR}/${PV}/nv-vm_flags-no-VM_LOCKED.patch # Fix calling of smp_processor_id() when preempt is enabled #epatch ${FILESDIR}/${PV}/nv-disable-preempt-on-smp_processor_id.patch
yes, just comment this out in nvidia-kernel-1.0.6629.ebuild #epatch ${FILESDIR}/${PV}/nv-disable-preempt-on-smp_processor_id.patch
*** Bug 72857 has been marked as a duplicate of this bug. ***
Fixed in cvs.
