From: "J. Hart" <af804@bfn.org>
To: linux raid <linux-raid@vger.kernel.org>
Subject: 2.6.19-rc5: Can't get built-in raid support, modular works correctly
Date: Thu, 19 Jul 2007 22:54:04 +0900 [thread overview]
Message-ID: <469F6CFC.5050700@bfn.org> (raw)
When I configure a 2.6.19-rc5 linux kernel for "built-in" raid support,
I do not get the expected /proc/mdstat entry. I set the following
kernel parameters for this :
CONFIG_MD=Y
BLK_DEV_MD=y
MD_RAID0=y
When I configure the kernel for modular raid support in otherwise
identical fashion, I do get the expected /proc/mdstat "file". I have no
difficulty configuring "built-in" support under kernel 2.6.13 on another
32 bit X86 based system with IDE drives. The system I am trying to set
up raid support for is X86_64 based, and has only SATA drives. I have
not configured IDE support for it. Any ideas would be greatly appreciated.
next reply other threads:[~2007-07-19 13:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-19 13:54 J. Hart [this message]
2007-07-19 16:04 ` 2.6.19-rc5: Can't get built-in raid support, modular works correctly Justin Piszcz
2007-07-19 21:54 ` J. Hart
2007-07-20 10:13 ` Justin Piszcz
2007-07-20 16:06 ` J. Hart
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=469F6CFC.5050700@bfn.org \
--to=af804@bfn.org \
--cc=linux-raid@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 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).