All of lore.kernel.org
 help / color / mirror / Atom feed
From: Balaji Ravindran <b@w1an.in>
To: Linux Wireless List <linux-wireless@vger.kernel.org>
Subject: Kernel compilation Question
Date: Sat, 21 Nov 2009 08:02:02 -0800	[thread overview]
Message-ID: <4B080EFA.6000300@w1an.in> (raw)

Hi all,

I tried compiling the wireless 2.6 kernel on my debian machine using
make-kpkg and being lazy, i just did make defconfig, and saw that my
compilation went fine without any issues, but i noticed that there was
no ramdisk image that was generated when i installed the linux-image*.deb.

i did use --initrd option,

Was it because, using make defconfig compiles everything on the kernel
itself? Aren't there any 'm' option in defaults?(dunno just asking if
this is the case)

or did i miss something out

Please see if i missed some step

Summary of steps performed.

extracted wireless 2.6 source onto /usr/src

created symbolic link

make defconfig (i did not copy my existing config file to .config, i
just wanted to try out make defconfig option)

make-kpkg --initrd --append-to-version=foo --revision=bar kernel_image
modules_image kernel_headers

this created 2 files linux-image* and linux-headers*, i was missing the
modules image also(but that was a second question)

did dpkg -i linux-image*

updated grub and placed files in /boot, but did not create initrd image.
Why is that?

Thanks

Balaji R

             reply	other threads:[~2009-11-21 16:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-21 16:02 Balaji Ravindran [this message]
2009-11-21 18:10 ` Kernel compilation Question Stefan Lippers-Hollmann
2009-11-21 18:46   ` Balaji Ravindran
  -- strict thread matches above, loose matches on Subject: below --
2009-11-21 17:41 Balaji Ravindran
2005-09-26  9:40 Kernel Compilation Question Woody.Wu
2005-09-26  7:00 Woody.Wu
2005-09-26  7:52 ` Valdis.Kletnieks
2005-09-26 10:16 ` Alan Cox

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=4B080EFA.6000300@w1an.in \
    --to=b@w1an.in \
    --cc=linux-wireless@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.