On 14/03/13 23:34, Lucas De Marchi wrote: > Do you realize you are quoting the man page of modutils? It's not > kmod or module-init-tools, which kmod replaced. It's the old modutils > used with Linux 2.4. kmod is a drop-in replacement to m-i-t, but we > are not putting back the things from modutils if we don't have a > reason to.
It wasn't documented in m-i-t but it was supported. See line 167 of the following file: https://github.com/vadmium/module-init-tools/blob/master/generate-modprobe.conf > Why do you want to get the initstate of an inexistent module? Why do > you think null and off should be special? And more important, you > still didn't answer why the available options are not working for you > - you said you cannot get the initstate - but that is a non-issue > since libkmod shouldn't even try to get the initstate. > > Please give some real example of what you are trying to do so we can > figure out a solution. All I'm saying is that modprobe raises an error if it finds strings such as the following in configuration files in /etc/modprobe.d/ : alias nouveau off As in comment 15, this is particularly annoying when it causes update-initramfs to fail: update-initramfs: Generating /boot/initrd.img-3.8.0-3-generic modprobe: ../tools/modprobe.c:550: print_action: Assertion `kmod_module_get_initstate(m) == KMOD_MODULE_BUILTIN' failed. Aborted (core dumped) It seems that update-initramfs calls modprobe in the following way: modprobe --set-version=3.8.0-3-generic --ignore-install --quiet --show-depends nouveau And, from what I can see, this involves calling kmod_module_get_initstate(). My patch is an attempt to avoid this problem which, unless I'm wrong, is the topic of this bug report. -- Alberto Milone Software Engineer Hardware Enablement Team Professional and Engineering Services -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
