Kernel version mismatch error

[Joe Thompson]

When I compile and load the tulip.c v0.91g, it complains that the kernel
version it was compiled for (2.0.33) is different from the running kernel
(2.0.34).  The problem is that the module was in fact compiled under kernel
2.0.34:

crowley:~$ uname -a
Linux crowley 2.0.34 #2 Thu Jul 9 10:57:48 EST 1998 i686 unknown

So I have a couple of questions:

1) I just took the standard compile command from the comments at the end of
the source and ran it as-is, and the module compiled without complaint.
Did I forget to include something I should have in the compile command?

2) Currently I have it hacked up so that insmod -f runs as part of the
network section of the boot sequence.  The problem is that when the kernel
mismatch error pops up, everything stops until I hit Ctrl-C, at which point
the remainder of the network stuff is aborted -- which means it's not
possible to load my Western Digital ISA card as eth1 as I'd like to do.  (I
suppose I could put it at the top of the next file, but that seems...
inelegant.)  Should adding debug=0 to the insmod command allow the network
driver loading to continue without incident?

I'd prefer to get it to just recognize the kernel version properly, but the
second solution would be acceptable as well. -- Joe
-- 
       Joe Thompson | "It's software.  It comes in a tiny box.
Charlottesville, VA | You can't even see it from the moon."
  joe@orion-com.com | -- Nicholas Petreley on Windows 98
       http://kensey.home.mindspring.com/