Question : 2.6 Kernel problems (scsi_mod) fails to load

I'm trying to compile a kernel for CentOS 4.1, and its failing.

Current kernel

# uname -a
Linux localhost.localdomain 2.6.9-5.0.3.ELsmp #1 SMP Sat Feb 19 19:38:02 CST 2005 i686 i686 i386 GNU/Linux

Want to install linux-2.6.9-11.EL. Compliled everything, installed all the files in /boot

This is the message I'm getting at the bootup::

Uncompressing Linux ... Ok, booting the kernel
audit (1121264021.534:0) : initialized
insmod: error inserting '/lib/scsi_mod.ko': -1 operation not permitted
ERROR: /bin/insmod exited abnormally (pid 177)
insmod: error inserting '/lib/sd_mod.ko': -1 operation not permitted
ERROR: /bin/insmod exited abnormally (pid 178)

Current lsmod

[root@localhost src]# lsmod
Module                  Size  Used by
iptable_filter          6721  0
ip_tables              21441  1 iptable_filter
parport_pc             27904  1
lp                     15405  0
parport                37641  2 parport_pc,lp
autofs4                22085  0
i2c_dev                14273  0
i2c_core               25921  1 i2c_dev
sunrpc                137637  1
button                 10449  0
battery                12869  0
ac                      8773  0
md5                     8001  1
ipv6                  238817  12
uhci_hcd               32473  0
ehci_hcd               31813  0
snd_intel8x0           34537  2
snd_ac97_codec         65297  1 snd_intel8x0
snd_pcm_oss            52345  0
snd_mixer_oss          21825  2 snd_pcm_oss
snd_pcm                92101  2 snd_intel8x0,snd_pcm_oss
snd_timer              27973  1 snd_pcm
snd_page_alloc         13641  2 snd_intel8x0,snd_pcm
snd_mpu401_uart        11329  1 snd_intel8x0
snd_rawmidi            27749  1 snd_mpu401_uart
snd_seq_device         11849  1 snd_rawmidi
snd                    56485  11 snd_intel8x0,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer,snd_mpu401_uart,snd_rawmidi,snd_seq_device
soundcore              12961  2 snd
tg3                    79173  0
floppy                 58065  0
dm_snapshot            20837  0
dm_zero                 6337  0
dm_mirror              24989  2
ext3                  118473  2
jbd                    59481  1 ext3
dm_mod                 57157  6 dm_snapshot,dm_zero,dm_mirror
aic79xx               187613  2
sd_mod                 20545  3
scsi_mod              116301  2 aic79xx,sd_mod

# ls -la /boot
total 9868
drwxr-xr-x   4 root root    1024 Jul 13 14:10 .
drwxr-xr-x  25 root root    4096 Jul 13 14:19 ..
-rw-r--r--   1 root root    5824 Feb 21 14:43 boot.b
-rw-r--r--   1 root root     612 Feb 21 14:43 chain.b
-rw-r--r--   1 root root   48181 Feb 19 20:18 config-2.6.9-5.0.3.EL
-rw-r--r--   1 root root   47676 Feb 19 21:30 config-2.6.9-5.0.3.ELsmp
drwxr-xr-x   2 root root    1024 Jul 12 13:11 grub
-rw-r--r--   1 root root 1130233 Jul 13 14:10 initrd-2.6.9-11EL.img
-rw-r--r--   1 root root 1123556 Jul 12 12:42 initrd-2.6.9-5.0.3.EL.img
-rw-r--r--   1 root root 1112359 Jul 12 12:42 initrd-2.6.9-5.0.3.ELsmp.img
drwx------   2 root root   12288 Jul 12 08:34 lost+found
-rw-r--r--   1 root root   81860 Feb 21 14:35 memtest86+-1.26
-rw-r--r--   1 root root   10213 Feb 26 12:39 message
-rw-r--r--   1 root root   10213 Feb 26 12:39 message.ja
-rw-r--r--   1 root root     640 Feb 21 14:43 os2_d.b
lrwxrwxrwx   1 root root      28 Jul 13 12:57 System.map -> System.map-2.6.9-11.ELcustom
-rw-r--r--   1 root root  742002 Jul 13 12:57 System.map-2.6.9-11.ELcustom
-rw-r--r--   1 root root  712690 Feb 19 20:18 System.map-2.6.9-5.0.3.EL
-rw-r--r--   1 root root  741047 Feb 19 21:30 System.map-2.6.9-5.0.3.ELsmp
lrwxrwxrwx   1 root root      25 Jul 13 12:57 vmlinuz -> vmlinuz-2.6.9-11.ELcustom
-rw-r--r--   1 root root 1400539 Jul 13 13:48 vmlinuz-2.6.9-11.ELcustom
-rw-r--r--   1 root root 1433883 Feb 19 20:18 vmlinuz-2.6.9-5.0.3.EL
-rw-r--r--   1 root root 1400375 Feb 19 21:30 vmlinuz-2.6.9-5.0.3.ELsmp

# cat /etc/grub.conf
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE:  You have a /boot partition.  This means that
#          all kernel and initrd paths are relative to /boot/, eg.
#          root (hd1,0)
#          kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00
#          initrd /initrd-version.img
#boot=/dev/sda
default=0
timeout=20
splashimage=(hd1,0)/grub/splash.xpm.gz
hiddenmenu
title CentOS 4.0 (2.6.9-5.0.3.ELsmp)
        root (hd1,0)
        kernel /vmlinuz-2.6.9-5.0.3.ELsmp ro root=/dev/VolGroup00/LogVol00 rhgb quiet
        initrd /initrd-2.6.9-5.0.3.ELsmp.img
title CentOS 4.0-up (2.6.9-5.0.3.EL)
        root (hd1,0)
        kernel /vmlinuz-2.6.9-5.0.3.EL ro root=/dev/VolGroup00/LogVol00 rhgb quiet
        initrd /initrd-2.6.9-5.0.3.EL.img
title CentOS 4.0-up (2.6.9-11.ELsmp)
        root (hd1,0)
        kernel /vmlinuz-2.6.9-11.ELcustom ro root=/dev/VolGroup00/LogVol00 rhgb quiet
        initrd /initrd-2.6.9-11EL.img

What I used to compile my kernel :

make gconfig
make
make modules_install
cp arch/i386/boot/bzImage /boot/vmlinuz-2.6.9-11.ELcustom

I didn't get any errors during the complilation, I just had to make my initrd manually.  
The .config file form the pervious kernel was used automatically by gconfig, I didn't change anything.

Here are my questions :

1. What am I missing here?    Looks like some SCSI modules are not loading, question is "Why" .  Did I miss somethign in gconfig, isn't it supposed to be a "working" copy from the previous kernel?

2. When I do lsmod, how can I link the modules in the lsmod in the .config file, meaning how can I ensure that they will be present/properly selected when I run gconfig

3. Any kind of other explanations between lsmod, inslmod, depmod, rmmod, etc when making a kernel are welcome

Answer : 2.6 Kernel problems (scsi_mod) fails to load

Have a look at the man page for mkinitrd.
Random Solutions  
 
programming4us programming4us