View Single Post
Old 06-22-03, 02:04 PM   #6
churritz
Registered User
 
Join Date: Jun 2003
Posts: 11
Unhappy

ok i'm back, i needed to boot another kernel and now when i booted back my orig custom kernel the driver barfed. OK then, i thought, well, then i'll just start over, recompiled the kernel, did the ndivia.run and i got the same bleeding error even though i specified the --kernel-include-path thing, well this time i have a new nvidia-installer.log to show. there were no compile errors just resolving errors:

-> Kernel module compilation complete.
ERROR: Unable to load the kernel module 'nvidia.o'. This is most likely
because the kernel module was built using the wrong kernel header files.
Please make sure you have installed the kernel header files for your
kernel; on Red Hat Linux systems, for example, be sure you have the
'kernel-source' rpm installed. If you know the correct kernel header
files are installed, you may specify the kernel include path with the
'--kernel-include-path' commandline option.
-> Kernel module load error: ./usr/src/nv/nvidia.o: unresolved symbol
__global_cli
./usr/src/nv/nvidia.o: unresolved symbol smp_call_function
./usr/src/nv/nvidia.o: unresolved symbol tqueue_lock
./usr/src/nv/nvidia.o: unresolved symbol __global_save_flags
./usr/src/nv/nvidia.o: unresolved symbol __global_restore_flags
./usr/src/nv/nvidia.o: unresolved symbol smp_num_cpus
./usr/src/nv/nvidia.o:


ack. i didn't change any kernel configs, and it's now unresolving different symbols, and at one point it resolved them all, creepy, any clues?
churritz is offline   Reply With Quote