Description of problem: 'sensors-detection' identifies correctly the sensor chip on my M/B; 'sensors' displays the various chip values but does not take into account any configuration statement (e.g. label, ignore, set) of the sensor3.conf file Version-Release number of selected component (if applicable): - kernel-2.6.31.9-174.fc12.x86_64 - lm_sensors-3.1.1-4.fc12.x86_64 How reproducible: Modify any "w83627ehf-*" configuration statement of the /etc/sensors3.conf file, then check how they affect the 'sensors' command output Steps to Reproduce: 1. edit /etc/sensors3.conf file to modify any "w83627ehf-*" configuration statement, the save the file 2. run 'sensors -s' from terminal 3. run 'sensors' from terminal Actual results: The output of the 'sensors' command is not affected by any changes in the sensors3.conf' file Expected results: The output of the 'sensors' command should by affected by changes in the sensors3.conf' file Additional info: I run FC12-x86_64 on an Asus K8V-X M/B that mounts a Winbond W83697HF sensor chip
Hi, Most likely your chip is not a w83627ehf, but some variant (which gets handled by the same driver, please execute the following 2 commands: cat /sys/class/hwmon/hwmon?/name cat /sys/class/hwmon/hwmon?/device/name One of these should print something like w83627ehf, but slightly different, use that inside sensors.conf If this does not work, please supply the output of the 2 above commands, and execute: dmesg > log And attach the resulting log file. Regards, Hans
Hi Hans, I forgot to mention that everything worked just fine with FC11. Following your instructions: # cat /sys/class/hwmon/hwmon1/device/name w83697hf w83697hf is what I'm using in sensors3.conf, but it doesn't work. And here is the dmesg output: .... Adding 4087736k swap on /dev/md3. Priority:-1 extents:1 across:4087736k powernow-k8: Found 1 AMD Athlon(tm) 64 Processor 3000+ processors (1 cpu cores) (version 2.20.00) powernow-k8: 0 : fid 0xc (2000 MHz), vid 0x2 powernow-k8: 1 : fid 0xa (1800 MHz), vid 0x6 powernow-k8: 2 : fid 0x2 (1000 MHz), vid 0x12 Marking TSC unstable due to cpufreq changes NET: Registered protocol family 10 lo: Disabled Privacy Extensions ip6_tables: (C) 2000-2006 Netfilter Core Team Clocksource tsc unstable (delta = -175662289 ns) w83627hf: Found W83697HF chip at 0x290 skge eth0: enabling interface ADDRCONF(NETDEV_UP): eth0: link is not ready ..... Thanks and regards Enrico
Hi, Can you attach the sensors.conf you are trying to use please ? Regards, Hans
Hi Hans, I just noticed the different chip IDs (cat /sys/class/hwmon/hwmon1/device/name vs. dmesg log); I put the right ID in the sensors3,conf and everything is OK now. Thanks again for your suggestion. Regards Enrico