All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Belhomme <rico@ricospirit.net>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-scsi@vger.kernel.org,
	"bugme-daemon@kernel-bugs.osdl.org"
	<bugme-daemon@bugzilla.kernel.org>
Subject: Re: Fw: [Bugme-new] [Bug 7999] New: MegaRAID Legacy doesn't work with LSI MegaRAID i4 since release 2.00.4
Date: Tue, 13 Feb 2007 22:35:24 +0100	[thread overview]
Message-ID: <45D22F1C.7060604@ricospirit.net> (raw)
In-Reply-To: <1171389557.3382.34.camel@mulgrave.il.steeleye.com>

James Bottomley a écrit :

> This is by design ... the i4 is now supported by the new megaraid_mbox
> driver.  Please retry with that driver.
> 
Damn ! I spent many hours trying many kernel version, but I never 
imagined the card support would be translated on megaraid NG !!!

By the way, I added megaraid NG modules on my 2.6.20 and my i4 card is 
now recognized... But I can't figure how it works :

hole:/home/rico# lsmod|grep megaraid
megaraid_mbox          35368  0
megaraid_mm            12068  1 megaraid_mbox
megaraid               41704  1
scsi_mod              151980  7 
megaraid_mbox,sr_mod,sd_mod,megaraid,sg,aic7xxx,scsi_transport_spi
ho

So if I understand well, the module actively used with the LSI card is 
megaraid, the legacy one ! but the mbox and mm are loaded and seems to 
be necessary for the legacy driver ?

Never mind, sorry for the inconvenience... and the noise on the lkdml !

Regards,

-- 
Rico
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2007-02-13 21:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-13 17:29 Fw: [Bugme-new] [Bug 7999] New: MegaRAID Legacy doesn't work with LSI MegaRAID i4 since release 2.00.4 Andrew Morton
2007-02-13 17:59 ` James Bottomley
2007-02-13 21:35   ` Eric Belhomme [this message]
2007-02-13 22:36     ` James Bottomley
2007-02-14  9:54       ` Eric Belhomme
  -- strict thread matches above, loose matches on Subject: below --
2007-02-15  0:19 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=45D22F1C.7060604@ricospirit.net \
    --to=rico@ricospirit.net \
    --cc=James.Bottomley@SteelEye.com \
    --cc=akpm@linux-foundation.org \
    --cc=bugme-daemon@bugzilla.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.