From: Chris Pearson <chris-linux-scsi@twock.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: /dev/megadev0 missing with 2.6.26 kernel megaraid_mm
Date: Sun, 17 May 2009 20:27:16 +0100 [thread overview]
Message-ID: <20090517192716.GB9759@lamity.org> (raw)
In-Reply-To: <1242587981.11755.11.camel@mulgrave.int.hansenpartnership.com>
On Sun, May 17, 2009 at 02:19:41PM -0500, James Bottomley wrote:
> >From 2.6.25 onwards, megaraid_mm (the new megaraid driver) doesn't
> define its own block device like 2.4 did, but instead uses the misc
> devices. So, if you cat /proc/misc and megadev0 doesn't show up, it's a
> kernel problem. If it does, it's a debian udev problem.
Ahh, I see. It does indeed show up there so I'll raise it in a more
appropriate place. Thanks for the help.
Cheers,
Chris
prev parent reply other threads:[~2009-05-17 19:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-17 17:28 /dev/megadev0 missing with 2.6.26 kernel megaraid_mm Chris Pearson
2009-05-17 19:19 ` James Bottomley
2009-05-17 19:27 ` Chris Pearson [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=20090517192716.GB9759@lamity.org \
--to=chris-linux-scsi@twock.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-scsi@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