[lm-sensors] Acer Aspire 8930G laptop and general approach for reverse engineering sensors

[lm-sensors] Acer Aspire 8930G laptop and general approach for reverse engineering sensors

[Tom Metro]

UnVubmluZyBsbS1zZW5zb3JzIG9uIFVidW50dSAxMi4wNCBvbiBhbiBBY2VyIEFzcGlyZSA4OTMw
RyBsYXB0b3AgYW5kIEkgc2VlOgoKJSBzZW5zb3JzCmFjcGl0ei12aXJ0dWFsLTAKQWRhcHRlcjog
VmlydHVhbCBkZXZpY2UKdGVtcDE6ICAgICAgICArMzguMMKwQyAgKGNyaXQgPSArMTA2LjDCsEMp
CnRlbXAyOiAgICAgICAgKzQ4LjDCsEMgIChjcml0ID0gKzEwNi4wwrBDKQp0ZW1wMzogICAgICAg
ICs0OC4wwrBDICAoY3JpdCA9ICsxMDYuMMKwQykKdGVtcDQ6ICAgICAgICArNDMuMMKwQyAgKGNy
aXQgPSArMTA2LjDCsEMpCgpub3V2ZWF1LXBjaS0wMTAwCkFkYXB0ZXI6IFBDSSBhZGFwdGVyCnRl
bXAxOiAgICAgICAgKzQ5LjDCsEMgIChoaWdoID0gKzEwMC4wwrBDLCBjcml0ID0gKzExMC4wwrBD
KQoKY29yZXRlbXAtaXNhLTAwMDAKQWRhcHRlcjogSVNBIGFkYXB0ZXIKQ29yZSAwOiAgICAgICAr
MzMuMMKwQyAgKGhpZ2ggPSArMTA1LjDCsEMsIGNyaXQgPSArMTA1LjDCsEMpCkNvcmUgMTogICAg
ICAgKzMzLjDCsEMgIChoaWdoID0gKzEwNS4wwrBDLCBjcml0ID0gKzEwNS4wwrBDKQoKSSdkIGxp
a2UgdG8gZmlndXJlIG91dCBwcm9wZXIgbGFiZWxzIGZvciB0aGVzZS4gVGhlIHR3byBjb3JldGVt
cCBzZW5zb3JzIChpZgp3b3JraW5nKSBhcmUgb2J2aW91cywgYW5kIG5vdXZlYXUgSSdkIGFzc3Vt
ZSBpcyB0aGUgR1BVIHRlbXAuIFRoZSByZXN0IGZyb20KYWNwaXR6LXZpcnR1YWwtMCBhcmUgbGVz
cyBjbGVhci4gVGhleSBhcHByb3hpbWF0ZWx5IG1hcCBvdXQgdGhlIHNhbWUKcGF0dGVybiwgdHJh
Y2tpbmcgc3lzdGVtIGxvYWRpbmcsIHdpdGggc2xpZ2h0bHkgZGlmZmVyZW50IHNjYWxpbmcgZmFj
dG9ycy4KCkkgZGlkbid0IHNlZSBhbnkgZ3VpZGFuY2UgaW4gdGhlIEZBUSBvbiBhIGdlbmVyYWwg
YXBwcm9hY2ggdG8gcmV2ZXJzZQplbmdpbmVlcmluZyB0aGUgbGFiZWxpbmcgZm9yIHNlbnNvcnMu
IFRoZXJlIG11c3QgYmUgYSByZWNvbW1lbmRlZCBhcHByb2FjaApmb3IgdGhpcy4KCkkgZGlkIHNl
ZSBpbiB0aGUgRkFRIHRoYXQgdGhlcmUgaXMgbm8gZGF0YWJhc2Ugb2YgY29uZmlndXJhdGlvbnMg
cGVyCm1vdGhlcmJvYXJkL2xhcHRvcCwgYnV0IEkgd291bGQgZXhwZWN0IHRoYXQgd2l0aCBhbGwg
dGhlIHRlbXBlcmF0dXJlCm1vbml0b3JpbmcgdXRpbGl0aWVzIGZvciBXaW5kb3dzLCBvbmUgb3Ig
bW9yZSBvZiB0aGVtIGxpa2VseSBoYXMgYnVuZGxlZApjb25maWd1cmF0aW9uIGZpbGVzIHRoYXQg
Y2FuIGJlIHVzZWQgYXMgYSByZWZlcmVuY2UuIChJZiBzbywgdGhpcyBzb3J0IG9mCmFnZ3JlZ2F0
ZWQgZmFjdHVhbCBpbmZvcm1hdGlvbiBjb3VsZCBldmVuIGJlIGJ1bGsgY29udmVydGVkIHRvIHNl
bnNvcnMuY29uZgpmb3JtYXQgbGVnYWxseS4pCgogLVRvbQoKCgpfX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fXwpsbS1zZW5zb3JzIG1haWxpbmcgbGlzdApsbS1z
ZW5zb3JzQGxtLXNlbnNvcnMub3JnCmh0dHA6Ly9saXN0cy5sbS1zZW5zb3JzLm9yZy9tYWlsbWFu
L2xpc3RpbmZvL2xtLXNlbnNvcnM

