The script /etc/init.d/powernowd tries to use /sbin/lsmod:
load_modules() {
#stop the kernel printk'ing at all while we load.
PRINTK=`cat /proc/sys/kernel/printk`
[ "$VERBOSE" = no ] && echo "1 1 1 1" > /proc/sys/kernel/printk
#build a list of current modules so we don't load a module twice LIST=`/sbin/lsmod|awk '!/Module/ {print $1}'` ^^^^^^^^
But modern module-init-tools package installs /bin/lsmod, not /sbin/lsmod:
The script /etc/init. d/powernowd tries to use /sbin/lsmod:
load_modules() { kernel/ printk` kernel/ printk
#stop the kernel printk'ing at all while we load.
PRINTK=`cat /proc/sys/
[ "$VERBOSE" = no ] && echo "1 1 1 1" > /proc/sys/
#build a list of current modules so we don't load a module twice
LIST=` /sbin/lsmod| awk '!/Module/ {print $1}'`
^^ ^^^^^^
But modern module-init-tools package installs /bin/lsmod, not /sbin/lsmod:
{root 21:59:29} dpkg -L module-init-tools | fgrep lsmod man/man8/ lsmod.8. gz
/usr/share/
/bin/lsmod
I suspect this is really an old problem (not just Jaunty) as I am able to see recommendations to do
# ln -s /bin/lsmod /sbin/lsmod
for different reasons on different distributions. So it is possible that the problem is not Jaunty-specific.
To be sure that module-init-tools does not create a link in postinstallation script, I reinstalled it - no link has been created.