lm sensors not configured

[tameboy]

I noticed a warning on boot regarding lm sensors not being configured. I ran sensors-detect and got the following output:

# sensors-detect revision 5249 (2008-05-11 22:56:25 +0200)

This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. 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.
Do you want to probe now? (YES/no): y
Probing for PCI bus adapters...
Use driver `i2c-i801' for device 0000:00:1f.3: Intel 82801EB ICH5

We will now try to load each adapter module in turn.
Module `i2c-i801' already loaded.
If you have undetectable or unsupported I2C/SMBus adapters, you can have
them scanned by manually loading the modules before running this script.

We are now going to do the I2C/SMBus adapter probings. Some chips may
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.

Next adapter: SMBus I801 adapter at efe0 (i2c-0)
Do you want to scan it? (YES/no/selectively): y
Client found at address 0x50
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... Yes
(confidence 8, not a hardware monitoring chip)
Probing for `EDID EEPROM'... No
Client found at address 0x51
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... Yes
(confidence 8, not a hardware monitoring chip)
Probing for `EDID EEPROM'... No
Client found at address 0x52
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... Yes
(confidence 8, not a hardware monitoring chip)
Probing for `EDID EEPROM'... No
Client found at address 0x53
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... Yes
(confidence 8, not a hardware monitoring chip)
Probing for `EDID EEPROM'... No

