From: Sam Ravnborg <sam@ravnborg.org>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: Kirk Reiser <kirk@braille.uwo.ca>, linux-kernel@vger.kernel.org
Subject: Re: unknown symbols loading modules under 2.6.x
Date: Mon, 22 Sep 2003 18:34:32 +0200 [thread overview]
Message-ID: <20030922163432.GA3208@mars.ravnborg.org> (raw)
In-Reply-To: <20030922091800.3b2532ec.rddunlap@osdl.org>
On Mon, Sep 22, 2003 at 09:18:00AM -0700, Randy.Dunlap wrote:
> On Mon, 22 Sep 2003 12:07:45 -0400 Kirk Reiser <kirk@braille.uwo.ca> wrote:
>
> | Hello Everyone: I have been trying to hunt down the answer to
> | aproblem I am having attempting to load my modules under the 2.6.x
> | kernels. They load just fine under the 2.4.x kernels. Have there
> | been changes which need to be made to get symbols found with modprobe
> | other than the EXPORT_SYMBOL() macro? The symbols show up in the
> | modules.symbols file created by depmod. They appear to reference the
> | correct loadable module. The loadable module these symbols are
> | exported in however is comprised of two separate .o files during
> | compile. I am not sure whether that has anything to do with it or
> | not.
> |
> | If someone could give me an idea what to read to solve this I'd
> | appreciate it.
>
> Make sure that you have the current version of module-init-tools
> installed from http://www.kernel.org/pub/linux/kernel/people/rusty/modules/
> and that scripts are using them (ie, check PATH).
Also make sure that you use kbuild when compiling your module.
See Documentation/modules.txt (or Documentation/kbuild/modules.txt
in BK-latest).
Sam
next prev parent reply other threads:[~2003-09-22 16:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-22 16:07 unknown symbols loading modules under 2.6.x Kirk Reiser
2003-09-22 16:18 ` Randy.Dunlap
2003-09-22 16:34 ` Sam Ravnborg [this message]
2003-09-22 16:49 ` John Levon
2003-09-22 19:56 ` Sam Ravnborg
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=20030922163432.GA3208@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=kirk@braille.uwo.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox