From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-kernel@vger.kernel.org
Subject: Re: unresolved symbols problem
Date: Wed, 23 Oct 2002 14:31:53 +0200 [thread overview]
Message-ID: <20021023123153.GB24969@lug-owl.de> (raw)
In-Reply-To: <20021023122549.57302.qmail@web40603.mail.yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 1405 bytes --]
On Wed, 2002-10-23 13:25:49 +0100, Cathal Daly <cdaly24@yahoo.co.uk>
wrote in message <20021023122549.57302.qmail@web40603.mail.yahoo.com>:
> it. I am trying to load an e1000 driver as a module
> but I am getting unresolved symbols. The hash values
> at the end of the exported symbols do not match the
> corresponding hash values in the /proc/ksyms file in
> the running kernel. I gather that this is because
> module versioning is turned on in the kernel. I can't
> compile the driver against the kernel as I don't have
> the correct kernel sources. Is there any possible way
> to get the network driver to load into this kernel
> image without the kernel sources. I imagine the hash
> values from /proc/ksyms and the driver unresolved
> symbols will have to match but how can this be done. I
By recompiling the whole kernel, inclusive e1000. There's no way loading
the module while not risking an Oops or other bad things. Linux tries to
maintain source compatibility, but there's no binary compatibility (as
you obviously see:-)
Do a fresh compile and that'll succeed...
MfG, JBG
--
- Eine Freie Meinung in einem Freien Kopf für
- einen Freien Staat voll Freier Bürger
Gegen Zensur im Internet
Jan-Benedict Glaw . jbglaw@lug-owl.de . +49-172-7608481
-- New APT-Proxy written in shell script --
http://lug-owl.de/~jbglaw/software/ap2/
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2002-10-23 12:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-23 12:25 Cathal Daly
2002-10-23 12:31 ` Jan-Benedict Glaw [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=20021023123153.GB24969@lug-owl.de \
--to=jbglaw@lug-owl.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®