Re: Kernel or patch suggestions for DMA enables Marvell Driver

[Terrence Martin <tmartin@physics.ucsd.edu>]

Bogdan Costescu wrote:

> On Wed, 21 Dec 2005, Terrence Martin wrote:
>
>> So I compiled 2.6.15-r5 without MSI enabled.
>
>
> Hmm, so far all reports indicated that MSI had to be disabled... so 
> maybe the Marvell controller is at fault.
>
>> Looking at MSI though it seems to indicate that without it I cannot 
>> get PCI-Express to work?
>
>
> I think that INTx emulation should be present by default if MSI is not 
> enabled, but I'm not sure...
>
Well I can see the PCI-E port on lspci. I can test them out with a PCI-E 
ethernet card on tuesday just ot make sure.

As for the card being a problem, possibly. I know I got one of my 
opterons to work with the marvell controller with the Marvell written 
driver and as far as I can tell RedHat enables MSI according to the 
kernel config in /boot. That was a binary driver though and on an 
Opteron, although the controller is claimed to be the same as what I 
have in the Xeons according to lspci.  I have not done the same steps 
for these Xeons. I have had little or no luck getting the marvell code 
to work with Redhat stock kernels in Centos 4.2 and was only able to use 
the Marvell driver as a binary compiled by supermicro with a 4.0 system.

I also do not see any mention of MSI in the instructions on how to 
install with the Marvell driver in RH FC.  
http://www.keffective.com/mvsata/ . At a glance it does not seem that 
MSI comes into play with the Marvell written driver, unfortunately that 
driver does not seem to like newer kernels, and I have not been able to 
get it to work myself when compiled from source. I am trying to track 
that problem down with Supermicro and my vendor.

Perhaps this might mean something to someone. With the Marvell source 
code I can get one of the versions to build with 2.6.15-rc5, however I 
get an error "insmod: error inserting 'mv_sata.ko': -1 Unknown symbol in 
module". Any ideas why that error?

Terrence