Intel SASMF8I
in [Kernel]
|
Prev: x86-32: Split cache flush handler from simd handler
Next: Cosmetic:Partially remove deprecated __initcall() and change to
From: Marco Schindler on 19 Mar 2010 18:50 Hello, this card (using LSISAS1068(E)) is not recognized by FUSION_SAS, after patching the device code it appears to work nicely.
From: Ilia Mirkin on 19 Mar 2010 18:50 On Fri, Mar 19, 2010 at 6:39 PM, Marco Schindler <marco.schindler(a)gmail.com> wrote: > Hello, > this card (using LSISAS1068(E)) is not recognized by FUSION_SAS, after > patching the device code it appears to work nicely. > I was 99% of the way there to submit a similar patch (actually there's a few more places where you want to add the new ID), but noticed a previous discussion when a comparable patch was rejected. Turns out there was a jumper on my motherboard (Supermicro X8DT3) which switches between "raid" and "regular" mode (except they were called something much fancier), and the regular mode switches the PCI ID to 0x58 which in turn is recognized. [And the mptsas driver doesn't support the RAID features anyways... there's a what appears to be proprietary driver for that, megasr, which I did not need.] -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Marco Schindler on 19 Mar 2010 19:10 On 19.03.10 23:46, Ilia Mirkin wrote: > On Fri, Mar 19, 2010 at 6:39 PM, Marco Schindler > <marco.schindler(a)gmail.com> wrote: >> Hello, >> this card (using LSISAS1068(E)) is not recognized by FUSION_SAS, after >> patching the device code it appears to work nicely. >> > > I was 99% of the way there to submit a similar patch (actually there's > a few more places where you want to add the new ID), but noticed a > previous discussion when a comparable patch was rejected. Turns out > there was a jumper on my motherboard (Supermicro X8DT3) which switches > between "raid" and "regular" mode (except they were called something > much fancier), and the regular mode switches the PCI ID to 0x58 which > in turn is recognized. [And the mptsas driver doesn't support the RAID > features anyways... there's a what appears to be proprietary driver > for that, megasr, which I did not need.] SASMF8I doesn't seem to have any jumpers for "regular" mode and I don't want to use the sw raid of the chip. As far as I remember megasr didn't let me access drives directly. Is there no option then, except patching locally? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Christoph Hellwig on 20 Mar 2010 10:00
On Sat, Mar 20, 2010 at 12:04:16AM +0100, Marco Schindler wrote: > SASMF8I doesn't seem to have any jumpers for "regular" mode and I don't > want to use the sw raid of the chip. As far as I remember megasr didn't > let me access drives directly. Is there no option then, except patching > locally? I think we should add it in that case. There's no reason to cripple Linux on hardware just because the bios pretends it has some useless fake raid capabilities. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |