Hi Alberto First of all, please inline your patch next time, so we can comment on it.
On Wed, Mar 13, 2013 at 1:15 PM, Alberto Milone <alberto.mil...@canonical.com> wrote: > Hi all, > > I think the problem is that modprobe looks for the module (which in this > case is aliased as "off") in /sys and raises an error if it doesn't find > it (there's no such thing as an "off" module in /sys). > > In the attached patch I check that the module name is not "off" or > "null" before doing assert(kmod_module_get_initstate(m) == > KMOD_MODULE_BUILTIN). Why is "off" and "null" special? > > This solves the problem on my systems. What are you solving that is not solved by putting /bin/true or blacklisting the module? Lucas De Marchi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
