Le jeudi 4 février 2010 19:58:32 Aurelien Jarno, vous avez écrit :
> Hi,
> 
> > since the 2010-01-30, "sensors" fails to read my sensors.
> 
> Do you mean it was working before?

Hi again,

Yes. I have a munin instance running that stopped reporting values on that day, 
after a reboot (I guess).

> >     No sensors found!
> >     Make sure you loaded all the kernel drivers you need.
> >     Try sensors-detect to find out which these are.
> >
> > I haven't changed anything related to my modules or the sensors program
> > itself, but it fails for a reason I can't find.
> 
> Did you upgrade your kernel recently? It might be interesting to
> apt/aptitude log to see what has changed.

I don't remember having done so, but it might be possible. I attached the 
aptitude.1.gz with the updates around that date.

> > >From the kernel log, I get things like that, which I don't fully get.
> >
> > [ 3659.067814] smsc47m1: Found SMSC LPC47M15x/LPC47M192/LPC47M997
> > [ 3659.067910] ACPI: I/O resource smsc47m1 [0x680-0x6ff] conflicts with
> > ACPI region RTIO [0x680-0x6ff]
> > [ 3659.067971] ACPI: If an ACPI driver is available for this device, you
> > should use it instead of the native driver
> 
> You should try to unload acpi before trying to load smsc47m192.

After "fresh" reboot: 

$ lsmod | grep acpi
$ lsmod | grep sm
smsc47m192              9264  0
hwmon_vid               1828  1 smsc47m192
psmouse                49521  0
i2c_core               15584 / 2 smsc47m192,i2c_i801
$ ls /sys/class/hwmon/
$

> > Don't hesitate to ask for details. I also noted that it might be a
> > duplicate of #524038 (same module) or  #566184 (It also fails to set the
> > defaults, obviously).
> 
> I really doubt, it is related. In the first one, the sensors works, it's
> just they don't correspond correctly to the machine (the formulas to
> compute the values may change from motherboard to motherboard), and the
> second one is problem setting the default value.
> 
> lm-sensors is actually just a program that read raw values from
> /sys/classes/hwmon and display it in a nice way. Could you check in
> this directory if your smsc47m192 device is present or not.

As mentioned above, I have nothing in /sys/class/hwmon ("es" too much I 
guessed).

Maybe I wrecked the havoc (hardware failure) ?

Regards, 

OdyX

-- 
Didier Raboud, proud Debian user.
CH-1020 Renens
[email protected]

Attachment: aptitude.1.gz
Description: GNU Zip compressed data

Reply via email to