On 2005-07-18 18:03 Brad Dameron wrote:
On Mon, 2005-07-18 at 11:15 +0200, Anders Norrbring wrote:
On 2005-07-18 11:07 Sandy Drobic wrote:
Anders Norrbring wrote:
Well, the installtion detects the HBA correctly, lists it at the correct PCI slot etc. When the module is loaded, it tried to get adapter status, and fails doing so. The exact error displayed is: aborting=2 cmd=2 <c=0 t=1 l=0>.
I have tried the HBA in 3 different systems, same shit on all of them, except for the Arima HDAMA board where the installation locks up before even going to the first selection screen where I choose Installation, Rescue, Boot installed system, Memtest, etc.
I'll try to plug it into a Windows 2k server system, just to see what happens there...
I've sent a report to LSI-Logic as well, maybe it's a RMA case.
Just to be thorough, have you tried to exchange the SCSI cable and the terminator? Defective terminators often have strange effects.
Oh yeah.. It doesn't even load without anything connected!
Anders.
Try booting with mem=2000M. There are known issues with installing certain versions of SuSe and these controllers. Once you get it installed update your kernel and edit your /boot/grum/menu.lst file and remove the mem statement. Should work fine. If this does not fix it you could very possibly have a bad controller. LSI is very good with warranties.
Nope, it's not that either.. The controller now works fine in both tested 64-bit PCI systems. However, it still doesn't answer to the "get status" command when seated in a 32-bit PCI slot. LSI suggests it's a driver problem, but as far as I can see, the driver that comes on the 32-bit SLES distribution disks should be supporting a 32-bit bus. I'm not sure though. Anders.