From: "Vishwanath Kalbagilmath" <kalbagil@india.hp.com>
To: "John S J Anderson" <jacobs@genehack.org>
Cc: <ma-linux@tux.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [ma-linux] problem loading module
Date: Tue, 28 Oct 2003 18:58:53 +0530 [thread overview]
Message-ID: <01ee01c39d57$6f69dbf0$19de4c0f@nta2225> (raw)
In-Reply-To: <87vfqqzm9x.fsf@mendel.genehack.org>
Hi All,
After including some of the versioning header files and some macros like
MODVERSIONS, I am still unable to load the module into the kernel.
Now the printk(), kmalloc() problems are solved, now only left out
is unresolved symbol is register_chrdev_Rsmp_904e3677 but ksyms has
register_chrdev_Rsmp_e337b494
Please let me know where I am making mistake...
Thanks in Adv
Vishwanath
----- Original Message -----
From: "John S J Anderson" <jacobs@genehack.org>
To: "Vishwanath Kalbagilmath" <kalbagil@india.hp.com>
Cc: <ma-linux@tux.org>
Sent: Wednesday, October 15, 2003 6:32 PM
Subject: Re: [ma-linux] problem loading module
> "Vishwanath Kalbagilmath" <kalbagil@india.hp.com> writes:
>
> > these are the unresolved symbols that I get when trying the loadable
> > module in RH 7.3 and RHAS 2.1 as well, can anybody suggest some soln
> > to this...
> >
> > mydrv.o: unresolved symbol unregister_chrdev_Rc192d491
> > mydrv.o: unresolved symbol register_chrdev_Rd115e0a6
> > mydrv.o: unresolved symbol snprintf_Raf25400d
> > mydrv.o: unresolved symbol kmalloc_R6f6c1cf7
> > mydrv.o: unresolved symbol printk_R827d5807
>
> If you're not seeing printk(), you're almost certainly doing
> something wrong. Have you looked at the Module HOWTO?
>
> <http://www.tldp.org/HOWTO/Module-HOWTO/index.html>
>
> john.
> --
> Linux's power is that we FIX stuff. That we make it the best system
> possible, and that we don't just whine and argue about things.
> -- Linus Torvalds in
> <Pine.LNX.4.44.0205070827050.1343-100000@home.transmeta.com>
>
parent reply other threads:[~2003-10-28 13:29 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <87vfqqzm9x.fsf@mendel.genehack.org>]
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='01ee01c39d57$6f69dbf0$19de4c0f@nta2225' \
--to=kalbagil@india.hp.com \
--cc=jacobs@genehack.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ma-linux@tux.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
all inboxes | Powered by JetHome®