Hi, thanks for reporting this bug.
As there is no maintainer for this package I added the committers in CC.

(Please set the status to 'assigned' if you are working on it)

CC: (none) => cazzaniga.sandro, dmorganec

The module w83627ehf should be loaded. sensors-detect says:

Trying family `VIA/Winbond/Nuvoton/Fintek'...               Yes
Found `Nuvoton NCT6776F Super IO Sensors'                   Success!
    (address 0x290, driver `w83627ehf')

See : http://khali.linux-fr.org/devel/misc/w83627ehf/
Instructions :
  http://khali.linux-fr.org/devel/misc/INSTALL

I have succeeded to compile the driver but I had no success to install it.

The driver is compiled in the kernel.
# grep -r "CONFIG_HWMON" /usr/src/linux-2.6.38.8-desktop-9.mga/
displays : CONFIG_HWMON=Y

Works with :
1- the last http://dl.lm-sensors.org/lm-sensors/files/sensors-detect (upgrade it)
2- run sensors-detect
3- run 'systemctl enable lm_sensors.service'
Then sensors works...

UPGRADE sensors-detect please
When urpmi installs lm_sensors, run sensors-detect and systemctl enable lm_sensors.service

Then the bug will be closed for mga2. Mageia 1 must be also upgraded.

we can't upgra

Keywords: (none) => Junior_job
Version: 1 => Cauldron
Summary: sensors-detect cannot find any sensor => updated sensors-detect (was: sensors-detect cannot find any sensor)

Just pushing...

On my system i need to manually modprobe w83627ehf, then a lof of sensors works fine.  Cauldron 64 bit, on Intel i7 on AUSUS Sabretooth P67 main board.

CC: (none) => fri

Do you still have the problem with the latest version from Cauldron?  

My system loads w83627ehf automatically, but I have an AMD based ASUS MB.

CC: (none) => jeffrobinsSAE

After a fresh install of Mageia 2 beta 1 from the DVD x86_64 to a disk (no VM), nothing is changed, even after updates.

What is the output of the following, run as root?

1) "service lm_sensors status"

2) "chkconfig --list lm_sensors"

I don't think the service is enabled by default and the service loads the w83627ehf module.

--Jeff

IMO, service and chkconfig are a bit outdated thanks to systemctl...

drakxservices said the lm_sensors is activated.
# chkconfig --list lm_sensors
Note: This output shows SysV services only and does not include native
      systemd services. SysV configuration data might be overriden by native
      systemd configuration.
lm_sensors      0:arrêt 1:arrêt 2:marche        3:marche        4:marche        5:marche        6:arrêt 7:arrêt

# service lm_sensors status
lm_sensors.service - LSB: Sensors daemon
          Loaded: loaded (/etc/rc.d/init.d/lm_sensors)
          Active: active (running) since Tue, 28 Feb 2012 02:07:03 +0100; 17min ago
         Process: 6503 ExecStop=/etc/rc.d/init.d/lm_sensors stop (code=exited, status=0/SUCCESS)
         Process: 6562 ExecStart=/etc/rc.d/init.d/lm_sensors start (code=exited, status=0/SUCCESS)
          CGroup: name=systemd:/system/lm_sensors.service
                  â 6584 sensord -i 1m -l 30m
Feb 28 02:07:03 azkar lm_sensors[6562]: [52B blob data]
Feb 28 02:07:03 azkar lm_sensors[6562]: No sensors found!
Feb 28 02:07:03 azkar lm_sensors[6562]: Make sure you loaded all the kernel drivers you need.
Feb 28 02:07:03 azkar lm_sensors[6562]: Try sensors-detect to find out which these are.
Feb 28 02:07:03 azkar sensord[6584]: sensord started
Feb 28 02:07:03 azkar lm_sensors[6562]: [48B blob data]

                    _______________________________

With Cauldron, sensors works fine with my other ASUS mothercard P5Q AND Intel core 2 Duo. Th problem is with ASUS P8Z68-V LX  and Intel i5-2500K (4 cores).

Please read carefuly comments 2, 3 and 4 which were the result of mails and a discussion I had with Jean Delvare who is the maintainer of lm_sensors and a contributor to OpenSuSE.

Pierre,

My original question was actually for Morgan.  I am sorry for not specifying that.  I was writing the responses from my phone.

I'm going to ask some questions, just for clarification.  I know you've answered some of them before, but I need to know the state on the Mageia 2, Beta 1 machine.  I know some of them may sound stupid, but I'm just trying to narrow down the possibilities, so please bear with me.

1) Can you ask "sensors" for it's version?  I'm only asking because lm_sensors was updated to 3.3.1, which is the latest version from the website.  I have confirmed this from the SRPM.

2) The current package does not run "sensors-detect" or enable the service.  I see that you've enabled the service, but have you run "sensors-detect" as root?

3) Can you attach "/etc/sysconfig/lm_sensors"?

4) What is the result of trying to load the "w83627ehf" module manually?

Thank you,

Jeff

1- # sensors -v
sensors version 3.3.1 with libsensors version 3.3.1
# rpm -qa "*sensor*"
lm_sensors-3.3.1-1.mga2
lib64qtsensors1-1.2.0-5.mga2  <= same without it
lib64lm_sensors4-3.3.1-1.mga2

2- I have run sensors-detect as root and also:
systemctl enable lm_sensors.service

3- In /etc/sysconfig/lm_sensors, the only uncommented lines are:

HWMON_MODULES="w83627ehf"
MODULE_0=w83627ehf

After systemctl enable lm_sensors.service I have 3 lines
HWMON_MODULES="coretemp w83627ehf"
MODULE_0=coretemp
MODULE_1=w83627ehf

4- I don't succed to load manually w83627ehf. How must I do it?

Created attachment 1654 [details]
Output of  sensors-detect

Pierre,

Please enter the following into the command-line as root to manually load it:

"modprobe -v w83627ehf"

If there is no output then the module is already loaded and we will have to delve deeper into how lm_sensors works.

Also, my /etc/sysconfig/lm_sensors doesn't change after I start the service.  That may have something to do with the problem, if the kernel module is not the problem.

Pierre,

Please also try the following:

"modprobe -v w83627ehf force_id=0xa020"

I found that here: 
http://vip.asus.com/forum/view.aspx?id=20090518224331815&board_id=1&model=Rampage+II+Gene&page=1&SLanguage=en-us

Also, here is the appropriate config file contents for your motherboard, which has the proper gains for the voltage readings.  It looks like it might be calling out a different chip/module, but I'm not sure.

http://khali.linux-fr.org/devel/lm-sensors/sensors3-Asus-P8Z68-V-LX.conf

Full update now.  Sensors not present after boot, but after that modprobe, sensors are visible in KDE system watcher (i do not know the correct english name)

Some command output below, chronologically.
Tell me if you need more.

# sensors -v
sensors version 3.3.1 with libsensors version 3.3.1
# rpm -qa "*sensor*
lm_sensors-3.3.1-1.mga2
lib64qtsensors1-1.2.0-5.mga2
lib64lm_sensors4-3.3.1-1.mga2
# cat  /etc/sysconfig/lm_sensors
cat: /etc/sysconfig/lm_sensors: Filen eller katalogen finns inte
# modprobe -v w83627ehf
insmod /lib/modules/3.2.7-desktop-1.mga2/kernel/drivers/hwmon/hwmon-vid.ko.xz 
insmod /lib/modules/3.2.7-desktop-1.mga2/kernel/drivers/hwmon/w83627ehf.ko.xz 
# service lm_sensors status
    <that command gave no output>
# chkconfig --list lm_sensors

Note: This output shows SysV services only and does not include native
      systemd services. SysV configuration data might be overriden by native
      systemd configuration.

lm_sensors      0:av    1:av    2:på    3:på    4:på    5:på    6:av    7:av

av=off, på=on

Output oc # sensors-detect, saying y to try all, skipping all "No" answers:
Trying family `VIA/Winbond/Nuvoton/Fintek'...               Yes
Found `Nuvoton NCT6776F Super IO Sensors'                   Success!
    (address 0x290, driver `w83627ehf')
Using driver `i2c-i801' for device 0000:00:1f.3: Intel Cougar Point (PCH)
Module i2c-dev loaded successfully.
Next adapter: Radeon aux bus DP-auxch (i2c-8)
Do you want to scan it? (YES/no/selectively): y
Client found at address 0x50
Probing for `EDID EEPROM'...                                Yes
    (confidence 8, not a hardware monitoring chip)
Next adapter: SMBus I801 adapter at f000 (i2c-9)
Client found at address 0x51
Probing for `SPD EEPROM'...                                 Yes
    (confidence 8, not a hardware monitoring chip)
Client found at address 0x53
Probing for `SPD EEPROM'...                                 Yes
    (confidence 8, not a hardware monitoring chip)

Do you want to generate /etc/sysconfig/lm_sensors? (YES/no): y
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

I did not do anything that it said in that paragraph,
just checked my /etc/sysconfig/lm_sensors now exist and contain
HWMON_MODULES="w83627ehf"
MODULE_0=w83627ehf
  (comment lines omitted)

And after rebooting sensors are alive :)

