The command modules-update always gives the "* Warning: could not generate /etc/modprobe.conf!" message when run if module-init-tools-3.1 has been compiled with the no-old-linux use-flag. Reproducible: Always Steps to Reproduce: 1. run modules-update Actual Results: The content of /etc/modprobe.conf is not changed, a new file is not generated. Expected Results: The content of /etc/modules.d/* is analysed and written into /etc/modprobe.conf. /sbin/generate-modprobe.conf fails with "Cannot find old version of modprobe. Giving up.", causing the modules-update script to fail. The whole point of the no-old-linux use-flag apparently is not to install the old modutils, though. strace()ing modprobe (modprobe -V: module-init-tools version 3.1) yields, among others: open("/etc/modprobe.conf", O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY) = -1 ENOENT (No such file or directory) open("/etc/modprobe.conf", O_RDONLY) = -1 ENOENT (No such file or directory) open("/etc/modprobe.d", O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY) = -1 ENOENT (No such file or directory) open("/etc/modprobe.d", O_RDONLY) = -1 ENOENT (No such file or directory) Which are not generated, so module support is broken.
*** This bug has been marked as a duplicate of 66504 ***
