kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: ali@internetdog.org (Ali Bahar)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Problem with newly compiled kernel 2.6.39 (initrd.img not being created)
Date: Sun, 12 Jun 2011 09:38:20 +0800	[thread overview]
Message-ID: <20110612013820.GA23566@internetdog.org> (raw)
In-Reply-To: <595682.86118.qm@web137605.mail.in.yahoo.com>

On Sat, Jun 11, 2011 at 11:15:38PM +0530, Naman shekhar Mishra wrote:
> My platform is Intel 32 bit. 
> 
> I am using kernel 2.6.35-22 generic for these steps and the newly compiled kernel is 2.6.39
> 
> Here's my steps:

Typically, I precede with 'make mrproper', but AFAIK it won't make a
difference if you are compiling a brand new source tree, and doing so
_within_ it (ie without a separate build directory.)


> $make defconfig

I always go over the resulting .config anyway, to ensure -- though I
admit that that can be very time-consuming if you have not done it
before.


 
> $make -j2 CC="ccache gcc"
> $make modules
> #make modules_install
> #make install
> #update-grub
> 
> After these sequence of steps, I tried to boot into the new kernel and there was nothing (except for the blinking caps lock) .So I checked and there was no initrd.img in /boot. So I tried using mkinitranfs and it created the ramdisk and then I booted but still it won't work.
> Though I can boot into recovery mode but the shell prompt is strange like (initramfs)...

Typically, when I am getting an 'initramfs' shell-prompt, I have to
tackle issues other than mkinitramfs. The solution has (IIRC) always
been to add missing options in the .config file. The lines immediately
preceding the shell prompt give a hint as to where things (eg which
options) croaked!

later,
ali

  reply	other threads:[~2011-06-12  1:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-11 17:45 Problem with newly compiled kernel 2.6.39 (initrd.img not being created) Naman shekhar Mishra
2011-06-12  1:38 ` Ali Bahar [this message]
2011-06-13  1:13 ` Mulyadi Santosa

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=20110612013820.GA23566@internetdog.org \
    --to=ali@internetdog.org \
    --cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).