linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Bob Piatek" <bobtek@fishcamp.com>
To: <linuxppc-embedded@lists.linuxppc.org>
Cc: "'Tom Rini'" <trini@kernel.crashing.org>
Subject: RE: unresolved symbol
Date: Mon, 31 Dec 2001 14:47:28 -0800	[thread overview]
Message-ID: <000501c1924d$1fd40410$a2341204@P4> (raw)
In-Reply-To: <20011231153213.GB28513@cpe-24-221-152-185.az.sprintbbd.net>


Tom,

I'm using YellowDog Linux 2.1 for my development system.  I don't think
the modutils update is needed for 2.1 and, indeed, I can compile and
'insmod' modules on my host system just fine.

My problem is that I can't load modules on my embedded system.  Sorry I
wasn't clear about that in my posting.  I am using the kernel from:

ftp://ftp.denx.de/pub/LinuxPPC/usr/src/linux-2.4.4-2001-11-24.tar.bz2

and ramdisk:

ftp://ftp.denx.de/pub/LinuxPPC/usr/src/simple-ramdisk.image.gz

and have ported it to my custom hardware running with an MPC860.  BTW...
thanks to all who have contributed software for this effort especially
the PPCBoot project!

Correct me if I'm wrong, but it looks like the problem is caused by the
kernel not exporting the symbols that are needed by the module and not
in the actual module itself.  Is it that I built the kernel wrong
somehow, or maybe the libraries in 'simple-ramdisk' image aren't
sufficient, or is it something else?

Bob


fishcamp engineering
105 W. Clark Ave
Orcutt, CA  93455
TEL: 805-937-6365
FAX: 805-937-6252


-----Original Message-----
From: owner-linuxppc-embedded@lists.linuxppc.org
[mailto:owner-linuxppc-embedded@lists.linuxppc.org] On Behalf Of Tom
Rini
Sent: Monday, December 31, 2001 7:32 AM
To: Bob Piatek
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: unresolved symbol


On Sun, Dec 30, 2001 at 05:02:43PM -0800, Bob Piatek wrote:

> When attempting to load a module via 'insmod' I get the following:
>
> insmod unresolved symbol kmalloc
> insmod unresolved symbol unregister_chrdev
> insmod unresolved symbol register_chrdev
> ...
> insmod unresolved symbol printk
>
>
> It seems that there was another person with the same problem on Sept
24,
> 2001 to this list.  However, the solution to the problem was not
posted
> to the list.

It sounds like you're running YellowDog Linux 2.0, and thus need to
install the modutils update.

--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2001-12-31 22:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-31  1:02 unresolved symbol Bob Piatek
2001-12-31 15:32 ` Tom Rini
2001-12-31 22:47   ` Bob Piatek [this message]
2001-12-31 23:01     ` Tom Rini
2002-01-01  0:47       ` Bob Piatek
  -- strict thread matches above, loose matches on Subject: below --
2005-08-24  7:11 zhonglei
2005-08-24  7:07 zhonglei
2005-08-24  8:59 ` Alex Zeffertt
     [not found] <B25E2E5A003CD311B61E00902778AF2A034573AB@SERVER1>
2001-09-24 16:31 ` Shoudong XU
2001-09-24 15:24 Shoudong XU

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='000501c1924d$1fd40410$a2341204@P4' \
    --to=bobtek@fishcamp.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=trini@kernel.crashing.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;
as well as URLs for NNTP newsgroup(s).