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. > > 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). Some fans are self regulating, independent of what the motherboard does. Maybe you have one of these? > > 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. 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. -- Jean Delvare SUSE L3 Support _______________________________________________ lm-sensors mailing list lm-sensors@xxxxxxxxxxxxxx http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
