From: "Alasdair McWilliam" <allymcw2000@hotmail.com>
To: solca@guug.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: Unresolved symbols of _mmx_memcpy in modules on an Athlon XP system
Date: Thu, 14 Aug 2003 16:22:37 +0100 [thread overview]
Message-ID: <Law10-F417rkWLoLBNJ0005120b@hotmail.com> (raw)
The configuration file has never been setup for an Intel chip, it was
originally an AMD K6-II/500MHz. I've tried reconfiguring from a brand new
tarball for Athlon. What do I get?
depmod: *** Unresolved symbols in
/lib/modules/2.4.22-rc2/kernel/drivers/block/floppy.o
depmod: _mmx_memcpy
depmod: *** Unresolved symbols in
/lib/modules/2.4.22-rc2/kernel/drivers/block/loop.o
depmod: _mmx_memcpy
depmod: *** Unresolved symbols in
/lib/modules/2.4.22-rc2/kernel/drivers/cdrom/cdrom.o
depmod: _mmx_memcpy
depmod: *** Unresolved symbols in
/lib/modules/2.4.22-rc2/kernel/drivers/ide/ide-cd.o
depmod: _mmx_memcpy
.....etc
Alasdair :(
>From: Otto Solares <solca@guug.org>
>To: Alasdair McWilliam <allymcw2000@hotmail.com>
>CC: linux-kernel@vger.kernel.org
>Subject: Re: PROBLEM: Unresolved symbols of _mmx_memcpy in modules on an
>Athlon XP system
>Date: Wed, 13 Aug 2003 20:41:29 -0600
>
>On Thu, Aug 14, 2003 at 02:02:02AM +0100, Alasdair McWilliam wrote:
> > 1. PROBLEM: Unresolved symbols of _mmx_memcpy in modules on an Athlon XP
> > system
>
>you must save your .config to another dir, then make mrproper,
>then move your .config to your source tree, then make normally.
>
>happens to me when i had an intel configured source tree, then
>compile for amd.
>
>-solca
>
_________________________________________________________________
Tired of 56k? Get a FREE BT Broadband connection
http://www.msn.co.uk/specials/btbroadband
next reply other threads:[~2003-08-14 15:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-14 15:22 Alasdair McWilliam [this message]
2003-08-14 18:19 ` Otto Solares
-- strict thread matches above, loose matches on Subject: below --
2003-08-14 15:24 Alasdair McWilliam
2003-08-14 1:02 Alasdair McWilliam
2003-08-14 2:41 ` Otto Solares
2003-08-14 2:46 ` Marc-Christian Petersen
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=Law10-F417rkWLoLBNJ0005120b@hotmail.com \
--to=allymcw2000@hotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=solca@guug.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®