Tilman Schmidt wrote:
> Am 28.09.2006 11:55 schrieb pedrocsort-e@yahoo.com:
>> I rebooted the server and everything was ok.
>> Even lm_sensors work.
>> So the problem in my home PC is not tainted drivers for sure.
>
> That just goes to show what a very bad idea this SuSE-specific
> "module not supported" message is. It really constitutes a
> red herring for the user trying to figure out why something
> went wrong, needlessly diverting his or her attention from
> any real issues that might exist.
>
> To reiterate:
>
> - An "unsupported module" or "tainting kernel" message does
> NOT indicate an error.
>
> - Tainting the kernel does NOT impair the functioning of the
> system.
>
> - A module that taints the kernel may load and run just as
> fine as one that doesn't.
>
> - The only function of the tainting mechanism is to set a
> marker in the system saying "tainted" and which cannot be
> cleared later, not even by unloading the module.
>
> - The only function of that marker is, that if you later ask
> for support from SuSE/Novell for any problem whatsoever (not
> necessarily related to the module that did the tainting!),
> and the support person finds that marker set, he or she will
> know you have loaded an unsupported module, and may
> consequently refuse to give you support.
>
> (The rationale being that any module you load could in theory
> corrupt anything in the entire kernel, so once a "foreign"
> module has been loaded you cannot rely on anything anymore.)

No kernel maintainer will give any support. Once you allow any binary code unlimited access to the
inner ring of the machine, nothing can be trusted. Who wants to chase a bug introduced by a driver
written by someone who refuses to divulge the specifications of their device? I certainly do not.

Larry