On Wed, Mar 31, 2010 at 12:13 PM, Mark Knecht <markkne...@gmail.com> wrote: > On Wed, Mar 31, 2010 at 10:01 AM, Paul Hartman > <paul.hartman+gen...@gmail.com> wrote: >> On Tue, Mar 30, 2010 at 7:33 PM, Mark Knecht <markkne...@gmail.com> wrote: >>> I'm trying to blacklist firewire-ohci and firewire-core but I'm doing >>> something wrong. >>> >>> I added then to /etc/modprobe.d/blacklist, ran update-modules and then >>> rebooted but they continue to load. What am I doing wrong? >> >> (Keep in mind that is based on me running ~amd64 and whatever versions >> of openrc/baselayound/module-init-tools that entails.) >> >> Rename it to blacklist.conf and other files in that directory that >> don't end in .conf should also be renamed. If you have >> /etc/modprobe.conf it can be deleted (but be sure the contents of that >> file are handled by the files in /etc/modprobe.d/). I don't think >> running update-modules is even necessary anymore. >> > > My bad in writing the original post. It's already named blacklist.conf > > keeper ~ # ls /etc/modprobe.d/ > aliases.conf alsa.conf blacklist.conf i386.conf nvidia.conf > pnp-aliases.conf > keeper ~ # > > > and the firewire stuff is in the blacklist.conf file: > > keeper ~ # cat /etc/modprobe.d/blacklist.conf | grep firewire > blacklist firewire-ochi > blacklist firewire-core > keeper ~ # > > > I don't have a modprobe.conf file: > > keeper ~ # ls -al /etc/modprobe.conf > ls: cannot access /etc/modprobe.conf: No such file or directory > keeper ~ # > > and the modules continue to be loaded: > > keeper ~ # lsmod | grep firewire > firewire_ohci 20022 0 > firewire_core 36109 1 firewire_ohci > keeper ~ # > > This is a new machine built with a March Gentoo install image so > hopefully it's all basically correct from the outset but the modules > are still getting loaded.
Hmm, looks like you have everything set up right (or at least set up the same as me!:) The only other thing I can think of is perhaps you need to use an underscore in the blacklist line, rather than a dash.
