mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Reinaldo Carvalho" <reinaldow@gmail.com>
To: "Jesper Juhl" <jesper.juhl@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: megaraid.c, all kernel versions, problem with multi-luns
Date: Wed, 30 May 2007 20:19:43 -0300	[thread overview]
Message-ID: <ec36785a0705301619x470f4ecel5f1c191afa429c78@mail.gmail.com> (raw)
In-Reply-To: <9a8748490705301615y73a11fcfn5fc7a88bf6eef2b1@mail.gmail.com>

Yes CONFIG_SCSI_MULTI_LUN as build-in.

-- 
Reinaldo Carvalho


2007/5/30, Jesper Juhl <jesper.juhl@gmail.com>:
> On 31/05/07, Reinaldo Carvalho <reinaldow@gmail.com> wrote:
> > Hi,
> >
> > I have a Dell PowerEdge Expandable RAID controller, with a hardware
> > Raid-5 at Channel 01 running perfectly, and a nCipher Crypter at
> > Channel 02.
> >
> > This controller doesn't correctly detect devices (e.g. nCipher
> > Crypter) with multiples LUNs. Only one LUN is detected.
> >
> > At another controller (e.g. Adaptec 79xx) two LUNs were detect. I
> > compiled 2.6.8, 2.6.18 and 2.6.21.3 to test megaraid driver and all
> > failed detecting two LUNs.
> >
>
> Did you build your kernel with CONFIG_SCSI_MULTI_LUN enabled?  This
> option will force the SCSI driver to probe for multiple LUN's.
> Without this option only one LUN may be detected, and since that's the
> common case (devices only having one LUN) people often forget about
> this option :)
>
> --
> Jesper Juhl <jesper.juhl@gmail.com>
> Don't top-post  http://www.catb.org/~esr/jargon/html/T/top-post.html
> Plain text mails only, please      http://www.expita.com/nomime.html
>

  reply	other threads:[~2007-05-30 23:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-30 23:09 Reinaldo Carvalho
2007-05-30 23:15 ` Jesper Juhl
2007-05-30 23:19   ` Reinaldo Carvalho [this message]
2007-06-01 23:42 ` Andrew Morton
2007-06-02  1:40 ` Patro, Sumant

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=ec36785a0705301619x470f4ecel5f1c191afa429c78@mail.gmail.com \
    --to=reinaldow@gmail.com \
    --cc=jesper.juhl@gmail.com \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®