Kernel Modules

You have to generate a new ramdisk (initrd.gz) with the new modules by
issuing
a command like "mkintrd --preload module-name initrd-2.2.xx.img 2.2.xx"

(this assumes you built ramdisk support into your kernel, you can find
out by looking into your /boot/config-2.2.xx file)

and edit lilo.conf with something like

initrd="/boot/initrd-2.2.xx.gz"
append="load_ramdisk=1 ramdisk_size=2880"

(change the above to reflect your system and remove the quotes)

to reflect the change and run lilo...

or

Build loop back support, scsi device support, scsi disk support and your
particular low-level scsi driver support into the kernel.

HTH,

Bucky in Prescott Valley

Don Harrop wrote:
>
> I've recompiled, for tuning reasons, a linux kernel before. Now I'm in
> the midst of upgrading and building a new kernal from the sources. I've
> got the new kernel in place and it boots but none of my scsi stuff comes
> up. The reason being that I don't have any modules for the new
> kernel. I'm on a RH system so the modules for the previous kernel are in
> the /lib/modules/linux-2.2.xx directory. Where do I find and how do I
> build the modules for the new kernel. I thought they would come with the
> source of the new kernel but I guess not.

--
(defun do-nothing()
(interactive)
)