http://bugzilla.suse.com/show_bug.cgi?id=1092648
http://bugzilla.suse.com/show_bug.cgi?id=1092648#c11
--- Comment #11 from Thomas Blume
So, are we now switch to /lib/modprobe.d instead of /etc/modprobe.d with TW?
Sorry, that went out of my focus. I have reproduced the issue. The dracut code shows that /etc/modprobe.d gets overwritten by /lib/modprobe.d for the _modprobe_d variable: --> _modprobe_d=/etc/modprobe.d if [ -d /usr/lib/modprobe.d ] ; then _modprobe_d=/usr/lib/modprobe.d elif [ -d /lib/modprobe.d ] ; then _modprobe_d=/lib/modprobe.d --< This is a local variable that determines the location for the blacklist: --> for i in $(getargs rd.driver.blacklist -d rdblacklist=); do ( IFS=, for p in $i; do echo "blacklist $p" >> $_modprobe_d/initramfsblacklist.conf done ) done --< I'm not really sure whether it makes a differences if the blacklist is below /lib/modprobe.d or /etc/modprobe.d but IMHO a blacklist is something custom that should rather go below /etc. At least we should make sure to not introduce regressions when the blacklist gets moved to /lib/modprobe.d. I will create a testpackage and run some tests therefore. -- You are receiving this mail because: You are on the CC list for the bug.