Update SuSE 10.1 and LM85 tainted modules ...

Hi,

I just updated OpenSuSE 10.1 and I had sensors running before this update.
sudently it seems that after then kerbnel up-date
from the original 2.6.16.13 to 2.6.16.21
there is a kernel message that says (dmesg):

hwmon_vid: module not supported by Novell, setting U taint flag.
lm85: module not supported by Novell, setting U taint flag.

This was working before, moreover: it is installed in the kernel source
tree of the lattest kernel.

How can I "untaint" this module

Best regards,
Pedro Coelho

On 26.09.2006 23:56, pedrocsort-e@yahoo.com wrote:
> I just updated OpenSuSE 10.1 and I had sensors running before this update.
> sudently it seems that after then kerbnel up-date
> from the original 2.6.16.13 to 2.6.16.21
> there is a kernel message that says (dmesg):
>
> hwmon_vid: module not supported by Novell, setting U taint flag.
> lm85: module not supported by Novell, setting U taint flag.
>
> This was working before,

And it probably does still work.

> moreover: it is installed in the kernel source
> tree of the lattest kernel.

But not in 2.6.16.21, so there.

> How can I "untaint" this module

You can't, and moreover, you don't need to. It wouldn't change
anything for you. Just ignore that silly message. It's just Novell
abusing the Linux kernel taint mechanism for telling you: "Don't
come to us if you have any problems with this."

HTH
Tilman

PS: <personalgripe>
Had no end of trouble with this myself as co-maintainer of an
open source driver which SuSE all of a sudden decided to denounce
as "tainting their kernel" even though it is under GPL and all.
Nowadays my driver's README file has an additional paragraph just
for telling the users: "If you run SuSE/Novell please ignore their
silly taint message." But of course the complaints along the lines
of: "Your driver is tainting my kernel, why isn't it open source
licensed?" still keep coming.

Thank you, SuSE. NOT.
</personalgripe>

--
Tilman Schmidt E-Mail: tilman@imap.cc
Bonn, Germany
- In theory, there is no difference between theory and practice.
In practice, there is.

Hi Tilman ,

Thanks for your reply.
It seems to me that the problem is not that "inocent".
dmesg shows:

i2c /dev entries driver
hwmon: module not supported by Novell, setting U taint flag.
hwmon_vid: module not supported by Novell, setting U taint flag.
lm85: module not supported by Novell, setting U taint flag.
pnp: Device 00:07 disabled.

Meaning that lm85 simply does not work.
lm_sensors stopped working.
I can not even run /usr/sbin/sensors-detect because it can not find any
sensor on the PC!

Is there a way to make hwmon accept tainted modules?

Best regards,
Pedro



> On 26.09.2006 23:56, pedrocsort-e@yahoo.com wrote:
> > I just updated OpenSuSE 10.1 and I had sensors running before this update.
> > sudently it seems that after then kerbnel up-date
> > from the original 2.6.16.13 to 2.6.16.21
> > there is a kernel message that says (dmesg):
> >
> > hwmon_vid: module not supported by Novell, setting U taint flag.
> > lm85: module not supported by Novell, setting U taint flag.
> >
> > This was working before,
>
> And it probably does still work.
>
> > moreover: it is installed in the kernel source
> > tree of the lattest kernel.
>
> But not in 2.6.16.21, so there.
>
> > How can I "untaint" this module
>
> You can't, and moreover, you don't need to. It wouldn't change
> anything for you. Just ignore that silly message. It's just Novell
> abusing the Linux kernel taint mechanism for telling you: "Don't
> come to us if you have any problems with this."
>
> HTH
> Tilman
>
> PS: <personalgripe>
> Had no end of trouble with this myself as co-maintainer of an
> open source driver which SuSE all of a sudden decided to denounce
> as "tainting their kernel" even though it is under GPL and all.
> Nowadays my driver's README file has an additional paragraph just
> for telling the users: "If you run SuSE/Novell please ignore their
> silly taint message." But of course the complaints along the lines
> of: "Your driver is tainting my kernel, why isn't it open source
> licensed?" still keep coming.
>
> Thank you, SuSE. NOT.
> </personalgripe>
>
> --
> Tilman Schmidt E-Mail: tilman@imap.cc
> Bonn, Germany
> - In theory, there is no difference between theory and practice.
> In practice, there is.

Hi,
I just rebooted and everything was ok.
Moreover. In the server lm_sensors work just fine!
So it realy is not tainted drivers ...
I installed a new version of lm_sensors and I am still a bit puzzled withe
the results ..

Regards,
Pedro

> Hi Tilman ,
>
> Thanks for your reply.
> It seems to me that the problem is not that "inocent".
> dmesg shows:
>
> i2c /dev entries driver
> hwmon: module not supported by Novell, setting U taint flag.
> hwmon_vid: module not supported by Novell, setting U taint flag.
> lm85: module not supported by Novell, setting U taint flag.
> pnp: Device 00:07 disabled.
>
> Meaning that lm85 simply does not work.
> lm_sensors stopped working.
> I can not even run /usr/sbin/sensors-detect because it can not find any
> sensor on the PC!
>
> Is there a way to make hwmon accept tainted modules?
>
> Best regards,
> Pedro
>
>
>
> > On 26.09.2006 23:56, pedrocsort-e@yahoo.com wrote:
> > > I just updated OpenSuSE 10.1 and I had sensors running before this
update.
> > > sudently it seems that after then kerbnel up-date
> > > from the original 2.6.16.13 to 2.6.16.21
> > > there is a kernel message that says (dmesg):
> > >
> > > hwmon_vid: module not supported by Novell, setting U taint flag.
> > > lm85: module not supported by Novell, setting U taint flag.
> > >
> > > This was working before,
> >
> > And it probably does still work.
> >
> > > moreover: it is installed in the kernel source
> > > tree of the lattest kernel.
> >
> > But not in 2.6.16.21, so there.
> >
> > > How can I "untaint" this module
> >
> > You can't, and moreover, you don't need to. It wouldn't change
> > anything for you. Just ignore that silly message. It's just Novell
> > abusing the Linux kernel taint mechanism for telling you: "Don't
> > come to us if you have any problems with this."
> >
> > HTH
> > Tilman
> >
> > PS: <personalgripe>
> > Had no end of trouble with this myself as co-maintainer of an
> > open source driver which SuSE all of a sudden decided to denounce
> > as "tainting their kernel" even though it is under GPL and all.
> > Nowadays my driver's README file has an additional paragraph just
> > for telling the users: "If you run SuSE/Novell please ignore their
> > silly taint message." But of course the complaints along the lines
> > of: "Your driver is tainting my kernel, why isn't it open source
> > licensed?" still keep coming.
> >
> > Thank you, SuSE. NOT.
> > </personalgripe>
> >
> > --
> > Tilman Schmidt E-Mail: tilman@imap.cc
> > Bonn, Germany
> > - In theory, there is no difference between theory and practice.
> > In practice, there is.
>