From: "Andrew Haninger" <ahaning@gmail.com>
To: "tim tim" <tictactoe.tim@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel installation --depmod
Date: Tue, 7 Mar 2006 01:42:10 -0500 [thread overview]
Message-ID: <105c793f0603062242h4c03b95fy8871e3ee50501ac1@mail.gmail.com> (raw)
In-Reply-To: <503e0f9d0603062203x21cdf4e4w4e7da8c0f106fb73@mail.gmail.com>
On 3/7/06, tim tim <tictactoe.tim@gmail.com> wrote:
> hello andrew.. i even tried with modutils & mod init tools but even
> after that we r getting the depmod errors.. i don't think there is a
> problem in make modules.. since Sam Ravnborg has mentioned something
> that make modules is problem.. can any other suggestions u can offer
> for us..
I don't know what else I can really suggest. Perhaps it's time to find
a distribution that includes the kernel release you want (or a more
recent one).
Please answer the questions Sam asked:
> The warnings you see is a module that references symbols that it cannot
> resolve.
> Do you have a vmlinux in the root of your kernel tree?
Look in your kernel source directory. Is there a file there called "vmlinux"?
> Does Module.symvers include the symbols that you get warnings on?
This file should be found in the root of your kernel tree, too.
> You need to do a successful build of the kernel before you can build
> the modules.
Is the build of the kernel failing, thus leaving certain dependancies
not met for the build of the modules? Do you get any error messages
when you run "make" in the kernel source directory?
Again, unless this is a "just for fun" exercise, it might be more
worth your while to get a different distribution with all of this
stuff preconfigured.
-Andy
prev parent reply other threads:[~2006-03-07 6:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-07 6:03 tim tim
2006-03-07 6:41 ` Sam Ravnborg
2006-03-07 6:42 ` Andrew Haninger [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=105c793f0603062242h4c03b95fy8871e3ee50501ac1@mail.gmail.com \
--to=ahaning@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tictactoe.tim@gmail.com \
/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®