public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Csillag Tamas <cstamas@digitus.itk.ppke.hu>
To: "Ju, Seokmann" <Seokmann.Ju@lsil.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: megaraid not working in 2.6.18
Date: Wed, 11 Oct 2006 08:57:43 +0200	[thread overview]
Message-ID: <20061011065742.GE905@digitus> (raw)
In-Reply-To: <890BF3111FB9484E9526987D912B261932E3CE@NAMAIL3.ad.lsil.com>

On 10/10, Ju, Seokmann wrote:
>  
> Hi,
> > However the legacy megaraid drivers does not work either. I get
> > unknown-block-device error when the kernel tries to mount sdaX.
> > I do not even see the megaraid driver coming up! no detecting 
> > messages like
> > in 2.6.11
> From 2.6.13 or later, old megaraid controllers, like yours, has to go with megaraid legacy driver.
> I'm not sure why the driver gets failed to load. 
> For further assist, please contact LSI customer service if you bought directly from LSI, or contact your system maker.
> 
> Thank you,

Well that's an old (legacy? ;-) server we do not want to throw out. The
vendor is HP. We do not have support for linux AFAIK we never had.

I will start examining the source (and the patches after 2.6.13) if I
can see some obvious...

But if you have any hints please tell me.

Thanks.

-- 
"If you have an apple and I have  an apple and we  exchange apples then you
and I will still each have  one apple. But  if you have an idea and I have
an idea and we exchange these ideas, then each of us will have two ideas."
                 -- George Bernard Shaw

CSILLAG Tamas (cstamas) - http://digitus.itk.ppke.hu/~cstamas

  reply	other threads:[~2006-10-11  6:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-10 13:03 megaraid not working in 2.6.18 Ju, Seokmann
2006-10-11  6:57 ` Csillag Tamas [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-10-10  9:07 Csillag Tamas

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=20061011065742.GE905@digitus \
    --to=cstamas@digitus.itk.ppke.hu \
    --cc=Seokmann.Ju@lsil.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