[lm-sensors] k10temp is detected but not shown

* [lm-sensors] k10temp is detected but not shown
@ 2010-10-25  8:14 Mahmood Naderan
  2010-10-25 14:45 ` Mahmood Naderan
                   ` (22 more replies)
  0 siblings, 23 replies; 24+ messages in thread
From: Mahmood Naderan @ 2010-10-25  8:14 UTC (permalink / raw)
  To: lm-sensors

[-- Attachment #1.1: Type: text/plain, Size: 6749 bytes --]

Hi,
I want to see AMD sensors with lm-sensors. Here is what I did:

mahmood@localhost:~$ sudo sensors-detect
# sensors-detect revision 5818 (2010-01-18 17:22:07 +0100)
# System: empty empty
# Board: TYAN S8230
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): yes
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...                           Success!
    (driver `k10temp')
AMD Family 11h thermal sensors...                           No
Intel Core family thermal sensor...                         No
Intel Atom 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): yes
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor'...                   No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               Yes
Found `Winbond W83627DHG-P Super IO Sensors'                Success!
    (address 0xa10, driver `w83627ehf')
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor'...                   No
Trying family `SMSC'...                                     Yes
Found unknown chip with ID 0x0b00
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): yes
Found `IPMI BMC KCS' at 0xca2...                            Success!
    (confidence 8, driver `ipmisensors')
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): yes
Using driver `i2c-piix4' for device 0000:00:14.0: ATI Technologies Inc 
SB600/SB700/SB800 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
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 Super IO Sensors' (confidence: 9)
Driver `ipmisensors':
  * ISA bus, address 0xca2
    Chip `IPMI BMC KCS' (confidence: 8)
Driver `k10temp':
  * Chip `AMD Family 10h thermal sensors' (confidence: 9)
Warning: the required module ipmisensors is not currently installed
on your system. If it is built into the kernel then it's OK.
Otherwise, check http://www.lm-sensors.org/wiki/Devicesfor
driver availability.
Warning: the required module k10temp is not currently installed
on your system. If it is built into the kernel then it's OK.
Otherwise, check http://www.lm-sensors.org/wiki/Devicesfor
driver availability.
To load everything that is needed, add this to /etc/modules:
#----cut here----
# Adapter drivers
ipmi-si
# 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)yes
Successful!
Monitoring programs won't work until the needed modules are
loaded. You may want to run '/etc/init.d/module-init-tools start'
to load them.
Unloading i2c-dev... OK

I then start the service:
mahmood@localhost:~$ sudo /etc/init.d/module-init-tools start
Rather than invoking init scripts through /etc/init.d, use the service(8)
utility, e.g. service module-init-tools start
Since the script you are attempting to invoke has been converted to an
Upstart job, you may also use the start(8) utility, e.g. start module-init-tools
module-init-tools stop/waiting

Seems that all things are fine, however when I run "sensors" there is no cpu 
temps:mahmood@localhost:~$ sensors
w83627dhg-isa-0a10
Adapter: ISA adapter
Vcore:       +1.11 V  (min =  +0.00 V, max =  +1.74 V)
in1:         +1.11 V  (min =  +1.91 V, max =  +1.63 V)   ALARM
AVCC:        +3.33 V  (min =  +2.98 V, max =  +3.63 V)
VCC:         +3.33 V  (min =  +2.98 V, max =  +3.63 V)
in4:         +2.03 V  (min =  +0.80 V, max =  +1.18 V)   ALARM
in5:         +1.66 V  (min =  +1.52 V, max =  +1.02 V)   ALARM
in6:         +1.12 V  (min =  +1.12 V, max =  +1.71 V)
3VSB:        +3.28 V  (min =  +2.98 V, max =  +3.63 V)
Vbat:        +3.25 V  (min =  +2.70 V, max =  +3.30 V)
fan1:          0 RPM  (min = 2109 RPM, div = 128)  ALARM
fan2:          0 RPM  (min = 1757 RPM, div = 128)  ALARM
fan3:          0 RPM  (min = 10546 RPM, div = 128)  ALARM
fan4:          0 RPM  (min =  878 RPM, div = 128)  ALARM
fan5:          0 RPM  (min = 10546 RPM, div = 128)  ALARM
temp1:       +42.0Â°C  (high = -58.0Â°C, hyst = +99.0Â°C)  sensor = thermistor
temp2:       +41.0Â°C  (high = +80.0Â°C, hyst = +75.0Â°C)  sensor = thermistor
temp3:       -60.0Â°C  (high = +80.0Â°C, hyst = +75.0Â°C)  sensor = transistor
cpu0_vid:   +0.375 V

I use Ubuntu 10.04 on AMD64. Also I used the lm-sensors package from synaptick.
Any idea? k10temp is detected but not shown. Thanks

// Naderan *Mahmood;

[-- Attachment #1.2: Type: text/html, Size: 13308 bytes --]

[-- Attachment #2: Type: text/plain, Size: 153 bytes --]

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

^ permalink raw reply	[flat|nested] 24+ messages in thread