From: Studying MTD <studying_mtd@yahoo.com>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: agoddard@purdue.edu, joshk@triplehelix.org, linux-kernel@vger.kernel.org
Subject: Re: linux-2.6.0-test1 : modules not working
Date: Wed, 30 Jul 2003 15:08:04 -0700 (PDT) [thread overview]
Message-ID: <20030730220804.27148.qmail@web20512.mail.yahoo.com> (raw)
In-Reply-To: <20030730080115.28fd5d4f.rddunlap@osdl.org>
Thanks for your help, I am able to insert the module
but not able to remove it.
#insmod modtest.ko
: module licence 'unspecified' taints kernel.
Hello World
#lsmod
Module Size Used by
896 0 - Live 0xc0102000
#rmmod modtest
Can't open 'modtest' : No such file or directory
#rmmod 896
Can't open '896' : No such file or directory
Please help me to rmmod it.
Thanks.
--- "Randy.Dunlap" <rddunlap@osdl.org> wrote:
> On Wed, 30 Jul 2003 00:34:41 -0700 (PDT) Studying
> MTD <studying_mtd@yahoo.com> wrote:
>
> | I am curious that linux-2.6.0-test1 supports
> external
> | modules yet or not ?
> |
> | Thanks.
> |
> | --- Alex Goddard <agoddard@purdue.edu> wrote:
> | > On Tue, 29 Jul 2003, Studying MTD wrote:
> | >
> | > > I tried hello world example from
> | > > http://lwn.net/Articles/21817/
> | > >
> | > > but i am still getting :-
> | > >
> | > > #insmod hello_module.o
> | > > No module found in object
> | > > Error inserting 'hello_module.o': -1 Invalid
> | > module
> | > > format
> | >
> | > [Snip]
> | >
> | > 'kay. So modules are enabled and everything.
> More
> | > specifically, I was
> | > after information such as the gcc options and
> stuff
> | > you used to compile
> | > hello_module.o
> | >
> | > Check the second article at that URL, and try
> | > building your hello_module
> | > with the basic Makefile it gives. That uses the
> | > best way for building
> | > external modules. After building your kernel
> that
> | > way, try inserting the
> | > hello_module.ko.
>
> So you can insmod hello_module.ko successfully now?
>
> Sure, 2.6 supports external modules (if you mean
> modules that are
> built outside of the kernel source tree), but for
> now you also
> need a full kernel source tree for the build system
> to reference.
> I.e., you can't build an external module without
> having a full
> kernel source tree installed and configured.
>
> --
> ~Randy
> | http://developer.osdl.org/rddunlap/ |
> http://www.xenotime.net/linux/ |
> -
> To unsubscribe from this list: send the line
> "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at
> http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
prev parent reply other threads:[~2003-07-30 22:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-30 4:37 Studying MTD
2003-07-30 4:51 ` Joshua Kwan
2003-07-30 5:41 ` Studying MTD
2003-07-30 6:21 ` Alex Goddard
2003-07-30 6:50 ` Studying MTD
2003-07-30 7:25 ` Alex Goddard
2003-07-30 7:34 ` Studying MTD
2003-07-30 15:01 ` Randy.Dunlap
2003-07-30 18:02 ` Studying MTD
2003-07-30 18:50 ` Richard B. Johnson
2003-07-30 22:08 ` Studying MTD [this message]
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=20030730220804.27148.qmail@web20512.mail.yahoo.com \
--to=studying_mtd@yahoo.com \
--cc=agoddard@purdue.edu \
--cc=joshk@triplehelix.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.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®