Mageia forum

Clean install of Mageia 4. I have the service lm_sensors set to start at boot but it will not start.

I realized this after I ran as root sensors-detect which gave:

Code: Select all

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

Driver `w83627hf':
  * ISA bus, address 0x290
    Chip `Winbond W83627HF/F/HG/G Super IO Sensors' (confidence: 9)

Driver `k8temp':
  * Chip `AMD K8 thermal sensors' (confidence: 9)

Do you want to overwrite /etc/sysconfig/lm_sensors? (YES/no):
Job for lm_sensors.service failed. See 'systemctl status lm_sensors.service' and 'journalctl -xn' for details.
Unloading i2c-dev... OK
Unloading cpuid...

so then I ran systemctl status lm_sensors.service

Code: Select all

# systemctl status lm_sensors.service
lm_sensors.service - Initialize hardware monitoring sensors
   Loaded: loaded (/usr/lib/systemd/system/lm_sensors.service; enabled)
   Active: failed (Result: exit-code) since Wed 2014-04-02 18:15:58 CDT; 20s ago
  Process: 15082 ExecStart=/usr/bin/sensors -s (code=exited, status=1/FAILURE)
  Process: 15078 ExecStart=/sbin/modprobe -qab $BUS_MODULES $HWMON_MODULES (code=exited, status=1/FAILURE)
 Main PID: 15082 (code=exited, status=1/FAILURE)

Apr 02 18:15:58 localhost sensors[15082]: No sensors found!
Apr 02 18:15:58 localhost sensors[15082]: Make sure you loaded all the kernel drivers you need.
Apr 02 18:15:58 localhost sensors[15082]: Try sensors-detect to find out which these are.
Apr 02 18:15:58 localhost systemd[1]: lm_sensors.service: main process exited, code=exited, status=1/FAILURE
Apr 02 18:15:58 localhost systemd[1]: Failed to start Initialize hardware monitoring sensors.
Apr 02 18:15:58 localhost systemd[1]: Unit lm_sensors.service entered failed state.

next I tried:

Code: Select all

#enable lm_sensors
# systemctl start lm_sensors
Job for lm_sensors.service failed. See 'systemctl status lm_sensors.service' and 'journalctl -xn' for details.

the contents of /etc/sysconfig/lm_sensors

Code: Select all

# Generated by sensors-detect on Wed Apr  2 18:18:33 2014
# This file is sourced by /etc/init.d/lm_sensors and defines the modules to
# be loaded/unloaded.
#
# The format of this file is a shell script that simply defines variables:
# HWMON_MODULES for hardware monitoring driver modules, and optionally
# BUS_MODULES for any required bus driver module (for example for I2C or SPI).

HWMON_MODULES="k8temp w83627hf

As suggested in 63477 (https://bugs.freedesktop.org/show_bug.cgi?id=63477) I removed all comments from this file but it did not help.

Suggestions?

daniewicz wrote:HWMON_MODULES="k8temp w83627hf

Just a copy&paste omission or is there really a doublequote sign missing at the end of the line?

Also, can you successfully load those kernel modules manually?

Code: Select all

modprobe k8temp
modprobe w83627hf
lsmod | grep -e k8temp -e w83627hf

Yes, the missing double-quote was a copy/paste error

Code: Select all

# modprobe k8temp
# modprobe w83627hf
modprobe: ERROR: could not insert 'w83627hf': Device or resource busy

# lsmod | grep -e k8temp -e w83627hf
k8temp                 12978  0


daniewicz wrote:# modprobe w83627hf
modprobe: ERROR: could not insert 'w83627hf': Device or resource busy

Well, this seems like your issue. If the module for the sensor cannot be loaded, you better look at the output from dmesg to find out why.

I am in over my head and do not know how to interpret this

Code: Select all

# modprobe w83627hf
modprobe: ERROR: could not insert 'w83627hf': Device or resource busy

]# dmesg | grep -i w83627
[16377.018336] w83627hf: w83627hf: Found W83627HF chip at 0x290


Can you try if this helps? http://forums.gentoo.org/viewtopic-p-6317918.html

using acpi_enforce_resources=lax did the trick

Thanks!