SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
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.
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.
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