[asterisk-bugs] [DAHDI-tools 0013910]: later debians: modprobe of blacklisted modules fails from init script

Mon Nov 17 13:44:57 CST 2008

The following issue has been SUBMITTED. 
====================================================================== 
http://bugs.digium.com/view.php?id=13910 
====================================================================== 
Reported By:                tzafrir
Assigned To:                
====================================================================== 
Project:                    DAHDI-tools
Issue ID:                   13910
Category:                   General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     new
====================================================================== 
Date Submitted:             2008-11-17 13:44 CST
Last Modified:              2008-11-17 13:44 CST
====================================================================== 
Summary:                    later debians: modprobe of blacklisted modules fails
from init script
Description: 
I believe hat this is a distribution bug (or maybe a feature), but I figure
DAHDI users will run into it and thus I prefer to at least document the
workaround.

It seems that in Debian Lenny (5.0) and probably also in some of the
latest versions of Ubuntu the init scripts are run with the environment
variable MODPROBE_OPTIONS set to -qb or -Qb . This means that modprobe will
silently fail to load any module that is listed as "blacklist" in the
modprobe configuration.

By default dahdi configures all the dahdi modules as blacklisted, to allow
strict control of their load order.

Possible workarounds:

1. in the 'start)' target of /etc/init.d/dahdi , unset this variable:

  unset MODPROBE_OPTIONS

2. If you don't have more than one dahdi device: don't blacklist the dahdi
modules.

3. Load the dahid modules in /etc/modules instead.

To test this, run the following command as root (checks the value of
MODPROBE_OPTIONS in the init process)

tr '\0' '\n' </proc/1/environ | grep ^MODPROBE_OPTIONS=