Re: [lm-sensors] Acer Aspire 8930G laptop and general approach for reverse engineering sensors

[Guenter Roeck]

T24gMTEvMTcvMjAxMyAwNzo0MSBQTSwgVG9tIE1ldHJvIHdyb3RlOgo+IFJ1bm5pbmcgbG0tc2Vu
c29ycyBvbiBVYnVudHUgMTIuMDQgb24gYW4gQWNlciBBc3BpcmUgODkzMEcgbGFwdG9wIGFuZCBJ
IHNlZToKPgo+ICUgc2Vuc29ycwo+IGFjcGl0ei12aXJ0dWFsLTAKPiBBZGFwdGVyOiBWaXJ0dWFs
IGRldmljZQo+IHRlbXAxOiAgICAgICAgKzM4LjDCsEMgIChjcml0ID0gKzEwNi4wwrBDKQo+IHRl
bXAyOiAgICAgICAgKzQ4LjDCsEMgIChjcml0ID0gKzEwNi4wwrBDKQo+IHRlbXAzOiAgICAgICAg
KzQ4LjDCsEMgIChjcml0ID0gKzEwNi4wwrBDKQo+IHRlbXA0OiAgICAgICAgKzQzLjDCsEMgIChj
cml0ID0gKzEwNi4wwrBDKQo+Cj4gbm91dmVhdS1wY2ktMDEwMAo+IEFkYXB0ZXI6IFBDSSBhZGFw
dGVyCj4gdGVtcDE6ICAgICAgICArNDkuMMKwQyAgKGhpZ2ggPSArMTAwLjDCsEMsIGNyaXQgPSAr
MTEwLjDCsEMpCj4KPiBjb3JldGVtcC1pc2EtMDAwMAo+IEFkYXB0ZXI6IElTQSBhZGFwdGVyCj4g
Q29yZSAwOiAgICAgICArMzMuMMKwQyAgKGhpZ2ggPSArMTA1LjDCsEMsIGNyaXQgPSArMTA1LjDC
sEMpCj4gQ29yZSAxOiAgICAgICArMzMuMMKwQyAgKGhpZ2ggPSArMTA1LjDCsEMsIGNyaXQgPSAr
MTA1LjDCsEMpCj4KPiBJJ2QgbGlrZSB0byBmaWd1cmUgb3V0IHByb3BlciBsYWJlbHMgZm9yIHRo
ZXNlLiBUaGUgdHdvIGNvcmV0ZW1wIHNlbnNvcnMgKGlmCj4gd29ya2luZykgYXJlIG9idmlvdXMs
IGFuZCBub3V2ZWF1IEknZCBhc3N1bWUgaXMgdGhlIEdQVSB0ZW1wLiBUaGUgcmVzdCBmcm9tCj4g
YWNwaXR6LXZpcnR1YWwtMCBhcmUgbGVzcyBjbGVhci4gVGhleSBhcHByb3hpbWF0ZWx5IG1hcCBv
dXQgdGhlIHNhbWUKPiBwYXR0ZXJuLCB0cmFja2luZyBzeXN0ZW0gbG9hZGluZywgd2l0aCBzbGln
aHRseSBkaWZmZXJlbnQgc2NhbGluZyBmYWN0b3JzLgo+ClllcywgdGhhdCBpcyBwcm9iYWJseSB3
aGF0IGl0IGlzLgoKPiBJIGRpZG4ndCBzZWUgYW55IGd1aWRhbmNlIGluIHRoZSBGQVEgb24gYSBn
ZW5lcmFsIGFwcHJvYWNoIHRvIHJldmVyc2UKPiBlbmdpbmVlcmluZyB0aGUgbGFiZWxpbmcgZm9y
IHNlbnNvcnMuIFRoZXJlIG11c3QgYmUgYSByZWNvbW1lbmRlZCBhcHByb2FjaAo+IGZvciB0aGlz
Lgo+CllvdSBzaG91bGQgYmUgYWJsZSB0byBmaW5kIG91dCBtb3JlIGJ5IGRlY29kaW5nIHRoZSBE
U0RULgoKPiBJIGRpZCBzZWUgaW4gdGhlIEZBUSB0aGF0IHRoZXJlIGlzIG5vIGRhdGFiYXNlIG9m
IGNvbmZpZ3VyYXRpb25zIHBlcgo+IG1vdGhlcmJvYXJkL2xhcHRvcCwgYnV0IEkgd291bGQgZXhw
ZWN0IHRoYXQgd2l0aCBhbGwgdGhlIHRlbXBlcmF0dXJlCj4gbW9uaXRvcmluZyB1dGlsaXRpZXMg
Zm9yIFdpbmRvd3MsIG9uZSBvciBtb3JlIG9mIHRoZW0gbGlrZWx5IGhhcyBidW5kbGVkCj4gY29u
ZmlndXJhdGlvbiBmaWxlcyB0aGF0IGNhbiBiZSB1c2VkIGFzIGEgcmVmZXJlbmNlLiAoSWYgc28s
IHRoaXMgc29ydCBvZgo+IGFnZ3JlZ2F0ZWQgZmFjdHVhbCBpbmZvcm1hdGlvbiBjb3VsZCBldmVu
IGJlIGJ1bGsgY29udmVydGVkIHRvIHNlbnNvcnMuY29uZgo+IGZvcm1hdCBsZWdhbGx5LikKPgpX
b3VsZCBiZSBncmVhdC4gVW5mb3J0dW5hdGVseSwgaXQgYXBwZWFycyB0aGF0IHRoZSBjcmVhdG9y
cyBvZiB0aGUgdmFyaW91cyBXaW5kb3dzCnV0aWxpdGllcyBhcmUgbm90IHZlcnkgZW50aHVzaWFz
dGljIGFib3V0IHNoYXJpbmcgdGhlIGluZm9ybWF0aW9uIHRoZXkgaGF2ZS4KUGFydCBvZiBpdCBt
YXkgYmUgYmVjYXVzZSB0aGV5IGdldCBhdCBsZWFzdCBzb21lIG9mIHRoZSBpbmZvcm1hdGlvbiB1
bmRlciBOREEsCmJ1dCBhdCBsZWFzdCBzb21lIG9mIHRoZW0gYXJlIHNpbXBseSBub3QgaW4gYSBj
b29wZXJhdGl2ZSBtaW5kLiBLZWVwIGluIG1pbmQKdGhhdCBXaW5kb3dzIGlzIGluaGVyZW50bHkg
YSBjbG9zZWQtc291cmNlIGVudmlyb25tZW50LCBhbmQgcGVvcGxlJ3MgbWluZHNldAppbiBhIGNs
b3NlZC1zb3VyY2Ugd29ybGQgaXMgYSBiaXQgZGlmZmVyZW50LgoKR3VlbnRlcgoKCl9fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCmxtLXNlbnNvcnMgbWFpbGlu
ZyBsaXN0CmxtLXNlbnNvcnNAbG0tc2Vuc29ycy5vcmcKaHR0cDovL2xpc3RzLmxtLXNlbnNvcnMu
b3JnL21haWxtYW4vbGlzdGluZm8vbG0tc2Vuc29ycw=

