lm-sensors detecteert dme1737 niet

Pagina: 1
Acties:

Acties:
  • 0 Henk 'm!

  • DizzyVacation
  • Registratie: November 2006
  • Niet online
Ik heb een Siemens Box PC 627 waarop ik ubuntu 14.04 heb gezet.
Nu wil ik de fan speed aanpassen zodat deze minder geluid maakt echter krijg ik lm-sensors niet werkend.

sensors-detect geeft de volgende output:
code:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
user@ubuntu:~$ sudo sensors-detect
# sensors-detect revision 6170 (2013-05-20 21:25:22 +0200)
# System: SIEMENS AG SIMATIC BoxPC627
# 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
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

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)y
Successful!

Monitoring programs won't work until the needed modules are
loaded. You may want to run 'service kmod start'
to load them.


Na het updaten van /etc/modules krijg ik nog geen sensor waardes:
code:
1
2
3
4
5
6
user@ubuntu:~$ sudo service kmod start
kmod stop/waiting
user@ubuntu:~$ sudo sensors
No sensors found!
Make sure you loaded all the kernel drivers you need.
Try sensors-detect to find out which these are.


Onder windows is de fan speed wel te wijzigen met speedfan. Deze geeft aan dat de sensoren aan de DME1737 chip zitten op de SMBus op adres 2E.
De dme1737 wordt ondersteund door lm-sensors. Ik heb al geprobeerd om via `modprobe mde1737` zelf de driver te laden, ook kwam ik via google de kernel optie acpi_enforce_resources tegen, maar beide werken niet. Heeft hier iemand nog een tip waar het wellicht aan kan liggen?

Acties:
  • 0 Henk 'm!

  • Hero of Time
  • Registratie: Oktober 2004
  • Laatst online: 20:34

Hero of Time

Moderator LNX

There is only one Legend

Als /etc/modules is aangepast, moet je de modules nog handmatig laden, of even herstarten. Zie je de fan snelheid dan wel?

Commandline FTW | Tweakt met mate


Acties:
  • 0 Henk 'm!

  • DizzyVacation
  • Registratie: November 2006
  • Niet online
Zoals ik in mijn post laat zien doe ik een `sudo service kmod start`, dit zou de modules moeten laden. Heb ook al gereboot.
Zelf de modules laden lijkt ook niet te werken:
code:
1
2
3
4
5
6
7
8
9
10
user@ubuntu:~$ sudo modprobe lm75
user@ubuntu:~$ sensors
No sensors found!
Make sure you loaded all the kernel drivers you need.
Try sensors-detect to find out which these are.
user@ubuntu:~$ sudo modprobe dme1737
user@ubuntu:~$ sensors
No sensors found!
Make sure you loaded all the kernel drivers you need.
Try sensors-detect to find out which these are.

Acties:
  • 0 Henk 'm!

  • Hero of Time
  • Registratie: Oktober 2004
  • Laatst online: 20:34

Hero of Time

Moderator LNX

There is only one Legend

Krijg je wel temperaturen te zien als je de coretemp module hebt geladen? Vind 't een beetje vreemd dat die niet genoemd wordt, terwijl dat de meest basis module is om iig temperaturen uit te lezen.

Commandline FTW | Tweakt met mate


Acties:
  • 0 Henk 'm!

  • DizzyVacation
  • Registratie: November 2006
  • Niet online
Die wil niet eens laden. dmesg laat geen fout zien.
code:
1
2
user@ubuntu:~$ sudo modprobe coretemp
modprobe: ERROR: could not insert 'coretemp': No such device

[ Voor 12% gewijzigd door DizzyVacation op 08-09-2014 20:47 ]


Acties:
  • 0 Henk 'm!

  • Thc_Nbl
  • Registratie: Juli 2001
  • Laatst online: 21-05 22:24
ik zou zeggen probeer eens een nieuwere kernel:

http://kernel.ubuntu.com/.../mainline/v3.16.2-utopic/
installeer linux-headers (+all) en linux-image en probeer opnieuw.

Als je een beetje rond googled. zie je dat er veel meer met deze problemen zitten.
Nieuwere kernel is nieuwere drivers, questie van even proberen.

ehhh.. noppes


Acties:
  • 0 Henk 'm!

  • DizzyVacation
  • Registratie: November 2006
  • Niet online
Met die nieuwe kernel vind sensors-detect niets, zelfs niet de lm75 module welke hij in de eerste post wil gebruiken.
Ook zelf de modules laden geeft geen resultaat met de nieuwere kernel.
Pagina: 1