I've just build a 2.1.62 kernel (make dep && make clean && make -j),
put that in place and installed the modules (make -j modules && make
install_modules). However, when Linux boots up, I see this:
Finding module dependencies***Unresolved symbols in module /lib/modules/2.1.62/fs/autofs.o
***Unresolved symbols in module /lib/modules/2.1.62/fs/binfmt_java.o
...
and so on, for about a page or so. I'm using it with Redhat 4.1 or 4.2
distribution (comes with 2.0.29/30 kernel). The kernel compiled cleanly,
except for a few warnings about type compatibility problems.
What's the story ? Do I need updated userland tools ?
Relevant kernel options:
CONFIG_MODULES=y
CONFIG_MODVERSIONS=y
CONFIG_KERNELD=y
Also, I see these, is this normal ? Can they be turned off ?
d_alloc: 433 unused, pruning dcache
[and so on]
Darren
p.s. when is this crap going to be shovelled into the rubbish tip and
replaced with something that actually works ? It simply *doesn't* make
*any* sense to me why this doesn't work. Both kernel and object modules
are from the same kernel version! If there's a user/kernel mismatch
between modprobe & friends, then some sort of warning or message saying
that would be a good idea...