Kernel 2.6.16-1.2122_FC5 & lmsensors

[Laurence Vanek]

Jean Delvare wrote:
>> On Mon, May 22, 2006 at 12:08:56PM -0500, Laurence Vanek wrote:
>>  > Upon updating to the latest kernel (2.6.16-1.2122_FC5) & rebooting I 
>>  > find that I no longer have lmsensors.  /var/log/messages gives this in 
>>  > the suspect area:
>>  > 
>>  > ==========
>>  > May 22 11:42:42 localhost kernel: i2c_adapter i2c-0: SMBus Quick command 
>>  > not supported, can't probe for chips
>>  > May 22 11:42:42 localhost kernel: i2c_adapter i2c-1: SMBus Quick command 
>>  > not supported, can't probe for chips
>>  > May 22 11:42:42 localhost kernel: i2c_adapter i2c-2: SMBus Quick command 
>>  > not supported, can't probe for chips
>>  > =========
>>  > 
>>  > something new in this release?
>>
>> Probably a side-effect of [PATCH] smbus unhiding kills thermal management
>> merged in 2.6.16.17.  Is this an ASUS board ?
>>     
>
> The fact that lm_sensors disappeared could indeed be caused by this
> patch if the system is based on one of the affected boards (which are
> NOT only Asus board, despite of some comments in the code). I _did_
> expect people to complain... There's nothing we can do for now though.
>
> The error messages are definitely not related though. I suspect that
> they were already there before, or this is just a coincidence.
>
> What does the following command return?
> cat /sys/class/i2c-adapter/i2c-*/device/name
>
> (Or even better "i2cdetect -l" if you have that installed.)
>
> I'd guess that i2c-0, i2c-1 and i2c-2 are from either a framebuffer
> driver or a tv card driver. Anything like that on this system? Probably
> the eeprom driver (if you load it as I presume) is trying to probe
> these busses and they don't want to be probed.
>
>   
well, the messages are not there with the previous kernel boot so that 
why I thought they were relevant.

As for your other comments, all I can say is that Ive been running 
lmsensors on this same system thru many kernels dating back to FC2 with 
no issues until now.