PDA

View Full Version : lm_sensors "No sensors found!"



|znogooD
22nd March 2005, 01:52 AM
I installed FC3 (full install). Now i am trying to get torsmo to work. But for some reason it cant display my cpu temp. I have used gkrellm and it finds my cpu. In the setup it sais thermal_zone/THRM. But this does not help me alot. tormo needs a i2c value and and my research tells me that i need lm_sensors to work for i2c to work?

But i cant get lm_sensors to work!

#sensors
No sensors found!

System:

abit kv7
AMD xp2500

imdeemvp
22nd March 2005, 03:21 AM
If you done you repos setup you can install via yum:
yum install lm-sensors

ghaefb
22nd March 2005, 09:56 AM
Did you run /usr/sbin/sensors-detect (as root) ?

Dr_Strangelove
22nd March 2005, 01:40 PM
I was having a similar problem. No CPU temps, no Volts, and no Fan Speed in GKrellM. I tried running "sensors-detect" as su/root and it would not work for some reason. Logged out of user and back in as root and sensors-detect worked fine. It asks you a few questions along the way which I answered Yes to all.

The output is a bit long (sorry) but looks something like this:
================================================
[root@localhost ~]# 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): y
Probing for PCI bus adapters...
Use driver `i2c-piix4' for device 00:07.3: Intel 82371AB PIIX4 ACPI
Probe succesfully concluded.

We will now try to load each adapter module in turn.
Module `i2c-piix4' already loaded.
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 already loaded.

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).

Next adapter: SMBus PIIX4 adapter at 0440
Do you want to scan it? (YES/no/selectively): y
Client found at address 0x32
Client found at address 0x33
Client at address 0x52 can not be probed - unload all client drivers first!
Client at address 0x53 can not be probed - unload all client drivers first!
Client found at address 0x69

Some chips are also accessible through the ISA bus. ISA probes are
typically a bit more dangerous, as we have to write to I/O ports to do
this. This is usually safe though.

Do you want to scan the ISA bus? (YES/no): y
Probing for `National Semiconductor LM78'
Trying address 0x0290... Success!
(confidence 7, driver `lm78')
Probing for `National Semiconductor LM78-J'
Trying address 0x0290... Failed!
Probing for `National Semiconductor LM79'
Trying address 0x0290... Failed!
Probing for `Winbond W83781D'
Trying address 0x0290... Success!
(confidence 8, driver `w83781d')
Probing for `Winbond W83782D'
Trying address 0x0290... Failed!
Probing for `Winbond W83627HF'
Trying address 0x0290... Failed!
Probing for `Winbond W83697HF'
Trying address 0x0290... Failed!
Probing for `Silicon Integrated Systems SIS5595'
Trying general detect... Failed!
Probing for `VIA Technologies VT82C686 Integrated Sensors'
Trying general detect... Failed!
Probing for `VIA Technologies VT8231 Integrated Sensors'
Trying general detect... Failed!
Probing for `ITE IT8705F / IT8712F / SiS 950'
Trying address 0x0290... Failed!
Probing for `IPMI BMC KCS'
Trying address 0x0ca0... Failed!
Probing for `IPMI BMC SMIC'
Trying address 0x0ca8... Failed!

Some Super I/O chips may also contain sensors. Super I/O probes are
typically a bit more dangerous, as we have to write to I/O ports to do
this. This is usually safe though.

Do you want to scan for Super I/O sensors? (YES/no): y
Probing for `ITE 8702F Super IO Sensors'
Failed! (skipping family)
Probing for `Nat. Semi. PC87351 Super IO Fan Sensors'
Failed! (skipping family)
Probing for `SMSC 47B27x Super IO Fan Sensors'
Failed! (skipping family)
Probing for `VT1211 Super IO Sensors'
Failed! (skipping family)

Do you want to scan for secondary Super I/O sensors? (YES/no): y
Probing for `ITE 8702F Super IO Sensors'
Failed! (skipping family)
Probing for `Nat. Semi. PC87351 Super IO Fan Sensors'
Failed! (skipping family)
Probing for `SMSC 47B27x Super IO Fan Sensors'
Failed! (skipping family)
Probing for `VT1211 Super IO Sensors'
Failed! (skipping family)

Now follows a summary of the probes I have just done.
Just press ENTER to continue:

Driver `lm78' (may not be inserted):
Misdetects:
* ISA bus address 0x0290 (Busdriver `i2c-isa')
Chip `National Semiconductor LM78' (confidence: 7)

Driver `w83781d' (should be inserted):
Detects correctly:
* ISA bus address 0x0290 (Busdriver `i2c-isa')
Chip `Winbond W83781D' (confidence: 8)


I will now generate the commands needed to load the I2C modules.
Sometimes, a chip is available both through the ISA bus and an I2C bus.
ISA bus access is faster, but you need to load an additional driver module
for it. If you have the choice, do you want to use the ISA bus or the
I2C/SMBus (ISA/smbus)? ISA

To make the sensors modules behave correctly, add these lines to
/etc/modules.conf:

#----cut here----
# I2C module options
alias char-major-89 i2c-dev
#----cut here----

To load everything that is needed, add this to some /etc/rc* file:

#----cut here----
# I2C adapter drivers
modprobe i2c-isa
# I2C chip drivers
modprobe w83781d
# sleep 2 # optional
/usr/bin/sensors -s # recommended
#----cut here----

WARNING! If you have some things built into your kernel, the list above
will contain too many modules. Skip the appropriate ones! You really should
try these commands right now to make sure everything is working properly.
Monitoring programs won't work until it's done.

Do you want to generate /etc/sysconfig/lm_sensors? (YES/no): y
Copy prog/init/lm_sensors.init to /etc/rc.d/init.d/lm_sensors
for initialization at boot time.
[root@localhost ~]#
==================================

Good Luck :)

|znogooD
22nd March 2005, 11:16 PM
I finaly found the /usr/sbin/sensors-detect ;) But it it quits with this msg:

[root@localhost anders]# /usr/sbin/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 `rivatv' for device 01:00.0: GeForce FX 5950 Ultra
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 `rivatv' (say NO if built into your kernel)? (YES/no): YES
FATAL: Module rivatv not found.
Loading failed... skipping.
** Note: rivatv module is available at http://rivatv.sourceforge.net/
Module `i2c-viapro' already loaded.
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 already loaded.

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 /usr/sbin/sensors-detect line 4695, <STDIN> line 2.
Couldn't find i2cdetect program!! at /usr/sbin/sensors-detect line 4695, <STDIN> line 2.

As you can se i skipped the nvida part. Cous i allready have drivers for that and dont want to mess things up. But it can find all the drivers it need but quits with this.

Dr_Strangelove
23rd March 2005, 05:16 AM
Perhaps yum did not install everything correctly??

What version kernel are you running?

As root type> sensors -v

That will tell you what version lm_sensors that you have. ver 2.9.0-38.1 is the latest I believe.
You want this for 32bit:
http://download.atrpms.net/production/packages/fedora-3-i386/atrpms/lm_sensors-2.9.0-38.1.rhfc3.at.i386.rpm

Or this for 64bit:
http://download.atrpms.net/production/packages/fedora-3-i386/atrpms/lm_sensors-2.9.0-38.1.rhfc3.at.x86_64.rpm

|znogooD
24th March 2005, 02:57 AM
I runned the sensors-detect in su when i should have used "su ." ;) thanks for all the help.

