| Summary: | DAHTOOL-00007: [patch] later debians: modprobe of blacklisted modules fails from init script | ||
| Reporter: | Tzafrir Cohen (tzafrir) | Labels: | |
| Date Opened: | 2008-11-17 13:44:57.000-0600 | Date Closed: | 2008-12-12 15:34:17.000-0600 |
| Priority: | Minor | Regression? | No |
| Status: | Closed/Complete | Components: | General |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ( 0) modprobe_options.diff | |
| 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= See also: http://bugs.debian.org/426465 http://bugs.ubuntu.com/291619 A trivial patch is included here to implement (1) . | ||
| Comments: | By: Leif Madsen (lmadsen) 2008-11-24 13:27:58.000-0600 Oops... this should have been marked confirmed, not acknowledged (there is a patch) By: Leif Madsen (lmadsen) 2008-11-24 13:28:17.000-0600 I've assigned this to jpeeler for now to review. Please reassign as appropriate. Thanks! By: Tzafrir Cohen (tzafrir) 2008-11-24 13:42:11.000-0600 This is a distro bug. I still hope it will be fixed in time for Lenny. I'm not sure exactly hich versions of Uuntu are affected. Maybe for starters add a remmed-out 'unset MODPROBE_PARAMETERS' line in the init.d script and document this issue. Somebody might be actually relying on MODPROBE_PARAMETERS. By: Tzafrir Cohen (tzafrir) 2008-11-30 04:34:15.000-0600 It seems this affects Ubuntu 8.10 but not 8.4 . By: Jeff Peeler (jpeeler) 2008-12-12 15:34:17.000-0600 Work around 1 (unset MODPROBE_OPTIONS) was committed on Nov 19: http://svn.digium.com/view/dahdi?view=rev&revision=5334 | ||