Skip to contentSkip to conversation

Intel SASMF8I

PATCH Marco Schindler 3 participants 4 messages Mar 19, 2010 – Mar 20, 2010

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

Hello,
this card (using LSISAS1068(E)) is not recognized by FUSION_SAS, after patching the device code it appears to work nicely.

drivers/message/fusion/lsi/mpi_cnfg.h +1 -0
diff -ru --exclude=auto.conf --exclude=autoconf.h --exclude=mptsas.mod.c --exclude='*.o' --exclude='*.ko' linux.old/drivers/message/fusion/lsi/mpi_cnfg.h linux.new/drivers/message/fusion/lsi/mpi_cnfg.h
@@ -569,6 +569,7 @@
 #define MPI_MANUFACTPAGE_DEVID_SAS1066E             (0x005A)
 #define MPI_MANUFACTPAGE_DEVID_SAS1068              (0x0054)
 #define MPI_MANUFACTPAGE_DEVID_SAS1068E             (0x0058)
+#define MPI_MANUFACTPAGE_DEVID_SAS1068_820XELP      (0x0059)
 #define MPI_MANUFACTPAGE_DEVID_SAS1078              (0x0062)
 
 
drivers/message/fusion/mptsas.c +2 -0
diff -ru --exclude=auto.conf --exclude=autoconf.h --exclude=mptsas.mod.c --exclude='*.o' --exclude='*.ko' linux.old/drivers/message/fusion/mptsas.c linux.new/drivers/message/fusion/mptsas.c
@@ -3335,6 +3335,8 @@
 		PCI_ANY_ID, PCI_ANY_ID },
 	{ PCI_VENDOR_ID_LSI_LOGIC, MPI_MANUFACTPAGE_DEVID_SAS1078,
 		PCI_ANY_ID, PCI_ANY_ID },
+	{ PCI_VENDOR_ID_LSI_LOGIC, MPI_MANUFACTPAGE_DEVID_SAS1068_820XELP,
+		PCI_ANY_ID, PCI_ANY_ID },
 	{0}	/* Terminating entry */
 };
 MODULE_DEVICE_TABLE(pci, mptsas_pci_table);
#1 lore raw
Quoted 4 lines · Marco Schindler

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.]

#2 lore raw
Quoted 7 lines · Ilia Mirkin
Quoted 4 lines · Marco Schindler

Hello,
this card (using LSISAS1068(E)) is not recognized by FUSION_SAS, after patching the device code it appears to work nicely.

Quoted 9 lines

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?

#3 lore raw
Quoted 4 lines · Marco Schindler

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.