kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: razvan.ghitulete@gmail.com (Razvan Ghitulete)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Rebuild kernel so complicated?
Date: Fri, 14 Mar 2014 01:14:50 +0100	[thread overview]
Message-ID: <532249FA.1020903@gmail.com> (raw)
In-Reply-To: <CAJFpruKnnWPwKe3LtfS775=9_zZQ3Mrhi0p7sVPxV_3eTWsLJQ@mail.gmail.com>

On 12/07/2013 12:57 PM, ??? wrote:
> AFAIK, rebuild the kernel should follow those steps at least:
>
>   * /copy /boot/system-$(uname -r).map to ${kernel_src}/
>   * /copy /boot/config-$(uname -r) to ${kernel_src}/
>   * /cd ${kernel_src}/
>   * /make menuconfig/, save config(If I don't wanna change anything
>     for test).
>   * /make -j9 bzImage./
>   * /override /boot/vmlinuz-$(uname -r) with
>     ${kernel_src}/arch/x86/boot/bzImage/
>
I might be in the wrong...but why are you copying your running kernel 
system.map to the src dir? AFAIK the system.map is generated during the 
build process. Also you should consider building the modules and 
installing them. Most probably your distro modules will have some 
problems with a custom built kernel(even though you have the same config).


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20140314/caad0ed1/attachment.html 

      parent reply	other threads:[~2014-03-14  0:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-07 11:57 Rebuild kernel so complicated? 乃宏周
2013-12-08 18:25 ` Sudip Mukherjee
2014-03-14  0:14 ` Razvan Ghitulete [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=532249FA.1020903@gmail.com \
    --to=razvan.ghitulete@gmail.com \
    --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).