[Bug 81350] Re: init script broken
david butler
croepha at gmail.com
Tue Jul 8 14:27:32 UTC 2014
I came across this trying to troubleshoot a similar issue, I was getting
log output like that because my modules file had dos newlines
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to module-init-tools in Ubuntu.
https://bugs.launchpad.net/bugs/81350
Title:
init script broken
Status in “module-init-tools” package in Ubuntu:
Invalid
Bug description:
Binary package hint: module-init-tools
* Add a few modules to /etc/modules
* export VERBOSE=1
* Restart the computer or run /etc/init.d/module-init-tools
* no debugging information is shown
* the modules are not loaded
replacing the line:
if [ "$VERBOSE" != no ]; then
with:
if [ "$VERBOSE" ]; then
results in output. However the output is completely messed up:
* Loading manual drivers... ng module not found.le
[fail]
ng module lp not found.le lp
[fail]
ng module not found.le
[fail]
ng module i2c-viapro not found.le i2c_viapro
[fail]
ng module i2c-isa not found.le i2c_isa
[fail]
ng module eeprom not found.le eeprom
[fail]
ng module w83627hf not found.le w83627hf
[fail]
[ ok ]
Adding al line
echo " modprobe $module $args"
shows that the command line is correct. Apparently, modprobe cannot
locate the modules.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/module-init-tools/+bug/81350/+subscriptions
More information about the foundations-bugs
mailing list