Morgan,

Did you see any messages about having to run sensors-detect as root when you installed lm_sensors?

Did you tell the lm_sensors daemon to start automatically or was it set to start by the installation?

--Jeff

Today i did not do any more than i wrote in #16

I am pretty certain i have not told lm-sensors to start automatically, but i can not swear.

I checked back to my thread in the forum and it seems i did never try sensors-detect on cauldron.

In short, sensors-detect failed in mga1, and so did loading w83627ehf, but on cauldron manually loading w83627ehf worked immediately, but not automatically.

I thought sensors-detect was just for testing, i had no idea it could create an important file...

Maybe sensors-detect should been run at install, or every boot?

This system was not installed from scratch, but cloned from mga1, changed repos, and updated.

Forgot to answer "Did you see any messages about having to run sensors-detect as root when you installed lm_sensors?"

I do not remember anything such.
And probably it just got updated with the whole system as i upgraded it from mga1... where i also do not remember seeing it.  But i do not read all update information...

Morgan,

Unfortunately, "sensors-detect" isn't safe to run at every boot or even automatically.  "sensors-detect" either operates with no problems or causes a major problem.  

Chapter 3 of the lm_sensors FAQ gives some examples of problems:
http://lm-sensors.org/wiki/FAQ/Chapter3

SMBus Lock-up:
http://lm-sensors.org/wiki/FAQ/Chapter3#SMBustransactionsonmyPIIX4simplydontworktimeoutshappen.Why

