Can't get sensors to work...

[Thiago Guzella]

Hi there guys...

I have FC2 x86_64 running on Athlon64 Box, with an Asus A8V Deluxe Rev
A2 (VIA K8T800Pro + VT8237)...
I have been trying to install the mobo monitoring sensors, in order to
check the system's temperature...
I am using the default 2.6.5 kernel (uname -a returns: 
"Linux Guzella 2.6.5-1.358 #1 Sat May 8 09:01:26 EDT 2004 x86_64
x86_64 x86_64 GNU/Linux").
When executing /usr/sbin/sensors-detect (as root), I get the following error:

---
$ sudo ./sensors-detect

This program will help you determine which I2C/SMBus modules you need to
load to use lm_sensors most effectively. You need to have i2c and
lm_sensors installed before running this program.
Also, you need to be `root', or at least have access to the /dev/i2c-*
files, for most things.
If you have patched your kernel and have some drivers built in, you can
safely answer NO if asked to load some modules. In this case, things may
seem a bit confusing, but they will still work.

It is generally safe and recommended to accept the default answers to all
questions, unless you know what you're doing.

We can start with probing for (PCI) I2C or SMBus adapters.
 You do not need any special privileges for this.
 Do you want to probe now? (YES/no): yes
Probing for PCI bus adapters...
Use driver `i2c-viapro' for device 00:11.0: VIA Technologies VT8237
South BridgeProbe succesfully concluded.

We will now try to load each adapter module in turn.
Load `i2c-viapro' (say NO if built into your kernel)? (YES/no): yes
Module loaded succesfully.
If you have undetectable or unsupported adapters, you can have them
scanned by manually loading the modules before running this script.

To continue, we need module `i2c-dev' to be loaded.
 If it is built-in into your kernel, you can safely skip this.
 i2c-dev is not loaded. Do you want to load it now? (YES/no): yes
 Module loaded succesfully.

We are now going to do the adapter probings. Some adapters may hang halfway
 through; we can't really help that. Also, some chips will be double detected;
 we choose the one with the highest confidence value in that case.
 If you found that the adapter hung after probing a certain address, you can
 specify that address to remain unprobed. That often
 includes address 0x69 (clock chip).
Can't exec "i2cdetect": No such file or directory at ./sensors-detect
line 4366, <STDIN> line 3.
Couldn't find i2cdetect program!! at ./sensors-detect line 4366, <STDIN> line 3.
--

The weird thing is that the "i2cdetect" program is located in the same
directory (/usr/sbin):
-rwxr-xr-x  1 root root 13744 Apr 13  2004 /usr/sbin/i2cdetect

By running i2cdetect (again as root), I get the following info:

$ sudo ./i2cdetect
Error: No i2c-bus specified!
Syntax: i2cdetect [-f] I2CBUS
  I2CBUS is an integer
  With -f, scans all addresses (NOT RECOMMENDED)
  i2cdetect -l lists installed busses only
  Installed I2C busses:
    i2c-0       unknown         SMBus Via Pro adapter at 0400         
 Algorithm unavailable

Any clues on how to solve this??
Also, has anyone successfully installed it on this mobo??

Thanks
Thiago Guzella

[ne...]

On Oct 17, 2004 at 19:21, Thiago Guzella in a soothing rage wrote:

[...]
> Can't exec "i2cdetect": No such file or directory at ./sensors-detect
> line 4366, <STDIN> line 3.
> Couldn't find i2cdetect program!! at ./sensors-detect line 4366, <STDIN> line 3.
> --
>
> The weird thing is that the "i2cdetect" program is located in the same
> directory (/usr/sbin):
> -rwxr-xr-x  1 root root 13744 Apr 13  2004 /usr/sbin/i2cdetect

[...]
> Any clues on how to solve this??
> Also, has anyone successfully installed it on this mobo??

You need to run sensors-detect as root, not sudo or 'su'. Use
'su -' instead. Else you have to go the other route by adding
/usr/sbin and /sbin to your PATH variable.

HTH
N.Emile...

[Thiago Guzella]

Hi there,

I've tried doing "su" and "./sensors-detect", and got the same error...

On Mon, 18 Oct 2004 09:50:48 -0400 (EDT), ne...  wrote:
> On Oct 17, 2004 at 19:21, Thiago Guzella in a soothing rage wrote:
>
> [...]
> > Can't exec "i2cdetect": No such file or directory at ./sensors-detect
> > line 4366, <STDIN> line 3.
> > Couldn't find i2cdetect program!! at ./sensors-detect line 4366, <STDIN> line 3.
> > --
> >
> > The weird thing is that the "i2cdetect" program is located in the same
> > directory (/usr/sbin):
> > -rwxr-xr-x  1 root root 13744 Apr 13  2004 /usr/sbin/i2cdetect
>
> [...]
> > Any clues on how to solve this??
> > Also, has anyone successfully installed it on this mobo??
>
> You need to run sensors-detect as root, not sudo or 'su'. Use
> 'su -' instead. Else you have to go the other route by adding
> /usr/sbin and /sbin to your PATH variable.
>
> HTH
> N.Emile...
> --
> Registered Linux User # 125653 (http://counter.li.org)
> Switch to: http://www.speakeasy.net/refer/190653
> I never failed to convince an audience that the best thing they
> could do was to go away.
> 09:47:42  up 112 days,  3:02,  5 users,  load average: 0.00, 0.00, 0.00

[Alexander Dalloz]

Am Di, den 19.10.2004 schrieb Thiago Guzella um 17:40:
> I've tried doing "su" and "./sensors-detect", and got the same error...

su -
sensors-detect

Alexander

[Vinicius]

I've tried successfuly, but it shows "To load everything that is needed,
add this to some /etc/rc* file:" .
What "rc*" file that should I use, please?

Em Ter, 2004-10-19 às 17:55 +0200, Alexander Dalloz escreveu:
> Am Di, den 19.10.2004 schrieb Thiago Guzella um 17:40:
> > I've tried doing "su" and "./sensors-detect", and got the same error...
>
> su -
> sensors-detect
>
> Alexander

[Colin J Thomson]

On Saturday 13 Nov 2004 21:29, Vinicius wrote:
> I've tried successfuly, but it shows "To load everything that is needed,
> add this to some /etc/rc* file:" .
> What "rc*" file that should I use, please?

Use rc.local, found in /etc in FC2,  then the modules will load during a 
reboot.

HTH

Colin

[Gene Heskett]

On Saturday 13 November 2004 16:29, Vinicius wrote:
> I've tried successfuly, but it shows "To load everything that is
> needed, add this to some /etc/rc* file:" .
> What "rc*" file that should I use, please?

1. Don't top post.
> Em Ter, 2004-10-19 às 17:55 +0200, Alexander Dalloz escreveu:
> > Am Di, den 19.10.2004 schrieb Thiago Guzella um 17:40:
> > > I've tried doing "su" and "./sensors-detect", and got the same
> > > error...
> >
> > su -
> > sensors-detect
> >
> > Alexander
>
> --
> Vinicius

2. normally that would go into /etc/rc.d/rc.local

[Vinicius]

Now, it shows
"Do you want to generate /etc/sysconfig/lm_sensors? (YES/no):
Copy prog/init/lm_sensors.init to /etc/rc.d/init.d/lm_sensors
for initialization at boot time."

"# ls -l lm_sensors
-rwxr-xr-x  1 root root 3097 Out 14 12:06 lm_sensors"

"# locate lm_sensors.init
/usr/share/doc/lm_sensors-2.8.7/lm_sensors.init
/usr/share/doc/lm_sensors-2.8.7/lm_sensors.init.redhat
/usr/share/doc/lm_sensors-2.8.7/lm_sensors.init.suse"

Then, should I copy the first one to "/etc/rc.d/init.d/lm_sensors",
please?

Em Sáb, 2004-11-13 às 21:35 +0000, Colin J Thomson escreveu:
> On Saturday 13 Nov 2004 21:29, Vinicius wrote:
> > I've tried successfuly, but it shows "To load everything that is needed,
> > add this to some /etc/rc* file:" .
> > What "rc*" file that should I use, please?
>
> Use rc.local, found in /etc in FC2,  then the modules will load during a 
> reboot.
>
> HTH
> Colin
>
> Fedora Core 2, Custom Built Kernel 2.6.9-ck3
> KDE-Redhat-3.3.1-0.2.2.kde
> Registered Linux user number #342953

[Alexander Dalloz]

Am Sa, den 13.11.2004 schrieb Vinicius um 22:52:

Please don't top-post!
> Now, it shows
> "Do you want to generate /etc/sysconfig/lm_sensors? (YES/no):
> Copy prog/init/lm_sensors.init to /etc/rc.d/init.d/lm_sensors
> for initialization at boot time."
>
> "# ls -l lm_sensors
> -rwxr-xr-x  1 root root 3097 Out 14 12:06 lm_sensors"
>
> "# locate lm_sensors.init
> /usr/share/doc/lm_sensors-2.8.7/lm_sensors.init
> /usr/share/doc/lm_sensors-2.8.7/lm_sensors.init.redhat
> /usr/share/doc/lm_sensors-2.8.7/lm_sensors.init.suse"
>
> Then, should I copy the first one to "/etc/rc.d/init.d/lm_sensors",
> please?

Yes, or the lm_sensors.init.redhat. You will have to do some
modifications so that the init script will work on FC2. Set the needed
modules in /etc/sysconfig/lm_sensors. Don't set the modules being loaded
in /etc/rc.local. It is much better to use the init script in the
desired runlevel (you will have to use chkconfig too) than to put the
loading into the rc.local script file.

Alexander

[Colin J Thomson]

On Saturday 13 Nov 2004 22:09, Alexander Dalloz wrote:
> Am Sa, den 13.11.2004 schrieb Vinicius um 22:52:
>
> Please don't top-post!
> > Now, it shows
> > "Do you want to generate /etc/sysconfig/lm_sensors? (YES/no):
> > Copy prog/init/lm_sensors.init to /etc/rc.d/init.d/lm_sensors
> > for initialization at boot time."
> >
> > "# ls -l lm_sensors
> > -rwxr-xr-x  1 root root 3097 Out 14 12:06 lm_sensors"
> >
> > "# locate lm_sensors.init
> > /usr/share/doc/lm_sensors-2.8.7/lm_sensors.init
> > /usr/share/doc/lm_sensors-2.8.7/lm_sensors.init.redhat
> > /usr/share/doc/lm_sensors-2.8.7/lm_sensors.init.suse"
> >
> > Then, should I copy the first one to "/etc/rc.d/init.d/lm_sensors",
> > please?
>
> Yes, or the lm_sensors.init.redhat. You will have to do some
> modifications so that the init script will work on FC2. Set the needed
> modules in /etc/sysconfig/lm_sensors. Don't set the modules being loaded
> in /etc/rc.local. It is much better to use the init script in the
> desired runlevel (you will have to use chkconfig too) than to put the
> loading into the rc.local script file.

Hmm, thats good advice Alexander, I have a few things in rc.local to load at 
boot time (that do not use or need an init file). 
I was not aware of the lm_sensors.init script though :( 
Is it really required to be a service? Surley this should of been done right 
by the RPM packagers if it is needed.

Just my thoughts,

Colin

[Vinicius]

Em Sáb, 2004-11-13 às 23:09 +0100, Alexander Dalloz escreveu:
> Am Sa, den 13.11.2004 schrieb Vinicius um 22:52:
>
> Please don't top-post!
> > Now, it shows
> > "Do you want to generate /etc/sysconfig/lm_sensors? (YES/no):
> > Copy prog/init/lm_sensors.init to /etc/rc.d/init.d/lm_sensors
> > for initialization at boot time."
> >
> > "# ls -l lm_sensors
> > -rwxr-xr-x  1 root root 3097 Out 14 12:06 lm_sensors"
> >
> > "# locate lm_sensors.init
> > /usr/share/doc/lm_sensors-2.8.7/lm_sensors.init
> > /usr/share/doc/lm_sensors-2.8.7/lm_sensors.init.redhat
> > /usr/share/doc/lm_sensors-2.8.7/lm_sensors.init.suse"
> >
> > Then, should I copy the first one to "/etc/rc.d/init.d/lm_sensors",
> > please?
>
> Yes, or the lm_sensors.init.redhat. You will have to do some
> modifications so that the init script will work on FC2. Set the needed
> modules in /etc/sysconfig/lm_sensors. Don't set the modules being loaded
> in /etc/rc.local. It is much better to use the init script in the
> desired runlevel (you will have to use chkconfig too) than to put the
> loading into the rc.local script file.
>
> Alexander

sorry twice!

I'm using FC3.

[Alexander Dalloz]

Am Sa, den 13.11.2004 schrieb Colin J Thomson um 23:23:
> Hmm, thats good advice Alexander, I have a few things in rc.local to load at 
> boot time (that do not use or need an init file). 
> I was not aware of the lm_sensors.init script though :( 
> Is it really required to be a service? Surley this should of been done right 
> by the RPM packagers if it is needed.
> Colin

I wouldn't enforce lm_sensors need to be configured as a service. It is
just my personal taste - some sort of that :) - that as using a System V
system one should configure things with (chkconfig compatible) init
scripts where ever possible. Sure many things do simple work too if
invoked by rc.local.

Yes, I think it would be nice if the lm_sensors RPM maintainer would
have a look at it.

At Vinicius: it does not matter whether FC2 or FC3. I actually still run
FC2 and can't tell you for sure which changes to the example init script
from the docs directory are needed to let lm_sensors initialize as a
service.

Alexander

[Vinicius]

Em Sáb, 2004-11-13 às 23:41 +0100, Alexander Dalloz escreveu:
> Am Sa, den 13.11.2004 schrieb Colin J Thomson um 23:23:
> > Hmm, thats good advice Alexander, I have a few things in rc.local to load at 
> > boot time (that do not use or need an init file). 
> > I was not aware of the lm_sensors.init script though :( 
> > Is it really required to be a service? Surley this should of been done right 
> > by the RPM packagers if it is needed.
> > Colin
>
> I wouldn't enforce lm_sensors need to be configured as a service. It is
> just my personal taste - some sort of that :) - that as using a System V
> system one should configure things with (chkconfig compatible) init
> scripts where ever possible. Sure many things do simple work too if
> invoked by rc.local.
>
> Yes, I think it would be nice if the lm_sensors RPM maintainer would
> have a look at it.
>
> At Vinicius: it does not matter whether FC2 or FC3. I actually still run
> FC2 and can't tell you for sure which changes to the example init script
> from the docs directory are needed to let lm_sensors initialize as a
> service.
>
> Alexander

Thanks a lot!

It's working fine, I think.

Are the alarms below correct, please?

"$ sensors
w83627hf-isa-0290
Adapter: ISA adapter
VCore 1:   +1.50 V  (min =  +0.00 V, max =  +0.00 V)       ALARM
VCore 2:   +1.73 V  (min =  +0.00 V, max =  +0.00 V)       ALARM
+3.3V:     +3.23 V  (min =  +3.14 V, max =  +3.47 V)
+5V:       +4.97 V  (min =  +4.76 V, max =  +5.24 V)       ALARM
+12V:     +11.86 V  (min = +10.82 V, max = +13.19 V)       ALARM
-12V:      +1.54 V  (min = -13.18 V, max = -10.80 V)
-5V:       +2.59 V  (min =  -5.25 V, max =  -4.75 V)
V5SB:      +5.38 V  (min =  +4.76 V, max =  +5.24 V)
VBat:      +2.35 V  (min =  +2.40 V, max =  +3.60 V)
fan1:     2934 RPM  (min =   -1 RPM, div = 2)
fan2:        0 RPM  (min = 14062 RPM, div = 32)              ALARM
fan3:        0 RPM  (min =   -1 RPM, div = 2)              ALARM
temp1:       +40°C  (high =   -32°C, hyst =   +16°C)   sensor =
PII/Celeron diode
temp2:      +7.5°C  (high =   +80°C, hyst =   +75°C)   sensor =
thermistor
temp3:      -4.5°C  (high =  +122°C, hyst =  +121°C)   sensor =
thermistor
ERROR: Can't get VID data!
alarms:   Chassis intrusion detection                      ALARM
beep_enable:
          Sound alarm disabled

eeprom-i2c-0-50
Adapter: SMBus I801 adapter at e800
Memory type:            DDR SDRAM DIMM
Memory size (MB):       256"

TIA, Vinicius.

[Alexander Dalloz]

Am Sa, den 13.11.2004 schrieb Vinicius um 23:56:
> Thanks a lot!
>
> It's working fine, I think.

Fine :)
> Are the alarms below correct, please?
>
> "$ sensors
> w83627hf-isa-0290
> Adapter: ISA adapter
> VCore 1:   +1.50 V  (min =  +0.00 V, max =  +0.00 V)       ALARM
> VCore 2:   +1.73 V  (min =  +0.00 V, max =  +0.00 V)       ALARM

There are no boundary values for min and max.
> +3.3V:     +3.23 V  (min =  +3.14 V, max =  +3.47 V)
> +5V:       +4.97 V  (min =  +4.76 V, max =  +5.24 V)       ALARM

Between min and max - can't explain the alarm.
> +12V:     +11.86 V  (min = +10.82 V, max = +13.19 V)       ALARM

Here too.
> -12V:      +1.54 V  (min = -13.18 V, max = -10.80 V)
> -5V:       +2.59 V  (min =  -5.25 V, max =  -4.75 V)
> V5SB:      +5.38 V  (min =  +4.76 V, max =  +5.24 V)
> VBat:      +2.35 V  (min =  +2.40 V, max =  +3.60 V)
> fan1:     2934 RPM  (min =   -1 RPM, div = 2)
> fan2:        0 RPM  (min = 14062 RPM, div = 32)              ALARM
> fan3:        0 RPM  (min =   -1 RPM, div = 2)              ALARM

No fan rotation detected.
> temp1:       +40°C  (high =   -32°C, hyst =   +16°C)   sensor =
> PII/Celeron diode
> temp2:      +7.5°C  (high =   +80°C, hyst =   +75°C)   sensor =
> thermistor
> temp3:      -4.5°C  (high =  +122°C, hyst =  +121°C)   sensor =
> thermistor
> ERROR: Can't get VID data!
> alarms:   Chassis intrusion detection                      ALARM

Ok here too.
> beep_enable:
>           Sound alarm disabled
>
> eeprom-i2c-0-50
> Adapter: SMBus I801 adapter at e800
> Memory type:            DDR SDRAM DIMM
> Memory size (MB):       256"

You should customize / adjust the /etc/sensors.conf.
> TIA, Vinicius.

Alexander

[Colin J Thomson]

On Saturday 13 Nov 2004 23:25, Alexander Dalloz wrote:
> Am Sa, den 13.11.2004 schrieb Vinicius um 23:56:
> > Are the alarms below correct, please?
> >
> > "$ sensors
> > w83627hf-isa-0290
> > Adapter: ISA adapter
> > VCore 1:   +1.50 V  (min =  +0.00 V, max =  +0.00 V)       ALARM
> > VCore 2:   +1.73 V  (min =  +0.00 V, max =  +0.00 V)       ALARM
>
> There are no boundary values for min and max.
> > +3.3V:     +3.23 V  (min =  +3.14 V, max =  +3.47 V)
> > +5V:       +4.97 V  (min =  +4.76 V, max =  +5.24 V)       ALARM
>
> Between min and max - can't explain the alarm.
> > +12V:     +11.86 V  (min = +10.82 V, max = +13.19 V)       ALARM
>
> Here too.
> > -12V:      +1.54 V  (min = -13.18 V, max = -10.80 V)
> > -5V:       +2.59 V  (min =  -5.25 V, max =  -4.75 V)
> > V5SB:      +5.38 V  (min =  +4.76 V, max =  +5.24 V)
> > VBat:      +2.35 V  (min =  +2.40 V, max =  +3.60 V)
> > fan1:     2934 RPM  (min =   -1 RPM, div = 2)
> > fan2:        0 RPM  (min = 14062 RPM, div = 32)              ALARM
> > fan3:        0 RPM  (min =   -1 RPM, div = 2)              ALARM
>
> No fan rotation detected.
> > temp1:       +40°C  (high =   -32°C, hyst =   +16°C)   sensor =
> > PII/Celeron diode
> > temp2:      +7.5°C  (high =   +80°C, hyst =   +75°C)   sensor =
> > thermistor
> > temp3:      -4.5°C  (high =  +122°C, hyst =  +121°C)   sensor =
> > thermistor
> > ERROR: Can't get VID data!

Is due to changes in the kernel etc, this is fixed with lm_sensors 2.8.8 and 
the latest kernel tree (I2C changes), not sure about Fedora's kernel though 
or what version of lm_sensors is with FC3,

Run "sensors" again, some of the Alarms may go (the ones that are set right) 
once things have settled down, especially after a reboot.
> Ok here too.
> > beep_enable:
> >           Sound alarm disabled
> >
> > eeprom-i2c-0-50
> > Adapter: SMBus I801 adapter at e800
> > Memory type:            DDR SDRAM DIMM
> > Memory size (MB):       256"
>
> You should customize / adjust the /etc/sensors.conf.

FYI, when you make changes to sensors.conf (its quite well documented in the 
file) to see the changes straight away you need to run "sensors -s" and then 
"sensors" for the changes to take affect.

Colin