Dave Reisner wrote:
With module-init-tools being declared a dead project by its current maintainer, a new project has stepped up to take its place: kmod. This is intended to be a drop-in replacement, though deprecated functionality in module-init-tools has not been reimplemented.
If, upon upgrade, pacman moves /etc/modprobe.d/modprobe.conf to a .pacsave, you should move it back.
The new module-init-tools 3.8 package changes the location of the configuration file: /etc/modprobe.conf is no longer read, instead /etc/modprobe.d/modprobe.conf is used. Files in /etc/modprobe.d without a .conf suffix will be ignored in the future.
Please adjust your local configuration files after the update.
juanbobo wrote:For whatever reason with a vanilla kernel modprobe will not look in the extramodules directory.Sure it will -- it has absolutely nothing to do with the kernel itself. /usr/lib/depmod.d/search.conf ensures that the extramodules directory for any given kernel will be searched in during index creation.
I tried reloading each of the modules I had listed above. Below is the output for each module:modprobe: FATAL: Module compat not found.modprobe: ERROR: could not insert 'i915': Unknown symbol in module, or unknown parameter (see dmesg)modprobe: ERROR: could not insert 'drm': Unknown symbol in module, or unknown parameter (see dmesg)modprobe: ERROR: could not insert '
I have the nvidia module blacklisted in /etc/modprobe.d/modprobe.conf.I have bbswitch set to turn the card off when it loads up using "options bbswitch load_state=0 unload_state=0" in /etc/modprobe.d/modprobe.conf.I have confirmed that the bbswitch module believes these configuration options are set, and I know that the card is successfully turned off when Bumblebee loads up.But when I l