unresolved symbol

unresolved symbol

[Bob Piatek]

Hi,

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.

Can anyone give me some advice on where to look?

Bob Piatek

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


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

Re: unresolved symbol

[Tom Rini]

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/

RE: unresolved symbol

[Bob Piatek]

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/

Re: unresolved symbol

[Tom Rini]

On Mon, Dec 31, 2001 at 02:47:28PM -0800, Bob Piatek wrote:

> 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?

Well, the kernel knows about its symbols at compile time, based on stuff
from the modutils program.  So, if you have a bad/missing genksyms
program, you won't get any symbols.

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

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

RE: unresolved symbol

[Bob Piatek]

OK. I updated the modutils package and that fixed it!  Thanks so much.

Bob

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


-----Original Message-----
From: Tom Rini [mailto:tmrini@cpe-24-221-152-185.az.sprintbbd.net] On
Behalf Of Tom Rini
Sent: Monday, December 31, 2001 3:02 PM
To: Bob Piatek
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: unresolved symbol

On Mon, Dec 31, 2001 at 02:47:28PM -0800, Bob Piatek wrote:

> 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?

Well, the kernel knows about its symbols at compile time, based on stuff
from the modutils program.  So, if you have a bad/missing genksyms
program, you won't get any symbols.

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


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

unresolved symbol

[vasanth]

