From: "Randy.Dunlap" <rddunlap@osdl.org>
To: "Silk Thadeum" <thadeum@hotmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: /drivers/net/tulip/dmfe.c may be outdated : kernel loading problem
Date: Wed, 7 Jan 2004 21:15:21 -0800 [thread overview]
Message-ID: <20040107211521.467dd421.rddunlap@osdl.org> (raw)
In-Reply-To: <Sea2-F38LFQG101s7hp0000e306@hotmail.com>
On Thu, 08 Jan 2004 05:41:17 +0100 "Silk Thadeum" <thadeum@hotmail.com> wrote:
| Hello,
|
| I have been working on Linux 2.4.20 for a couple of months and use a Davicom
| Semiconductor Ethernet network card driver known as dmfe.c for module dmfe.
|
| I had no problem since here, but on Linux 2.6.0-i386-stable kernel is
| refusing to load the module :
|
| --
| $ insmod dmfe.o
| insmod: error inserting 'dmfe.o': -1 Invalid module format
| $ lspci | grep Davicom
| 00:0a.0 Ethernet controller : Davicom Semiconductor, Inc. Ethernet 100/10
| Mbit (rev 31)
| --
In Linux 2.6.x, you load modules with names like 'dmfe.ko'.
And be sure to use module-init-tools, not modutils.
The module-init-tools location is listed in the Documentation/Changes
file.
|
| I tried to load the module by various ways : with old (for 2.4.20) and new
| (from 2.6.0 stable) compiled driver, but that didn't work. I quickly looked
| at the source code which seems quite old. I can't actually help you in
| having a deeper workaround because I don't yet have sufficient technical
| skills for that.
Are you building the module for 2.6.x in the norm(al) way
or using some homebrew commands or script?
| I'm working on a Debian Sarge testing prerelease.
|
| Have fun in debug ;p
of course ;)
--
~Randy
MOTD: Always include version info.
prev parent reply other threads:[~2004-01-08 5:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-08 4:41 /drivers/net/tulip/dmfe.c may be outdated : kernel loading problem Silk Thadeum
2004-01-08 5:15 ` Randy.Dunlap [this message]
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=20040107211521.467dd421.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thadeum@hotmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).