DLINK driver installer error

[Ken Schweigert]

I get this error occasionally and forgot what fixed it, so I did a little
digging around and refreshed my memory.  It seems that "unresolved symbol"
errors are caused when you try to load a module built from a kernel 
source that is not your current/running kernel.  i.e. you downloaded
2.4.20 and built 8139too from it, but your active kernel is something like
2.4.19-4a.

This is a message I found on the Matrox video board that explains it better:
http://forum.matrox.com/mgaforum/Forum2/HTML/001966.html
------------
The error you specified in your original post indicates that the matrox module 
was compiled against a kernel with the "Set kernel version information on all 
modules" turned on, and you're trying to load the module on a kernel that was 
not compiled against the same source tree (remembering that doing a 
'make distclean' is essentially the same as putting in a different kernel).

As I have said before, you have to:
a) compile the kernel in /usr/src/linux yourself before compiling the matrox module.
and
b) make sure you are *RUNNING* the kernel you compiled when trying to load the mtx.o module.

If you don't do BOTH steps, and kernel versioned symbols are enabled, then 
you will get the errors you pasted above. They are the result of the kernel's 
versioned symbols not matching the versioned symbols compiled into the mtx.o module.
------------

You can verify your running kernel with:
  [ken@byteme ken]$ uname -r
  2.4.19-4a
  [ken@byteme ken]$

Hope this helps.

-ken

On Thu, Feb 27, 2003 at 08:10:00AM -0700, Andrew Jacobs wrote:
> I haven't heard anything back about this yet, so I thought I'd post again:
> 
> Many thanks for the tips Robert and Nathan.  I'd already tried replacing
> that file with the slab.h, but that didn't help.  I did recompile the kernel
> again (with source from kernel.org), and included the 8139too as a module,
> but when I try to insert it this is what I get.  Can anyone help me here?
> (The irony of the situation is that I borrowed a friends 3com card which
> worked like a charm-put in PCI slot, rebooted, done-no recompiling, 
> etc.)
> 
> 
> 
> [root@neo net]# pwd
> /lib/modules/2.4.20/kernel/drivers/net
> [root@neo net]# insmod 8139too.o=20
> 8139too.o: unresolved symbol generic_mii_ioctl_Rf8e429ef
> 8139too.o: unresolved symbol mii_ethtool_gset_Re33d57e7
> 8139too.o: unresolved symbol mii_ethtool_sset_R2d85519a
> 8139too.o: unresolved symbol mii_nway_restart_Rec07b713
> 8139too.o: unresolved symbol mii_link_ok_Ra4c832df
> [root@neo net]#
> -Andrew
> 
> >The driver is included with the kernel source . Try the 8139too module
> 
> >
> 
> >-Rob
> 
> =20
> 
> =20
> 
> On Mon, 24 Feb 2003 09:37:48 -0700
> 
> Andrew Jacobs <andrewj@byu.edu> wrote:
> 
> =20
> 
> > I'm trying  to installed a DLINK DFE-530TX+ in a YDL 2.2 install on
> 
> > an 8500.  What RH version is YDL 2.2 equivalent to?  They are made
> 
> > about the same, right?  Here's the make error I'm getting, and DLINK
> 
> > support has been _no_ help so far.  Does anyone have this card
> 
> > working?
> 
> >=20
> 
> > -Andrew
> 
> _______________________________________________
> yellowdog-general mailing list
> yellowdog-general@lists.terrasoftsolutions.com
> http://lists.terrasoftsolutions.com/mailman/listinfo/yellowdog-general
> 

-- 
Ken Schweigert, Network Administrator
Byte Productions, LLC
http://www.byte-productions.com