Re: bad temperature values from w83781d in 2.6.22

2007-08-08 Thread Joerg Sommrey
Hi Mark, just to eliminate as many impacts as possible, I did: - reinstall the unmodified sensors.conf from Tyan's support page - power off before rebooting A call to "sensors -s" is done without errors in all cases. The module parameters I use currently with both kernels: options w83781d force_

Re: bad temperature values from w83781d in 2.6.22

2007-08-07 Thread Mark M. Hoffman
Hi Joerg: (I tried to follow-up using the gmane.org mail/news gateway... didn't seem to work.) * Joerg Sommrey <[EMAIL PROTECTED]> [2007-08-05 12:26:04 +0200]: > Hi, > > after upgrading from 2.6.21 to 2.6.22 the CPU temperatures shown by > w83781d look unreal. They were in a range from 40°C whe

Re: bad temperature values from w83781d in 2.6.22

2007-08-05 Thread Joerg Sommrey
Thanks for your reply. the sensors.conf I'm currently using is provided by Tyan, so this seems to be ok. One major difference that I can see: I don't have compute statements for the CPU temperatures. If I use your config, I get 7.8°C :-) So there is definitely some difference in our hardware en

Re: bad temperature values from w83781d in 2.6.22

2007-08-05 Thread Rene Herman
On 08/05/2007 12:26 PM, Joerg Sommrey wrote: after upgrading from 2.6.21 to 2.6.22 the CPU temperatures shown by w83781d look unreal. They were in a range from 40°C when idle to 75°C under full load with 2.6.21. The values shown now are in a very small range from 77°C to 82°C. From the (low)