Some chips are also accessible through the ISA I/O ports. We have to
write to arbitrary I/O ports to probe them. This is usually safe though.
Yes, you do have ISA I/O ports even if you do not have any ISA slots!
Do you want to scan the ISA I/O ports? (YES/no): y
Probing for `National Semiconductor LM78' at 0x290... No
Probing for `National Semiconductor LM78-J' at 0x290... No
Probing for `National Semiconductor LM79' at 0x290... No
Probing for `Winbond W83781D' at 0x290... No
Probing for `Winbond W83782D' at 0x290... No
Probing for `IPMI BMC KCS' at 0xca0... No
Probing for `IPMI BMC SMIC' at 0xca8... No

Some Super I/O chips may also contain sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no): y
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor'... No
Trying family `SMSC'... Yes
Found `SMSC LPC47M172 Super IO Fan Sensors' Success!
(address 0xc00, driver `to-be-written')
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Fintek'... No
Trying family `ITE'... No

Some south bridges, CPUs or memory controllers may also contain
embedded sensors. Do you want to scan for them? (YES/no): y
Silicon Integrated Systems SIS5595... No
VIA VT82C686 Integrated Sensors... No
VIA VT8231 Integrated Sensors... No
AMD K8 thermal sensors... No
AMD K10 thermal sensors... No
Intel Core family thermal sensor... No
Intel AMB FB-DIMM thermal sensor... No

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

Driver `to-be-written' (should be inserted):
Detects correctly:
* ISA bus, address 0xc00
Chip `SMSC LPC47M172 Super IO Fan Sensors' (confidence: 9)

Do you want to overwrite /etc/sysconfig/lm_sensors? (YES/no):
Starting lm_sensors: not configured, run sensors-detect [WARNING]


The end message seems to be telling me to repeat what I have just done. Needless to say doing this just produces the same result. Anybody any idea why this should happen?

Any help very much appreciated.

[Hlingler]

Look at file: /etc/sysconfig/lm_sensors. What sensor modules does it say are needed ? Chances are you'll see these or similar:
MODULE_0=i2c-i801
MODULE_1=adm1025
MODULE_2=smsc47m1

Open a terminal as root user, and command:
modprobe i2c-i801
modprobe <insert-next-module-name>
modprobe <etc.>

Then:
service lm_sensors restart

V

[tameboy]

Thanks for your suggestion...

This is the end of my lm_sensors file. It seems to be updated when I run sensors-detect but no modules are added - despite the fact that it seems to detect some during sensors-detect:

# List the modules that are to be loaded for your system
#
# Generated by sensors-detect on Wed Jul 16 21:18:54 2008

[Hlingler]

Thanks for your suggestion...

This is the end of my lm_sensors file. It seems to be updated when I run sensors-detect but no modules are added - despite the fact that it seems to detect some during sensors-detect:Well, that won't do.... You are of course running sensors-detect as root user, correct ? Because a normal user can't write to that output file. :eek:

Nevermind - I see that sensors-detect can't be run by anyone except root user (at least, not here). How about checking package integrity:
rpm -V lm_sensors libsensors3

No output = all is well. You could even try re-installing those packages, or check for updates to them - including testing updates. Or, try one of the 3rd-party repos for more up-to-date packages than "stock" Fedora Project.

As a last resort, you could guess at the required modules. Based on the output, my best guess:
# Generated by sensors-detect on Thu Jul 19 18:59:13 2007
MODULE_0=i2c-i801
MODULE_1=eeprom
MODULE_2=smsc47m1

But I really wouldn't trust myself completely on this one. :D

Good Luck,
V

[tameboy]

thanks Hlinger

says libsenors3 is not installed so I found an rpm and installed it.

Now when I try
rpm -V lm_sensors libsensors3
I get :
S.5....T c /etc/sysconfig/lm_sensors

and sensors-detect still wont write to lm_sensors file

any ideas??

[Hlingler]

Well, looking into this a little deeper, I see:
> libsensors3 is a package specific to ATRPMs repo - the same sensor libraries are included in the lm_sensors package in "stock" Fedora packages.
> ATRPMs' *sensor* packages are considerably more up-to-date than Fedora Project - in fact, the most up-to-date of any repo, which is why I use them, even though it's taboo to "mix repos". So, both lm_sensors and libsensors3 should come from ATRPMs and have matching revision levels. If not, there may be a conflict.
> The output you got is expected: /etc/sysconfig/lm_sensors is the config file (denoted by the "c") that sensors-detect is proposing to write to, so it must have been written to at some point by someone(thing), since the file size ("S"), md5 checksum ("5"), and timestamp ("T") have changed.
> You could try completely removing both packages, (re)move the /etc/sysconfig/lm_sensors to a back-up location, then re-install the *sensor* package(s) and try again.
> It is possible that there are no sensors to detect, and therefore the failure. My oldest box is so: there simply are no sensors to detect. But your output seems to clearly indicate that there are at the very least fan sensors.
> Assuming that you are running sensors-detect as root user: the only other thing that I can think of is that permissions and/or attributes have somehow gotten screwed up on either the /etc/ or /etc/sysconfig/ folders, or the config file itself.

Beyond that, I'm baffled.

V

[Bill Richards]

Hi- I'm running a Dell Dimension something-or-other. I see exactly the same thing. lm_sensors detects the I/O chip correctly as follows:

Driver `to-be-written' (should be inserted):
Detects correctly:
* ISA bus, address 0xc00
Chip `SMSC LPC47M172 Super IO Fan Sensors' (confidence: 9)

Do you want to overwrite /etc/sysconfig/lm_sensors? (YES/no): YES
Starting lm_sensors: not configured, run sensors-detect [WARNING]

The problem is the chip is detectable, but no kernel module (driver) exists for it. If you go to http://www.lm_sensors.org, and check the Devices database, you'll see the chip is detectable but no driver exists, and there doesn't seem to be a plan to write one. That's why the lm_sensors script returns "to-be-written" for the driver module...

I think we're out of luck for now...

-br-

[Hlingler]

Ooh, nice catch - missed the target a little on that one, didn't I? Never noticed the "Driver `to-be-written' ".

Still, it would be nice if sensors-detect and/or lm_sensors didn't enter that eternal loop of "Starting lm_sensors: not configured, run sensors-detect [WARNING]". Really, there should be a sub-routine in sensors-detect or lm_sensors to stop that....

BTW, clearly "out of luck for now" based on your find.

V

[tameboy]

thanks for the info guys. WIll lay this issue to rest then. :(