From: Marco Schramel <Schramel.Linux@go.bartec.de>
To: "PPC_LINUX" <linuxppc-embedded@lists.linuxppc.org>
Subject: insmod trouble
Date: Tue, 25 May 2004 11:05:11 +0200 [thread overview]
Message-ID: <200405251105.11689.Schramel.Linux@go.bartec.de> (raw)
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/
next reply other threads:[~2004-05-25 9:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-25 9:05 Marco Schramel [this message]
2004-05-25 9:55 ` insmod trouble Wolfgang Denk
2004-05-25 11:30 ` Zusatz zuRe: " Marco Schramel
2004-05-27 7:15 ` Marco Schramel
-- strict thread matches above, loose matches on Subject: below --
2004-04-02 0:17 Insmod trouble Rune Torgersen
2004-04-02 6:42 ` Marc Leeman
2004-04-02 16:54 ` Wolfgang Denk
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=200405251105.11689.Schramel.Linux@go.bartec.de \
--to=schramel.linux@go.bartec.de \
--cc=linuxppc-embedded@lists.linuxppc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.