From: Alex Goddard How to debug module loading problems. The wording is a slightly changed version of what Rusty said. --- 25-akpm/Documentation/debugging-modules.txt | 18 ++++++++++++++++++ 1 files changed, 18 insertions(+) diff -puN /dev/null Documentation/debugging-modules.txt --- /dev/null Thu Apr 11 07:25:15 2002 +++ 25-akpm/Documentation/debugging-modules.txt Thu Feb 12 13:37:50 2004 @@ -0,0 +1,18 @@ +Debugging Modules after 2.6.3 +----------------------------- + +In almost all distributions, the kernel asks for modules which don't +exist, such as "net-pf-10" or whatever. Changing "modprobe -q" to +"succeed" in this case is hacky and breaks some setups, and also we +want to know if it failed for the fallback code for old aliases in +fs/char_dev.c, for example. + +In the past a debugging message which would fill people's logs was +emitted. This debugging message has been removed. The correct way +of debugging module problems is something like this: + +echo '#! /bin/sh' > /tmp/modprobe +echo 'echo "$@" >> /tmp/modprobe.log' >> /tmp/modprobe +echo 'exec /sbin/modprobe "$@"' >> /tmp/modprobe +chmod a+x /tmp/modprobe +echo /tmp/modprobe > /proc/sys/kernel/modprobe _