On Wed, Feb 15, 2012 at 10:51 PM, Jean Delvare <khali@xxxxxxxxxxxx> wrote:
Hi Kenneth,
Obviously this is useless data, I've added a filter to sensors-detect.
On Wed, 15 Feb 2012 18:36:40 -0800, Kenneth Cox wrote:
> Here is the results of sensors-detect as promised:
>
> # sensors-detect revision 5946 (2011-03-23 11:54:44 +0100)
> # System: To Be Filled By O.E.M. To Be Filled By O.E.M.
> # Board: ASRock A75M-HVS
> (...)
> Driver `to-be-written':Obviously this is your monitoring chip. A more recent version of
> * ISA bus, address 0x290
> Chip `Nuvoton NCT6776F Super IO Sensors' (confidence: 9)
sensors-detect [1] would have told you to use the w83627ehf driver. If
you run kernel 2.6.39 or later it should work (mostly) fine. For older
kernels, or if you are affected by a bug in the early support, Guenter
Roeck has a standalone version of the driver [2] which you could try if
the web server works for you (it doesn't for me at the moment.) I also
have a standalone version of the w83627ehf driver [3] but it isn't as
up-to-date as Guenter's.
[1] http://dl.lm-sensors.org/lm-sensors/files/sensors-detect
[2] http://roeck-us.net/linux/drivers/
[3] http://khali.linux-fr.org/devel/misc/w83627ehf/
Hope that helps,
--
Jean Delvare
http://khali.linux-fr.org/wishlist.html
Thanks for the response. I downloaded the new sensors-detect script and ran it. I also installed Roeck's driver. Here is the output of sensors-detect:
# sensors-detect revision 6022 (2012-02-16 07:44:31 +0100)
# Board: ASRock A75M-HVS
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):
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... Success!
(driver `k10temp')
AMD Family 15h thermal sensors... No
AMD Family 15h 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 `Nuvoton NCT6776F Super IO Sensors' Success!
(address 0x290, 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): yes
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):
Using driver `i2c-piix4' for device 0000:00:14.0: AMD Hudson-2 SMBus
Module i2c-dev loaded successfully.
Next adapter: SMBus PIIX4 adapter at 0b00 (i2c-0)
Do you want to scan it? (yes/NO/selectively): yes
Client found at address 0x50
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... Yes
(confidence 8, not a hardware monitoring chip)
Probing for `EDID EEPROM'... No
Client found at address 0x51
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... Yes
(confidence 8, not a hardware monitoring chip)
Now follows a summary of the probes I have just done.
Just press ENTER to continue:
Driver `w83627ehf':
* ISA bus, address 0x290
Chip `Nuvoton NCT6776F Super IO Sensors' (confidence: 9)
Driver `k10temp' (autoloaded):
* Chip `AMD Family 12h and 14h thermal sensors' (confidence: 9)
Do you want to overwrite /etc/sysconfig/lm_sensors? (YES/no):
Copy prog/init/lm_sensors.init to /etc/init.d/lm_sensors
for initialization at boot time.
You should now start the lm_sensors service to load the required
kernel modules.
Unloading i2c-dev... OK
Unloading cpuid... OK
But sensors does not give any more info:
k10temp-pci-00c3
Adapter: PCI adapter
temp1: +9.6°C (high = +70.0°C)
(crit = +70.0°C, hyst = +69.0°C)
Am I missing something?
Ken
_______________________________________________ lm-sensors mailing list lm-sensors@xxxxxxxxxxxxxx http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
