From: Nilesh Govindarajan <contact@nileshgr.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Anyone can afford information about build kernel?
Date: Sun, 09 Oct 2011 07:09:23 +0530 [thread overview]
Message-ID: <4E90FB4B.3010309@nileshgr.com> (raw)
In-Reply-To: <tencent_0CA7C366601F07487DA0E25F@qq.com>
On 10/09/2011 06:25 AM, Lavender wrote:
> It seems that no matter I build gentoo manually or with genkernel I
> can't have a fine-working kernel finally. Obviously I must solve it by
> myself , so I determined to build entire kernel all manually , it
> requests a lot of linux knowlege . All for that, I hope someone could
> tell me where to get this information , I haven't found them on
> gentoo.org , so please lead me to the correct direction, thank you for
> you all !
If you're new to building kernel, it will take some time to learn what
modules you need what options you should enable, etc.
You're building gentoo on some host Linux os, so you can use that os's
lsmod utility to know what modules you require.
Also, if some modules may be compiled right into the kernel you may not
be able to see them in the lsmod produces, instead use lspci -v for that.
One important thing I learnt the hard way while building gentoo for a
server- Always compile the critical modules like disk controllers, RAID,
also don't forget to use RAID autodetection if you're not going to use
an initramfs and filesystems (involved at boot) statically.
While citing my experience about building gentoo on a server, you have
to do the things invisibly, so you can't see what the kernel emits befor
panic.
It turned out that I'd disabled RAID autodetection and wasn't using an
initramfs either (which will load the arrays using mdadm).
--
Nilesh Govindarajan
http://nileshgr.com
next prev parent reply other threads:[~2011-10-09 1:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-09 0:55 [gentoo-user] Anyone can afford information about build kernel? Lavender
2011-10-09 1:19 ` Nick Khamis
2011-10-09 1:28 ` Dale
2011-10-09 1:39 ` Nilesh Govindarajan [this message]
2011-10-09 6:21 ` Volker Armin Hemmann
2011-10-09 13:56 ` Dale
2011-10-09 14:07 ` meino.cramer
2011-10-10 14:54 ` [gentoo-user] " James
-- strict thread matches above, loose matches on Subject: below --
2011-10-09 4:53 [gentoo-user] " Lavender
2011-10-09 5:55 ` Nilesh Govindarajan
2011-10-09 13:30 ` Michael Mol
2011-10-09 13:40 ` Michael Mol
2011-10-09 13:59 ` Dale
2011-10-09 14:05 ` Michael Mol
2011-10-09 14:02 ` Dale
2011-10-09 14:09 ` Michael Mol
2011-10-09 15:05 ` Dale
2011-10-09 9:49 Lavender
2011-10-09 16:53 ` Volker Armin Hemmann
2011-10-10 8:26 ` Spidey
2011-10-10 9:03 ` Neil Bothwick
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=4E90FB4B.3010309@nileshgr.com \
--to=contact@nileshgr.com \
--cc=gentoo-user@lists.gentoo.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