From: redhowlingwolves@nc.rr.com (scott)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Kernel compilation
Date: Wed, 05 Jan 2011 00:34:32 -0500 [thread overview]
Message-ID: <4D2402E8.5000708@nc.rr.com> (raw)
I'm new to the list and would like to say hello to everyone. Now on to
the meat.
I have tried to compile a kernel with a grsec patch 5 times now using a
couple of different methods and I keep getting a "No init found" and
"Couldn't support optional features" errors every time at bootup.
I'm trying to use a vanilla 2.6.32.27 kernel on 10.04 Ubuntu and it
compiles fine,
just will not boot.
I've tried "CONCURRENCY_LEVEL=`getconf _NPROCESSORS_ONLN` fakeroot make-kpkg
--initrd --append-to-version=-custom kernel_image kernel_headers",
"CONCURRENCY_LEVEL=3 make-kpkg --initrd --append-to-version=-586
kernel_image kernel_headers modules_image".
I have all the reqs for building kernels such as build-essentials, fakeroot,
kernel-package, kernel-wedge, nurces-dev and qt for xconfig.
These are the steps I've taken. DL the kernel image from kernels.org, get
the patch from grsec.net, untar the kernel, cd into the directory created,
do a 'cp /boot/config-`uname -r` .config', 'make oldconfig', apply the
patch, then either 'make menuconfig' or 'make xconfig'. Then I do a
'make-kpkg clean' and run one of the commands in the first paragraph above.
I get the debs built and can install them just fine, but I keep getting the
same errors. I've cut out as many "Experimental" options I thought might
cause a problem and still get a kernel panic at boot.
Anyone have a clue what I'm doing wrong?
Scott
next reply other threads:[~2011-01-05 5:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-05 5:34 scott [this message]
2011-01-05 6:46 ` Kernel compilation Mulyadi Santosa
2011-01-05 7:10 ` scott
2011-01-05 7:37 ` Robert P. J. Day
-- strict thread matches above, loose matches on Subject: below --
2011-05-02 18:32 Sleep and Wake up Abu Rasheda
2011-05-02 19:40 ` Kernel compilation Ezequiel García
2011-05-05 14:15 ` Pico Geyer
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=4D2402E8.5000708@nc.rr.com \
--to=redhowlingwolves@nc.rr.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).