mach_zero
26th June 2005, 03:07 AM
I finaly found the /usr/sbin/sensors-detect ;) But it it quits with this msg:

[root@localhost anders]# /usr/sbin/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 `rivatv' for device 01:00.0: GeForce FX 5950 Ultra
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 `rivatv' (say NO if built into your kernel)? (YES/no): YES
FATAL: Module rivatv not found.
Loading failed... skipping.
** Note: rivatv module is available at http://rivatv.sourceforge.net/
Module `i2c-viapro' already loaded.
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 already loaded.

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 /usr/sbin/sensors-detect line 4695, <STDIN> line 2.
Couldn't find i2cdetect program!! at /usr/sbin/sensors-detect line 4695, <STDIN> line 2.

As you can se i skipped the nvida part. Cous i allready have drivers for that and dont want to mess things up. But it can find all the drivers it need but quits with this.


I got the same "Can't exec i2cdetect" error message on my attempt to set up lm_sensors intitially. I opened sensors-detect in gedit and went to the line the error message referred to. It showed that sensors-detect was looking for i2cdetect in /usr/local/sbin rather than /usr/sbin. So what I did was create a link to i2cdetect in /usr/local/sbin and reran /usr/sbin/sensors-detect. It worked fine after that.

dnar
26th June 2005, 06:51 AM
Sensors detect failed for me also, but from earlier days with this mobo (CVS version of lm_sensors) Iknow what modules to load.

You can take a stab at it yourself, and if you find the right modules just add them to your /etc/rc.local

For my Abit NF7-S mobo its:

/sbin/modprobe i2c-isa
/sbin/modprobe w83781d

Gheko
28th April 2006, 11:37 PM
I got the same "Can't exec i2cdetect" error message on my attempt to set up lm_sensors intitially. I opened sensors-detect in gedit and went to the line the error message referred to. It showed that sensors-detect was looking for i2cdetect in /usr/local/sbin rather than /usr/sbin. So what I did was create a link to i2cdetect in /usr/local/sbin and reran /usr/sbin/sensors-detect. It worked fine after that.

How do you link the file?

thanks

::edit::
got it =]



su
cd /usr/local/sbin
ln -s /usr/sbin/i2cdetect