[solved] Dme1737

haikuhacker · 2009-12-02 00:32:24

I used to be able to find this module with "sensors-detect". Now the output is:
Sorry, no sensors were detected.
Either your system has no sensors, or they are not supported, or
they are connected to an I2C or SMBus adapter that is not
supported.
Is this an Arch issue or have newer kernels dropped support for the DME1737 module?

Last edited by haikuhacker (2009-12-16 21:25:06)

miau · 2009-12-02 01:00:09

Take a look here maybe this will help you: http://lists.lm-sensors.org/pipermail/l … 26109.html

haikuhacker · 2009-12-02 15:43:49

Thank you for the response Miau. It seems that Juerg Haefliger thinks its a motherboard bios issue, but I have had the same bios on the same mother board with the DME1737 module detected since kernel 2.6.23. I think it stopped being detected with kernel 2.6.30 and I think that makes it a kernel issue. I will join the lm_sensors mailing list and see what I can find out.

haikuhacker · 2009-12-04 01:20:11

This is what I learned from the lm_sensors mailing list:
http://bugzilla.kernel.org/show_bug.cgi?id=13967
When I tried booting with the

acpi_enforce_resources=no

boot option,

[root@myhost chris]# sensors-detect
# sensors-detect revision 5729 (2009-06-02 15:51:29 +0200)
# Board: Intel Corporation D101GGC

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): 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
VIA C7 thermal and voltage sensors...                       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): y
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor'...                   No
Trying family `SMSC'...                                     Yes
Found `SMSC DME1737 Super IO'                               
    (hardware monitoring capabilities accessible via SMBus only)
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 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): y
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): y
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): y
Using driver `i2c-piix4' for device 0000:00:14.0: ATI Technologies Inc IXP SB400 SMBus Controller
Module i2c-dev loaded successfully.

Next adapter: SMBus PIIX4 adapter at 0b00 (i2c-0)
Do you want to scan it? (YES/no/selectively): y
Client found at address 0x2e
Probing for `Myson MTP008'...                               No
Probing for `National Semiconductor LM78'...                No
Probing for `National Semiconductor LM79'...                No
Probing for `National Semiconductor LM80'...                No
Probing for `National Semiconductor LM85'...                No
Probing for `National Semiconductor LM96000 or PC8374L'...  No
Probing for `Analog Devices ADM1027'...                     No
Probing for `Analog Devices ADT7460 or ADT7463'...          No
Probing for `SMSC EMC6D100 or EMC6D101'...                  No
Probing for `SMSC EMC6D102'...                              No
Probing for `SMSC EMC6D103'...                              No
Probing for `Winbond WPCD377I'...                           No
Probing for `Analog Devices ADT7467 or ADT7468'...          No
Probing for `Analog Devices ADT7470'...                     No
Probing for `Analog Devices ADT7473'...                     No
Probing for `Analog Devices ADT7475'...                     No
Probing for `Analog Devices ADT7476'...                     No
Probing for `Andigilog aSC7611'...                          No
Probing for `Andigilog aSC7621'...                          No
Probing for `National Semiconductor LM87'...                No
Probing for `Analog Devices ADM1024'...                     No
Probing for `National Semiconductor LM93'...                No
Probing for `Winbond W83781D'...                            No
Probing for `Winbond W83782D'...                            No
Probing for `Winbond W83791D'...                            No
Probing for `Winbond W83792D'...                            No
Probing for `Winbond W83793R/G'...                          No
Probing for `Nuvoton W83795G/ADG'...                        No
Probing for `Winbond W83627HF'...                           No
Probing for `Winbond W83627EHF'...                          No
Probing for `Winbond W83627DHG'...                          No
Probing for `Asus AS99127F (rev.1)'...                      No
Probing for `Asus AS99127F (rev.2)'...                      No
Probing for `Asus ASB100 Bach'...                           No
Probing for `Winbond W83L786NR/NG/R/G'...                   No
Probing for `Winbond W83L785TS-S'...                        No
Probing for `Analog Devices ADM9240'...                     No
Probing for `Dallas Semiconductor DS1780'...                No
Probing for `National Semiconductor LM81'...                No
Probing for `Analog Devices ADM1026'...                     No
Probing for `Analog Devices ADM1025'...                     No
Probing for `Analog Devices ADM1029'...                     No
Probing for `Analog Devices ADM1030'...                     No
Probing for `Analog Devices ADM1031'...                     No
Probing for `Analog Devices ADM1022'...                     No
Probing for `Texas Instruments THMC50'...                   No
Probing for `Analog Devices ADM1028'...                     No
Probing for `Texas Instruments THMC51'...                   No
Probing for `ITE IT8712F'...                                No
Probing for `SMSC DME1737'...                               Success!
    (confidence 6, driver `dme1737')
