Re: depmod: *** Unresolved symbols in /lib/modules (????huh)

[Roger Chrisman <rogerhc@pacbell.net>]

> > When custom compiling kernel 2.6.3, I got all these depmod *** notices:
> >
> > depmod: *** Unresolved sybmols in /lib/modules/2.6.3.20040305-orca
> > /kernel/drivers/acpi/thermal.ko
>
>  Are you sure you have module-init-tools installed, preferably from deb?

Aha, I did *not* have module-init-tools installed. Thank you for that tip. So 
I have now installed it with 'apt-get install module-init-tools' and have 
re-compiled kernel 2.3.6, using the same .config as before, as follows:

$ cd /usr/src/linux	   ((linux is a link to kernel-source-2.6.3))

$ fakeroot make-kpkg clean

$ fakeroot make-kpkg --append-to-version=.20040309.raid.orca kernel_image &> 
roger.kernel.compile.output

I inspecting my output file, roger.kernel.compile.output, and find the 
following related to depmod:

if [ -r System.map ]; then /sbin/depmod -ae -F System.map -b /usr/src/linux/
debian/tmp-image -r 2.6.3.20040309.raid.orca; fi
make[2]: Leaving directory `/usr/src/kernel-source-2.6.3'
depmod -q -FSystem.map -b debian/tmp-image 2.6.3.20040309.raid.orca
make[1]: depmod: Command not found
make[1]: [real_stamp_image] Error 127 (ignored)

I *worry* about the 'make[1]: depmod: Command not found'. This is different 
from getting lots of 'depmod: *** Unresolved symbols in /lib/modules ....' 
output but not reassuring to me.

module-init-tools *is* installed this time.

Dose 'depmod: Command not found' mean I am still missing something important?

Thanks,

Roger :-)

My kernel compiling procedure notes:
rogerchrisman.com/linux/kernel_compiling