[lm-sensors] hwmon strangeness, no fan control on w83627dhg

[lm-sensors] hwmon strangeness, no fan control on w83627dhg

[Pavel Machek]

Hi!

hwmon is quite incosistent on my machine: in hwmon0 case, temperature
files are in directly in hwmon0 subdirectory, but in hwmon1 case, they
are in hwmon1/device/ . Is that expected? Why is it so?

root@amd:/sys/class/hwmon# ls hwmon0/
device			   subsystem	  temp2_input  temp3_crit
temp3_label
name	temp2_crit	  temp2_label  temp3_crit_alarm  temp3_max
power	temp2_crit_alarm  temp2_max    temp3_input	  uevent
root@amd:/sys/class/hwmon# ls hwmon1/
device/    power/     subsystem/ uevent
root@amd:/sys/class/hwmon# ls hwmon1/device
cpu0_vid		    in0_alarm  in6_alarm	       pwm2
 pwm4_stop_output
 driver		 in0_input  in6_input	       pwm2_enable
 pwm4_stop_time
 driver_override  in0_max    in6_max	       pwm2_max_output
 pwm4_target
 fan1_alarm	 in0_min    in6_min	       pwm2_mode
 pwm4_tolerance
 fan1_div	 in1_alarm  in7_alarm	       pwm2_start_output
 subsystem
 fan1_input	 in1_input  in7_input	       pwm2_step_output
 temp1_alarm
 fan1_min	 in1_max    in7_max	       pwm2_stop_output
 temp1_input
 fan2_alarm	 in1_min    in7_min	       pwm2_stop_time
 temp1_max
 fan2_div	 in2_alarm  in8_alarm	       pwm2_target
 temp1_max_hyst
 fan2_input	 in2_input  in8_input	       pwm2_tolerance
 temp1_offset
 fan2_min	 in2_max    in8_max	       pwm3
 temp1_type
 fan3_alarm	 in2_min    in8_min	       pwm3_enable
 temp2_alarm
 fan3_div	 in3_alarm  intrusion0_alarm   pwm3_mode
 temp2_input
 fan3_input	 in3_input  modalias	       pwm3_start_output
 temp2_max
 fan3_min	 in3_max    name	       pwm3_stop_output
 temp2_max_hyst
 fan4_alarm	 in3_min    power	       pwm3_stop_time
 temp2_offset
 fan4_div	 in4_alarm  pwm1	       pwm3_target
 temp2_type
 fan4_input	 in4_input  pwm1_enable        pwm3_tolerance
 temp3_alarm
 fan4_min	 in4_max    pwm1_mode	       pwm4
 temp3_input
 fan5_alarm	 in4_min    pwm1_start_output  pwm4_enable
 temp3_max
 fan5_div	 in5_alarm  pwm1_stop_output   pwm4_max_output
 temp3_max_hyst
 fan5_input	 in5_input  pwm1_stop_time     pwm4_mode
 temp3_offset
 fan5_min	 in5_max    pwm1_target        pwm4_start_output
 temp3_type
 hwmon		 in5_min    pwm1_tolerance     pwm4_step_output
 uevent
 root@amd:/sys/class/hwmon#

Plus, no matter what I do, I can't control the pwm2 (only one used on
my board):

root@amd:/sys/class/hwmon/hwmon1/device# cat pwm2
80
root@amd:/sys/class/hwmon/hwmon1/device# echo 0 > pwm2
root@amd:/sys/class/hwmon/hwmon1/device# cat pwm2
80
root@amd:/sys/class/hwmon/hwmon1/device#

I tried playing with other files, too, but no luck. Documentation
mentions:

Note: last six functions are influenced by other control bits, not yet
exported
      by the driver, so a change might not have any effect.


Any ideas what bits those are, and what needs to be implemented? (I'm
currently reading through the documentation).

Thanks,
								Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

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

Re: [lm-sensors] hwmon strangeness, no fan control on w83627dhg

[David Hubbard]

I see your machine is named "amd" but we need more information. Could you
please post the output of "sensor-detect"?
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] hwmon strangeness, no fan control on w83627dhg

[Pavel Machek]

On Thu 2015-01-08 12:32:07, David Hubbard wrote:
> I see your machine is named "amd" but we need more information. Could you
> please post the output of "sensor-detect"?

That machine is named "amd", but it is actually a core2 intel
system. sensors-detect is below, sensors output is a bonus :-):


root@amd:~# sensors
coretemp-isa-0000
Adapter: ISA adapter
Core 0:       +40.0°C  (high = +76.0°C, crit = +100.0°C)
Core 1:       +40.0°C  (high = +76.0°C, crit = +100.0°C)

