Package: module-init-tools
Version: 3.7-pre5-1 0
Severity: important

Recently kernels I built from upstream kernel source failed to boot
after unpacking them because no modules got included in the initramfs
initrd (and thus no root file system).
This problem was solved after downgrading to m-i-t 3.4.1.

The problem seems to be that depmod, which is run as part of the build,
generates a modules.dep file with incomplete paths. These incomplete paths
in turn cause initramfs-tools to create a broken initrd.

An example line from modules.dep, with old m-i-t:
/lib/modules/2.6.27.19/kernel/arch/s390/crypto/sha512_s390.ko: 
/lib/modules/2.6.27.19/kernel/arch/s390/crypto/sha_common.ko
With new m-i-t:
kernel/arch/s390/crypto/sha512_s390.ko: kernel/arch/s390/crypto/sha_common.ko


The depmod invocation used in the upstream kernel Makefile is:
      cmd_depmod = \
        if [ -r System.map -a -x $(DEPMOD) ]; then                              
\
                $(DEPMOD) -ae -F System.map                                     
\
                $(if $(strip $(INSTALL_MOD_PATH)), -b $(INSTALL_MOD_PATH) -r)   
\
                $(KERNELRELEASE);                                               
\
        fi

-- System Information:
Debian Release: 5.0
  APT prefers sid
  APT policy: (500, 'sid')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.29-rc7 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to