Blacklisting Nouveau
Matthew Saltzman
mjs at clemson.edu
Thu Jan 28 18:02:42 UTC 2010
On Thu, 2010-01-28 at 11:00 -0500, Paul W. Frields wrote:
> On Thu, Jan 28, 2010 at 08:08:29AM -0500, Matthew Saltzman wrote:
> > On Thu, 2010-01-28 at 17:23 +1100, Chris Smart wrote:
> > > 2010/1/28 Neal Becker <ndbecker2 at gmail.com>:
> > >
> > > >
> > > > You don't need to re-run dracut. All you need to do is add this the the
> > > > kernel command line:
> > > > rdblacklist=nouveau
> > > >
> > >
> > > This is completely unnecessary. The module has been black listed and
> > > all future kernel updates will exclude the module. The problem is that
> > > the current initramfs was not re-built when installing the nvidia
> > > driver (which it probably should do after blacklisting the module).
> > >
> > > > This is much simpler than other solutions.
> > >
> > > It's simpler than running a single dracut command?
> >
> > Sure. Once you've done it, it propagates to new kernels.
> >
> > > Even if you think
> > > that it is, it's more _correct_ to re-build the initramfs.
> >
> > That's probably true. That should be in the RPMfusion packaging,
> > though.
>
> Rebuilding an initial ramdisk is sufficiently intrusive that perhaps
> the RPMFusion maintainers were reticent to just do it automatically --
> especially if it might undo other customizations on the user side
> without warning.
Yeah, as somebody else pointed out, it makes switching back and forth
between nvidia and nouveau a pain in the A. Maybe RPMfusion should
update the default kernel line in /etc/grub.conf, though.
--
Matthew Saltzman
Clemson University Math Sciences
mjs AT clemson DOT edu
http://www.math.clemson.edu/~mjs
More information about the users
mailing list