[lm-sensors] Coretemp ERROR: Can't get value of subfeature

[lm-sensors] Coretemp ERROR: Can't get value of subfeature

[Dong Huang]

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

Hello everyone,

i am a newbie here, want to check the temperature of my motherboard with
lm_sensors, unfortunately i got error message as i run sensors. So I really
need your help, thanks in advance.

Here are some informations, that maybe useful to you.
*1. My motherboard info: *
    Manufacturer: "Intel Corporation"
    Product: "440BX Desktop Reference Platform"
    Version: "None"
    Serial: "None"
    Type: 0x01 (Other)

*2. Sensors and Kernel information*
sensors-3.1.1-3.5 i586
Linux version 2.6.31.12-0.2-desktop i686, System:  openSUSE 11.2 (i586),
KDE:  4.3.5

*3. The output of sensors: *
coretemp-isa-0000
Adapter: ISA adapter
ERROR: Can't get value of subfeature temp1_input: Can't read
Core 0:       +0.0°C  (high = +100.0°C, crit = +100.0°C)

*4. demsg:*
there's so many text, i put it in a file as an appendix.

*5. output of sensors-detect*
Shutting down sensors:

done
# sensors-detect revision 5729 (2009-06-02 15:51:29 +0200)
# System: VMware, Inc. VMware Virtual Platform
# Board: Intel Corporation 440BX Desktop Reference Platform

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):
Silicon Integrated Systems SIS5595...                       No
VIA VT82C686 Integrated Sensors...                          No
VIA VT8231 Integrated Sensors...                            No
AMD K8 thermal sensors...                                   No
AMD K10 thermal sensors...                                  No
Intel Core family thermal sensor...                         Success!
    (driver `coretemp')
Intel AMB FB-DIMM thermal sensor...                         No
VIA C7 thermal and voltage sensors...                       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/Fintek'...                       No
Trying family `ITE'...                                      No
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor'...                   No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/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):
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:07.3: Intel 82371AB PIIX4 ACPI
Module i2c-dev loaded successfully.

Now follows a summary of the probes I have just done.
Just press ENTER to continue:

Driver `coretemp':
  * Chip `Intel Core family thermal sensor' (confidence: 9)

Do you want to overwrite /etc/sysconfig/lm_sensors? (YES/no):
Unloading i2c-dev... OK

*6. output of lsmod*
Module                  Size  Used by
vmsync                  4572  0
vmmemctl               10556  0
vmblock                14468  1
edd                    10472  0
fuse                   74332  1
loop                   17228  0
ppdev                  10276  0
parport_pc             40356  0
parport                39948  2 ppdev,parport_pc
floppy                 61220  0
i2c_piix4              13840  0
sr_mod                 17572  0
pcspkr                  2784  0
vmxnet                 20132  0
pcnet32                38244  0
vmci                   36484  0
sg                     32884  0
cdrom                  40768  1 sr_mod
mptctl                 28804  0
shpchp                 36660  0
pci_hotplug            33696  1 shpchp
container               4064  0
intel_agp              31460  1
ac                      4964  0
button                  6608  0
ext4                  381512  3
jbd2                   96288  1 ext4
crc16                   1952  1 ext4
linear                  6500  0
dm_snapshot            30952  0
dm_mod                 84900  10 dm_snapshot
fan                     5028  0
processor              50576  0
ide_pci_generic         4036  0
piix                    6760  0
ide_core              122540  2 ide_pci_generic,piix
ata_generic             4836  0
mptspi                 17992  2
mptscsih               28288  1 mptspi
mptbase                71268  3 mptctl,mptspi,mptscsih
scsi_transport_spi     27552  1 mptspi
thermal                21084  0
thermal_sys            18344  3 fan,processor,thermal

*7. output of lspci -nn*
00:00.0 Host bridge [0600]: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX
Host bridge [8086:7190] (rev 01)
00:01.0 PCI bridge [0604]: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX AGP
bridge [8086:7191] (rev 01)
00:07.0 ISA bridge [0601]: Intel Corporation 82371AB/EB/MB PIIX4 ISA
[8086:7110] (rev 08)
00:07.1 IDE interface [0101]: Intel Corporation 82371AB/EB/MB PIIX4 IDE
[8086:7111] (rev 01)
00:07.3 Bridge [0680]: Intel Corporation 82371AB/EB/MB PIIX4 ACPI
[8086:7113] (rev 08)
00:07.7 System peripheral [0880]: VMware Virtual Machine Communication
Interface [15ad:0740] (rev 10)
00:0f.0 VGA compatible controller [0300]: VMware SVGA II Adapter [15ad:0405]
00:10.0 SCSI storage controller [0100]: LSI Logic / Symbios Logic 53c1030
PCI-X Fusion-MPT Dual Ultra320 SCSI [1000:0030] (rev 01)
00:11.0 PCI bridge [0604]: VMware PCI bridge [15ad:0790] (rev 02)
00:15.0 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
00:15.1 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
00:15.2 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
00:15.3 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
00:15.4 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
00:15.5 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
00:15.6 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
00:15.7 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
00:16.0 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
00:16.1 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
00:16.2 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
00:16.3 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
00:16.4 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
00:16.5 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
00:16.6 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
00:16.7 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
00:17.0 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
00:17.1 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
00:17.2 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
00:17.3 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
00:17.4 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
00:17.5 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
00:17.6 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
00:17.7 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
00:18.0 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
00:18.1 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
00:18.2 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
00:18.3 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
00:18.4 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
00:18.5 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
00:18.6 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
00:18.7 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
02:00.0 Ethernet controller [0200]: Advanced Micro Devices [AMD] 79c970
[PCnet32 LANCE] [1022:2000] (rev 10)

*8. output of i2cdetect -l* is empty.

I hope you can give me a hand. Thanks a lot.
kind regards
borat

[-- Attachment #1.2: Type: text/html, Size: 10797 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] Coretemp ERROR: Can't get value of subfeature

[Jean Delvare]

Hi Huang,

On Thu, 27 May 2010 10:41:14 +0200, Dong Huang wrote:
> Hello everyone,
> 
> i am a newbie here, want to check the temperature of my motherboard with
> lm_sensors, unfortunately i got error message as i run sensors. So I really
> need your help, thanks in advance.
> 
> (...)
> *5. output of sensors-detect*
> Shutting down sensors:
> 
> done
> # sensors-detect revision 5729 (2009-06-02 15:51:29 +0200)
> # System: VMware, Inc. VMware Virtual Platform
> # Board: Intel Corporation 440BX Desktop Reference Platform

It makes no sense to run sensors or any _hardware_ monitoring
application on a _virtual_ machine. Hardware monitoring should be done
on the host system, not on the guests.

> (...)
> *3. The output of sensors: *
> coretemp-isa-0000
> Adapter: ISA adapter
> ERROR: Can't get value of subfeature temp1_input: Can't read
> Core 0:       +0.0°C  (high = +100.0°C, crit = +100.0°C)

I presume that VMware simply doesn't allow guest drivers to access CPU
MSR. Nothing we can do.

-- 
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] Coretemp ERROR: Can't get value of subfeature

[Jean Delvare]

Huang,

Please keep the lm-sensors list in the loop, and please don't top-post.

On Thu, 27 May 2010 11:02:31 +0200, Dong Huang wrote:
> Hi Jean,
> thanks for the blitz answer,
> i am testing lm_sensors, it's why on a vitual machine, and my host is not
> linux, but windows, do you think it would work if i installed lm_sensor
> unter my windows operating system?

No. lm-sensors is Linux-only. But there are many hardware monitoring
tools available for Windows, starting with the one mainboard vendors
often provide themselves.

-- 
Jean Delvare

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

Re: [lm-sensors] Coretemp ERROR: Can't get value of subfeature temp1_input

[Guenter Roeck]

On Tue, Aug 14, 2012 at 07:12:53PM +0000, vadugs wrote:
> Jean Delvare <khali <at> linux-fr.org> writes:
> 
> > 
> > 
> > It makes no sense to run sensors or any _hardware_ monitoring
> > application on a _virtual_ machine. Hardware monitoring should be done
> > on the host system, not on the guests.
> > 
> > > (...)
> > > *3. The output of sensors: *
> > > coretemp-isa-0000
> > > Adapter: ISA adapter
> > > ERROR: Can't get value of subfeature temp1_input: Can't read
> > > Core 0:       +0.0°C  (high = +100.0°C, crit = +100.0°C)
> > 
> > I presume that VMware simply doesn't allow guest drivers to access CPU
> > MSR. Nothing we can do.
> > 
> 
> Hey I am facing the same error. I just wanted to ask if there any other way to 
> obtain temperature by running any hardware monitoring application on a virtual 
> machine?
> 
Only if the VM lets you do it.

Guenter

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