w83627dhg-isa-0a10
Adapter: ISA adapter
Vcore:        +1.26 V  (min =  +0.00 V, max =  +1.74 V)
in1:          +1.11 V  (min =  +0.15 V, max =  +1.80 V)
AVCC:         +3.36 V  (min =  +2.98 V, max =  +3.63 V)
+3.3V:        +3.36 V  (min =  +2.98 V, max =  +3.63 V)
in4:          +1.29 V  (min =  +1.78 V, max =  +0.49 V)  ALARM
in5:          +0.75 V  (min =  +1.94 V, max =  +1.41 V)  ALARM
in6:          +0.87 V  (min =  +1.18 V, max =  +0.73 V)  ALARM
3VSB:         +3.41 V  (min =  +2.98 V, max =  +3.63 V)
Vbat:         +3.31 V  (min =  +2.70 V, max =  +3.63 V)
fan1:           0 RPM  (min = 5273 RPM, div = 64)  ALARM
fan2:         799 RPM  (min = 4440 RPM, div = 8)  ALARM
fan3:           0 RPM  (min = 4218 RPM, div = 64)  ALARM
fan4:           0 RPM  (min = 14673 RPM, div = 4)  ALARM
fan5:           0 RPM  (min = 28125 RPM, div = 4)  ALARM
temp1:        +35.0°C  (high = +34.0°C, hyst =  +4.0°C)  ALARM  sensor
= thermistor
temp2:        +25.0°C  (high = +80.0°C, hyst = +75.0°C)  sensor = CPU
diode
temp3:        +41.0°C  (high = +80.0°C, hyst = +75.0°C)  sensor =
thermistor
cpu0_vid:    +0.000 V
intrusion0:  ALARM

