From: Tom Rini <trini@kernel.crashing.org>
To: Meelis Roos <mroos@linux.ee>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PPC: unresolved module symbols in 2.4.20-pre7+bk
Date: Tue, 24 Sep 2002 16:48:15 -0700 [thread overview]
Message-ID: <20020924234815.GE788@opus.bloom.county> (raw)
In-Reply-To: <Pine.GSO.4.44.0209242216450.17647-100000@math.ut.ee>
On Tue, Sep 24, 2002 at 10:18:21PM +0300, Meelis Roos wrote:
> depmod: *** Unresolved symbols in /lib/modules/2.4.20-pre7/kernel/drivers/macintosh/nvram.o
> depmod: pmac_get_partition
> depmod: nvram_write_byte_R9ce3f83f
> depmod: nvram_read_byte_R0f28cb91
> depmod: *** Unresolved symbols in /lib/modules/2.4.20-pre7/kernel/drivers/media/video/tda7432.o
> depmod: __fixdfsi
> depmod: __floatsidf
> depmod: __divdf3
> depmod: __muldf3
> depmod: __subdf3
> depmod: *** Unresolved symbols in /lib/modules/2.4.20-pre7/kernel/drivers/sound/dmasound/dmasound_pmac.o
> depmod: pmac_xpram_read
> depmod: *** Unresolved symbols in /lib/modules/2.4.20-pre7/kernel/drivers/usb/storage/usb-storage.o
> depmod: ppc_generic_ide_fix_driveid
What compiler did you use, and when was the last time you did a
'mrproper' or 'distclean' in your tree or changed CONFIG_MODVERSIONS?
Two of the errors have modversions-type bits on them.
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
next prev parent reply other threads:[~2002-09-24 23:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-24 19:18 PPC: unresolved module symbols in 2.4.20-pre7+bk Meelis Roos
2002-09-24 23:48 ` Tom Rini [this message]
2002-09-26 8:31 ` Meelis Roos
2002-09-26 14:29 ` Tom Rini
2002-09-26 15:59 ` Björn Stenberg
2002-09-26 16:08 ` Tom Rini
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=20020924234815.GE788@opus.bloom.county \
--to=trini@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mroos@linux.ee \
/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).