[-- Attachment #1: Type: text/plain, Size: 463 bytes --]

Hi,

I am getting the folowing error message when i do insmod .
insmod: unresolved symbol __udelay
insmod: unresolved symbol atomic_add
insmod: unresolved symbol atomic_sub

I complied the driver code for mips processor using the folowing command
mips-linux-gcc -G O -mno-abicalls -fno-pic -pipe -mtune=4kc -mips32 -c lcddriver.c -I/mykernel/include
It is compiling without any error . 
Can anybody know how to solve this problem.?

Regards,
Vasanth.

[-- Attachment #2: Type: text/html, Size: 1389 bytes --]

unresolved symbol

[vasanth]

[-- Attachment #1: Type: text/plain, Size: 463 bytes --]

Hi,

I am getting the folowing error message when i do insmod .
insmod: unresolved symbol __udelay
insmod: unresolved symbol atomic_add
insmod: unresolved symbol atomic_sub

I complied the driver code for mips processor using the folowing command
mips-linux-gcc -G O -mno-abicalls -fno-pic -pipe -mtune=4kc -mips32 -c lcddriver.c -I/mykernel/include
It is compiling without any error . 
Can anybody know how to solve this problem.?

Regards,
Vasanth.

[-- Attachment #2: Type: text/html, Size: 1389 bytes --]

Re: unresolved symbol

[Ralf Baechle]

On Thu, Sep 08, 2005 at 07:26:17PM +0530, vasanth wrote:

> I am getting the folowing error message when i do insmod .
> insmod: unresolved symbol __udelay
> insmod: unresolved symbol atomic_add
> insmod: unresolved symbol atomic_sub
> 
> I complied the driver code for mips processor using the folowing command
> mips-linux-gcc -G O -mno-abicalls -fno-pic -pipe -mtune=4kc -mips32 -c lcddriver.c -I/mykernel/include
> It is compiling without any error . 

Use -O2.  In fact use _exactly_ the same options as for the kernel build
itself.

  Ralf

Re: unresolved symbol

[Daniel Jacobowitz]

On Thu, Sep 08, 2005 at 07:26:17PM +0530, vasanth wrote:
> Hi,
> 
> I am getting the folowing error message when i do insmod .
> insmod: unresolved symbol __udelay
> insmod: unresolved symbol atomic_add
> insmod: unresolved symbol atomic_sub
> 
> I complied the driver code for mips processor using the folowing command
> mips-linux-gcc -G O -mno-abicalls -fno-pic -pipe -mtune=4kc -mips32 -c lcddriver.c -I/mykernel/include
> It is compiling without any error . 
> Can anybody know how to solve this problem.?

Turn on optimization.

-- 
Daniel Jacobowitz
CodeSourcery, LLC

unresolved symbol

[zhonglei]

hi 
   My mod has no error or warning during compiling.But when I "insmod hello.o" , it shows:
   hello.o : unresolved symbol TaskStart
   hello.o : unresolved symbol TasksLoadImage
   hello.o : unresolved symbol TasksInitAPI
   ...
What's the problem?
BestRegards
zhonglei

unresolved symbol

[zhonglei]

hi
   My mod has no error or warning during compiling.But when I "insmod hello.o" , it shows:
   hello.o : unresolved symbol TaskStart
   hello.o : unresolved symbol TaskLoadImage
   hello.o : unresolved symbol TaskInitAPI
   ...
What's the problem?
BestRegards
zhonglei

Re: unresolved symbol

[Alex Zeffertt]

At compile time the compiler assumed these symbols would be defined externally, either by the kernel
or by another module loaded prior to hello.o.  The error message says that these symbols are not
exported by the kernel (or any currently loaded modules) prior to running "insmod hello.o".

Either:

1.	You need to insmod another module first (or use "modprobe hello" which may do this automatically)

2.	The module defining these symbols has not used the EXPORT_SYMBOL() macro to make them exported.

3.	These symbols are not defined in either the kernel or any modules.

Alex

On Wed, 24 Aug 2005 15:07:58 +0800
"zhonglei" <zhonglei@RCS-9000.COM> wrote:

> hi
>    My mod has no error or warning during compiling.But when I "insmod hello.o" , it shows:
>    hello.o : unresolved symbol TaskStart
>    hello.o : unresolved symbol TaskLoadImage
>    hello.o : unresolved symbol TaskInitAPI
>    ...
> What's the problem?
> BestRegards
> zhonglei
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded

Unresolved symbol

[Manuel Jander]

Building a pure USB alsa-driver set, I encountered the following
situation (ARM target):

The function snd_compat_strlcpy() does sometimes not get build when
only USB devices (no memory_wrapper.o being build). I guess this
function should go elsewhere.

The result: unresolved symbols: snd_compat_strlcpy()


Best Regards,
-- 
Manuel Jander


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id\x16492&op=click

Re: Unresolved symbol

[Takashi Iwai]

At Tue, 5 Jul 2005 14:04:55 +0200,
Manuel Jander wrote:
> 
> Building a pure USB alsa-driver set, I encountered the following
> situation (ARM target):
> 
> The function snd_compat_strlcpy() does sometimes not get build when
> only USB devices (no memory_wrapper.o being build). I guess this
> function should go elsewhere.
> 
> The result: unresolved symbols: snd_compat_strlcpy()

Which ALSA version?  Did you try CVS?


Takashi


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click

Re: Unresolved symbol

[Takashi Iwai]

At Tue, 5 Jul 2005 15:48:08 +0200,
Manuel Jander wrote:
> 
> Hi Takashi,
> 
> CVS, the same thing.... Somehow I believe that some few functions in
> acore are not were they should be. Indeed, some don't get exported
> because they seem to be in the wrong place: "EXPORT" statement in a
> different file than the function declaration.
> I'm compiling with the WRTG54 (armv4b-hardhat-linux) toolchain. That
> fact may be providing more fun than necesary too (but its my job to do
> this kind of stuff).

Is it 2.4 or 2.6 based?

> Compiling with only a usb-audio card, triggers the the problems I am
> encountering.
> If I get something working, I will let you know. If there is any known
> stuff about I would be very interested to know.

memory_wrapper.c is a part of snd-page-alloc module and always built
when PCM is selected.  This means that usb-audio also must enable the
compilation of memory_wrapper.c.

My rough guess was that configure script failed to detect the
strlcpy, but I'm not sure now.  Anyway check include/config.h.


Takashi

> 
> Best Regards,
> Manuel
> 
> On 7/5/05, Takashi Iwai <tiwai@suse.de> wrote:
> > At Tue, 5 Jul 2005 14:04:55 +0200,
> > Manuel Jander wrote:
> > >
> > > Building a pure USB alsa-driver set, I encountered the following
> > > situation (ARM target):
> > >
> > > The function snd_compat_strlcpy() does sometimes not get build when
> > > only USB devices (no memory_wrapper.o being build). I guess this
> > > function should go elsewhere.
> > >
> > > The result: unresolved symbols: snd_compat_strlcpy()
> > 
> > Which ALSA version?  Did you try CVS?
> > 
> > 
> > Takashi
> > 
> 
> 
> -- 
> Manuel Jander
> Electronic Engineer
> 


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click

Unresolved symbol

[Breno]

Hi ,

I tried to compile kernel 2.4.18 on amd athlon , but i received teh message
:

unresolved symbol __mmx_memcpy

EXPORT_SYMBOL(__mmx_memcpy) in ksyms.c can fix this ?

att,
Breno

Re: unresolved symbol

[Shoudong XU]

Thank you very much, It is a effective method to disable that option.

Best Regards
Shoudong


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

unresolved symbol

[Shoudong XU]

Hi,all.

    I'm running a Spruce board with NFS mode(load kernel image by tftp, then mount nfs as it's root file system), but When attempting to insert a module manually(/sbin/insmod xx.o), I get messages like:
    xx.o    unresolved symbol     unregister_chrdev
    xx.o    unresolved symbol     register_chrdev
    xx.o    unresolved symbol     __get_free_pages
    ...
    xx.o    unresolved symbol     printk

    And all those symbols are present in /boot/System.map, it seems this file is useless.

    Could you give me some advice?

Thanks

Shoudong

----------------------------------------------------------
 Shoudong XU             Email:  Shoudong.Xu@cern.ch
 CERN, EP Division       Tel:    +41.22.767-8113
 CH-1211 GENEVE 23       Fax:    +41.22.767-7793
 SUISSE/SWITZERLAND
-----------------------------------------------------------


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