root@amd:~# watch sensors
root@amd:~# sensors-detect
# sensors-detect revision 6209 (2014-01-14 22:51:58 +0100)
# Board: Intel Corporation DG41MJ

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):
modprobe: ERROR: ../libkmod/libkmod.c:557 kmod_search_moddep() could
not open moddep file '/lib/modules/3.19.0-rc3/modules.dep.bin'
Failed to load module cpuid.
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):
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor/ITE'...               No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               Yes
Found `Winbond W83627DHG-P/W83527HG Super IO Sensors'       Success!
    (address 0xa10, driver `w83627ehf')
    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):
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):

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):
Using driver `i2c-i801' for device 0000:00:1f.3: Intel 82801G ICH7
modprobe: ERROR: ../libkmod/libkmod.c:557 kmod_search_moddep() could
not open moddep file '/lib/modules/3.19.0-rc3/modules.dep.bin'
Failed to load module i2c-i801.
modprobe: ERROR: ../libkmod/libkmod.c:557 kmod_search_moddep() could
not open moddep file '/lib/modules/3.19.0-rc3/modules.dep.bin'
Failed to load module i2c-dev.

Next adapter: i915 gmbus ssc (i2c-0)
Do you want to scan it? (yes/NO/selectively):

Next adapter: i915 gmbus vga (i2c-1)
Do you want to scan it? (yes/NO/selectively):

Next adapter: i915 gmbus panel (i2c-2)
Do you want to scan it? (yes/NO/selectively):

Next adapter: i915 gmbus dpc (i2c-3)
Do you want to scan it? (yes/NO/selectively):

Next adapter: i915 gmbus dpb (i2c-4)
Do you want to scan it? (yes/NO/selectively):

Next adapter: i915 gmbus dpd (i2c-5)
Do you want to scan it? (yes/NO/selectively):

Next adapter: DPDDC-C (i2c-6)
Do you want to scan it? (yes/NO/selectively):


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

Driver `w83627ehf':
  * ISA bus, address 0xa10
      Chip `Winbond W83627DHG-P/W83527HG Super IO Sensors'
      (confidence: 9)

To load everything that is needed, add this to /etc/modules:
#----cut here----
# Chip drivers
w83627ehf
#----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)




-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

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

Re: [lm-sensors] hwmon strangeness, no fan control on w83627dhg

[Jean Delvare]

SGkgUGF2ZWwsCgpMZSBUaHVyc2RheSAwOCBKYW51YXJ5IDIwMTUgw6AgMjE6MjkgKzAxMDAsIFBh
dmVsIE1hY2hlayBhIMOpY3JpdCA6Cj4gaHdtb24gaXMgcXVpdGUgaW5jb3Npc3RlbnQgb24gbXkg
bWFjaGluZTogaW4gaHdtb24wIGNhc2UsIHRlbXBlcmF0dXJlCj4gZmlsZXMgYXJlIGluIGRpcmVj
dGx5IGluIGh3bW9uMCBzdWJkaXJlY3RvcnksIGJ1dCBpbiBod21vbjEgY2FzZSwgdGhleQo+IGFy
ZSBpbiBod21vbjEvZGV2aWNlLyAuIElzIHRoYXQgZXhwZWN0ZWQ/IFdoeSBpcyBpdCBzbz8KClRo
aXMgaXMgZm9yIGhpc3RvcmljYWwgcmVhc29ucy4gV2UgYXJlIGluIHRoZSBwcm9jZXNzIG9mIGNs
ZWFuaW5nIGl0IGFsbAp1cCAoYXR0cmlidXRlcyBzaG91bGQgYWx3YXlzIGJlIGluIHRoZSBod21v
biBjbGFzcyBkZXZpY2UpIGJ1dCB0aGVyZSBhcmUKbWFueSBkcml2ZXJzIGxlZnQgdG8gY29udmVy
dC4KCkFueXdheSwgYm90aCBsaWJzZW5zb3JzIGFuZCBwd21jb25maWcvZmFuY29udHJvbCBzdXBw
b3J0IGJvdGgsIHNvIGlmCnlvdXIgdmVyc2lvbiBvZiBsbS1zZW5zb3JzIGlzIHJlY2VudCBlbm91
Z2gsIHRoaXMgc2hvdWxkbid0IGJlIGFuIGlzc3VlLgoKPiAoLi4uKQo+IFBsdXMsIG5vIG1hdHRl
ciB3aGF0IEkgZG8sIEkgY2FuJ3QgY29udHJvbCB0aGUgcHdtMiAob25seSBvbmUgdXNlZCBvbgo+
IG15IGJvYXJkKToKPiAKPiByb290QGFtZDovc3lzL2NsYXNzL2h3bW9uL2h3bW9uMS9kZXZpY2Uj
IGNhdCBwd20yCj4gODAKPiByb290QGFtZDovc3lzL2NsYXNzL2h3bW9uL2h3bW9uMS9kZXZpY2Uj
IGVjaG8gMCA+IHB3bTIKPiByb290QGFtZDovc3lzL2NsYXNzL2h3bW9uL2h3bW9uMS9kZXZpY2Uj
IGNhdCBwd20yCj4gODAKPiByb290QGFtZDovc3lzL2NsYXNzL2h3bW9uL2h3bW9uMS9kZXZpY2Uj
Cj4gCj4gSSB0cmllZCBwbGF5aW5nIHdpdGggb3RoZXIgZmlsZXMsIHRvbywgYnV0IG5vIGx1Y2su
IERvY3VtZW50YXRpb24KPiBtZW50aW9uczoKPiAKPiBOb3RlOiBsYXN0IHNpeCBmdW5jdGlvbnMg
YXJlIGluZmx1ZW5jZWQgYnkgb3RoZXIgY29udHJvbCBiaXRzLCBub3QgeWV0Cj4gZXhwb3J0ZWQK
PiAgICAgICBieSB0aGUgZHJpdmVyLCBzbyBhIGNoYW5nZSBtaWdodCBub3QgaGF2ZSBhbnkgZWZm
ZWN0Lgo+IAo+IAo+IEFueSBpZGVhcyB3aGF0IGJpdHMgdGhvc2UgYXJlLCBhbmQgd2hhdCBuZWVk
cyB0byBiZSBpbXBsZW1lbnRlZD8gKEknbQo+IGN1cnJlbnRseSByZWFkaW5nIHRocm91Z2ggdGhl
IGRvY3VtZW50YXRpb24pLgoKQ2hlY2sgdGhlIHZhbHVlIG9mIHB3bTJfZW5hYmxlLiBJZiBhdXRv
bWF0aWMgbW9kZSBpcyBzZXQgKHB3bTJfZW5hYmxlID49CjIpLCB5b3UgY2FuJ3QgY29udHJvbCB0
aGUgb3V0cHV0IHZhbHVlIGRpcmVjdGx5LiBTYW1lIGlmIGNvbnRyb2wgaXMKZGlzYWJsZWQgYWx0
b2dldGhlciAocHdtMl9lbmFibGUgPSAwKSBidXQgSSdtIG5vdCBzdXJlIGlmIHRoZSB3ODM2Mjdl
aGYKZHJpdmVyIHN1cHBvcnRzIHRoYXQuIFlvdSBjYW4gb25seSBjb250cm9sIGlmIGluIG1hbnVh
bCBtb2RlCihwd20yX2VuYWJsZSA9IDEuKQoKLS0gCkplYW4gRGVsdmFyZQpTVVNFIEwzIFN1cHBv
cnQKCgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwpsbS1z
ZW5zb3JzIG1haWxpbmcgbGlzdApsbS1zZW5zb3JzQGxtLXNlbnNvcnMub3JnCmh0dHA6Ly9saXN0
cy5sbS1zZW5zb3JzLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2xtLXNlbnNvcnM

Re: [lm-sensors] hwmon strangeness, no fan control on w83627dhg

[Pavel Machek]

Hi!

> Le Thursday 08 January 2015 à 21:29 +0100, Pavel Machek a écrit :
> > hwmon is quite incosistent on my machine: in hwmon0 case, temperature
> > files are in directly in hwmon0 subdirectory, but in hwmon1 case, they
> > are in hwmon1/device/ . Is that expected? Why is it so?
> 
> This is for historical reasons. We are in the process of cleaning it all
> up (attributes should always be in the hwmon class device) but there are
> many drivers left to convert.

So my "hwmon0" is correct and "hwmon1" needs conversion, right?

> Anyway, both libsensors and pwmconfig/fancontrol support both, so if
> your version of lm-sensors is recent enough, this shouldn't be an
> issue.

Ok, good to know.

> > I tried playing with other files, too, but no luck. Documentation
> > mentions:
> > 
> > Note: last six functions are influenced by other control bits, not yet
> > exported
> >       by the driver, so a change might not have any effect.
> > 
> > 
> > Any ideas what bits those are, and what needs to be implemented? (I'm
> > currently reading through the documentation).
> 
> Check the value of pwm2_enable. If automatic mode is set (pwm2_enable >=
> 2), you can't control the output value directly. Same if control is
> disabled altogether (pwm2_enable = 0) but I'm not sure if the w83627ehf
> driver supports that. You can only control if in manual mode
> (pwm2_enable = 1.)

It is in manual mode after boot... (but I think there's some fan
control going on, weird; I may be imagining it, was not able to
trigger it on purpose).

root@amd:/sys/class/hwmon/hwmon1/device# cat pwm2_enable
1
root@amd:/sys/class/hwmon/hwmon1/device# cat pwm2
80
root@amd:/sys/class/hwmon/hwmon1/device# echo 0 > pwm2
root@amd:/sys/class/hwmon/hwmon1/device# cat pwm2
80
root@amd:/sys/class/hwmon/hwmon1/device#

I even tried to set it to 1, but no luck:

root@amd:/sys/class/hwmon/hwmon1/device# echo 1 > pwm2_enable
root@amd:/sys/class/hwmon/hwmon1/device# echo 0 > pwm2
root@amd:/sys/class/hwmon/hwmon1/device# cat pwm2
80
root@amd:/sys/class/hwmon/hwmon1/device# echo 2 > pwm2
root@amd:/sys/class/hwmon/hwmon1/device# cat pwm2
80
root@amd:/sys/class/hwmon/hwmon1/device#

...and set it there and back:

root@amd:/sys/class/hwmon/hwmon1/device# echo 2 > pwm2_enable
root@amd:/sys/class/hwmon/hwmon1/device# echo 1 > pwm2_enable
root@amd:/sys/class/hwmon/hwmon1/device# cat pwm2
80
root@amd:/sys/class/hwmon/hwmon1/device# echo 40 > pwm2
root@amd:/sys/class/hwmon/hwmon1/device# cat pwm2
80
root@amd:/sys/class/hwmon/hwmon1/device#

Any other ideas?

Thanks,
								Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

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

Re: [lm-sensors] hwmon strangeness, no fan control on w83627dhg

[Jean Delvare]

SGkgUGF2ZWwsCgpPbiBUaHUsIDggSmFuIDIwMTUgMjM6NTg6MjUgKzAxMDAsIFBhdmVsIE1hY2hl
ayB3cm90ZToKPiA+IExlIFRodXJzZGF5IDA4IEphbnVhcnkgMjAxNSDDoCAyMToyOSArMDEwMCwg
UGF2ZWwgTWFjaGVrIGEgw6ljcml0IDoKPiA+ID4gaHdtb24gaXMgcXVpdGUgaW5jb3Npc3RlbnQg
b24gbXkgbWFjaGluZTogaW4gaHdtb24wIGNhc2UsIHRlbXBlcmF0dXJlCj4gPiA+IGZpbGVzIGFy
ZSBpbiBkaXJlY3RseSBpbiBod21vbjAgc3ViZGlyZWN0b3J5LCBidXQgaW4gaHdtb24xIGNhc2Us
IHRoZXkKPiA+ID4gYXJlIGluIGh3bW9uMS9kZXZpY2UvIC4gSXMgdGhhdCBleHBlY3RlZD8gV2h5
IGlzIGl0IHNvPwo+ID4gCj4gPiBUaGlzIGlzIGZvciBoaXN0b3JpY2FsIHJlYXNvbnMuIFdlIGFy
ZSBpbiB0aGUgcHJvY2VzcyBvZiBjbGVhbmluZyBpdCBhbGwKPiA+IHVwIChhdHRyaWJ1dGVzIHNo
b3VsZCBhbHdheXMgYmUgaW4gdGhlIGh3bW9uIGNsYXNzIGRldmljZSkgYnV0IHRoZXJlIGFyZQo+
ID4gbWFueSBkcml2ZXJzIGxlZnQgdG8gY29udmVydC4KPiAKPiBTbyBteSAiaHdtb24wIiBpcyBj
b3JyZWN0IGFuZCAiaHdtb24xIiBuZWVkcyBjb252ZXJzaW9uLCByaWdodD8KCkNvcnJlY3QuIE9y
IHRvIHB1dCBpdCBpbiBtb3JlIGNvbmNyZXRlIHdvcmRzOiB0aGUgY29yZXRlbXAgZHJpdmVyIHdh
cwphbHJlYWR5IGNvbnZlcnRlZCAoc2luY2Uga2VybmVsIHYzLjE1KSBidXQgdGhlIHc4MzYyN2Vo
ZiBkcml2ZXIgd2FzIG5vdC4KCj4gPiBBbnl3YXksIGJvdGggbGlic2Vuc29ycyBhbmQgcHdtY29u
ZmlnL2ZhbmNvbnRyb2wgc3VwcG9ydCBib3RoLCBzbyBpZgo+ID4geW91ciB2ZXJzaW9uIG9mIGxt
LXNlbnNvcnMgaXMgcmVjZW50IGVub3VnaCwgdGhpcyBzaG91bGRuJ3QgYmUgYW4KPiA+IGlzc3Vl
Lgo+IAo+IE9rLCBnb29kIHRvIGtub3cuCj4gCj4gPiA+IEkgdHJpZWQgcGxheWluZyB3aXRoIG90
aGVyIGZpbGVzLCB0b28sIGJ1dCBubyBsdWNrLiBEb2N1bWVudGF0aW9uCj4gPiA+IG1lbnRpb25z
Ogo+ID4gPiAKPiA+ID4gTm90ZTogbGFzdCBzaXggZnVuY3Rpb25zIGFyZSBpbmZsdWVuY2VkIGJ5
IG90aGVyIGNvbnRyb2wgYml0cywgbm90IHlldAo+ID4gPiBleHBvcnRlZAo+ID4gPiAgICAgICBi
eSB0aGUgZHJpdmVyLCBzbyBhIGNoYW5nZSBtaWdodCBub3QgaGF2ZSBhbnkgZWZmZWN0Lgo+ID4g
PiAKPiA+ID4gCj4gPiA+IEFueSBpZGVhcyB3aGF0IGJpdHMgdGhvc2UgYXJlLCBhbmQgd2hhdCBu
ZWVkcyB0byBiZSBpbXBsZW1lbnRlZD8gKEknbQo+ID4gPiBjdXJyZW50bHkgcmVhZGluZyB0aHJv
dWdoIHRoZSBkb2N1bWVudGF0aW9uKS4KPiA+IAo+ID4gQ2hlY2sgdGhlIHZhbHVlIG9mIHB3bTJf
ZW5hYmxlLiBJZiBhdXRvbWF0aWMgbW9kZSBpcyBzZXQgKHB3bTJfZW5hYmxlID49Cj4gPiAyKSwg
eW91IGNhbid0IGNvbnRyb2wgdGhlIG91dHB1dCB2YWx1ZSBkaXJlY3RseS4gU2FtZSBpZiBjb250
cm9sIGlzCj4gPiBkaXNhYmxlZCBhbHRvZ2V0aGVyIChwd20yX2VuYWJsZSA9IDApIGJ1dCBJJ20g
bm90IHN1cmUgaWYgdGhlIHc4MzYyN2VoZgo+ID4gZHJpdmVyIHN1cHBvcnRzIHRoYXQuIFlvdSBj
YW4gb25seSBjb250cm9sIGlmIGluIG1hbnVhbCBtb2RlCj4gPiAocHdtMl9lbmFibGUgPSAxLikK
PiAKPiBJdCBpcyBpbiBtYW51YWwgbW9kZSBhZnRlciBib290Li4uIChidXQgSSB0aGluayB0aGVy
ZSdzIHNvbWUgZmFuCj4gY29udHJvbCBnb2luZyBvbiwgd2VpcmQ7IEkgbWF5IGJlIGltYWdpbmlu
ZyBpdCwgd2FzIG5vdCBhYmxlIHRvCj4gdHJpZ2dlciBpdCBvbiBwdXJwb3NlKS4KClNvbWUgZmFu
cyBhcmUgc2VsZiByZWd1bGF0aW5nLCBpbmRlcGVuZGVudCBvZiB3aGF0IHRoZSBtb3RoZXJib2Fy
ZApkb2VzLiBNYXliZSB5b3UgaGF2ZSBvbmUgb2YgdGhlc2U/Cgo+IAo+IHJvb3RAYW1kOi9zeXMv
Y2xhc3MvaHdtb24vaHdtb24xL2RldmljZSMgY2F0IHB3bTJfZW5hYmxlCj4gMQo+IHJvb3RAYW1k
Oi9zeXMvY2xhc3MvaHdtb24vaHdtb24xL2RldmljZSMgY2F0IHB3bTIKPiA4MAo+IHJvb3RAYW1k
Oi9zeXMvY2xhc3MvaHdtb24vaHdtb24xL2RldmljZSMgZWNobyAwID4gcHdtMgo+IHJvb3RAYW1k
Oi9zeXMvY2xhc3MvaHdtb24vaHdtb24xL2RldmljZSMgY2F0IHB3bTIKPiA4MAo+IHJvb3RAYW1k
Oi9zeXMvY2xhc3MvaHdtb24vaHdtb24xL2RldmljZSMKPiAKPiBJIGV2ZW4gdHJpZWQgdG8gc2V0
IGl0IHRvIDEsIGJ1dCBubyBsdWNrOgo+IAo+IHJvb3RAYW1kOi9zeXMvY2xhc3MvaHdtb24vaHdt
b24xL2RldmljZSMgZWNobyAxID4gcHdtMl9lbmFibGUKPiByb290QGFtZDovc3lzL2NsYXNzL2h3
bW9uL2h3bW9uMS9kZXZpY2UjIGVjaG8gMCA+IHB3bTIKPiByb290QGFtZDovc3lzL2NsYXNzL2h3
bW9uL2h3bW9uMS9kZXZpY2UjIGNhdCBwd20yCj4gODAKPiByb290QGFtZDovc3lzL2NsYXNzL2h3
bW9uL2h3bW9uMS9kZXZpY2UjIGVjaG8gMiA+IHB3bTIKPiByb290QGFtZDovc3lzL2NsYXNzL2h3
bW9uL2h3bW9uMS9kZXZpY2UjIGNhdCBwd20yCj4gODAKPiByb290QGFtZDovc3lzL2NsYXNzL2h3
bW9uL2h3bW9uMS9kZXZpY2UjCj4gCj4gLi4uYW5kIHNldCBpdCB0aGVyZSBhbmQgYmFjazoKPiAK
PiByb290QGFtZDovc3lzL2NsYXNzL2h3bW9uL2h3bW9uMS9kZXZpY2UjIGVjaG8gMiA+IHB3bTJf
ZW5hYmxlCj4gcm9vdEBhbWQ6L3N5cy9jbGFzcy9od21vbi9od21vbjEvZGV2aWNlIyBlY2hvIDEg
PiBwd20yX2VuYWJsZQo+IHJvb3RAYW1kOi9zeXMvY2xhc3MvaHdtb24vaHdtb24xL2RldmljZSMg
Y2F0IHB3bTIKPiA4MAo+IHJvb3RAYW1kOi9zeXMvY2xhc3MvaHdtb24vaHdtb24xL2RldmljZSMg
ZWNobyA0MCA+IHB3bTIKPiByb290QGFtZDovc3lzL2NsYXNzL2h3bW9uL2h3bW9uMS9kZXZpY2Uj
IGNhdCBwd20yCj4gODAKPiByb290QGFtZDovc3lzL2NsYXNzL2h3bW9uL2h3bW9uMS9kZXZpY2Uj
Cj4gCj4gQW55IG90aGVyIGlkZWFzPwoKVGhhdCB3b3VsZCBiZSBhIGJ1Zy4gV2hpY2gga2VybmVs
IHZlcnNpb24gYXJlIHlvdSBydW5uaW5nPyBZb3VyIGNoaXAgaXMKdGhlICJQIiBmbGF2b3Igb2Yg
dGhlIFc4MzYyN0RIRywgaXQgaXMgbW9yZSByZWNlbnQgYW5kIGxlc3MgcG9wdWxhciBzbwppdCBp
cyBlbnRpcmVseSBwb3NzaWJsZSB0aGF0IGl0IHdhc24ndCBwcm9wZXJseSB0ZXN0ZWQgYW5kIHNv
bWUKZGlmZmVyZW5jZXMgd2l0aCB0aGUgb3JpZ2luYWwgVzgzNjI3REhHIGFyZSBub3QgaGFuZGxl
ZCBieSB0aGUgZHJpdmVyLgpSaWdodCBub3cgdGhlIGRyaXZlciBoYW5kbGVzIGJvdGggY2hpcHMg
YXMgZXF1aXZhbGVudC4KCkkgZG9uJ3QgaGF2ZSBtdWNoIHRpbWUgdG8gc3BlbmQgb24gdGhpcyBy
aWdodCBub3cgYnV0IHlvdSBzaG91bGQgc3RhcnQKYnkgY29tcGFyaW5nIHRoZSBkYXRhc2hlZXRz
IG9mIHRoZSBXODM2MjdESEcgYW5kIHRoZSBXODM2MjdESEctUApsb29raW5nIGZvciBkaWZmZXJl
bmNlcy4KCi0tIApKZWFuIERlbHZhcmUKU1VTRSBMMyBTdXBwb3J0CgpfX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwpsbS1zZW5zb3JzIG1haWxpbmcgbGlzdAps
bS1zZW5zb3JzQGxtLXNlbnNvcnMub3JnCmh0dHA6Ly9saXN0cy5sbS1zZW5zb3JzLm9yZy9tYWls
bWFuL2xpc3RpbmZvL2xtLXNlbnNvcnM

Re: [lm-sensors] hwmon strangeness, no fan control on w83627dhg

[Pavel Machek]

On Mon 2015-01-12 08:22:38, Jean Delvare wrote:
> Hi Pavel,
> 
> On Thu, 8 Jan 2015 23:58:25 +0100, Pavel Machek wrote:
> > > Le Thursday 08 January 2015 à 21:29 +0100, Pavel Machek a écrit :
> > > > hwmon is quite incosistent on my machine: in hwmon0 case, temperature
> > > > files are in directly in hwmon0 subdirectory, but in hwmon1 case, they
> > > > are in hwmon1/device/ . Is that expected? Why is it so?
> > > 
> > > This is for historical reasons. We are in the process of cleaning it all
> > > up (attributes should always be in the hwmon class device) but there are
> > > many drivers left to convert.
> > 
> > So my "hwmon0" is correct and "hwmon1" needs conversion, right?
> 
> Correct. Or to put it in more concrete words: the coretemp driver was
> already converted (since kernel v3.15) but the w83627ehf driver was
> not.

I assume that is this commit?

commit d72d19c26c417d514787ae85b197af34de286c0a
Author: Guenter Roeck <linux@roeck-us.net>
Date:   Sun Feb 16 15:49:04 2014 -0800

    hwmon: (coretemp) Convert to use
    devm_hwmon_device_register_with_groups

    Simplify code, reduce code size, and attach sysfs attributes to
    hwmon device.

    For this driver, the only attribute created is the name attribute.
        Other attributes are still created and removed dynamically as
        cores
	    are added or removed.

Signed-off-by: Guenter Roeck <linux@roeck-us.net>
Reviewed-by: Jean Delvare <jdelvare@suse.de>
Tested-by: Jean Delvare <jdelvare@suse.de>
	    

> > > Check the value of pwm2_enable. If automatic mode is set (pwm2_enable >=
> > > 2), you can't control the output value directly. Same if control is
> > > disabled altogether (pwm2_enable = 0) but I'm not sure if the w83627ehf
> > > driver supports that. You can only control if in manual mode
> > > (pwm2_enable = 1.)
> > 
> > It is in manual mode after boot... (but I think there's some fan
> > control going on, weird; I may be imagining it, was not able to
> > trigger it on purpose).
> 
> Some fans are self regulating, independent of what the motherboard
> does. Maybe you have one of these?

Dunno. When I switch the mode from PWM to voltage control, fan does
speed up a lot. So there is _some_ control from the w83627ehf.

> > 
> > root@amd:/sys/class/hwmon/hwmon1/device# cat pwm2_enable
> > 1
> > root@amd:/sys/class/hwmon/hwmon1/device# cat pwm2
> > 80
> > root@amd:/sys/class/hwmon/hwmon1/device# echo 0 > pwm2
> > root@amd:/sys/class/hwmon/hwmon1/device# cat pwm2
> > 80
> > root@amd:/sys/class/hwmon/hwmon1/device#
> > 
> > I even tried to set it to 1, but no luck:
> > 
> > root@amd:/sys/class/hwmon/hwmon1/device# echo 1 > pwm2_enable
> > root@amd:/sys/class/hwmon/hwmon1/device# echo 0 > pwm2
> > root@amd:/sys/class/hwmon/hwmon1/device# cat pwm2
> > 80
> > root@amd:/sys/class/hwmon/hwmon1/device# echo 2 > pwm2
> > root@amd:/sys/class/hwmon/hwmon1/device# cat pwm2
> > 80
> > root@amd:/sys/class/hwmon/hwmon1/device#
> > 
> > ...and set it there and back:
> > 
> > root@amd:/sys/class/hwmon/hwmon1/device# echo 2 > pwm2_enable
> > root@amd:/sys/class/hwmon/hwmon1/device# echo 1 > pwm2_enable
> > root@amd:/sys/class/hwmon/hwmon1/device# cat pwm2
> > 80
> > root@amd:/sys/class/hwmon/hwmon1/device# echo 40 > pwm2
> > root@amd:/sys/class/hwmon/hwmon1/device# cat pwm2
> > 80
> > root@amd:/sys/class/hwmon/hwmon1/device#
> > 
> > Any other ideas?
> 
> That would be a bug. Which kernel version are you running? Your chip is
> the "P" flavor of the W83627DHG, it is more recent and less popular so
> it is entirely possible that it wasn't properly tested and some
> differences with the original W83627DHG are not handled by the driver.
> Right now the driver handles both chips as equivalent.

This was 3.18 or 3.19-rc. Probably latter.

> I don't have much time to spend on this right now but you should start
> by comparing the datasheets of the W83627DHG and the W83627DHG-P
> looking for differences.

Ok, let me take a look...
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

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

Re: [lm-sensors] hwmon strangeness, no fan control on w83627dhg

[Pavel Machek]

On Thu 2015-01-08 21:29:19, Pavel Machek wrote:
> Hi!
>

> Plus, no matter what I do, I can't control the pwm2 (only one used on
> my board):
> 
> root@amd:/sys/class/hwmon/hwmon1/device# cat pwm2
> 80
> root@amd:/sys/class/hwmon/hwmon1/device# echo 0 > pwm2
> root@amd:/sys/class/hwmon/hwmon1/device# cat pwm2
> 80
> root@amd:/sys/class/hwmon/hwmon1/device#
> 
> I tried playing with other files, too, but no luck. Documentation
> mentions:
> 
> Note: last six functions are influenced by other control bits, not yet
> exported
>       by the driver, so a change might not have any effect.
> 
> 
> Any ideas what bits those are, and what needs to be implemented? (I'm
> currently reading through the documentation).

I have pwm2_mode set to 1. I can set it to 0 and can hear the fan
spinning up, and rpm go to >1500. So I have _some_ kind of
control... But normally fan is around 800, and nothing else seems to
change it...


								Pavel

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

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

Re: [lm-sensors] hwmon strangeness, no fan control on w83627dhg

[Pavel Machek]

Hi!

> I don't have much time to spend on this right now but you should start
> by comparing the datasheets of the W83627DHG and the W83627DHG-P
> looking for differences.

I got the datasheets, (-P version is novuton, the other one is
winbond), and there are pretty similar.

The hardware monitoring chapter is pretty similar. Section 5 (PECI) is
completely rewritten. Section 6.3 has some differences, it looks -P
has new smart fan III+ feature. Section 6.3.4 (smart fan III+) is
new. There are differences in 7.1.3.1. section, but that is some SMI
interrupt stuff, not interesting for us.

Chapter 8/9 (hardware monitor register set) has completely different
graphics... but seems to describe same hardware. Hmm, it has even the
same value (5CA3) in the identification register. Sections .70-.84 seems to
describe new registers for smart fan III+ mode and more. And there are
more new registers near section .98 and .119.

But it seems hardware should be backwards-compatible...
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

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

Re: [lm-sensors] hwmon strangeness, no fan control on w83627dhg

[Pavel Machek]

Hi!

> > I don't have much time to spend on this right now but you should start
> > by comparing the datasheets of the W83627DHG and the W83627DHG-P
> > looking for differences.
> 
> I got the datasheets, (-P version is novuton, the other one is
> winbond), and there are pretty similar.
> 
> The hardware monitoring chapter is pretty similar. Section 5 (PECI) is
> completely rewritten. Section 6.3 has some differences, it looks -P
> has new smart fan III+ feature. Section 6.3.4 (smart fan III+) is
> new. There are differences in 7.1.3.1. section, but that is some SMI
> interrupt stuff, not interesting for us.
> 
> Chapter 8/9 (hardware monitor register set) has completely different
> graphics... but seems to describe same hardware. Hmm, it has even the
> same value (5CA3) in the identification register. Sections .70-.84 seems to
> describe new registers for smart fan III+ mode and more. And there are
> more new registers near section .98 and .119.
> 
> But it seems hardware should be backwards-compatible...

Ok, it seems it is. But by default it starts in (non-compatible) smart
fan III+ mode. I can do port(0x15e) &= ~0x20 to kick it back into
compatible mode, and I can then control CPU fan speed in 800..1700 RPM
range as expected; but my goal was to stop the fan to make the machine
quiet... No success with that so far.

Best regards,
								Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

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

Re: [lm-sensors] hwmon strangeness, no fan control on w83627dhg

[Guenter Roeck]

On 02/14/2015 02:56 AM, Pavel Machek wrote:
> Hi!
>
>>> I don't have much time to spend on this right now but you should start
>>> by comparing the datasheets of the W83627DHG and the W83627DHG-P
>>> looking for differences.
>>
>> I got the datasheets, (-P version is novuton, the other one is
>> winbond), and there are pretty similar.
>>
>> The hardware monitoring chapter is pretty similar. Section 5 (PECI) is
>> completely rewritten. Section 6.3 has some differences, it looks -P
>> has new smart fan III+ feature. Section 6.3.4 (smart fan III+) is
>> new. There are differences in 7.1.3.1. section, but that is some SMI
>> interrupt stuff, not interesting for us.
>>
>> Chapter 8/9 (hardware monitor register set) has completely different
>> graphics... but seems to describe same hardware. Hmm, it has even the
>> same value (5CA3) in the identification register. Sections .70-.84 seems to
>> describe new registers for smart fan III+ mode and more. And there are
>> more new registers near section .98 and .119.
>>
>> But it seems hardware should be backwards-compatible...
>
> Ok, it seems it is. But by default it starts in (non-compatible) smart
> fan III+ mode. I can do port(0x15e) &= ~0x20 to kick it back into
> compatible mode, and I can then control CPU fan speed in 800..1700 RPM
> range as expected; but my goal was to stop the fan to make the machine
> quiet... No success with that so far.
>

Not all CPU fans can be stopped. Maybe that is the case here ?

Guenter


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

Re: [lm-sensors] hwmon strangeness, no fan control on w83627dhg

[Pavel Machek]

Hi!

> >>But it seems hardware should be backwards-compatible...
> >
> >Ok, it seems it is. But by default it starts in (non-compatible) smart
> >fan III+ mode. I can do port(0x15e) &= ~0x20 to kick it back into
> >compatible mode, and I can then control CPU fan speed in 800..1700 RPM
> >range as expected; but my goal was to stop the fan to make the machine
> >quiet... No success with that so far.
> 
> Not all CPU fans can be stopped. Maybe that is the case here ?

All the CPU fans can be stopped, with enough force :-).

Trouble is, I'd like to stop this one with software, and that might
not be possible. (I wonder how they do it? Clearly fan _is_ connected
to the PWM output somehow. Do they have second, hard-coded PWM
generator and logical OR on board...?)
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

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