install kernel 2.4.26-1-686-smp failure in modules.dep

[BillS]

I am trying to bring a 3.3 system up to date by adding in the 2.4.26 kernel like the 3.4 CD has. I did the install and recieved some warnings.

Setting up kernel-image-2.4.26-1-686-smp (2.4.26-2) ...
depmod: *** Unresolved symbols in /lib/modules/extra/alsa/snd-ad1816a.o
depmod: *** Unresolved symbols in /lib/modules/extra/alsa/snd-als100.o
depmod: *** Unresolved symbols in /lib/modules/extra/alsa/snd-azt2320.o
depmod: *** Unresolved symbols in /lib/modules/extra/alsa/snd-cmi8330.o
depmod: *** Unresolved symbols in /lib/modules/extra/alsa/snd-cs4232.o
depmod: *** Unresolved symbols in /lib/modules/extra/alsa/snd-cs4236.o
depmod: *** Unresolved symbols in /lib/modules/extra/alsa/snd-cs4281.o
depmod: *** Unresolved symbols in /lib/modules/extra/alsa/snd-cs46xx.o

Then I istalled:
kernel-headers... kernel-source ... module-init-tools was current.
I adjusted lilo.config, set vga=normal and rebooted.

The interesting files in /boot/ are:

-rw-r--r--    1 root     root        38746 Oct  3  2003 config-2.4.22-xfs
-rw-r--r--    1 root     root       921593 Oct  3  2003 vmlinuz-2.4.22-xfs
-rw-r--r--    1 root     root       541726 Oct  3  2003 System.map-2.4.22-xfs
lrwxrwxrwx    1 root     root           18 Jan 28 02:24 vmlinuz -> vmlinuz-2.4.22-xfs
lrwxrwxrwx    1 root     root           21 Jan 28 02:24 System.map -> System.map-2.4.22-xfs
-rw-r--r--    1 root     root       148574 Jan 28 02:37 initrd.gz
-rw-r--r--    1 root     root          512 Jan 28 02:37 knoppix-old-mbr.1075275478
      <.....>
-rw-r--r--    1 root     root        44553 May  1 05:14 config-2.4.26-1-686-smp
-rw-r--r--    1 root     root       924113 May  1 10:11 vmlinuz-2.4.26-1-686-smp
-rw-r--r--    1 root     root       547093 May  1 10:11 System.map-2.4.26-1-686-smp
-rw-r--r--    1 root     root          512 May  3 16:23 boot.0340
-rw-r--r--    1 root     root      4554752 Jul  1 15:20 initrd.img-2.4.26-1-686-smp
drwxr-xr-x   30 root     root         4096 Jul  1 15:20 ..
-rw-------    1 root     root        90112 Jul  1 15:40 map
drwxr-xr-x    2 root     root         4096 Jul  1 15:40 .

/etc/lilo.conf looks like:

default=2.4.22

image=/boot/vmlinuz-2.4.26-1-686-smp
        label=2.4.26
        initrd=/boot/initrd.img-2.4.26-1-686-smp
        read-only
        
image=/boot/vmlinuz-2.4.22-xfs
        label=2.4.22
        initrd=/boot/initrd.gz
        read-only
#       restricted
#       alias=1

Upon booting 2.4.26, 3 screens of text scroll by so fast as to be unreadable. But the end was many lines of:

modprobe:modprobe: Can't open dependancies file /lib/modules/extra/modules.dep

The file does exist and I can read it. The funny part is that all the paths point to the old 2.4.22-xfs, not the newly installed 2.4.26. Shouldn't there be one of these /extra/ directories for each kernel version. The other thing that may be just a coincidence is that all the modules in the /extra/ directory are here beacause of alsa, which I can't get to make a peep.

What next ?? Delete all the files in /extra/ and worry about the incomplete package later?

BillS

[BillS]

Here are some other items or observations:
> This kernel was obtained with a apt-get install; not a hdinstall from the CD
> Using the SCROLLLOCK key, these are the lines immediately before and after the modprobes bring down the systen:

Freeing unused kernel memory :120k freed
initrd-tools: 0.1.70
modprobe -k ide-core options= "hda=scsi" ..."hdh=scsi"
modprobe: Can't open dependencies file /lib/modules/extra/modulrs.dep
   <lots of copies of this>
pivot-root: No such file or directory
/sbin/init: 424: can not open /dev/console
Kernel panic:Attempted to kill init!

> When 2.4.26 boots (on another machine) that resulted from a HD-install, it uses 'initrd-tools: 0.1.68'. Could this difference be causing the ram disk image to be different somehow? If so, how does one retrogress to a specific version number?

Any guidance will be appreciated

BillS