RE: [expert] Kernel Modules and Version Numbers

[BOUCARON Julien CNET/DSE/SOP]

Hello,

I caught an other trouble with the same consequence , while installing
Mandrake 5.3 and 6.0 on a Fujitsu Laptop which has a DEC Tulip Eth Card.
DEC Tulip chipset is on many cards but DEC ( Compaq) lets the manufacturers
of  Eth Card using this chipset change the microcode of the Chip, so that
not all the DEC Tulip Eth Card are supported , so if you know exactly the
model of you card , have a look on a HOWTO, FAQ or in the kernel source of
the tulip module you're using.
After fixing the Version problem ( i got the same problem and no answer yet
) , try also the "de4x5" module if you got other trouble , it is also a DEC
Tulip driver.
For the Fujitsu Laptop i got no problem on 10 and 100 Mb LAN using this
module.


-----Message d'origine-----
De: Tom Berger [mailto:[EMAIL PROTECTED]]
Date: jeudi 9 septembre 1999 23:50
�: [EMAIL PROTECTED]
Objet: Re: [expert] Kernel Modules and Version Numbers


[EMAIL PROTECTED] wrote:
> 
> I helped a friend of mine install Linux-Mandrake 6.1pre, and we ran
> into a problem with it- it doesn't see his Tulip 24020 NIC.  During the
> installation, we chose the DEC Tulip 21040 card, but install says it
> doesn't see it anywhere in the system!  This card works fine in Windows.
> 
> The manufacturer has a Linux driver available for download- you download
> the file, compile it, and get a kernel module: tulip.o
> 
> However, we've run into another problem.  After compiling it, we [are
> told by the manufacturer's web page to] run the following commands:
> 
> # depmod -a
> /lib/modules/2.2.13-2mdk/net/tulip.o: unresolved symbol(s)
> /lib/modules/2.2.13-2mdk/misc/wavefront.o: unresolved symbol(s)
> /lib/modules/2.2.13-2mdk/misc/eicon.o: unresolved symbol(s)
> 
> Forgive me for being an ignorant savage: I'd think that having
> unresolved symbols would be a bad thing (i.e. that module is broken?),
> so why would there be unresolved symbols in modules included with
> Mandrake?
> 
> # modprobe tulip.o
> /lib/modules/2.2.13-2mdk/net/tulip.o: kernel-module version mismatch
>         /lib/modules/2.2.13-2mdk/net/tulip.o was compiled for kernel
version 2.2.13-pre4_2mdk
>         while this kernel is version 2.2.13-2mdk.
> 
> Wait a minute!  Why would the version of the included kernel source be
> different from the version of the compiled kernel?!  Anyway, I
> remembered (or thought I did) that the kernel version number was set in
> the Makefile, so I thought (apparently incorrectly) that if I changed
> "-4_pre2mdk" to "-4mdk" in the Makefile, then the module version for
> the tulip module would then be the same as the kernel.  However,
> after recompiling, all the error messages returned, with no changes.
> Could this version mismatch also be the cause of the "unresolved
> symbols" from depmod's output, or is that unrelated to this?
> 
> How can I change the module version to match the kernel version?  Also,
> why does the included kernel source have a different version number
> than the precompiled kernel?
> 
> --
> -Matt Stegman
> <[EMAIL PROTECTED]>

>From /usr/src/linux/Documentation/networking/tulip.txt:

"This driver is designed to work with PCI Ethernet
cards which use the DECchip DC21x4x family."

The driver doesn't support your friend's card (otherwise it wouldn't make
sense
for the hardware manufucturer to supply a driver on his own, would it? ;-))

Could you please:

rpm -q kernel-source
rpm -q kernel
rpm -q kernel-headers

Do the versions match? The kernel section has been quite busy during the
last
few days (and is so still). Surest thing would be to compile and install a
new
kernel from the sources. 
If I recall correctly the problems with the eicon and wavefront are known,
but
doesn't seem to affect the drivers.

Regards

tom

-- 
"Never trust a Shoggoth!"
Thomas 'tom' Berger, [EMAIL PROTECTED]
LSTB - "advancing the community"