Slackware 11.0 and IBM ServeRAID SCSI Controller

merchtemeagle · 01-16-2007, 04:33 PM

I'm having the same problem as the topicstarter of
http://tinyurl.com/y36cp5 . I tried the suggested solution, but the module
ips can not be found.

Alien Bob · 01-16-2007, 05:36 PM

I guess you're running a self-compiled kernel then?

Code:

~$ /sbin/modinfo /lib/modules/2.4.33.3/kernel/drivers/scsi/ips.o.gz 
filename:       /lib/modules/2.4.33.3/kernel/drivers/scsi/ips.o.gz
kernel_version: 2.4.33.3
parm_ips:       s
license:        GPL
description:    IBM ServeRAID Adapter Driver 7.10.18


$ /sbin/modinfo ips
filename:       /lib/modules/2.6.17.13/kernel/drivers/scsi/ips.ko
license:        GPL
description:    IBM ServeRAID Adapter Driver 7.12.02
version:        7.12.02

It is there.

Eric

merchtemeagle · 01-16-2007, 06:11 PM

It's during the installation of Slackware, so the kernels I tried (scsi.s, scsi2.s, scsi3.s and some others) are the ones on the installation DVD.

Alien Bob · 01-16-2007, 11:46 PM

The ips driver is part of the "raid.s" boot kernel. Did you try that one?

Eric

merchtemeagle · 01-17-2007, 07:16 AM

Code:

boot: raid.s

Logged in as root:

Code:

#modprobe ips
modprobe: can't locate module ips

Alien Bob · 01-17-2007, 09:12 AM

The ips driver is part of the raid.s kernel, i.e. it is not available as a separate module. The booting kernel should recognize the ServeRAID adapter. Check the kernel message buffer (run "dmesg") to see whether the ServeRAID was mentioned during the boot-up.

Eric

merchtemeagle · 01-17-2007, 09:33 AM

Ok, I'll check it out. Thanks for your help.

cereal83 · 01-17-2007, 09:49 AM

I have used this card before and installed from cd is pretty much standard.

You boot with raid.s and it will detect your raid card, you then fdisk and format the drives and go ahead with a normal install.

After the install, you will most likely recompile the kernel. If the raid is your primary harddrive that will have the OS on it, then you can't use a module but have to compile support for this card into the driver. Usually IBM uses Adaptec Raid controllers so you will have to compile in Adaptec AACRAID but it can't be a module or else it won't boot, if it isn't the Adaptec driver then user SCSI --> SCSI Low Level drivers you will find a IBM ServeRaid option and you build that into the kernel. Then you recompile and reboot and it should work.

Hope this helps

merchtemeagle · 01-19-2007, 07:35 AM

Code:

$fdisk /dev/sda

Unable to open

Code:

$cfdisk /dev/sda

fatal error: cannot open disk drive

Alien Bob · 01-19-2007, 09:40 AM

What does

Code:

fdisk -l

report?

Eric

merchtemeagle · 01-19-2007, 09:48 AM

When booting with huge26.s cfdisk works. Could it be that raid.s does no longer contains the aacraid driver?

cereal83 · 01-19-2007, 09:58 AM

Quote:

Originally Posted by merchtemeagle

When booting with huge26.s cfdisk works. Could it be that raid.s does no longer contains the aacraid driver?

I looked into it and it actually seems like it's the IBM Serveraid option in the kernel on our server. raid.s always worked with us but we usually use test26.s or huge.s when we use Slack 11.

After you boot in and it is detected do dmesg and go through it to see what driver it is using and then you will know for sure and after you install the OS, you will know what the recompile in the kernel

Alien Bob · 01-19-2007, 10:08 AM

Quote:

Originally Posted by merchtemeagle

When booting with huge26.s cfdisk works. Could it be that raid.s does no longer contains the aacraid driver?

The raid.s kernel of Slackware 11 has aacraid in the kernel:

Code:

CONFIG_SCSI_AACRAID=y

Eric