From: "Mukund JB." <mukundjb@esntechnologies.co.in>
To: "Arjan van de Ven" <arjan@infradead.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: Errors while booting the newly built 2.6.12 kernel??
Date: Mon, 12 Dec 2005 13:28:46 +0530 [thread overview]
Message-ID: <3AEC1E10243A314391FE9C01CD65429B1BDB03@mail.esn.co.in> (raw)
Dear Arjun,
Thanks for your quick response
After I compiled the kernel, I verified the 'initrd-2.6.12.img' and it was present.
But it is 10000 bytes less than the initial FC4 initrd img.
I did the following steps to build the kernel:
Copied the existing '.config' file from the old kernel and copied to the 2.6.12 kernel base directory.
Then,
# make
# make modules
# make modules_install
# make install
Is there is any thing additional needed for building the kernels in 2.6.x kernels?
I verified the support for inbuilt ext3 too and its present too.
What else could be the problem area?
Thanks & Regards,
Mukund Jampala
-----Original Message-----
From: Arjan van de Ven [mailto:arjan@infradead.org]
Sent: Monday, December 12, 2005 12:54 PM
To: Mukund JB.
Cc: linux-kernel@vger.kernel.org
Subject: Re: Errors while booting the newly built 2.6.12 kernel??
On Mon, 2005-12-12 at 12:44 +0530, Mukund JB. wrote:
> Dear Kernel Team,
>
> I am facing a strange error after I compiled the Linux kernel-2.6.12(downloaded from kernel.org).
> Please see the errors I get when I try to boot the newly built 2.6.12 kernel.
>
> I found lot of members in the groups discussing this and no definite solution is suggestion.
you forgot to make an initrd.
next reply other threads:[~2005-12-12 8:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-12 7:58 Mukund JB. [this message]
2005-12-12 8:22 ` Jesper Juhl
2005-12-12 9:06 ` Digvijoy Chatterjee
-- strict thread matches above, loose matches on Subject: below --
2005-12-12 7:14 Mukund JB.
2005-12-12 7:23 ` Arjan van de Ven
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=3AEC1E10243A314391FE9C01CD65429B1BDB03@mail.esn.co.in \
--to=mukundjb@esntechnologies.co.in \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.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®