adaptec.s kernel upgrade for slackware?

cybrjackle · 12-08-2003, 08:46 AM

I just built a new system that has aic7889 scsi contoller. It is an SMP box and I will have to re-build the kernel to support the smp, anyway here is my question when I update 2.4.22 to .23, i plan on grabbing the "adaptec.s" ".config" for .23 but i don't have much experience with aic and scsi on linux so I have a few questions.

On my ide system, I would just go to slackware-current, grab

kernel-source-2.4.23-noarch-2.tgz
kernel-headers-2.4.23-i386-1
kernel-ide-2.4.23-i486-1
kernel-modules-2.4.23-i486-1

and just "upgradepkg", lilo and reboot and I'm done.

This is from slack

Quote:

Use upgradepkg to install the new kernel, kernel-modules, and alsa packages.
After installing the kernel-ide package you will need to run lilo ('lilo' at
a command prompt) or create a new system boot disk ('makebootdisk'), and
reboot.

If desired, a kernel from the kernels/ directory may be used instead. For
example, to use the kernel in kernels/scsi.s/, you would copy it to the
boot directory like this:

cd kernels/scsi.s
cp bzImage /boot/vmlinuz-scsi.s-2.4.23

Create a symbolic link:
ln -sf /boot/vmlinuz-scsi.s-2.4.23 /boot/vmlinuz

Then, run 'lilo' or create a new system boot disk and reboot.

So, in my case I would use the "adaptec.s" kernel. but do I still need the "headers & modules" packages?

What is the best way to get multiple kernels to boot? Using symlinks? It seems that /lib/mod<blahblahblah> gets confused with multiple kernels. Should I be using several sym's to point to one another?

Last question, what exactly does System.map do? Any good reads out there about it.

thx,

Tinkster · 12-09-2003, 03:08 PM

If you are about to build a custom kernel
you will only need the vanilla-source ...

Cheers,
Tink

DaHammer · 12-09-2003, 07:58 PM

When you install the new kernel it should update /lib/modules appropiately. Everything for the new kernel, if it's a different version, goes under it's own directory. This is done automatically when you install the modules from the source tree. Like so:

Code:

DaHammer@slack:/lib/modules$ ls -l
total 12
drwxr-xr-x    4 root     root         4096 Nov 26 04:19 2.4.22/
drwxr-xr-x    3 root     root         4096 Nov 26 16:35 2.6.0-test10/
drwxr-xr-x    3 root     root         4096 Dec  1 22:02 2.6.0-test11/