From: gmate.amit@gmail.com (Kumar amit mehta)
To: kernelnewbies@lists.kernelnewbies.org
Subject: kernel build error
Date: Sun, 24 Mar 2013 22:04:25 -0700 [thread overview]
Message-ID: <20130325050425.GA2810@gmail.com> (raw)
In-Reply-To: <CAGdaadYb2vAdteBoSk-krM4k1fBLKYVz6y38oFHP8kwCnkN6qA@mail.gmail.com>
On Sun, Mar 24, 2013 at 12:49:55PM +0700, Mulyadi Santosa wrote:
> On 3/22/13, Kumar amit mehta <gmate.amit@gmail.com> wrote:
> > I've uploaded the kernel configuration and the screenshot in google drive
> > [1].
>
> ok let's see........... hmmm, stuck during I/O memory mapping?.....
> sadly, no further info that explains the reason why it stuck there....
>
> > Just to be a little more verbose, I've listed below the steps that I follow
> > to
> > build and boot from the newly built kernel on my ubuntu box:
> >
> > $ sudo apt-get install build-essential
> > $ make oldconfig
> > $ make -jX all ;;Where X= Number of CPU cores
>
> somewhere I've read that to make sure compilation goes without any
> glitches, better run without any -j at all.
>
> > $ sudo make modules_install install
>
> regarding kernel image install, I usually do manual copy to /boot and
> adjust Grub config manually.
>
> Then when it comes to modules compilation and installation, usually I do :
> sudo make modules
> sudo make modules_install
>
>
> > $ sudo update-grub
> > $ sudo shutdown -y now
>
> try not using "quiet" kernel parameter, in case you currently use it.
> check /etc/default/grub..... and re run update-grub.
>
Thank you so much for your help.
Meanwhile I have updated my workspace with the latest linux-next tree and will
later try out the options that you've mentioned.
-Amit
next prev parent reply other threads:[~2013-03-25 5:04 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-17 15:28 kernel build error Kumar amit mehta
2013-03-18 4:21 ` Mulyadi Santosa
2013-03-19 5:28 ` Kumar amit mehta
2013-03-19 14:43 ` Mulyadi Santosa
2013-03-20 6:56 ` Kumar amit mehta
2013-03-20 7:07 ` Kumar amit mehta
2013-03-20 9:48 ` Ben Wu
2013-03-20 9:49 ` wake_lock in linux kernel Ben Wu
2013-03-21 4:34 ` Yuva Raj
2013-03-20 17:32 ` kernel build error Valdis.Kletnieks at vt.edu
2013-03-21 6:16 ` Kumar amit mehta
2013-03-22 3:41 ` Mulyadi Santosa
2013-03-22 10:17 ` Kumar amit mehta
2013-03-24 5:49 ` Mulyadi Santosa
2013-03-25 5:04 ` Kumar amit mehta [this message]
2013-03-25 7:36 ` Mulyadi Santosa
[not found] ` <20130331044544.GA3291@gmail.com>
2013-04-02 3:04 ` Mulyadi Santosa
2013-04-02 6:19 ` Kumar amit mehta
2013-04-02 13:40 ` Mulyadi Santosa
-- strict thread matches above, loose matches on Subject: below --
2019-08-22 12:27 Kernel " James David Lyons
2016-04-26 6:30 Kernel Build error Harinath maddelal
2016-04-26 6:43 ` Khem Raj
2016-04-26 7:10 ` Harinath maddelal
2016-04-26 14:17 ` Khem Raj
2005-05-12 22:30 Kernel build error mcnernbm
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=20130325050425.GA2810@gmail.com \
--to=gmate.amit@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 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.