megaraid_mbox and megaraid_mm are the modules for "new generation". There is no dependency of these modules to megaraid legacy. Could you please send me the lspci output from the system under test? --Sumant -----Original Message----- From: linux-scsi-owner@xxxxxxxxxxxxxxx [mailto:linux-scsi-owner@xxxxxxxxxxxxxxx] On Behalf Of Eric Belhomme Sent: Wednesday, February 14, 2007 1:55 AM To: James Bottomley Cc: Andrew Morton; linux-scsi@xxxxxxxxxxxxxxx; bugme-daemon@xxxxxxxxxxxxxxxxxxxx Subject: Re: Fw: [Bugme-new] [Bug 7999] New: MegaRAID Legacy doesn't work with LSI MegaRAID i4 since release 2.00.4 James Bottomley a écrit : >> 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 ? > > Actually, it shouldn't be. megaraid_mbox depends on megaraid_mm as > your lsmod shows, which is correct. However, nothing's depending on > legacy megaraid ... I'm not sure why it's showing as loaded and in use. > but it is ! moreover I have a /proc/megaraid/hba1/ directory structure fully filled with my RAID card, drives, and RAID volumes informations, and I don't hav any entry in sysfs directory tree (witch is the right place for megaraid NG module) I'd like to understand _why_ this module supposed to be independant from the "new generation" megaraid module needs megaraid NG to be compiled to work correctly ? I looked over the sources but I didn't found any link between the legacy driver and the newgen one... quite strange ! Regards, -- Rico - To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html - To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