Re: [lm-sensors] Acer Aspire 8930G laptop and general approach for reverse engineering sensors

[Tom Metro]

Guenter Roeck wrote:
> Tom Metro wrote:
>> I did see in the FAQ that there is no database of configurations per
>> motherboard/laptop, but I would expect that with all the temperature
>> monitoring utilities for Windows, one or more of them likely has bundled
>> configuration files that can be used as a reference.
>
> Would be great. Unfortunately, it appears that the creators of the 
> various Windows utilities are not very enthusiastic about sharing...

While voluntary sharing would be preferable, I was thinking more along
the lines of reverse engineering their configuration files. Then
creating a script to translate them into a collection of sensors.conf
files. (You can't copyright a compilation of factual data, like a phone
book, so there's isn't a legal problem with doing this. Though it might
inspire them to start encrypting the data. Or downloading settings
on-demand from an online service.)

Is anyone aware of a Windows utility that comes with accessible
configuration files covering a wide range of hardware?


>> % sensors
>> acpitz-virtual-0
>> Adapter: Virtual device
>> temp1:        +38.0°C
>> temp2:        +48.0°C
>> temp3:        +48.0°C
>> temp4:        +43.0°C
>>[...]
>> I'd like to figure out proper labels for these.
>> I didn't see any guidance in the FAQ on a general approach to reverse
>> engineering the labeling for sensors. There must be a recommended
>> approach for this.
>
> You should be able to find out more by decoding the DSDT.

