legacy megaraid status

legacy megaraid status

[Yiannis Mavroukakis]

Hello,

What is the current situation with the legacy megaraid driver? It seems 
that is is broken for a lot
of people with old raid cards.

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________

Re: legacy megaraid status

[Kenneth Porter]

--On Wednesday, September 21, 2005 4:01 PM +0100 Yiannis Mavroukakis 
<jander@darthvader.us> wrote:

> What is the current situation with the legacy megaraid driver? It seems
> that is is broken for a lot
> of people with old raid cards.

Any particular card you're interested in?

I've got a test kernel built based on Fedora Core 4's installation kernel 
to try the new driver with the old i4-100 (ATA100 RAID) but haven't had a 
chance to build a boot disk with it so I can test it on my working Fedora 
Core 2 server. (Gotta re-learn how to make boot media. Haven't done that 
since I made a boot floppy with Red Hat 6.)

Re: legacy megaraid status

[Yiannis Mavroukakis]

Kenneth Porter wrote:

> --On Wednesday, September 21, 2005 4:01 PM +0100 Yiannis Mavroukakis 
> <jander@darthvader.us> wrote:
>
>> What is the current situation with the legacy megaraid driver? It seems
>> that is is broken for a lot
>> of people with old raid cards.
>
>
> Any particular card you're interested in?
>
> I've got a test kernel built based on Fedora Core 4's installation 
> kernel to try the new driver with the old i4-100 (ATA100 RAID) but 
> haven't had a chance to build a boot disk with it so I can test it on 
> my working Fedora Core 2 server. (Gotta re-learn how to make boot 
> media. Haven't done that since I made a boot floppy with Red Hat 6.)
> -
> 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

This bunny
02:01.1 I2O: Intel Corporation 80960RP [i960RP Microprocessor] (rev 05) 
(prog-if 01)
        Subsystem: Hewlett-Packard Company HP NetRAID-1Si
        Flags: bus master, fast Back2Back, medium devsel, latency 32, IRQ 17
        Memory at fe000000 (32-bit, prefetchable) [size=4M]
        Expansion ROM at <unassigned> [disabled] [size=32K]
        Capabilities: [80] Power Management version 2

I'm stuck with 2.6.11-mm4 at the mo :)

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________

Re: legacy megaraid status

[Kenneth Porter]

--On Thursday, September 22, 2005 9:50 AM +0100 Yiannis Mavroukakis 
<jander@darthvader.us> wrote:

> 02:01.1 I2O: Intel Corporation 80960RP [i960RP Microprocessor] (rev 05)
> (prog-if 01)
>         Subsystem: Hewlett-Packard Company HP NetRAID-1Si
>         Flags: bus master, fast Back2Back, medium devsel, latency 32, IRQ
> 17
>         Memory at fe000000 (32-bit, prefetchable) [size=4M]
>         Expansion ROM at <unassigned> [disabled] [size=32K]
>         Capabilities: [80] Power Management version 2

Any idea what the PCI ID quad is? (See the pci.ids file for examples.)

One possibility is that it's "close enough" to one of the cards listed in 
the PCI ID table in megaraid_mbox.c and you can just add the ID for this 
one. I'll wait for one of the LSI people to weigh in on whether that would 
work.

Re: legacy megaraid status

[Markus Lidel]

Hello,

Kenneth Porter wrote:
> --On Thursday, September 22, 2005 9:50 AM +0100 Yiannis Mavroukakis 
> <jander@darthvader.us> wrote:
> 
>> 02:01.1 I2O: Intel Corporation 80960RP [i960RP Microprocessor] (rev 05)
>> (prog-if 01)
>>         Subsystem: Hewlett-Packard Company HP NetRAID-1Si
>>         Flags: bus master, fast Back2Back, medium devsel, latency 32, IRQ
>> 17
>>         Memory at fe000000 (32-bit, prefetchable) [size=4M]
>>         Expansion ROM at <unassigned> [disabled] [size=32K]
>>         Capabilities: [80] Power Management version 2
> Any idea what the PCI ID quad is? (See the pci.ids file for examples.)
> One possibility is that it's "close enough" to one of the cards listed 
> in the PCI ID table in megaraid_mbox.c and you can just add the ID for 
> this one. I'll wait for one of the LSI people to weigh in on whether 
> that would work.

If changing the PCI ID doesn't work, you could switch the controller to 
I2O mode and use the I2O driver. But after doing so it's not possible to 
use the megaraid utilities anymore.


Best regards,


Markus Lidel
------------------------------------------
Markus Lidel (Senior IT Consultant)

Shadow Connect GmbH
Carl-Reisch-Weg 12
D-86381 Krumbach
Germany

Phone:  +49 82 82/99 51-0
Fax:    +49 82 82/99 51-11

E-Mail: Markus.Lidel@shadowconnect.com
URL:    http://www.shadowconnect.com

Re: legacy megaraid status

[Yiannis Mavroukakis]

Markus Lidel wrote:

> Hello,
>
> Kenneth Porter wrote:
>
>> --On Thursday, September 22, 2005 9:50 AM +0100 Yiannis Mavroukakis 
>> <jander@darthvader.us> wrote:
>>
>>> 02:01.1 I2O: Intel Corporation 80960RP [i960RP Microprocessor] (rev 05)
>>> (prog-if 01)
>>>         Subsystem: Hewlett-Packard Company HP NetRAID-1Si
>>>         Flags: bus master, fast Back2Back, medium devsel, latency 
>>> 32, IRQ
>>> 17
>>>         Memory at fe000000 (32-bit, prefetchable) [size=4M]
>>>         Expansion ROM at <unassigned> [disabled] [size=32K]
>>>         Capabilities: [80] Power Management version 2
>>
>> Any idea what the PCI ID quad is? (See the pci.ids file for examples.)
>> One possibility is that it's "close enough" to one of the cards 
>> listed in the PCI ID table in megaraid_mbox.c and you can just add 
>> the ID for this one. I'll wait for one of the LSI people to weigh in 
>> on whether that would work.
>
>
> If changing the PCI ID doesn't work, you could switch the controller 
> to I2O mode and use the I2O driver. But after doing so it's not 
> possible to use the megaraid utilities anymore.
>
>
> Best regards,
>
>
> Markus Lidel

It seems to be closest to this one

* INTEL RAID Controller SRCS16         1000    1960    8086    0523

However I am not quite about the SSID..Is this the Subsystem hex lspci 
reports?

02:01.1 Class 0e00: 8086:1960 (rev 05) (prog-if 01)
Subsystem: 103c:10cd


______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________

Re: legacy megaraid status

[Kenneth Porter]

--On Friday, September 23, 2005 10:35 AM +0100 Yiannis Mavroukakis 
<jander@darthvader.us> wrote:

> However I am not quite about the SSID..Is this the Subsystem hex lspci
> reports?

I'm not at the machine right now to check, but I recall skimming through 
the source to the various macros and enumeration code to figure out how 
this information was extracted.

Re: legacy megaraid status

[Yiannis Mavroukakis]

Kenneth Porter wrote:

> --On Friday, September 23, 2005 10:35 AM +0100 Yiannis Mavroukakis 
> <jander@darthvader.us> wrote:
>
>> However I am not quite about the SSID..Is this the Subsystem hex lspci
>> reports?
>
>
> I'm not at the machine right now to check, but I recall skimming 
> through the source to the various macros and enumeration code to 
> figure out how this information was extracted.
>
> -
> 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

When you get a moment, if you could point me in the right direction I 
would appreciate it

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________

Re: legacy megaraid status

[Kenneth Porter]

--On Wednesday, September 28, 2005 3:30 PM +0100 Yiannis Mavroukakis 
<jander@darthvader.us> wrote:

>>> However I am not quite about the SSID..Is this the Subsystem hex lspci
>>> reports?
>>
>>
>> I'm not at the machine right now to check, but I recall skimming
>> through the source to the various macros and enumeration code to
>> figure out how this information was extracted.
>
> When you get a moment, if you could point me in the right direction I
> would appreciate it

Took a little backtracking, but look at drivers/pci/probe.c and the symbols 
in pci.h for the offsets in the configuration space.