Probing for `SMSC SCH5027D-NW'...                           No
Probing for `Fintek F75373S/SG'...                          No
Probing for `Fintek F75375S/SP'...                          No
Probing for `Fintek F75387SG/RG'...                         No
Probing for `Winbond W83791SD'...                           No
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 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)

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

Driver `dme1737':
  * Bus `SMBus PIIX4 adapter at 0b00'
    Busdriver `i2c_piix4', I2C address 0x2e
    Chip `SMSC DME1737' (confidence: 6)

Do you want to overwrite /etc/conf.d/lm_sensors? (YES/no): y
Copy prog/init/lm_sensors.init to /etc/rc.d/lm_sensors
for initialization at boot time.
You should now start the lm_sensors service to load the required
kernel modules.

Unloading i2c-dev... OK

found the DME1737 module.

from lm_sensors

# Generated by sensors-detect on Thu Dec 10 10:15:36 2009
# This file is sourced by /etc/rc.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="dme1737"

# For compatibility reasons, modules are also listed individually as variables
#    MODULE_0, MODULE_1, MODULE_2, etc.
# You should use BUS_MODULES and HWMON_MODULES instead if possible.

MODULE_0=dme1737

from rc.conf

DAEMONS=(hal syslog-ng network netfs crond alsa openntpd sensord)

Why can't I access the DME1737 sensors with xsensors or gkrellm?

Last edited by haikuhacker (2009-12-10 18:45:12)

haikuhacker · 2009-12-10 20:33:42

/etc/rc.d/sensors start

and the sensors are able to be read.
is there another way to start sensors at boot, besides adding sensorsd to the daemon list in rc.conf?

pyther · 2009-12-10 21:38:48

I believe that all the sensors do is read the configuration in conf.d/sensors and load the modules that are listed. So you should just be able to add the need modules in the MODULES=() section of rc.conf

haikuhacker · 2009-12-10 22:00:09

pyther wrote:

I believe that all the sensors do is read the configuration in conf.d/sensors and load the modules that are listed. So you should just be able to add the need modules in the MODULES=() section of rc.conf

thanks pyther
do you mean MODULES=(HWMON_MODULES)
MODULES=(MODULE_0) or
MODULES=(dme1737) or
MODULES=(?)

pyther · 2009-12-10 22:09:11

likely you'll want something like MODULES=(dme1737) and if you have more than one it would look something like (dme1737 deathforce)

for example if I want to load the nvidia module on boot I would have MODULES=(nvidia)
There might be more than one module that sensors load. On my desktop I believe two modules get loaded.
There is a file that stores the modules that are need to be loaded, however unfortunately I forget which file that is.

haikuhacker · 2009-12-10 22:16:36

thanks again, pyther. that worked.

Arch Linux

#1 2009-12-02 00:32:24

[solved] Dme1737

#2 2009-12-02 01:00:09

Re: [solved] Dme1737

#3 2009-12-02 15:43:49

Re: [solved] Dme1737

#4 2009-12-04 01:20:11

Re: [solved] Dme1737

#5 2009-12-10 20:33:42

Re: [solved] Dme1737

#6 2009-12-10 21:38:48

Re: [solved] Dme1737

#7 2009-12-10 22:00:09

Re: [solved] Dme1737

#8 2009-12-10 22:09:11

Re: [solved] Dme1737

#9 2009-12-10 22:16:36

Re: [solved] Dme1737

Board footer