| 2009-03-10 02:10:21 |
Alex Sidorenko |
bug |
|
|
added bug |
| 2009-03-10 03:27:03 |
Noel J. Bergman |
bug |
|
|
added attachment 'powernowd.patch' (powernowd.patch) |
| 2009-03-10 03:27:22 |
Noel J. Bergman |
powernowd: status |
New |
Confirmed |
|
| 2009-03-10 03:27:22 |
Noel J. Bergman |
powernowd: statusexplanation |
|
|
|
| 2009-03-11 18:38:09 |
Florent |
description |
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:
{root 21:59:29} dpkg -L module-init-tools | fgrep lsmod
/usr/share/man/man8/lsmod.8.gz
/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. |
Two problems with script /etc/init.d/powernowd:
- it tries to use /sbin/lsmod
- it prints a "Usage:" message on standard output
The first problem affects other packages: see bug #341262
The second problem was first reported on bug #340300, now marked as duplicate.
These problems can be reproduced as follows.
root@jaunty:/var/log# /etc/init.d/powernowd.early start
/etc/init.d/powernowd: 180: /sbin/lsmod: not found
Usage: modprobe [-v] [-V] [-C config-file] [-d <dirname> ] [-n] [-i] [-q] [-b] [-o <modname>] [ --dump-modversions ] <modname> [parameters...]
modprobe -r [-n] [-i] [-v] <modulename> ...
modprobe -l -t <dirname> [ -a <modulename> ...]
Usage: modprobe [-v] [-V] [-C config-file] [-d <dirname> ] [-n] [-i] [-q] [-b] [-o <modname>] [ --dump-modversions ] <modname> [parameters...]
modprobe -r [-n] [-i] [-v] <modulename> ...
modprobe -l -t <dirname> [ -a <modulename> ...]
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:
{root 21:59:29} dpkg -L module-init-tools | fgrep lsmod
/usr/share/man/man8/lsmod.8.gz
/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.
|
|
| 2009-03-11 19:55:41 |
Florent |
description |
Two problems with script /etc/init.d/powernowd:
- it tries to use /sbin/lsmod
- it prints a "Usage:" message on standard output
The first problem affects other packages: see bug #341262
The second problem was first reported on bug #340300, now marked as duplicate.
These problems can be reproduced as follows.
root@jaunty:/var/log# /etc/init.d/powernowd.early start
/etc/init.d/powernowd: 180: /sbin/lsmod: not found
Usage: modprobe [-v] [-V] [-C config-file] [-d <dirname> ] [-n] [-i] [-q] [-b] [-o <modname>] [ --dump-modversions ] <modname> [parameters...]
modprobe -r [-n] [-i] [-v] <modulename> ...
modprobe -l -t <dirname> [ -a <modulename> ...]
Usage: modprobe [-v] [-V] [-C config-file] [-d <dirname> ] [-n] [-i] [-q] [-b] [-o <modname>] [ --dump-modversions ] <modname> [parameters...]
modprobe -r [-n] [-i] [-v] <modulename> ...
modprobe -l -t <dirname> [ -a <modulename> ...]
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:
{root 21:59:29} dpkg -L module-init-tools | fgrep lsmod
/usr/share/man/man8/lsmod.8.gz
/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.
|
Two problems with script /etc/init.d/powernowd:
- it tries to use /sbin/lsmod
- it prints a "Usage:" message on standard output
The first problem affects other packages: it is tracked on bug #340666
The second problem was first reported on bug #340300, now marked as duplicate.
These problems can be reproduced as follows.
root@jaunty:/var/log# /etc/init.d/powernowd.early start
/etc/init.d/powernowd: 180: /sbin/lsmod: not found
Usage: modprobe [-v] [-V] [-C config-file] [-d <dirname> ] [-n] [-i] [-q] [-b] [-o <modname>] [ --dump-modversions ] <modname> [parameters...]
modprobe -r [-n] [-i] [-v] <modulename> ...
modprobe -l -t <dirname> [ -a <modulename> ...]
Usage: modprobe [-v] [-V] [-C config-file] [-d <dirname> ] [-n] [-i] [-q] [-b] [-o <modname>] [ --dump-modversions ] <modname> [parameters...]
modprobe -r [-n] [-i] [-v] <modulename> ...
modprobe -l -t <dirname> [ -a <modulename> ...]
|
|
| 2009-03-11 23:32:33 |
Florent |
bug |
|
|
added attachment 'fix-powernowd-init.patch' (fix-powernowd-init.patch) |
| 2009-03-13 11:20:07 |
Launchpad Janitor |
powernowd: status |
Confirmed |
Fix Released |
|
| 2009-12-05 06:33:09 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/powernowd |
|
