Which module taints kernel?

Matt Domsch Matt_Domsch at dell.com
Wed Apr 5 08:42:08 CDT 2006

On Wed, Apr 05, 2006 at 08:14:20PM +1000, Jonathan Adamczewski wrote:
> Alex Dyas wrote:
> > Thanks for the quick response.  So I'm assuming if I configure a more 
> > generic driver I won't need the module and my kernel will be untainted? 
> >   The machine is a server so I don't need anything particularly quick.
> If not dcdbas, perhaps dcdipm is the tainting module. A quick grep 
> through my source tree gives no indication that it is in the vanilla 
> kernel source (unlike dcdbas which is there, and *I believe* was added 
> to the stock kernel a couple of releases back?)

yes, dcdbas and dcdipm in current versions of OMSA will "taint" the
kernel.  Yes, this will be fixed in the next version of OMSA, as all
its drivers have been made GPL-licensed and included in kernel.org.

> Regardless, a tainted kernel is only a problem if you can't get support 
> when you need it. If kernel guys don't want to help you, I suspect the 
> Dell guys will still be here (along with the rest of us) to assist where 
> we can.



Matt Domsch
Software Architect
Dell Linux Solutions linux.dell.com & www.dell.com/linux
Linux on Dell mailing lists @ http://lists.us.dell.com

More information about the Linux-PowerEdge mailing list