How to compile module to avoid "unresolved symbols" ??

[Kenward Vaughan <kaynjay@igalaxy.net>]

Sorry for what may be a silly question, but I've struggled on and off with
getting my 3dfx module to insert correctly.  I keep getting unresolved
symbols on boot-up.  Yes, the device is defined in /dev with
ownership/permissions set as suggested in the docs. 

I assume that the problem involves its compilation from the package.  I've
always dl'd the .deb, unzipped it where it lay in /usr/src, and run the
script to make the package.  This is followed by its installation.

Is this wrong??  Should it be unzipped somewhere inside of /usr/src/linux
and compiled With the kernel?  Does a line for it show up when one uses "make
menuconfig?"  I don't recall ever seeing errors on compilation.  

Another thought is whether I should change something in the Makefile which
would make it compatible with my Athlon??? (obviously assuming something there 
would screw that up...)

Frustrated In Bakersfield,

Kenward

ps: insmod reports the following:

hpotter:/home/daddy# insmod 3dfx
Using /lib/modules/2.2.17/misc/3dfx.o
/lib/modules/2.2.17/misc/3dfx.o: unresolved symbol remap_page_range
/lib/modules/2.2.17/misc/3dfx.o: unresolved symbol unregister_chrdev
/lib/modules/2.2.17/misc/3dfx.o: unresolved symbol register_chrdev
/lib/modules/2.2.17/misc/3dfx.o: unresolved symbol printk
hpotter:/home/daddy#
-- 
Hi! I'm a .signature virus! Copy me into your ~/.signature, please!
--