This post concerns users who have made changes / applied overrides for the distribution-shipped modprobe configuration files, in particular who have un-blacklisted modules which are blacklisted by default. With the forthcoming update of suse-module-tools (16.0.16, sr#935939), the organization of files in /usr/lib/modprobe.d will be changed. So far we've collected almost all configuration defaults in two files, /usr/lib/modprobe.d/00-system.conf and /usr/lib/modprobe.d/50-blacklist.conf. In the future, we will have "one file per module". This is how the modprobe.d directory looks like after the change, on x86: $ ls /usr/lib/modprobe.d/ 10-unsupported-modules.conf 40-alias-autofs.conf 40-alias-nfs.conf 40-alias-paride.conf 40-alias-parport.conf 40-alias-qemu-acpiphp.conf 40-apm.conf 40-bttv_skip_it.conf 40-cifs.conf 40-rtc.conf 40-sonypi.conf 40-toshiba.conf 50-blacklist-acpi_power_meter.conf 50-blacklist-bfusb.conf 50-blacklist-dpt_i2o.conf 50-blacklist-evbug.conf 50-blacklist-fb.conf 50-blacklist-mtd.conf 50-blacklist-pata_acpi.conf 50-blacklist-snd_bt87x.conf 50-blacklist-usbcore.conf 50-blacklist-xircom.conf 60-blacklist_fs-adfs.conf [ more fs blacklist files, you know these already ] 60-blacklist_fs-ufs.conf 70-softdep-ata_piix.conf 70-softdep-csiostor.conf 70-softdep-dm_crypt.conf 70-softdep-ehci_hcd.conf 70-softdep-usb_storage.conf 80-options-ch.conf firewalld-sysctls.conf README systemd.conf You don't need to worry about this, unless you have applied changes to the configuration, overriding the distribution defaults (e.g. if you have un-blacklisted some of the modules in 50-blacklist.conf). Changing / overrinding these distribution defaults will be easier and more transparent in the future. The handling of overrides during package updates will also be improved. For example, to override the blacklist entry for the acpi_power_meter driver, you'd just do something like this: ln -s /dev/null /etc/modprobe.d/50-blacklist-acpi_power_meter.conf This symlink will shadow the distro-shipped file of the same name in /usr/lib/modprobe.d and thus override the blacklist entry that that file contains. However, there is *no automatism* for carrying over your changes / overrides to the new scheme. If you have copied and edited either 00- system.conf or 50-blacklist.conf, you will need to adapt your overrides as above. It is recommended to delete files containing overrides according to the old scheme, because they would mostly create confusion in the future. Note 1: If you have *added* some custom statements like "softdep" or "install" to your local configuration, these statements will remain effective if you don't adapt. But if you have un-blacklisted some modules by commenting out blacklist entries and shadowing 50- blacklist.conf and/or 00-system.conf, you will need to use the technique described above to shadow the new files, too. Note 2: This reorganization will cause a slowdown for modprobe operations, because reading many small files is slower than reading two large ones. According to my measurements, this slowdown amounts to no more than 1-3% of the execution time of modprobe. But please don't hesitate to notify me if you observe a larger slowdown or some other regressions. Note 3: In the course of making these changes, I have also removed some modprobe.conf directives that concern obsolete modules which we haven't shipped for a long time. Again, notify me if you oberve issues. Regards Martin