All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Chava Leviatan <chavale@actcom.net.il>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Ethernet driver module compilation  (8139too)
Date: Mon, 29 May 2006 03:53:44 -0600	[thread overview]
Message-ID: <20060529035344.A25913@openss7.org> (raw)
In-Reply-To: <023201c6830a$827539b0$c400a8c0@Chavalaptop>; from chavale@actcom.net.il on Mon, May 29, 2006 at 12:27:34PM +0200

Chava,

On Mon, 29 May 2006, Chava Leviatan wrote:

> Hi Brian,
> 
> I did reboot the machine, and saw that during boot time there is a call to 
> depmod.
> I did depmod -ae as you've requested, and here are the results:
>   [root@NettGain root]# depmod -ae >chav.dat
> depmod: /lib/modules/2.4.18-3/kernel/drivers/net/makefile.8139 is not an ELF 
> file
> depmod: /lib/modules/2.4.18-3/kernel/drivers/net/makefile.eepro is not an 
> ELF file
> depmod: *** Unresolved symbols in 
> /lib/modules/2.4.18-3/kernel/drivers/net/8139too.o
> depmod:         __netdev_watchdog_up
> depmod:         flush_signals
...
...
> depmod:         mii_ethtool_gset
...
...
> 
> Please note that if I manually insmod mii , then the insmod 8139too passes 
> w/o problems .
> 

I don't see how it could with all those depmod errors.  Try doing
this:

 grep uregister_netdev /proc/ksyms

If you get something like this:

  c0194ef0 unregister_netdev_Rc45f34ea
  c01d5270 unregister_netdevice_notifier_Rfe769456
  c01d6ca0 unregister_netdevice_R52c1d940

then your kernel has versioned symbols.

In which case, you are probably missing

 -DMODVERSIONS -include linux/modversions.h

from your compile statement.

Hope that helps.

--brian

  reply	other threads:[~2006-05-29  9:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-29  9:05 Ethernet driver module compilation (8139too) Chava Leviatan
2006-05-29  8:13 ` Brian F. G. Bidulock
2006-05-29 10:27   ` Chava Leviatan
2006-05-29  9:53     ` Brian F. G. Bidulock [this message]
2006-05-29 11:34       ` Chava Leviatan
2006-05-29 12:24         ` David Woodhouse
2006-05-29 12:34           ` test Suresh G

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060529035344.A25913@openss7.org \
    --to=bidulock@openss7.org \
    --cc=chavale@actcom.net.il \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.