DME1737 not recognized

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

I have a SIMATIC BOX PC 627[0] on which I'm trying to control my fans. The machine is running an updated ubuntu 14.04 server installation.
I can't get lm-sensors working correctly. sensors-detect doesn't really seem to fully detect the chips.
When I run windows on the machine I am able to control the fans using speedfan. Speedfan shows that there is a DME1737 chip present on the board to read some temperatures and control a few fans. Next to that there is also a MAX1617A available for some more temperatures.

As far as I can see the DME1737 should be supported.
Manually loading the DME1737 driver and/or the driver suggested by sensors-detect doesn't show any info.
All (linux related) info added below is with the acpi_enforce_resources=lax kernel option added.

Does anybody see what I'm missing?

Thanks,
~ Scott

[0]: http://support.automation.siemens.com/WW/llisapi.dll?func=cslib.csinfo&lang=en&objid=6ES76476A.......&caller=view

## general info

$ uname -a
Linux ubuntu 3.13.0-35-generic #62-Ubuntu SMP Fri Aug 15 01:58:01 UTC 2014 i686 i686 i686 GNU/Linux
$ sensors --version
sensors version 3.3.4 with libsensors version 3.3.4

## sensors-detect output

$ sudo sensors-detect
# sensors-detect revision 6170 (2013-05-20 21:25:22 +0200)
# System: SIEMENS AG SIMATIC BoxPC627 [6ES7647-6AE30-0GK1]
# Board: SIEMENS AG A5E00329102
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
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...                           No
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
AMD Family 16h 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): y
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor/ITE'...               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/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): 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-i801' for device 0000:00:1f.3: Intel 82801FB ICH6
Module i2c-i801 loaded successfully.
Module i2c-dev loaded successfully.
Next adapter: i915 gmbus ssc (i2c-0)
Do you want to scan it? (yes/NO/selectively): y
Next adapter: i915 gmbus vga (i2c-1)
Do you want to scan it? (yes/NO/selectively): y
Next adapter: i915 gmbus panel (i2c-2)
Do you want to scan it? (yes/NO/selectively): y
Next adapter: i915 gmbus dpc (i2c-3)
Do you want to scan it? (yes/NO/selectively): y
Next adapter: i915 gmbus dpb (i2c-4)
Do you want to scan it? (yes/NO/selectively): y
Next adapter: i915 gmbus dpd (i2c-5)
Do you want to scan it? (yes/NO/selectively): y
Next adapter: SDVO DDC proxy (i2c-6)
Do you want to scan it? (yes/NO/selectively): y
Client found at address 0x4a
Probing for `National Semiconductor LM75'...                No
Probing for `National Semiconductor LM75A'...               No
Probing for `Dallas Semiconductor DS75'...                  Success!
    (confidence 3, driver `lm75')
Probing for `National Semiconductor LM77'...                No
Probing for `Analog Devices ADT7410/ADT7420'...             No
Probing for `Analog Devices ADT7411'...                     No
Probing for `Maxim MAX6642'...                              No
Probing for `National Semiconductor LM73'...                No
Probing for `National Semiconductor LM92'...                No
Probing for `National Semiconductor LM76'...                No
Probing for `Maxim MAX6633/MAX6634/MAX6635'...              No
Probing for `NXP/Philips SA56004'...                        No
Client found at address 0x4b
Probing for `National Semiconductor LM75'...                No
Probing for `National Semiconductor LM75A'...               No
Probing for `Dallas Semiconductor DS75'...                  No
Probing for `National Semiconductor LM77'...                No
Probing for `Analog Devices ADT7410/ADT7420'...             No
Probing for `Analog Devices ADT7411'...                     No
Probing for `Maxim MAX6642'...                              No
Probing for `National Semiconductor LM92'...                No
Probing for `National Semiconductor LM76'...                No
Probing for `Maxim MAX6633/MAX6634/MAX6635'...              No
Probing for `NXP/Philips SA56004'...                        No
Probing for `Analog Devices ADT7481'...                     No
Now follows a summary of the probes I have just done.
Just press ENTER to continue:
Driver `lm75':
  * Bus `SDVO DDC proxy'
    Busdriver `drm', I2C address 0x4a
    Chip `Dallas Semiconductor DS75' (confidence: 3)
To load everything that is needed, add this to /etc/modules:
#----cut here----
# Chip drivers
lm75
#----cut here----
If you have some drivers built into your kernel, the list above will
contain too many modules. Skip the appropriate ones!
Do you want to add these lines automatically to /etc/modules? (yes/NO)n
Unloading i2c-dev... OK
Unloading i2c-i801... OK
Unloading cpuid... OK

$ sudo modprobe -a dme1737 lm75
$ sudo sensors
No sensors found!
Make sure you loaded all the kernel drivers you need.
Try sensors-detect to find out which these are.
$ lsmod
Module                  Size  Used by
lm75                   13357  0
dme1737                37981  0
hwmon_vid              12687  1 dme1737
i2c_dev                13675  0
i2c_i801               21996  0
cpuid                  12737  0
gpio_ich               13229  0
mac_hid                13037  0
i915                  705659  1
drm_kms_helper         47182  1 i915
drm                   244037  2 i915,drm_kms_helper
serio_raw              13230  0
lpc_ich                16864  0
i2c_algo_bit           13197  1 i915
lp                     13299  0
parport                40836  1 lp
video                  18903  1 i915
via_rhine              27653  0
mii                    13654  1 via_rhine

## dmesg after running sensors-detect

[  411.606947] i801_smbus 0000:00:1f.3: can't derive routing for PCI INT C
[  411.606958] i801_smbus 0000:00:1f.3: PCI INT C: no GSI
[  411.606969] ACPI Warning: 0x000018e0-0x000018ff SystemIO conflicts with Region \_SB_.PCI0.SBUS.SMBI 1 (20131115/utaddress-251)
[  411.606980] ACPI: This conflict may cause random problems and system instability
[  411.606983] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[  411.607004] i801_smbus 0000:00:1f.3: Failed to allocate irq 255: -22
[  411.607126] i801_smbus: probe of 0000:00:1f.3 failed with error -22
[  411.625116] i2c /dev entries driver
[  415.828027] [drm] GMBUS [i915 gmbus dpc] timed out, falling back to bit banging on pin 4
[  417.788024] [drm] GMBUS [i915 gmbus dpd] timed out, falling back to bit banging on pin 6

## speedfan log output containing some addresses (under windows)

Win9x:NO  64Bit:NO  GiveIO:NO  SpeedFan:YES
I/O properly initialized
Linked ISA BUS at $0290
Linked Intel 82801FB ICH6 SMBUS at $18E0
Scanning ISA BUS at $0290...
SuperIO Chip=DME1737
Scanning Intel SMBus at $18E0...
DME1737 (ID=$89) found on SMBus at $2E
MAX1617A (ID=$00) found on SMBus at $4C
MAX1617A (ID=$00) found on SMBus at $4E
Found FUJITSU MHT2060BH on AdvSMART
Found FUJITSU MHT2060BH on AdvSMART
End of detection
Loaded 0 events

_______________________________________________
lm-sensors mailing list
lm-sensors@xxxxxxxxxxxxxx
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors





[Index of Archives]     [Linux Kernel]     [Linux Hardware Monitoring]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]

  Powered by Linux