Hangs Board:
http://lm-sensors.org/wiki/FAQ/Chapter3#Insertingmoduleshangsmyboard

The I2C bus, which the SMBus is based off of, allows for devices to act on any stimulus to their address.  So, even if you're just reading an address and not completing any further action, then the device can act on the read.  One of the examples from the Specs is to turn power on or off depending on if it's a read or a write to the devices address, with no other communication.

Ah, I understand.  I have myself as hw engineer been hit by a I2C cirquit that was defective by design.

Suggestion: Add info about needing to run sensors-detect to the info that is visible when selecting lm_sensors in rpmdrake install/uninstall programs.

So is it a solution to update the sensor-detect script shipped with lm_sensors?

CC: (none) => malo

Malo,

"lm_sensors" and "sensors-detect" are actually up to date.  We should probably include a message after install telling the user that he/she has to run "sensors-detect" as root once for the sensors to be detected and configured.

Also, I'm not sure what the problem is with Pierre's system.  I need to see the output of the other commands I asked him to run, but I don't think it's something we can fix in the package.

Jeff, the message already exists (just uninstall lm_sensors and install it again to see it).
And (as Pierre Jarillon said) although the lm_sensors archive is up-to-date, there is an updated sensor-detect that can be found at http://dl.lm-sensors.org/lm-sensors/files/sensors-detect.
so maybe we can update the lm_sensor package with that new sensor-detect snapshot.

I am asking the lm_sensors maintainers for the current status of the "sensors-detect" script.

I'm hoping that they do another maintenance release for an updated "sensors-detect" script.

The package is now updated with recent sensors-detect file. Please test that it solves the problem.

No news, closing

Status: NEW => RESOLVED
Resolution: (none) => FIXED