Very Computer

We have done everyting by the book, but we can't compile a symetric
multiprocessor kernel with ServeRAID driver on IBM Netfinity 5500 M20.

Does any of you know something about this?

Thanx a lot:-)

R.

I found a link for the 5000 Model # 8659-6RY. I hope this helps

http://www.pc.ibm.com/qtechinfo/MIGR-
4C9RG6.html?lang=en_US&page=brand&brand=IBM+PC+Server%7CNetfinity+5000%
7C8659%7C6RY

Good Luck

Jason

Sent via Deja.com http://www.deja.com/
Before you buy.

Rolf,

For questions about this driver please use my email account at work:

Thanks. Only because that is where I did this and have all the information handy.

Yes, I have built and compiled such a kernel. So far the patches are specifically for the 2.2.5 and
above kernels. My particular machine is a Netfinity 5000 with dual PIII 500's and the 3L version of
the ServeRAID adapter, but the kernel will be the same. Start with a * 2.2.5 or above (although I
have tested only with exactly the 2.2.5-22 RedHat kernel). Make sure you apply or do not need the lilo
patch mentioned in the ips driver README. Then apply the kernel source patch for the ips driver,
exactly as described in the README. Or is it in the install instructions?

Then run the usual "make xconfig" (or "make config" or "make menuconfig"). Check off the 686
processor, the SMP kernel options. Make sure basic SCSI is on. You do NOT need to turn on RAID, since
you will most likely be presenting a single logical volume to the server from the hardware RAID array.
In the SCSI low level drivers turn on the IBM ServeRAID Adapter (ips driver) option. You may want to
turn on the Adaptec 294x/394x driver (aic7xxx driver) as well if you have a tape drive or something
else hooked up there. You may also want networking on, and the AMD PCnet PCI ethernet drivers. I have
compiled all these into the kernel, since they are in use all the time. This also makes making boot
diskettes and other options easier. When configuration is complete, save and exit.

Run "make dep;make clean".

Next you will build the kernel. Most likely the zImage kernel will be too big and give errors, so
instead use "make bzImage". This will provide extra kernel compression. It makes boot floppies very
slow to load, but they work with no ramdisk image.

The next instructions assume you are running this all on the Netfinity in question.

Next, do not use "make install". You probably will not need "make modules" and therefore "make
modules_install". Instead, just copy the bzImage file from /usr/src/linux/arch/i386/boot to /boot.

Next, edit /etc/lilo.conf and add a new "image=" section as follows:

 image=/boot/bzImage
       label=test

All the other stuff could be in the common area. If you have more lines than these two in the image
section that contains "label=linux", then duplicate the additional lines here. Save the file. Now run
the command "/sbin/lilo -v" and keep an eye on the messages. Make sure there are no showstoppers. They
could prevent you from booting. Otherwise, "shutdown -r now".

On reboot, at the "lilo:" prompt enter "test".

There is no need to compile the modules, and in fact I have had nothing but trouble when I try. If the
test boot is successful, you can move the /boot/bzImage file to /boot/vmlinuz-2.2.5-22, link
/boot/vmlinuz to it, and copy the vmlinux and System.map files from /usr/src/linux to /boot. Then
reconfigure lilo and run "lilo -v". Always check the lilo configuration and re-run the lilo command
any time you move or change kernels.

Hope this gets you farther than you already were.

linux.scsi,alt.os.linux,comp.os.linux.help,comp.os.linux.powerpc,comp.os.linux.setup,linux.support,no.
it.os.unix.linux.diverse

Werner Kliewer in Winnipeg
Using Virtual Access 4.52 build 277 (32-bit)