Re: Wheezy Driver for Intel RMS25CB080 RAID Controller
On 10/21/2012 10:10 AM, rick@microway.com wrote:
> I think the correct driver should be mpt2sas. That should be available in
> the regular kernel (no extra driver source needed), although I'm not sure
> off hand if Debian's binary kernel package includes it.
mpt2sas is for LSI based SAS/SATA HBAs. megaraid_sas is for LSI based
SAS/SATA RAID adapters.
Without further details from Chris I'm assuming megaraid_sas is loading
but not working. Is this the case Chris? If so I'm thinking the Intel
board simply isn't supported by the 3.2 megaraid_sas driver.
I sent an email this morning to James Bottomley hoping he can point
Chris in the right direction. Nothing back yet, but it's Sunday.
> I'm having similar trouble myself on another system because the isci
> driver is excluded. I posted several days ago but no one has replied about
> why isci is missing on the latest Debian testing release.
History seems to suggest that questions about kernel driver issues,
especially SCSI, don't get responses from Debian kernel team members.
I'd guess few, if any, sub this list. One is likely always better off
asking on the appropriate LKML sub lists, such as linux-scsi in this
case. The dev(s) who maintains megaraid_sas and mpt2sas sub that list.
And, if Debian has a team member who works with the SCSI subsystem,
s/he may be there as well. If not, surely someone there will ping him/her.
--
Stan
>> Anyone have any luck getting this family of new Intel RAID drivers working
>> in Debian Wheezy?
>>
>> It uses the LSI raid controller:
>> LSI Logic / Symbios Logic MegaRAID SAS 2208 [Thunderbolt]
>>
>> But the wheezy kernel's stock megaraid_sas driver does not seem to support
>> this card.
>>
>> I've downloaded the drivers from Intel, but they were written for the 2.6
>> kernel version
>> and for redhat and suse, not Debian or Ubuntu. So far I haven't gotten
>> them to build in wheezy.
>>
>> Intel raid card page:
>> http://www.intel.com/p/en_US/support/highlights/server/irm-rms25cb080
>>
>> Thanks,
>> Chris
>
>
>
Reply to: