1Debugging Modules after 2.6.3
   4In almost all distributions, the kernel asks for modules which don't
   5exist, such as "net-pf-10" or whatever.  Changing "modprobe -q" to
   6"succeed" in this case is hacky and breaks some setups, and also we
   7want to know if it failed for the fallback code for old aliases in
   8fs/char_dev.c, for example.
  10In the past a debugging message which would fill people's logs was
  11emitted.  This debugging message has been removed.  The correct way
  12of debugging module problems is something like this:
  14echo '#! /bin/sh' > /tmp/modprobe
  15echo 'echo "$@" >> /tmp/modprobe.log' >> /tmp/modprobe
  16echo 'exec /sbin/modprobe "$@"' >> /tmp/modprobe
  17chmod a+x /tmp/modprobe
  18echo /tmp/modprobe > /proc/sys/kernel/modprobe
  20Note that the above applies only when the *kernel* is requesting
  21that the module be loaded -- it won't have any effect if that module
  22is being loaded explicitly using "modprobe" from userspace.
  23 kindly hosted by Redpill Linpro AS, provider of Linux consulting and operations services since 1995.