Bugzilla Bug 131378

"blacklist foo" is a valid modules.conf file syntax, and is required in order
to handle blacklisting modules from being automatically loaded by udev at 
coldplug time, or when some devices are plugged in after booting.

My limited scripting foo could not find the error in the generate-modprobe.conf
file to try to fix this myself, sorry.

valid syntax according to who ?  generate-modprobe.conf doesnt care about
synatx, it's "modprobe.old" from the modutils package that is barfing on the
syntax ... baselayout basically does:
# cat /etc/modules.d/* > /etc/modprobe.conf

in other words, you should be talking to Keith Owens / Rusty Russell about this

Well, why would modprobe.old care about new style modprobe commands (like 
blacklist)?

Maybe the script needs to not call the .old programs if you aren't using
any 2.4 kernels.

Either way, we need to have a mechanism to get the blacklist lines into
the modprobe.conf file, and since we aren't supposed to be editing
that file by hand, but rather using these tools...

/etc/modules.d/ is for old modprobe

/etc/modprobe.d/ is for new modprobe

so if you're putting stuff into /etc/modules.d/ then it needs to be compatible
with the old modprobe

I do not have a /etc/modprobe.d/ on my system, what package creates this and
puts the same
stuff that currently is in /etc/modules.d/ into it (assuming that we want the
same kind of stuff in
it...)

nothing owns either directory ... that's sort of the point ... packages drop in
files as they need them

new modprobe from module-init-tools automatically scans /etc/modprobe.d/ and
reads /etc/modprobe.conf

old modprobe from modutils only reads /etc/modules.conf ... since that isnt
very friendly for updating on the fly, many distros use /etc/modules.d/ to hold
package-specific files which are then collected and placed into
/etc/modules.conf

since most packages still use old style /etc/modules.d/ syntax, and valid
syntax has changed from old modprobe to new modprobe, baselayout now parses out
the bits that the new modprobe accepts (like the "alias" keywords)

you still havent said who declared "blacklist foo" to be valid syntax ...
nowhere in the modules.conf nor modprobe.conf manpages can i find reference to
the "blacklist" keyword

The blacklist option is described in 'man modprobe.conf' under the "COMMANDS"
section.

must have had duplicate man windows of modules.conf open or i'm retarded and
cant type ... sorry about that

at any rate, you should be putting your blacklist stuff in /etc/modprobe.d/,
*not* in /etc/modules.d/ ... /etc/modules.d/ is for old linux-2.4 modutils

*** Bug 188914 has been marked as a duplicate of this bug. ***

*** Bug 234676 has been marked as a duplicate of this bug. ***