insmod trouble

insmod trouble

[Marco Schramel]

Hi all,

My MPC8270 system works with 2.4.26 (toolchain ELDK), for development i use NFS (opt/eldk/ppc_82xx as rootfs). Now i write  a device driver and have some trouble.
I ve searched the whole list, but i didn't found some helpfully comments.

--------------------------------------------------
bash-2.05b# insmod demodriver.o
demodriver.o: unresolved symbol module_unregister_chrdev
demodriver.o: unresolved symbol register_chrdev
demodriver.o: unresolved symbol led_init
demodriver.o: unresolved symbol printf
demodriver.o: unresolved symbol printk
------------------------------------------------

What is the reason for this messages ??
I have enabled module support in my kernel.

Thanks in advance

Marco



---------
Marco Schramel
R&D
Bartec GmbH
Schulstr. 30
94239 Gotteszell, Germany
www.bartec.de
Marco.Schramel@go.bartec.de
Phone:  +49 (0)9929/301332
Fax:    +49 (0)9929/301112


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

Re: insmod trouble

[Wolfgang Denk]

In message <200405251105.11689.Schramel.Linux@go.bartec.de> you wrote:
>
> My MPC8270 system works with 2.4.26 (toolchain ELDK), for development i use NFS (opt/eldk/ppc_82xx as rootfs). Now i write  a device driver and have some trouble.
> I ve searched the whole list, but i didn't found some helpfully comments.
>
> --------------------------------------------------
> bash-2.05b# insmod demodriver.o
> demodriver.o: unresolved symbol module_unregister_chrdev
> demodriver.o: unresolved symbol register_chrdev
> demodriver.o: unresolved symbol led_init
> demodriver.o: unresolved symbol printf
> demodriver.o: unresolved symbol printk
> ------------------------------------------------
>
> What is the reason for this messages ??

The reason is bugs in your driver code.

module_unregister_chrdev - there is no such function in the Linux kernel.
	Do you mean unregister_chrdev() or devfs_unregister_chrdev()?

led_init - there is no such exported kernel  symbol.  Which  function
        are you trying to call? Is this something in your own driver?

printk - there is no such function in the Linux kernel. Did you  mean
        printk() instead?

register_chrdev, printk - I can only speculate.  These  are  exported
        kernel  symbols.  probably you compile the driver with bad or
        incomplete compiler options?

Best regards,

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
Horses just naturally have mohawk haircuts.

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

Zusatz zuRe: insmod trouble

[Marco Schramel]

Ich habe noch vergessen, Ihnen meine Compileroptionen zu sagen,
"ppc_82xx-gcc -I /home/marco/linux-2.4.26/include -D __KERNEL__ -D MODULE -c Demodriver.c"
Ohne Warnungen mit ELDK 3.0
Gruß
Marco


--
---------
Marco Schramel
R&D
Bartec GmbH
Schulstr. 30
94239 Gotteszell, Germany
www.bartec.de
Marco.Schramel@go.bartec.de
Phone:  +49 (0)9929/301332
Fax:    +49 (0)9929/301112


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

Re: insmod trouble

[Marco Schramel]

Hi all,

my problem was ...
> > --------------------------------------------------
> > bash-2.05b# insmod demodriver.o
> > demodriver.o: unresolved symbol module_unregister_chrdev
> > demodriver.o: unresolved symbol register_chrdev
> > demodriver.o: unresolved symbol led_init
> > demodriver.o: unresolved symbol printk
> > ------------------------------------------------
> >
> > What is the reason for this messages ??

Solution: You have to disable "Set version information on all module symbols" under "Loadable module support" in our kernel config.

Thanx for comments
Marco


---------
Marco Schramel
R&D
Bartec GmbH
Schulstr. 30
94239 Gotteszell, Germany
www.bartec.de
Marco.Schramel@go.bartec.de
Phone:  +49 (0)9929/301332
Fax:    +49 (0)9929/301112


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

Insmod trouble

[Rune Torgersen]

Hi

I get the following unresolved functions when trying to insmod a module
with some floating point math in it:

proc_sysinfo: Unknown symbol __fixsfsi
proc_sysinfo: Unknown symbol __subsf3
proc_sysinfo: Unknown symbol __extendsfdf2
proc_sysinfo: Unknown symbol __floatsisf
proc_sysinfo: Unknown symbol __muldf3
proc_sysinfo: Unknown symbol __truncdfsf2
proc_sysinfo: Unknown symbol __mulsf3
proc_sysinfo: Unknown symbol __addsf3

Any ideas on how to get rid of these?
I'm using a 8266 cpu. (on 2.6.3)

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

Re: Insmod trouble

[Marc Leeman]

> proc_sysinfo: Unknown symbol __fixsfsi
> proc_sysinfo: Unknown symbol __subsf3
> proc_sysinfo: Unknown symbol __extendsfdf2
> proc_sysinfo: Unknown symbol __floatsisf
> proc_sysinfo: Unknown symbol __muldf3
> proc_sysinfo: Unknown symbol __truncdfsf2
> proc_sysinfo: Unknown symbol __mulsf3
> proc_sysinfo: Unknown symbol __addsf3

I would assume that these functions are not compiled in the kernel.
While compiling them as modules, the compiler assumes (via the include
file) that they are external and will not complain about these.

Double check if the source files that contain this functionality are
compiled and linked in the code. You can try to quick-'fix' it by static
inlining these functions in you module.

Maybe these functions assume some architecture and are in a conditional
ifdef CONFIG_XXX flag.

  marc.

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

Re: Insmod trouble

[Wolfgang Denk]

In message <DCEAAC0833DD314AB0B58112AD99B93B06DAAE@ismail.innsys.innovsys.com> you wrote:
>
> I get the following unresolved functions when trying to insmod a module
> with some floating point math in it:

You cannot use floating point in kernel mode.

Best regards,

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
God made machine language; all the rest is the work of man.

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