[lm-sensors] help with setup / chip support

[lm-sensors] help with setup / chip support

[Kenneth Cox]

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

I am having trouble getting lm-sensors to work as it should I believe that
part of the problem is support for a newer chip set. here are the specs:

CPU: AMD A4-3400 APU with Radeon(tm) HD Graphics
family(18) model(1) stepping(0)

MoBo: ASRock A75M-HVS

I'm using the onboard Radeon graphics.

I ran the sensors-detect script saying yes to everything. The output of
sensors:
k10temp-pci-00c3
Adapter: PCI adapter
temp1:         +9.8°C  (high = +70.0°C)
                       (crit = +70.0°C, hyst = +69.0°C)

That's much colder than room temp and only gives data for the PCI adapter.

I also tried downloading the latest version of sensors-detect from
http://www.lm-sensors.org/wiki/Devices and rerunning. It did not change
anything.

Is there a way to get sensor data for the CPU and accurate data from the
PCI adapter? Any help would be appreciated.

Thanks,
Ken

[-- Attachment #1.2: Type: text/html, Size: 1148 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

Re: [lm-sensors] help with setup / chip support

[Jean Delvare]

SGkgS2VubmV0aCwKCk9uIE1vbiwgMTMgRmViIDIwMTIgMTY6NDY6MzMgLTA4MDAsIEtlbm5ldGgg
Q294IHdyb3RlOgo+IEkgYW0gaGF2aW5nIHRyb3VibGUgZ2V0dGluZyBsbS1zZW5zb3JzIHRvIHdv
cmsgYXMgaXQgc2hvdWxkIEkgYmVsaWV2ZSB0aGF0Cj4gcGFydCBvZiB0aGUgcHJvYmxlbSBpcyBz
dXBwb3J0IGZvciBhIG5ld2VyIGNoaXAgc2V0LiBoZXJlIGFyZSB0aGUgc3BlY3M6Cj4gCj4gQ1BV
OiBBTUQgQTQtMzQwMCBBUFUgd2l0aCBSYWRlb24odG0pIEhEIEdyYXBoaWNzCj4gZmFtaWx5KDE4
KSBtb2RlbCgxKSBzdGVwcGluZygwKQo+IAo+IE1vQm86IEFTUm9jayBBNzVNLUhWUwo+IAo+IEkn
bSB1c2luZyB0aGUgb25ib2FyZCBSYWRlb24gZ3JhcGhpY3MuCj4gCj4gSSByYW4gdGhlIHNlbnNv
cnMtZGV0ZWN0IHNjcmlwdCBzYXlpbmcgeWVzIHRvIGV2ZXJ5dGhpbmcuIFRoZSBvdXRwdXQgb2YK
PiBzZW5zb3JzOgo+IGsxMHRlbXAtcGNpLTAwYzMKPiBBZGFwdGVyOiBQQ0kgYWRhcHRlcgo+IHRl
bXAxOiAgICAgICAgICs5LjjCsEMgIChoaWdoID0gKzcwLjDCsEMpCj4gICAgICAgICAgICAgICAg
ICAgICAgICAoY3JpdCA9ICs3MC4wwrBDLCBoeXN0ID0gKzY5LjDCsEMpCj4gCj4gVGhhdCdzIG11
Y2ggY29sZGVyIHRoYW4gcm9vbSB0ZW1wIGFuZCBvbmx5IGdpdmVzIGRhdGEgZm9yIHRoZSBQQ0kg
YWRhcHRlci4KClRoaXMgaXNuJ3QgdGhlIHRlbXBlcmF0dXJlIG9mICJ0aGUgUENJIGFkYXB0ZXIi
LCB0aGUgdmFsdWUgaXMgZnJvbSB5b3VyCkNQVS4gVGhpcyBoYXBwZW5zIHRvIGJlIGltcGxlbWVu
dGVkIGFzIGEgUENJIGRldmljZSBpbiBBTUQgcHJvY2Vzc29ycywKd2hpY2ggaXMgd2h5IHlvdSBz
ZWUgIlBDSSBhZGFwdGVyIiBpbiB0aGUgb3V0cHV0LCBidXQgdGhpcyBpcyByYXRoZXIKbWlzbGVh
ZGluZyBJIGFkbWl0LgoKVGhlIHJlcG9ydGVkIHRlbXBlcmF0dXJlIGluZGVlZCBsb29rcyB3cm9u
ZywgaG93ZXZlciBpdCBpc24ndApuZWNlc3NhcmlseSBzdXJwcmlzaW5nLiBUaGlzIGlzbid0IGFu
IGFic29sdXRlIHRlbXBlcmF0dXJlLCBidXQgcmF0aGVyCmEgdGVtcGVyYXR1cmUgbWFyZ2luIGZy
b20gdGhlIENQVSdzIG1heCwgYW5kIGl0IGlzIG9ubHkgYWNjdXJhdGUgd2hlbgp5b3UgZ2V0IGNs
b3NlIHRvIHRoZSBsaW1pdC4gU28gZnJvbSB0aGUgYWJvdmUsIG9uZSBjYW4gc2F5IHRoYXQgeW91
cgpDUFUgaXMgcnVubmluZyB2ZXJ5IGNvb2wgYW5zIHNhZmUsIGFuZCB0aGF0J3MgYWJvdXQgaXQu
CgpUaGF0IGJlaW5nIHNhaWQsIEkgdGhpbmsgdGhpcyBpcyB0aGUgZmlyc3QgcmVwb3J0IEkgc2Vl
IGZvciB0aGlzIGZhbWlseQpvZiBDUFUuIEFuZHJlYXMsIEFuZHJlLCBkbyB5b3UgdGhpbmsgdGhl
cmUncyBhbnkgYnVnIHRvIGJlIGZpeGVkIGhlcmU/Cgo+IEkgYWxzbyB0cmllZCBkb3dubG9hZGlu
ZyB0aGUgbGF0ZXN0IHZlcnNpb24gb2Ygc2Vuc29ycy1kZXRlY3QgZnJvbQo+IGh0dHA6Ly93d3cu
bG0tc2Vuc29ycy5vcmcvd2lraS9EZXZpY2VzIGFuZCByZXJ1bm5pbmcuIEl0IGRpZCBub3QgY2hh
bmdlCj4gYW55dGhpbmcuCj4gCj4gSXMgdGhlcmUgYSB3YXkgdG8gZ2V0IHNlbnNvciBkYXRhIGZv
ciB0aGUgQ1BVIGFuZCBhY2N1cmF0ZSBkYXRhIGZyb20gdGhlCj4gUENJIGFkYXB0ZXI/IEFueSBo
ZWxwIHdvdWxkIGJlIGFwcHJlY2lhdGVkLgoKV2hhdCBraW5kIG9mIHN5c3RlbSBpcyB0aGlzPyBJ
ZiB0aGlzIGlzIGEgbGFwdG9wIHlvdSdyZSBwcm9iYWJseSBvdXQgb2YKbHVjay4gSWYgdGhpcyBp
cyBhIGRlc2t0b3Agc3lzdGVtLCBJIHdvdWxkIGV4cGVjdCBhIGhhcmR3YXJlIG1vbml0b3JpbmcK
Y2hpcCBvbiB0aGUgU01CdXMgb3IgaW4gdGhlIFN1cGVyLUkvTyBjaGlwLiBNYXliZSBpdCBpcyB0
b28gcmVjZW50IGFuZAp3ZSBkb24ndCBrbm93IGFib3V0IGl0IHlldC4gUGxlYXNlIHByb3ZpZGUg
dGhlIGZ1bGwgb3V0cHV0IG9mCnNlbnNvcnMtZGV0ZWN0LgoKLS0gCkplYW4gRGVsdmFyZQoKX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KbG0tc2Vuc29ycyBt
YWlsaW5nIGxpc3QKbG0tc2Vuc29yc0BsbS1zZW5zb3JzLm9yZwpodHRwOi8vbGlzdHMubG0tc2Vu
c29ycy5vcmcvbWFpbG1hbi9saXN0aW5mby9sbS1zZW5zb3Jz

Re: [lm-sensors] help with setup / chip support

[Kenneth Cox]

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

Jean,

Thanks for the response.

On Tue, Feb 14, 2012 at 11:29 PM, Jean Delvare <khali@linux-fr.org> wrote:

> Hi Kenneth,
>
> On Mon, 13 Feb 2012 16:46:33 -0800, Kenneth Cox wrote:
> > I am having trouble getting lm-sensors to work as it should I believe
> that
> > part of the problem is support for a newer chip set. here are the specs:
> >
> > CPU: AMD A4-3400 APU with Radeon(tm) HD Graphics
> > family(18) model(1) stepping(0)
> >
> > MoBo: ASRock A75M-HVS
> >
> > I'm using the onboard Radeon graphics.
> >
> > I ran the sensors-detect script saying yes to everything. The output of
> > sensors:
> > k10temp-pci-00c3
> > Adapter: PCI adapter
> > temp1:         +9.8°C  (high = +70.0°C)
> >                        (crit = +70.0°C, hyst = +69.0°C)
> >
> > That's much colder than room temp and only gives data for the PCI
> adapter.
>
> This isn't the temperature of "the PCI adapter", the value is from your
> CPU. This happens to be implemented as a PCI device in AMD processors,
> which is why you see "PCI adapter" in the output, but this is rather
> misleading I admit.
>
> The reported temperature indeed looks wrong, however it isn't
> necessarily surprising. This isn't an absolute temperature, but rather
> a temperature margin from the CPU's max, and it is only accurate when
> you get close to the limit. So from the above, one can say that your
> CPU is running very cool ans safe, and that's about it.
>
> That being said, I think this is the first report I see for this family
> of CPU. Andreas, Andre, do you think there's any bug to be fixed here?
>

Got it. That's excellent news. At least I know I can trust the output to
let me know if it's getting to warm. I did not trust it at all before.

> I also tried downloading the latest version of sensors-detect from
> > http://www.lm-sensors.org/wiki/Devices and rerunning. It did not change
> > anything.
> >
> > Is there a way to get sensor data for the CPU and accurate data from the
> > PCI adapter? Any help would be appreciated.
>
> What kind of system is this? If this is a laptop you're probably out of
> luck. If this is a desktop system, I would expect a hardware monitoring
> chip on the SMBus or in the Super-I/O chip. Maybe it is too recent and
> we don't know about it yet. Please provide the full output of
> sensors-detect.
>
> --
> Jean Delvare
>

I built is a dual purpose HTPC and home server. It's in a micro ATX case.
This is the mother board: ASRock A75M-HVS FM1 AMD A75 (Hudson D3) HDMI SATA
6Gb/s USB 3.0 Micro ATX AMD Motherboard with UEFI BIOS. I'm running Ubuntu
11.10. Any other info that would be helpful?

The current configuration is sitting in a cabinet under the TV. I'm a bit
nervous about closing the cabinet door on it and not getting enough air
flow, so I wanted to monitor the temp with the door closed but I didn't
trust the output. There's a fair amount of space around the machine but
still. It's good to know now that I can trust the output to let me know if
it's getting too hot in there. Still it would be nice to see some other
output.

I'll send the output of sensors-detect this evening.

Thanks again,
Ken

[-- Attachment #1.2: Type: text/html, Size: 4157 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

Re: [lm-sensors] help with setup / chip support

[Andreas Herrmann]

On Wed, Feb 15, 2012 at 06:21:19AM -0800, Kenneth Cox wrote:
> Jean,
> 
> Thanks for the response.
> 
> On Tue, Feb 14, 2012 at 11:29 PM, Jean Delvare <khali@linux-fr.org> wrote:
> 
>     Hi Kenneth,
> 
>     On Mon, 13 Feb 2012 16:46:33 -0800, Kenneth Cox wrote:
>     > I am having trouble getting lm-sensors to work as it should I believe
>     that
>     > part of the problem is support for a newer chip set. here are the specs:
>     >
>     > CPU: AMD A4-3400 APU with Radeon(tm) HD Graphics
>     > family(18) model(1) stepping(0)
>     >
>     > MoBo: ASRock A75M-HVS
>     >
>     > I'm using the onboard Radeon graphics.
>     >
>     > I ran the sensors-detect script saying yes to everything. The output of
>     > sensors:
>     > k10temp-pci-00c3
>     > Adapter: PCI adapter
>     > temp1:         +9.8°C  (high = +70.0°C)
>     >                        (crit = +70.0°C, hyst = +69.0°C)
>     >
>     > That's much colder than room temp and only gives data for the PCI
>     adapter.
> 
>     This isn't the temperature of "the PCI adapter", the value is from your
>     CPU. This happens to be implemented as a PCI device in AMD processors,
>     which is why you see "PCI adapter" in the output, but this is rather
>     misleading I admit.
> 
>     The reported temperature indeed looks wrong, however it isn't
>     necessarily surprising. This isn't an absolute temperature, but rather
>     a temperature margin from the CPU's max, and it is only accurate when
>     you get close to the limit. So from the above, one can say that your
>     CPU is running very cool ans safe, and that's about it.
> 
>     That being said, I think this is the first report I see for this family
>     of CPU. Andreas, Andre, do you think there's any bug to be fixed here?
> 
> 
> Got it. That's excellent news. At least I know I can trust the output to let me
> know if it's getting to warm. I did not trust it at all before.
> 
> 
>     > I also tried downloading the latest version of sensors-detect from
>     > http://www.lm-sensors.org/wiki/Devices and rerunning. It did not change
>     > anything.
>     >
>     > Is there a way to get sensor data for the CPU and accurate data from the
>     > PCI adapter? Any help would be appreciated.
> 
>     What kind of system is this? If this is a laptop you're probably out of
>     luck. If this is a desktop system, I would expect a hardware monitoring
>     chip on the SMBus or in the Super-I/O chip. Maybe it is too recent and
>     we don't know about it yet. Please provide the full output of
>     sensors-detect.

Hi Kenneth,

I just can second what Jean already said. The reported temperature
(Tctl) is

  "on its own scale aligned to the processors cooling
  requirements. Therefore Tctl does not represent a temperature which
  could be measured on the die or the case of the processor. Instead,
  it specifies the processor temperature relative to the maximum
  operating temperature, Tctl_max."

(Quoted from the AMD Family 12h Processor BKDG.) You have a FM1 socket
processor. Tctl_max is 70 in your case.  So the reported temperature
of 9.8 is far below that maximum operating temperature.


HTH,

Andreas



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

Re: [lm-sensors] help with setup / chip support

[Kenneth Cox]

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

On Wed, Feb 15, 2012 at 7:17 AM, Andreas Herrmann <andreas.herrmann3@amd.com
> wrote:

> On Wed, Feb 15, 2012 at 06:21:19AM -0800, Kenneth Cox wrote:
> > Jean,
> >
> > Thanks for the response.
> >
> > On Tue, Feb 14, 2012 at 11:29 PM, Jean Delvare <khali@linux-fr.org>
> wrote:
> >
> >     Hi Kenneth,
> >
> >     On Mon, 13 Feb 2012 16:46:33 -0800, Kenneth Cox wrote:
> >     > I am having trouble getting lm-sensors to work as it should I
> believe
> >     that
> >     > part of the problem is support for a newer chip set. here are the
> specs:
> >     >
> >     > CPU: AMD A4-3400 APU with Radeon(tm) HD Graphics
> >     > family(18) model(1) stepping(0)
> >     >
> >     > MoBo: ASRock A75M-HVS
> >     >
> >     > I'm using the onboard Radeon graphics.
> >     >
> >     > I ran the sensors-detect script saying yes to everything. The
> output of
> >     > sensors:
> >     > k10temp-pci-00c3
> >     > Adapter: PCI adapter
> >     > temp1:         +9.8°C  (high = +70.0°C)
> >     >                        (crit = +70.0°C, hyst = +69.0°C)
> >     >
> >     > That's much colder than room temp and only gives data for the PCI
> >     adapter.
> >
> >     This isn't the temperature of "the PCI adapter", the value is from
> your
> >     CPU. This happens to be implemented as a PCI device in AMD
> processors,
> >     which is why you see "PCI adapter" in the output, but this is rather
> >     misleading I admit.
> >
> >     The reported temperature indeed looks wrong, however it isn't
> >     necessarily surprising. This isn't an absolute temperature, but
> rather
> >     a temperature margin from the CPU's max, and it is only accurate when
> >     you get close to the limit. So from the above, one can say that your
> >     CPU is running very cool ans safe, and that's about it.
> >
> >     That being said, I think this is the first report I see for this
> family
> >     of CPU. Andreas, Andre, do you think there's any bug to be fixed
> here?
> >
> >
> > Got it. That's excellent news. At least I know I can trust the output to
> let me
> > know if it's getting to warm. I did not trust it at all before.
> >
> >
> >     > I also tried downloading the latest version of sensors-detect from
> >     > http://www.lm-sensors.org/wiki/Devices and rerunning. It did not
> change
> >     > anything.
> >     >
> >     > Is there a way to get sensor data for the CPU and accurate data
> from the
> >     > PCI adapter? Any help would be appreciated.
> >
> >     What kind of system is this? If this is a laptop you're probably out
> of
> >     luck. If this is a desktop system, I would expect a hardware
> monitoring
> >     chip on the SMBus or in the Super-I/O chip. Maybe it is too recent
> and
> >     we don't know about it yet. Please provide the full output of
> >     sensors-detect.
>
> Hi Kenneth,
>
> I just can second what Jean already said. The reported temperature
> (Tctl) is
>
>  "on its own scale aligned to the processors cooling
>  requirements. Therefore Tctl does not represent a temperature which
>  could be measured on the die or the case of the processor. Instead,
>  it specifies the processor temperature relative to the maximum
>  operating temperature, Tctl_max."
>
> (Quoted from the AMD Family 12h Processor BKDG.) You have a FM1 socket
> processor. Tctl_max is 70 in your case.  So the reported temperature
> of 9.8 is far below that maximum operating temperature.
>
>
> HTH,
>
> Andreas
>
>
>
Thank you Andreas.

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

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')
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'...                   No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               Yes
Found `Nuvoton NCT6776F Super IO Sensors'                   Success!
    (address 0x290, driver `to-be-written')
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor'...                   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 `to-be-written':
  * 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)

Note: there is no driver for Nuvoton NCT6776F Super IO Sensors yet.
Check http://www.lm-sensors.org/wiki/Devices for updates.

No modules to load, skipping modules configuration.

Unloading i2c-dev... OK
Unloading cpuid... OK

Thanks,
Ken

[-- Attachment #1.2: Type: text/html, Size: 9725 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

Re: [lm-sensors] help with setup / chip support

[Jean Delvare]

Hi Kenneth,

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.

Obviously this is useless data, I've added a filter to sensors-detect.

> # Board: ASRock A75M-HVS
> (...)
> Driver `to-be-written':
>   * ISA bus, address 0x290
>     Chip `Nuvoton NCT6776F Super IO Sensors' (confidence: 9)

Obviously this is your monitoring chip. A more recent version of
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

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

Re: [lm-sensors] help with setup / chip support

[Kenneth Cox]

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

On Wed, Feb 15, 2012 at 10:51 PM, Jean Delvare <khali@linux-fr.org> wrote:

> Hi Kenneth,
>
> 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.
>
> Obviously this is useless data, I've added a filter to sensors-detect.
>
> > # Board: ASRock A75M-HVS
> > (...)
> > Driver `to-be-written':
> >   * ISA bus, address 0x290
> >     Chip `Nuvoton NCT6776F Super IO Sensors' (confidence: 9)
>
> Obviously this is your monitoring chip. A more recent version of
> 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

[-- Attachment #1.2: Type: text/html, Size: 7827 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

Re: [lm-sensors] help with setup / chip support

[Jean Delvare]

T24gVGh1LCAxNiBGZWIgMjAxMiAyMDoyOTowNCAtMDgwMCwgS2VubmV0aCBDb3ggd3JvdGU6Cj4g
VGhhbmtzIGZvciB0aGUgcmVzcG9uc2UuIEkgZG93bmxvYWRlZCB0aGUgbmV3IHNlbnNvcnMtZGV0
ZWN0IHNjcmlwdCBhbmQgcmFuCj4gaXQuIEkgYWxzbyBpbnN0YWxsZWQgUm9lY2sncyBkcml2ZXIu
IEhlcmUgaXMgdGhlIG91dHB1dCBvZiBzZW5zb3JzLWRldGVjdDoKPiAKPiAjIHNlbnNvcnMtZGV0
ZWN0IHJldmlzaW9uIDYwMjIgKDIwMTItMDItMTYgMDc6NDQ6MzEgKzAxMDApCj4gIyBCb2FyZDog
QVNSb2NrIEE3NU0tSFZTCj4gKC4uLikKPiBOb3cgZm9sbG93cyBhIHN1bW1hcnkgb2YgdGhlIHBy
b2JlcyBJIGhhdmUganVzdCBkb25lLgo+IEp1c3QgcHJlc3MgRU5URVIgdG8gY29udGludWU6Cj4g
Cj4gRHJpdmVyIGB3ODM2MjdlaGYnOgo+ICAgKiBJU0EgYnVzLCBhZGRyZXNzIDB4MjkwCj4gICAg
IENoaXAgYE51dm90b24gTkNUNjc3NkYgU3VwZXIgSU8gU2Vuc29ycycgKGNvbmZpZGVuY2U6IDkp
Cj4gCj4gRHJpdmVyIGBrMTB0ZW1wJyAoYXV0b2xvYWRlZCk6Cj4gICAqIENoaXAgYEFNRCBGYW1p
bHkgMTJoIGFuZCAxNGggdGhlcm1hbCBzZW5zb3JzJyAoY29uZmlkZW5jZTogOSkKPiAKPiBEbyB5
b3Ugd2FudCB0byBvdmVyd3JpdGUgL2V0Yy9zeXNjb25maWcvbG1fc2Vuc29ycz8gKFlFUy9ubyk6
Cj4gQ29weSBwcm9nL2luaXQvbG1fc2Vuc29ycy5pbml0IHRvIC9ldGMvaW5pdC5kL2xtX3NlbnNv
cnMKPiBmb3IgaW5pdGlhbGl6YXRpb24gYXQgYm9vdCB0aW1lLgo+IFlvdSBzaG91bGQgbm93IHN0
YXJ0IHRoZSBsbV9zZW5zb3JzIHNlcnZpY2UgdG8gbG9hZCB0aGUgcmVxdWlyZWQKPiBrZXJuZWwg
bW9kdWxlcy4KPiAKPiBVbmxvYWRpbmcgaTJjLWRldi4uLiBPSwo+IFVubG9hZGluZyBjcHVpZC4u
LiBPSwo+IAo+IEJ1dCBzZW5zb3JzIGRvZXMgbm90IGdpdmUgYW55IG1vcmUgaW5mbzoKPiAKPiBr
MTB0ZW1wLXBjaS0wMGMzCj4gQWRhcHRlcjogUENJIGFkYXB0ZXIKPiB0ZW1wMTogICAgICAgICAr
OS42wrBDICAoaGlnaCA9ICs3MC4wwrBDKQo+ICAgICAgICAgICAgICAgICAgICAgICAgKGNyaXQg
PSArNzAuMMKwQywgaHlzdCA9ICs2OS4wwrBDKQo+IAo+IAo+IEFtIEkgbWlzc2luZyBzb21ldGhp
bmc/CgpEaWQgeW91IHJlc3RhcnQgdGhlIGxtX3NlbnNvcnMgc2VydmljZSBhZnRlciB0aGF0PyBz
ZW5zb3JzLWRldGVjdCBvbmx5CmRldGVjdHMgd2hpY2ggZHJpdmVycyBhcmUgbmVlZGVkLCBpdCBk
b2Vzbid0IGxvYWQgdGhlbSBmb3IgeW91LgoKSWYgeW91IHN0aWxsIGRvbid0IGdldCBtb3JlIHZh
bHVlcyBldmVuIGFmdGVyIHRoYXQsIGNoZWNrIHRoZSBrZXJuZWwKbG9nIGZvciBlcnJvciBtZXNz
YWdlcy4KCi0tIApKZWFuIERlbHZhcmUKCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fCmxtLXNlbnNvcnMgbWFpbGluZyBsaXN0CmxtLXNlbnNvcnNAbG0tc2Vu
c29ycy5vcmcKaHR0cDovL2xpc3RzLmxtLXNlbnNvcnMub3JnL21haWxtYW4vbGlzdGluZm8vbG0t
c2Vuc29ycw=

Re: [lm-sensors] help with setup / chip support

[Kenneth Cox]

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

On Thu, Feb 16, 2012 at 11:35 PM, Jean Delvare <khali@linux-fr.org> wrote:

> On Thu, 16 Feb 2012 20:29:04 -0800, Kenneth Cox wrote:
> > 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
> > (...)
> > 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?
>
> Did you restart the lm_sensors service after that? sensors-detect only
> detects which drivers are needed, it doesn't load them for you.
>

How do you restart lm_sensors? I just rebooted and assumed that would
restart it ok.


>
> If you still don't get more values even after that, check the kernel
> log for error messages.


I don't know what I'm looking for in the kernel log. I searched the log for
"sensors" and came up with nothing. What should I be looking for?


>
> --
> Jean Delvare
>

Thanks for all your help on this.
Ken

[-- Attachment #1.2: Type: text/html, Size: 2730 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

Re: [lm-sensors] help with setup / chip support

[Jean Delvare]

Hi Kenneth,

On Fri, 17 Feb 2012 16:36:36 -0800, Kenneth Cox wrote:
> On Thu, Feb 16, 2012 at 11:35 PM, Jean Delvare <khali@linux-fr.org> wrote:
> > Did you restart the lm_sensors service after that? sensors-detect only
> > detects which drivers are needed, it doesn't load them for you.
> 
> How do you restart lm_sensors? I just rebooted and assumed that would
> restart it ok.

Depends on your distribution:
# rclm_sensors restart
would work on Suse unless you use systemd in which case it would rather
be:
# systemctl restart lm_sensors.service
Red Hat / Fedora is probably similar, while Debian and Ubuntu are
certainly different. Can't help you with these as I don't know them,
sorry.

Also note that most distributions modify sensors-detect slightly to
improve the integration. As you're using the upstream version of
sensors-detect you may be missing part of this integration.

Rebooting should work too, so if you did that, there's certainly
another problem.

> > If you still don't get more values even after that, check the kernel
> > log for error messages.
> 
> I don't know what I'm looking for in the kernel log. I searched the log for
> "sensors" and came up with nothing. What should I be looking for?

You should rather look for "w83627" and "nct67":

# dmesg | grep -i w83627
# dmesg | grep -i nct67
or
# grep -i w83627 /var/log/messages | tail
# grep -i nct67 /var/log/messages | tail

Most likely you are the victim of an ACPI resource conflict, this is
becoming very frequent and sensors-detect doesn't know about them yet.


-- 
Jean Delvare

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

Re: [lm-sensors] help with setup / chip support

[Kenneth Cox]

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

On Sat, Feb 18, 2012 at 1:46 PM, Jean Delvare <khali@linux-fr.org> wrote:

> Hi Kenneth,
>
> On Fri, 17 Feb 2012 16:36:36 -0800, Kenneth Cox wrote:
> > On Thu, Feb 16, 2012 at 11:35 PM, Jean Delvare <khali@linux-fr.org>
> wrote:
> > > Did you restart the lm_sensors service after that? sensors-detect only
> > > detects which drivers are needed, it doesn't load them for you.
> >
> > How do you restart lm_sensors? I just rebooted and assumed that would
> > restart it ok.
>
> Depends on your distribution:
> # rclm_sensors restart
> would work on Suse unless you use systemd in which case it would rather
> be:
> # systemctl restart lm_sensors.service
> Red Hat / Fedora is probably similar, while Debian and Ubuntu are
> certainly different. Can't help you with these as I don't know them,
> sorry.
>
> Also note that most distributions modify sensors-detect slightly to
> improve the integration. As you're using the upstream version of
> sensors-detect you may be missing part of this integration.
>
> Rebooting should work too, so if you did that, there's certainly
> another problem.
>
> > > If you still don't get more values even after that, check the kernel
> > > log for error messages.
> >
> > I don't know what I'm looking for in the kernel log. I searched the log
> for
> > "sensors" and came up with nothing. What should I be looking for?
>
> You should rather look for "w83627" and "nct67":
>
> # dmesg | grep -i w83627
> # dmesg | grep -i nct67
> or
> # grep -i w83627 /var/log/messages | tail
> # grep -i nct67 /var/log/messages | tail
>

None of those returned anything. :(


>
> Most likely you are the victim of an ACPI resource conflict, this is
> becoming very frequent and sensors-detect doesn't know about them yet.
>

So is it just a "wait for further developments" kind of thing? Thanks for
all your help on this. You've been excellent.


>
> --
> Jean Delvare
>

[-- Attachment #1.2: Type: text/html, Size: 2860 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

Re: [lm-sensors] help with setup / chip support

[Andrey Repin]

Greetings, Jean Delvare!

> Debian and Ubuntu are certainly different. Can't help you with these as I
> don't know them, sorry.

It is either "service servicename restart" or "invoke-rc.d servicename restart"
The first is more applicable to Ubuntu with it's upstart daemon.

> Also note that most distributions modify sensors-detect slightly to
> improve the integration. As you're using the upstream version of
> sensors-detect you may be missing part of this integration.

> Rebooting should work too, so if you did that, there's certainly
> another problem.

Could be that sensorsd wasn't configured to autostart with system.


--
WBR,
Andrey Repin (hell-for-yahoo@umail.ru) 24.02.2012, <09:24>

Sorry for my terrible english...


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

Re: [lm-sensors] help with setup / chip support

[Jean Delvare]

On Thu, 23 Feb 2012 21:03:37 -0800, Kenneth Cox wrote:
> So is it just a "wait for further developments" kind of thing? Thanks for
> all your help on this. You've been excellent.

No, I'm not done with you yet :p

I think the problem here is that you ended up using the sensors-detect
script from upstream while Debian/Ubuntu normally makes integration
changes to that script. So you ran the script but it did not update the
configuration files as it should have.

Please check file /etc/modules , see if you can see the following line:

w83627ehf

If it isn't present, add it, and reboot. This is how Debian loads hwmon
drivers and I presume Ubuntu does the same.

As root, you can also load the w83627ehf driver manually:

# modprobe w83627ehf

and see if the NCT6776F shows in the output of "sensors" then.

-- 
Jean Delvare
http://khali.linux-fr.org/wishlist.html

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