unresolved symbol

Bob Piatek bobtek at fishcamp.com
Tue Jan 1 09:47:28 EST 2002


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:


and ramdisk:


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?


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

-----Original Message-----
From: owner-linuxppc-embedded at lists.linuxppc.org
[mailto:owner-linuxppc-embedded at lists.linuxppc.org] On Behalf Of Tom
Sent: Monday, December 31, 2001 7:32 AM
To: Bob Piatek
Cc: linuxppc-embedded at 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
> 2001 to this list.  However, the solution to the problem was not
> to the list.

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

Tom Rini (TR1265)

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

More information about the Linuxppc-embedded mailing list