The Differentiated System Description Table?
https://wiki.archlinux.org/index.php/DSDT

OK, following the procedure here:
https://wiki.archlinux.org/index.php/DSDT#Recompiling_it_yourself

to extract and decompile:

% sudo aptitude install iasl
% sudo su
# cat /sys/firmware/acpi/tables/DSDT > dsdt.dat
# exit
% iasl -d dsdt.dat
Disassembly completed, written to "dsdt.dsl"
% head -22 dsdt.dsl
/*
 * Intel ACPI Component Architecture
 * AML Disassembler version 20100528
 *
 * Disassembly of dsdt.dat, Fri Nov 29 16:58:19 2013
 *
 *
 * Original Table Header:
 *     Signature        "DSDT"
 *     Length           0x0000913C (37180)
 *     Revision         0x01 **** ACPI 1.0, no 64-bit math support
 *     Checksum         0x1C
 *     OEM ID           "ACRSYS"
 *     OEM Table ID     "ACRPRDCT"
 *     OEM Revision     0x00000001 (1)
 *     Compiler ID      "1025"
 *     Compiler Version 0x01000013 (16777235)
 */
DefinitionBlock ("dsdt.aml", "DSDT", 1, "ACRSYS", "ACRPRDCT", 0x00000001)
{
    Name (SP2O, 0x4E)
    Name (SP1O, 0x164E)
[...]


OK, so there is over 9000 lines in that file. Any hints as to what I'm
looking for?

I see some mention of fans and a "ThermalZone":

    Name (DFEC, Zero)
    Scope (_TZ)
    {
        PowerResource (FN00, 0x00, 0x0000)
        {
            Method (_STA, 0, Serialized)
            {
                If (LEqual (DTSF, Zero))
                {
                    Return (Zero)
                }
                Else
                {
                    Return (One)
                }
            }

            Method (_ON, 0, Serialized)
            {
            }

            Method (_OFF, 0, Serialized)
            {
            }
        }

        Device (FAN0)
        {
            Name (_HID, EisaId ("PNP0C0B"))
            Name (_UID, Zero)
            Name (_PR0, Package (0x01)
            {
                FN00
            })
        }

        ThermalZone (TZ00)
        {
            Method (_AC0, 0, Serialized)
            {
                Return (Add (0x0AAC, Multiply (ACTT, 0x0A)))
            }

            Name (_AL0, Package (0x01)
            {
                FAN0
            })
[...]
            Method (_TMP, 0, Serialized)
            {
                Store (CRTP, Local0)
                If (And (Local0, 0x80))
                {
                    Subtract (Local0, 0x0100, Local0)
                }

                Return (Add (0x0AAC, Multiply (Local0, 0x0A)))
            }

            Method (_PSL, 0, Serialized)
            {
                If (CMPE)
                {
                    Return (Package (0x02)
                    {
                        \_PR.CPU0,
                        \_PR.CPU1
                    })
                }

                Return (Package (0x01)
                {
                    \_PR.CPU0
                })
            }

            Method (_TSP, 0, Serialized)
            {
                Return (0x96)
            }
        }

        ThermalZone (TZVR)
        {
            Method (_TMP, 0, Serialized)
            {
                Store (VRTP, Local0)
                If (And (Local0, 0x80))
                {
                    Subtract (Local0, 0x0100, Local0)
                }

                Return (Add (0x0AAC, Multiply (Local0, 0x0A)))
            }

            Method (_CRT, 0, NotSerialized)
            {
                Return (0x0ED0)
            }
        }

        ThermalZone (TZVL)
        {
            Method (_TMP, 0, Serialized)
            {
                Store (VLTP, Local0)
                If (And (Local0, 0x80))
                {
                    Subtract (Local0, 0x0100, Local0)
                }

                Return (Add (0x0AAC, Multiply (Local0, 0x0A)))
            }

            Method (_CRT, 0, NotSerialized)
            {
                Return (0x0ED0)
            }
        }

        ThermalZone (TZ01)
        {
            Method (_CRT, 0, Serialized)
            {
                Return (0x0ED0)
            }

            Method (_TMP, 0, Serialized)
            {
                Store (CLTP, Local0)
                If (And (Local0, 0x80))
                {
                    Subtract (Local0, 0x0100, Local0)
                }

                Return (Add (0x0AAC, Multiply (Local0, 0x0A)))
            }
        }
    }
[...]


Am I supposed to infer what subsystem is being monitored from the
ThermalZone name, like TZVL? And figure out how the correlate that with
one of the 4 sensors returned by the 'acpitz-virtual-0' device?

Any references for how to dig deeper?

According to:
http://acpi.sourceforge.net/documentation/thermal.html

the DSDT declares one or more Thermal Zones, and establishes some rules
for what happens when certain thresholds are reached, like performing a
passive cooling counter measure, such as dropping the CPU clock speed,
or performing an active counter measure, like turning on or speeding up
a fan.

The impression I get is that the DSDT is going to tell me how many zones
I have (which I already know is 4), but not necessarily what each zone
corresponds to. So far I'm not seeing any labels embedded in the code.

So not much more to be found here than what you can learn from poking
around in the /sys representation of the same info:

# find /sys -name 'thermal*'
/sys/devices/system/cpu/cpu0/thermal_throttle
/sys/devices/system/cpu/cpu1/thermal_throttle
/sys/devices/virtual/thermal
/sys/devices/virtual/thermal/thermal_zone0
/sys/devices/virtual/thermal/thermal_zone1
/sys/devices/virtual/thermal/thermal_zone2
/sys/devices/virtual/thermal/thermal_zone3
/sys/devices/LNXSYSTM:00/LNXCPU:00/thermal_cooling
/sys/devices/LNXSYSTM:00/LNXCPU:01/thermal_cooling
/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:00/LNXVIDEO:00/device:02/thermal_cooling
/sys/devices/LNXSYSTM:00/LNXSYBUS:01/PNP0C0B:00/thermal_cooling
/sys/devices/LNXSYSTM:00/LNXSYBUS:01/LNXTHERM:00/thermal_zone
/sys/devices/LNXSYSTM:00/LNXSYBUS:01/LNXTHERM:01/thermal_zone
/sys/devices/LNXSYSTM:00/LNXSYBUS:01/LNXTHERM:02/thermal_zone
/sys/devices/LNXSYSTM:00/LNXSYBUS:01/LNXTHERM:03/thermal_zone
/sys/bus/acpi/drivers/thermal
/sys/class/thermal
/sys/class/thermal/thermal_zone0
/sys/class/thermal/thermal_zone1
/sys/class/thermal/thermal_zone2
/sys/class/thermal/thermal_zone3
/sys/kernel/debug/ieee80211/phy0/iwlwifi/data/thermal_throttling
/sys/module/thermal

# ls -al /sys/devices/virtual/thermal/thermal_zone0/
total 0
drwxr-xr-x  3 root root    0 Nov 17 19:56 ./
drwxr-xr-x 10 root root    0 Nov 17 19:56 ../
lrwxrwxrwx  1 root root    0 Nov 29 17:28 cdev0 -> ../cooling_device0/
-r--r--r--  1 root root 4096 Nov 29 17:28 cdev0_trip_point
lrwxrwxrwx  1 root root    0 Nov 29 17:28 device ->
  ../../../LNXSYSTM:00/LNXSYBUS:01/LNXTHERM:00/
-rw-r--r--  1 root root 4096 Nov 29 17:28 mode
-rw-r--r--  1 root root 4096 Nov 29 17:28 passive
drwxr-xr-x  2 root root    0 Nov 29 17:26 power/
lrwxrwxrwx  1 root root    0 Nov 17 19:56 subsystem ->
  ../../../../class/thermal/
-r--r--r--  1 root root 4096 Nov 29 17:28 temp
-r--r--r--  1 root root 4096 Nov 29 17:28 trip_point_0_temp
-r--r--r--  1 root root 4096 Nov 29 17:28 trip_point_0_type
-r--r--r--  1 root root 4096 Nov 29 17:28 trip_point_1_temp
-r--r--r--  1 root root 4096 Nov 29 17:28 trip_point_1_type
-r--r--r--  1 root root 4096 Nov 29 17:28 type
-rw-r--r--  1 root root 4096 Nov 28 12:21 uevent


That's not to say nothing can be learned from the DSDT. Hypothetically,
if you had a system with multiple fans, you might be able to infer what
subsystem a Thermal Zone is protecting by which fan gets activated when
thresholds are tripped for that zone. (In combination with an inspection
of the hardware to see which fans are where, and some experimentation
with the ACPI code to manually turn on fans, so you know which physical
fan corresponds to FAN0, etc.) Similarly for passive cooling.

But practically speaking, in a system with only one fan, and the only
passive cooling options being throttling the CPU or GPU, that may not
shed much light.

Still, thanks for the DSDT tip.


One thing I haven't tried yet, is noting the current values of the 4
sensors, then rebooting and going into the BIOS to see if it displays
the current temperatures. If it does, that would be the easiest way to
match them up with labels.

 -Tom


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

Re: [lm-sensors] Acer Aspire 8930G laptop and general approach for reverse engineering sensors

[Guenter Roeck]

On Fri, Nov 29, 2013 at 06:29:27PM -0500, Tom Metro wrote:
> Guenter Roeck wrote:
> > Tom Metro wrote:
> >> I did see in the FAQ that there is no database of configurations per
> >> motherboard/laptop, but I would expect that with all the temperature
> >> monitoring utilities for Windows, one or more of them likely has bundled
> >> configuration files that can be used as a reference.
> >
> > Would be great. Unfortunately, it appears that the creators of the 
> > various Windows utilities are not very enthusiastic about sharing...
> 
> While voluntary sharing would be preferable, I was thinking more along
> the lines of reverse engineering their configuration files. Then
> creating a script to translate them into a collection of sensors.conf
> files. (You can't copyright a compilation of factual data, like a phone
> book, so there's isn't a legal problem with doing this. Though it might
> inspire them to start encrypting the data. Or downloading settings
> on-demand from an online service.)
> 
> Is anyone aware of a Windows utility that comes with accessible
> configuration files covering a wide range of hardware?
> 
I am not aware of any such packages which would let you do that.
Either configuration files don't exist and everything is hard-coded,
or the configuration is embedded in the code.

One exception is Open Hardware Monitor, for which source is available.
This package is already used for input whereever possible, though.

Guenter

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