Problem start lm_sensors

Hi everyone,
I have a problem to start lm_sensors.service.After start appears to me this :

redirecting to systemctl
Job failed. See system journal and ‘systemctl status’ for details.

Anybody can help me to resolve my problem?
Thanks in advance for help. :slight_smile:

And this is my log.

Feb 28 16:48:37 linux-SUSE kernel: [108189.703466] it87: Found IT8720F chip at 0x290, revision 2
Feb 28 16:48:37 linux-SUSE kernel: [108189.703577] ACPI Warning: 0x0000000000000295-0x0000000000000296 SystemIO conflicts with Region \_SB_.PCI0.SBRG.SIOR.ECRE 1 (20120320/utadd
ress-251)
Feb 28 16:48:37 linux-SUSE kernel: [108189.703594] ACPI Warning: 0x0000000000000295-0x0000000000000296 SystemIO conflicts with Region \_SB_.PCI0.SBRG.ASOC.SIOE 2 (20120320/utadd
ress-251)
Feb 28 16:48:37 linux-SUSE kernel: [108189.703610] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Feb 28 16:48:37 linux-SUSE lm_sensors[17295]: Starting up sensors: ..failed
Feb 28 16:48:37 linux-SUSE systemd[1]: lm_sensors.service: control process exited, code=exited status=1
Feb 28 16:48:37 linux-SUSE systemd[1]: Unit lm_sensors.service entered failed state.
1 Like

What output do you get when cmd

sensors-detect

is executed as root
(note this cmd is interactive)

After sensors-detect the problem continues. :frowning:

linux-SUSE:# sensors-detect
# sensors-detect revision 6031 (2012-03-07 17:14:01 +0100)
# Board: ASUSTeK Computer INC. M4A78T-E

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.

Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no): yes
Module cpuid loaded successfully.
Silicon Integrated Systems SIS5595...                       No
VIA VT82C686 Integrated Sensors...                          No
VIA VT8231 Integrated Sensors...                            No
AMD K8 thermal sensors...                                   No
AMD Family 10h thermal sensors...                           Success!
    (driver `k10temp')
AMD Family 11h thermal sensors...                           No
AMD Family 12h and 14h thermal sensors...                   No
AMD Family 15h thermal sensors...                           No
AMD Family 15h power sensors...                             No
Intel digital thermal sensor...                             No
Intel AMB FB-DIMM thermal sensor...                         No
VIA C7 thermal sensor...                                    No
VIA Nano thermal sensor...                                  No

Some Super I/O chips contain embedded 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): yes
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor/ITE'...               No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               No
Trying family `ITE'...                                      Yes
Found `ITE IT8720F Super IO Sensors'                        Success!
    (address 0x290, driver `it87')
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor/ITE'...               No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               No
Trying family `ITE'...                                      No

Some systems (mainly servers) implement IPMI, a set of common interfaces
through which system health data may be retrieved, amongst other things.
We first try to get the information from SMBIOS. If we don't find it
there, we have to read from arbitrary I/O ports to probe for such
interfaces. This is normally safe. Do you want to scan for IPMI
interfaces? (YES/no): yes
Probing for `IPMI BMC KCS' at 0xca0...                      No
Probing for `IPMI BMC SMIC' at 0xca8...                     No

Some hardware monitoring chips are 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): yes
Probing for `National Semiconductor LM78' 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

Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no): yes
Using driver `i2c-piix4' for device 0000:00:14.0: ATI Technologies Inc SB600/SB700/SB800 SMBus
Module i2c-dev loaded successfully.

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

Driver `it87':
  * ISA bus, address 0x290
    Chip `ITE IT8720F Super IO Sensors' (confidence: 9)

Driver `k10temp' (autoloaded):
  * Chip `AMD Family 10h thermal sensors' (confidence: 9)

Do you want to overwrite /etc/sysconfig/lm_sensors? (YES/no): yes
Copy prog/init/lm_sensors.service to /lib/systemd/system
and run 'systemctl enable lm_sensors.service'
for initialization at boot time.
Unloading i2c-dev... OK
Unloading cpuid... OK


In,

  • Yast Control Center
    – System
    — System Servies (Runleve)
    under Service Column (Simple Mode)
  • lm_sensor
    can you enable this?

on this pc when enabled tried the response is
“/etc/init.d/lm_sensors start returned 1 (unspecified error):”

but the following result is achieved:

Fri Mar  1 16:56:56 CET 2013
Sensors:   System Temperatures: cpu: 30.4C mobo: N/A 
           Fan Speeds (in rpm): cpu: N/A 

Do you have the same result?

NB: the kernel was update to 3.8.0-2-desktop x86_64 (64 bit)
at Thu Feb 28 10:14:14 CET 2013

Which kernel are you using?

Yes, when i starting the service in yast appear to me this error:

“/etc/init.d/lm_sensors start returned 1 (unspecified error):”

But i can see these sensors :slight_smile:

linux-SUSE:~> sensors
atk0110-acpi-0
Adapter: ACPI interface
Vcore Voltage:        +1.11 V  (min =  +0.85 V, max =  +1.70 V)
 +3.3 Voltage:        +3.46 V  (min =  +2.97 V, max =  +3.63 V)
 +5 Voltage:          +4.97 V  (min =  +4.50 V, max =  +5.50 V)
 +12 Voltage:        +12.48 V  (min = +10.20 V, max = +13.80 V)
CPU FAN Speed:        739 RPM  (min =  600 RPM, max = 7200 RPM)
CHASSIS FAN Speed:    795 RPM  (min =  600 RPM, max = 7200 RPM)
CHASSIS FAN 2 Speed:  729 RPM  (min =  600 RPM, max = 7200 RPM)
CPU Temperature:      +30.0°C  (high = +60.0°C, crit = +95.0°C)
MB Temperature:       +34.0°C  (high = +45.0°C, crit = +75.0°C)

k10temp-pci-00c3
Adapter: PCI adapter
temp1:         +0.0°C  (high = +70.0°C)
                       (crit = +90.0°C, hyst = +88.0°C)


FWIW

the sensors package was just installed on another laptop, not installed previously,
without any problem

enabling the service lm-sensor in yast, yielded,

/etc/init.d/lm_sensors start returned 0 (success):

so maybe for correct apearences all that is required is to delete the package

sensors

and then re-install and initialising it with sensors-detect

at the moment, here at least, logic does not seem to be working,
although the function is

1 Like

I was do it , but nothing changed. :expressionless:
Thanks for help I’ll use it so.:wink: