[lm-sensors] W83627DHG-P sensor shows a single voltage monitor for +5V and +12V on in4?

[lm-sensors] W83627DHG-P sensor shows a single voltage monitor for +5V and +12V on in4?

[ianp]

Hi,

I'm running Xubuntu 12.04.4 on an Asrock G41C-GS board.


$ uname -a

Linux box 3.12-11.dmz.1-liquorix-amd64 #1 ZEN SMP PREEMPT Sat Feb 15 21:48:42 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

$ apt-show-versions |grep sensors
libsensors4/precise uptodate 1:3.3.1-2ubuntu1
lm-sensors/precise uptodate 1:3.3.1-2ubuntu1

I found out that this sensor, W83627DHG-P, shows a single voltage monitor for +5V and +12V on in4, at least on this board, using this configuration:

chip "w83627dhg-*"
### Voltages
   label  in0  "Vcore"
   ignore in1
   label  in2  "AVcc"
   #ignore in3  # "+3.3V"
   #label  in4  "+5V" # uncomment for +5V monitoring
   label  in4  "+12V" # uncomment for +12V monitoring
   ignore in5
   label  in6  "Vram"
   label  in7  "3Vsb"
   #ignore in8  # "Vbat"
   ignore cpu0_vid

   #compute  in4  @*((20/10)+1), @/((20/10)+1) # uncomment for +5V monitoring
   compute  in4  @*((60/10)+1), @/((60/10)+1) # uncomment for +12V monitoring

   set in0_min 1.125 * 0.95
   set in0_max 1.125 * 1.05
   set in2_min 3.3 * 0.95
   set in2_max 3.3 * 1.05
   #set in4_min   5 * 0.95 # uncomment for +5V monitoring
   #set in4_max   5 * 1.05 # uncomment for +5V monitoring
   set in4_min  12 * 0.95 # uncomment for +12V monitoring
   set in4_max  12 * 1.05 # uncomment for +12V monitoring
   set in6_min 1.8
   set in6_max 1.9
### Temperatures
   label  temp1  "N/B Temp"
   label  temp2  "CPU Temp"
   ignore temp3

   set temp1_max 60
   set temp1_max_hyst 55
   set temp2_max 60
   set temp2_max_hyst 55
### Fans
   label  fan1  "CHA Fan"
   label  fan2  "CPU Fan"
   label  fan3  "PSU Fan"
   ignore fan4
   ignore fan5

   set fan1_min 0
   set fan2_min 900
   set fan3_min 0

$ sensors
w83627dhg-isa-0290
Adapter: ISA adapter
Vcore:        +1.11 V  (min =  +1.07 V, max =  +1.18 V)
AVcc:         +3.30 V  (min =  +2.98 V, max =  +3.63 V)
+3.3V:        +3.30 V  (min =  +2.98 V, max =  +3.63 V)
+12V:        +11.59 V  (min = +11.42 V, max = +12.60 V)
Vram:         +1.90 V  (min =  +1.80 V, max =  +1.90 V)
3Vsb:         +3.50 V  (min =  +2.98 V, max =  +3.63 V)
Vbat:         +3.33 V  (min =  +2.70 V, max =  +3.30 V)  ALARM
CHA Fan:        0 RPM  (min =    0 RPM, div = 128)
CPU Fan:     1704 RPM  (min =  902 RPM, div = 8)
PSU Fan:        0 RPM  (min =    0 RPM, div = 128)
N/B Temp:     +41.0°C  (high = +60.0°C, hyst = +55.0°C)  sensor = thermistor
CPU Temp:     +37.5°C  (high = +60.0°C, hyst = +55.0°C)  sensor = thermistor


Uncommenting and commenting the relevant lines for +5V monitoring, I get:

$ sensors
w83627dhg-isa-0290
Adapter: ISA adapter
Vcore:        +1.11 V  (min =  +1.07 V, max =  +1.18 V)
AVcc:         +3.30 V  (min =  +2.98 V, max =  +3.63 V)
+3.3V:        +3.30 V  (min =  +2.98 V, max =  +3.63 V)
+5V:          +4.97 V  (min =  +6.12 V, max =  +6.12 V)  ALARM
Vram:         +1.90 V  (min =  +1.80 V, max =  +1.90 V)
3Vsb:         +3.50 V  (min =  +2.98 V, max =  +3.63 V)
Vbat:         +3.33 V  (min =  +2.70 V, max =  +3.30 V)  ALARM
CHA Fan:        0 RPM  (min =    0 RPM, div = 128)
CPU Fan:     1654 RPM  (min =  902 RPM, div = 8)
PSU Fan:        0 RPM  (min =    0 RPM, div = 128)
N/B Temp:     +41.0°C  (high = +60.0°C, hyst = +55.0°C)  sensor = thermistor
CPU Temp:     +37.5°C  (high = +60.0°C, hyst = +55.0°C)  sensor = thermistor
intrusion0:  ALARM


To corroborate this behavior, I dumped the monitoring data in Windows using hwmonitor v1.24

CPUID HWMonitor Report
-------------------------------------------------------------------------

Binaries
-------------------------------------------------------------------------

HWMonitor version    1.2.4.0

Monitoring
-------------------------------------------------------------------------

Mainboard Model        G41C-GS (0x000001B6 - 0x004E5333)

LPCIO
-------------------------------------------------------------------------

LPCIO Vendor        Winbond
LPCIO Model        W83627DHG-P
LPCIO Vendor ID        0x5CA3
LPCIO Chip ID        0xB0
LPCIO Revision ID    0x73
Config Mode I/O address    0x2E
Config Mode LDN        0xB
Config Mode registers    
        00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 
    00    FF FF FF FF FF FF FF 0B FF FF FF FF FF FF FF FF 
    10    FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 
    20    B0 73 FF 00 44 00 00 FF 70 00 00 00 D2 21 00 FF 
    30    01 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 
    40    FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 
    50    FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 
    60    02 90 FF FF FF FF FF FF FF FF FF FF FF FF FF FF 
    70    00 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 
Register space        LPC, base address = 0x0290


Hardware Monitors
-------------------------------------------------------------------------

Hardware monitor    Winbond W83627DHG
    Voltage 0    1.11 Volts [0x8B] (CPU VCORE)
    Voltage 1    0.69 Volts [0x56] (VIN1)
    Voltage 2    3.30 Volts [0xCE] (+3.3V)
    Voltage 3    4.97 Volts [0xCF] (+5V)
    Voltage 4    11.54 Volts [0xCF] (+12V)
    Voltage 5    1.69 Volts [0xD3] (VIN5)
    Voltage 6    1.90 Volts [0xED] (VIN6)
    Temperature 0    40°C (104°F) [0x28] (SYSTIN)
    Temperature 1    39°C (101°F) [0x4D] (CPUTIN)
    Temperature 2    46°C (113°F) [0x5B] (AUXTIN)
    Fan 1        2250 RPM [0x4B] (CPUFANIN0)
Hardware registers    
Register space        LPC, base address = 0x0290
bank 0    
        00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 
    00    04 FF 04 B3 11 00 37 20 01 B3 01 FF 3C 3C 0A 0A 
    10    04 FF 10 00 00 01 01 3C 43 07 00 00 2D FF FF DA 
    20    8B 56 CE CF CF D3 ED 28 FF 4B FF DA 00 B4 72 E3 
    30    BA E3 BA EA 50 2B 0B EF D8 37 32 FF BB FF 05 FF 
    40    03 02 14 FF FF 00 3F F5 2D 00 00 C4 90 95 00 A3 
    50    FF FF 00 FF FF FF 00 80 C1 7F FF FF 19 A0 00 05 
    60    04 7F 40 00 01 01 3C FF 01 FF 01 FF FF FF FF 00 
    70    00 00 00 00 00 0E 7F 7F 7F 7F 7F 7F 00 28 FF FF 
    80    04 FF 04 B3 11 00 37 20 01 B3 01 FF 3C 3C 0A 0A 
    90    04 FF 10 00 00 01 01 3C 43 07 00 00 2D FF FF DA 
    A0    8B 56 CE CF CF D3 ED 28 FF 4B FF DA 00 B4 72 E3 
    B0    BA E3 BA EA 50 2B 0B EF D8 37 32 FF BB FF 05 FF 
    C0    03 00 10 FF FF 00 3F F5 2D 00 00 C4 90 95 00 A3 
    D0    FF FF 00 FF FF FF 00 80 C1 7F FF FF 19 A0 00 05 
    E0    04 7F 40 00 01 01 3C FF 01 FF 01 FF FF FF FF 00 
    F0    00 00 00 00 00 0E 7F 7F 7F 7F 7F 7F 00 28 FF FF 
bank 1    
    50    26 80 00 32 00 37 01 20 00 00 00 00 00 00 0E FF 
bank 2    
    50    2D 80 00 4B 00 50 1E 02 FF FF FF FF FF FF FF FF 
bank 3    
    50    06 07 07 00 04 02 02 01 06 00 00 00 7C 00 00 00 
bank 4    
    50    3A 13 FF 00 00 00 00 08 2A 02 14 AA 09 60 20 7F 



As you can see from above, +5V and +12V share the same address (0xCF).

My question is, how do you work around this apprently shared voltage monitoring in lm-sensors? I wish to show +5V and +12V monitors seperately like how hwmonitor does.


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

Re: [lm-sensors] W83627DHG-P sensor shows a single voltage monitor for +5V and +12V on in4?

[Guenter Roeck]

On 02/18/2014 05:23 PM, ianp wrote:
> Hi,
>
> I'm running Xubuntu 12.04.4 on an Asrock G41C-GS board.
>
>
> $ uname -a
>
> Linux box 3.12-11.dmz.1-liquorix-amd64 #1 ZEN SMP PREEMPT Sat Feb 15 21:48:42 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
>
> $ apt-show-versions |grep sensors
> libsensors4/precise uptodate 1:3.3.1-2ubuntu1
> lm-sensors/precise uptodate 1:3.3.1-2ubuntu1
>
> I found out that this sensor, W83627DHG-P, shows a single voltage monitor for +5V and +12V on in4, at least on this board, using this configuration:
>
> chip "w83627dhg-*"
> ### Voltages
>     label  in0  "Vcore"
>     ignore in1
>     label  in2  "AVcc"
>     #ignore in3  # "+3.3V"
>     #label  in4  "+5V" # uncomment for +5V monitoring
>     label  in4  "+12V" # uncomment for +12V monitoring
>     ignore in5
>     label  in6  "Vram"
>     label  in7  "3Vsb"
>     #ignore in8  # "Vbat"
>     ignore cpu0_vid
>
>     #compute  in4  @*((20/10)+1), @/((20/10)+1) # uncomment for +5V monitoring
>     compute  in4  @*((60/10)+1), @/((60/10)+1) # uncomment for +12V monitoring
>
>     set in0_min 1.125 * 0.95
>     set in0_max 1.125 * 1.05
>     set in2_min 3.3 * 0.95
>     set in2_max 3.3 * 1.05
>     #set in4_min   5 * 0.95 # uncomment for +5V monitoring
>     #set in4_max   5 * 1.05 # uncomment for +5V monitoring
>     set in4_min  12 * 0.95 # uncomment for +12V monitoring
>     set in4_max  12 * 1.05 # uncomment for +12V monitoring
>     set in6_min 1.8
>     set in6_max 1.9
> ### Temperatures
>     label  temp1  "N/B Temp"
>     label  temp2  "CPU Temp"
>     ignore temp3
>
>     set temp1_max 60
>     set temp1_max_hyst 55
>     set temp2_max 60
>     set temp2_max_hyst 55
> ### Fans
>     label  fan1  "CHA Fan"
>     label  fan2  "CPU Fan"
>     label  fan3  "PSU Fan"
>     ignore fan4
>     ignore fan5
>
>     set fan1_min 0
>     set fan2_min 900
>     set fan3_min 0
>
> $ sensors
> w83627dhg-isa-0290
> Adapter: ISA adapter
> Vcore:        +1.11 V  (min =  +1.07 V, max =  +1.18 V)
> AVcc:         +3.30 V  (min =  +2.98 V, max =  +3.63 V)
> +3.3V:        +3.30 V  (min =  +2.98 V, max =  +3.63 V)
> +12V:        +11.59 V  (min = +11.42 V, max = +12.60 V)
> Vram:         +1.90 V  (min =  +1.80 V, max =  +1.90 V)
> 3Vsb:         +3.50 V  (min =  +2.98 V, max =  +3.63 V)
> Vbat:         +3.33 V  (min =  +2.70 V, max =  +3.30 V)  ALARM
> CHA Fan:        0 RPM  (min =    0 RPM, div = 128)
> CPU Fan:     1704 RPM  (min =  902 RPM, div = 8)
> PSU Fan:        0 RPM  (min =    0 RPM, div = 128)
> N/B Temp:     +41.0°C  (high = +60.0°C, hyst = +55.0°C)  sensor = thermistor
> CPU Temp:     +37.5°C  (high = +60.0°C, hyst = +55.0°C)  sensor = thermistor
>
>
> Uncommenting and commenting the relevant lines for +5V monitoring, I get:
>
> $ sensors
> w83627dhg-isa-0290
> Adapter: ISA adapter
> Vcore:        +1.11 V  (min =  +1.07 V, max =  +1.18 V)
> AVcc:         +3.30 V  (min =  +2.98 V, max =  +3.63 V)
> +3.3V:        +3.30 V  (min =  +2.98 V, max =  +3.63 V)
> +5V:          +4.97 V  (min =  +6.12 V, max =  +6.12 V)  ALARM
> Vram:         +1.90 V  (min =  +1.80 V, max =  +1.90 V)
> 3Vsb:         +3.50 V  (min =  +2.98 V, max =  +3.63 V)
> Vbat:         +3.33 V  (min =  +2.70 V, max =  +3.30 V)  ALARM
> CHA Fan:        0 RPM  (min =    0 RPM, div = 128)
> CPU Fan:     1654 RPM  (min =  902 RPM, div = 8)
> PSU Fan:        0 RPM  (min =    0 RPM, div = 128)
> N/B Temp:     +41.0°C  (high = +60.0°C, hyst = +55.0°C)  sensor = thermistor
> CPU Temp:     +37.5°C  (high = +60.0°C, hyst = +55.0°C)  sensor = thermistor
> intrusion0:  ALARM
>
>
> To corroborate this behavior, I dumped the monitoring data in Windows using hwmonitor v1.24
>
> CPUID HWMonitor Report
> -------------------------------------------------------------------------
>
> Binaries
> -------------------------------------------------------------------------
>
> HWMonitor version    1.2.4.0
>
> Monitoring
> -------------------------------------------------------------------------
>
> Mainboard Model        G41C-GS (0x000001B6 - 0x004E5333)
>
> LPCIO
> -------------------------------------------------------------------------
>
> LPCIO Vendor        Winbond
> LPCIO Model        W83627DHG-P
> LPCIO Vendor ID        0x5CA3
> LPCIO Chip ID        0xB0
> LPCIO Revision ID    0x73
> Config Mode I/O address    0x2E
> Config Mode LDN        0xB
> Config Mode registers
>          00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
>      00    FF FF FF FF FF FF FF 0B FF FF FF FF FF FF FF FF
>      10    FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
>      20    B0 73 FF 00 44 00 00 FF 70 00 00 00 D2 21 00 FF
>      30    01 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
>      40    FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
>      50    FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
>      60    02 90 FF FF FF FF FF FF FF FF FF FF FF FF FF FF
>      70    00 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
> Register space        LPC, base address = 0x0290
>
>
> Hardware Monitors
> -------------------------------------------------------------------------
>
> Hardware monitor    Winbond W83627DHG
>      Voltage 0    1.11 Volts [0x8B] (CPU VCORE)
>      Voltage 1    0.69 Volts [0x56] (VIN1)
>      Voltage 2    3.30 Volts [0xCE] (+3.3V)
>      Voltage 3    4.97 Volts [0xCF] (+5V)
>      Voltage 4    11.54 Volts [0xCF] (+12V)
>      Voltage 5    1.69 Volts [0xD3] (VIN5)
>      Voltage 6    1.90 Volts [0xED] (VIN6)
>      Temperature 0    40°C (104°F) [0x28] (SYSTIN)
>      Temperature 1    39°C (101°F) [0x4D] (CPUTIN)
>      Temperature 2    46°C (113°F) [0x5B] (AUXTIN)
>      Fan 1        2250 RPM [0x4B] (CPUFANIN0)
> Hardware registers
> Register space        LPC, base address = 0x0290
> bank 0
>          00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
>      00    04 FF 04 B3 11 00 37 20 01 B3 01 FF 3C 3C 0A 0A
>      10    04 FF 10 00 00 01 01 3C 43 07 00 00 2D FF FF DA
>      20    8B 56 CE CF CF D3 ED 28 FF 4B FF DA 00 B4 72 E3
>      30    BA E3 BA EA 50 2B 0B EF D8 37 32 FF BB FF 05 FF
>      40    03 02 14 FF FF 00 3F F5 2D 00 00 C4 90 95 00 A3
>      50    FF FF 00 FF FF FF 00 80 C1 7F FF FF 19 A0 00 05
>      60    04 7F 40 00 01 01 3C FF 01 FF 01 FF FF FF FF 00
>      70    00 00 00 00 00 0E 7F 7F 7F 7F 7F 7F 00 28 FF FF
>      80    04 FF 04 B3 11 00 37 20 01 B3 01 FF 3C 3C 0A 0A
>      90    04 FF 10 00 00 01 01 3C 43 07 00 00 2D FF FF DA
>      A0    8B 56 CE CF CF D3 ED 28 FF 4B FF DA 00 B4 72 E3
>      B0    BA E3 BA EA 50 2B 0B EF D8 37 32 FF BB FF 05 FF
>      C0    03 00 10 FF FF 00 3F F5 2D 00 00 C4 90 95 00 A3
>      D0    FF FF 00 FF FF FF 00 80 C1 7F FF FF 19 A0 00 05
>      E0    04 7F 40 00 01 01 3C FF 01 FF 01 FF FF FF FF 00
>      F0    00 00 00 00 00 0E 7F 7F 7F 7F 7F 7F 00 28 FF FF
> bank 1
>      50    26 80 00 32 00 37 01 20 00 00 00 00 00 00 0E FF
> bank 2
>      50    2D 80 00 4B 00 50 1E 02 FF FF FF FF FF FF FF FF
> bank 3
>      50    06 07 07 00 04 02 02 01 06 00 00 00 7C 00 00 00
> bank 4
>      50    3A 13 FF 00 00 00 00 08 2A 02 14 AA 09 60 20 7F
>
>
>
> As you can see from above, +5V and +12V share the same address (0xCF).
>

That is not the same address, it is the same raw value.
The voltage registers are at address 0x20 .. 0x26 in above table.

Guenter


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

Re: [lm-sensors] W83627DHG-P sensor shows a single voltage monitor for +5V and +12V on in4?

[ianp]

> On Wednesday, February 19, 2014 10:00 AM, Guenter Roeck <linux@roeck-us.net> wrote:

> That is not the same address, it is the same raw value.
> The voltage registers are at address 0x20 .. 0x26 in above table.
> 

Hmmm, I must have been looking at it the wrong way then. So if it's the 
raw value that is the same for both monitors, can I trust that the +5V 
and +12V values are accurate?

Lastly, how can you separately show +5V and +12V in lm-sensors if both share a sinlge monitor on in4?


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

Re: [lm-sensors] W83627DHG-P sensor shows a single voltage monitor for +5V and +12V on in4?

[Guenter Roeck]

On 02/18/2014 06:27 PM, ianp wrote:
>> On Wednesday, February 19, 2014 10:00 AM, Guenter Roeck <linux@roeck-us.net> wrote:
>
Please don't drop the mailing liost from your replies.

>> That is not the same address, it is the same raw value.
>> The voltage registers are at address 0x20 .. 0x26 in above table.
>>
>
> Hmmm, I must have been looking at it the wrong way then. So if it's the raw value that is the same for both monitors, can I trust that the +5V and +12V values are accurate?
>
Ultimately you can only trust it to the point you trust the board vendor.
The chip reports what it gets on its input pins, but the board vendor
determines what is connected to those pins.

> Lastly, how can you separately show +5V and +12V in lm-sensors if both share a sinlge monitor on in4?
>

They don't. hwmonitor in Windows gives you the correct mapping for your board.

     Voltage 0    1.11 Volts [0x8B] (CPU VCORE)
     Voltage 1    0.69 Volts [0x56] (VIN1)
     Voltage 2    3.30 Volts [0xCE] (+3.3V)
     Voltage 3    4.97 Volts [0xCF] (+5V)
     Voltage 4    11.54 Volts [0xCF] (+12V)
     Voltage 5    1.69 Volts [0xD3] (VIN5)
     Voltage 6    1.90 Volts [0xED] (VIN6)

where Voltage X maps to inX.

Guenter


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

Re: [lm-sensors] W83627DHG-P sensor shows a single voltage monitor for +5V and +12V on in4?

[ianp]

> On Wednesday, February 19, 2014 10:55 AM, Guenter Roeck <linux@roeck-us.net> wrote:

> 
> Please don't drop the mailing liost from your replies.
>

Sorry about that.

> They don't. hwmonitor in Windows gives you the correct mapping for your 
> board.
> 
>      Voltage 0    1.11 Volts [0x8B] (CPU VCORE)
>      Voltage 1    0.69 Volts [0x56] (VIN1)
>      Voltage 2    3.30 Volts [0xCE] (+3.3V)
>      Voltage 3    4.97 Volts [0xCF] (+5V)
>      Voltage 4    11.54 Volts [0xCF] (+12V)
>      Voltage 5    1.69 Volts [0xD3] (VIN5)
>      Voltage 6    1.90 Volts [0xED] (VIN6)
> 
> where Voltage X maps to inX.
> 
> 
> Guenter
>

I though about it too at first, that Voltage X corresponds to inX in lm-sensors. The problem is, if you look at the default configuration lm-sensors provide at /etc/sensors3.conf:

chip "w83627ehf-*" "w83627dhg-*" "w83667hg-*" "nct6775-*" "nct6776-*"

    label in0 "Vcore"
    label in2 "AVCC"
    label in3 "+3.3V"
    label in7 "3VSB"
    label in8 "Vbat"

    set in2_min  3.3 * 0.90
    set in2_max  3.3 * 1.10
    set in3_min  3.3 * 0.90
    set in3_max  3.3 * 1.10
    set in7_min  3.3 * 0.90
    set in7_max  3.3 * 1.10
    set in8_min  3.0 * 0.90
    set in8_max  3.0 * 1.10

You can see that in3 is "+3.3V". Of course I tried modifying in3 in my configuration as follows:

label in3 "+5V"
set in3_min 5 * 0.95
set in3_max 5 * 1.05
compute  in4  @*((20/10)+1), @/((20/10)+1)

And here's the result:

# sensors -s
# sensors
w83627dhg-isa-0290
Adapter: ISA adapter
Vcore:        +1.11 V  (min =  +1.07 V, max =  +1.18 V)
AVcc:         +3.30 V  (min =  +2.98 V, max =  +3.63 V)
+5V:          +9.89 V  (min =  +2.98 V, max =  +3.65 V)  ALARM
+12V:        +11.59 V  (min = +11.42 V, max = +12.60 V)
Vram:         +1.90 V  (min =  +1.80 V, max =  +1.90 V)
3Vsb:         +3.50 V  (min =  +2.98 V, max =  +3.63 V)
Vbat:         +3.34 V  (min =  +2.70 V, max =  +3.30 V)  ALARM
CHA Fan:        0 RPM  (min =    0 RPM, div = 128)
CPU Fan:     1854 RPM  (min =  902 RPM, div = 8)
PSU Fan:        0 RPM  (min =    0 RPM, div = 128)
N/B Temp:     +42.0°C  (high = +60.0°C, hyst = +55.0°C)  sensor = thermistor
CPU Temp:     +38.5°C  (high = +60.0°C, hyst = +55.0°C)  sensor = thermistor

As you can see:

   +5V:          +9.89 V  (min =  +2.98 V, max =  +3.65 V)  ALARM

doesn't look right, and even the min and max values does not reflect the ones I set. Moreover, it looks as though in3 is really "+3.3V" in lm-sensors.

But if I modify in4 in my configuration as follows:

##### in4 as +5V monitor

label in4 "+5V"
set in4_min 5 * 0.95
set in4_max 5 * 1.05
compute  in4  @*((20/10)+1), @/((20/10)+1)

# sensors -s
# sensors
w83627dhg-isa-0290
Adapter: ISA adapter
Vcore:        +1.11 V  (min =  +1.07 V, max =  +1.18 V)
AVcc:         +3.30 V  (min =  +2.98 V, max =  +3.63 V)
+3.3V:        +3.30 V  (min =  +2.98 V, max =  +3.63 V)
+5V:          +4.97 V  (min =  +4.75 V, max =  +5.26 V)
Vram:         +1.90 V  (min =  +1.80 V, max =  +1.90 V)
3Vsb:         +3.50 V  (min =  +2.98 V, max =  +3.63 V)
Vbat:         +3.33 V  (min =  +2.70 V, max =  +3.30 V)  ALARM
CHA Fan:        0 RPM  (min =    0 RPM, div = 128)
CPU Fan:     1654 RPM  (min =  902 RPM, div = 8)
PSU Fan:        0 RPM  (min =    0 RPM, div = 128)
N/B Temp:     +41.0°C  (high = +60.0°C, hyst = +55.0°C)  sensor = thermistor
CPU Temp:     +37.5°C  (high = +60.0°C, hyst = +55.0°C)  sensor = thermistor
intrusion0:  ALARM

##### in4 as +12V monitor

label in4 "+12V"
set in4_min 12 * 0.95
set in4_max 12 * 1.05
compute  in4  @*((60/10)+1), @/((60/10)+1)

# sensors -s
# sensors
w83627dhg-isa-0290
Adapter: ISA adapter
Vcore:        +1.11 V  (min =  +1.07 V, max =  +1.18 V)
AVcc:         +3.30 V  (min =  +2.98 V, max =  +3.63 V)
+3.3V:        +3.30 V  (min =  +2.98 V, max =  +3.63 V)
+12V:        +11.59 V  (min = +11.42 V, max = +12.60 V)
Vram:         +1.90 V  (min =  +1.80 V, max =  +1.90 V)
3Vsb:         +3.50 V  (min =  +2.98 V, max =  +3.63 V)
Vbat:         +3.34 V  (min =  +2.70 V, max =  +3.30 V)  ALARM
CHA Fan:        0 RPM  (min =    0 RPM, div = 128)
CPU Fan:     1854 RPM  (min =  902 RPM, div = 8)
PSU Fan:        0 RPM  (min =    0 RPM, div = 128)
N/B Temp:     +42.0°C  (high = +60.0°C, hyst = +55.0°C)  sensor = thermistor
CPU Temp:     +38.5°C  (high = +60.0°C, hyst = +55.0°C)  sensor = thermistor
intrusion0:  ALARM

As you can see from above, I was able to successfully modify in4, and set min and max values for both +5V and +12V and showing the values as expected.

So what is the reason for this behavior?


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

Re: [lm-sensors] W83627DHG-P sensor shows a single voltage monitor for +5V and +12V on in4?

[ianp]

Minor correction:

> You can see that in3 is "+3.3V". Of course I tried modifying in3 in my 
> configuration as follows:
> 
> label in3 "+5V"
> set in3_min 5 * 0.95
> set in3_max 5 * 1.05
> compute  in3  @*((20/10)+1), @/((20/10)+1) #### was in4

Could this perhaps be a bug in the w83627ehf kernel module?


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

Re: [lm-sensors] W83627DHG-P sensor shows a single voltage monitor for +5V and +12V on in4?

[Guenter Roeck]

On 02/18/2014 07:18 PM, ianp wrote:
>> On Wednesday, February 19, 2014 10:55 AM, Guenter Roeck <linux@roeck-us.net> wrote:
>
>>
>> Please don't drop the mailing liost from your replies.
>>
>
> Sorry about that.
>
>> They don't. hwmonitor in Windows gives you the correct mapping for your
>> board.
>>
>>       Voltage 0    1.11 Volts [0x8B] (CPU VCORE)
>>       Voltage 1    0.69 Volts [0x56] (VIN1)
>>       Voltage 2    3.30 Volts [0xCE] (+3.3V)
>>       Voltage 3    4.97 Volts [0xCF] (+5V)
>>       Voltage 4    11.54 Volts [0xCF] (+12V)
>>       Voltage 5    1.69 Volts [0xD3] (VIN5)
>>       Voltage 6    1.90 Volts [0xED] (VIN6)
>>
>> where Voltage X maps to inX.
>>
>>
>> Guenter
>>
>
> I though about it too at first, that Voltage X corresponds to inX in lm-sensors. The problem is, if you look at the default configuration lm-sensors provide at /etc/sensors3.conf:
>
> chip "w83627ehf-*" "w83627dhg-*" "w83667hg-*" "nct6775-*" "nct6776-*"
>
>      label in0 "Vcore"
>      label in2 "AVCC"
>      label in3 "+3.3V"
>      label in7 "3VSB"
>      label in8 "Vbat"
>
>      set in2_min  3.3 * 0.90
>      set in2_max  3.3 * 1.10
>      set in3_min  3.3 * 0.90
>      set in3_max  3.3 * 1.10
>      set in7_min  3.3 * 0.90
>      set in7_max  3.3 * 1.10
>      set in8_min  3.0 * 0.90
>      set in8_max  3.0 * 1.10
>
> You can see that in3 is "+3.3V". Of course I tried modifying in3 in my configuration as follows:
>
That is just a generic description for settings which are
often seen for those SuperIO chips. That doesn't mean they
apply in any way to your board.

> label in3 "+5V"
> set in3_min 5 * 0.95
> set in3_max 5 * 1.05
> compute  in4  @*((20/10)+1), @/((20/10)+1)
>

You'll need the correct compute statement for in3.
You are labeling in3 as 5V and then provide a compute
statement for in4.

Where is the compute statement for in3 ?

> And here's the result:
>
> # sensors -s
> # sensors
> w83627dhg-isa-0290
> Adapter: ISA adapter
> Vcore:        +1.11 V  (min =  +1.07 V, max =  +1.18 V)
> AVcc:         +3.30 V  (min =  +2.98 V, max =  +3.63 V)
> +5V:          +9.89 V  (min =  +2.98 V, max =  +3.65 V)  ALARM
> +12V:        +11.59 V  (min = +11.42 V, max = +12.60 V)
> Vram:         +1.90 V  (min =  +1.80 V, max =  +1.90 V)
> 3Vsb:         +3.50 V  (min =  +2.98 V, max =  +3.63 V)
> Vbat:         +3.34 V  (min =  +2.70 V, max =  +3.30 V)  ALARM
> CHA Fan:        0 RPM  (min =    0 RPM, div = 128)
> CPU Fan:     1854 RPM  (min =  902 RPM, div = 8)
> PSU Fan:        0 RPM  (min =    0 RPM, div = 128)
> N/B Temp:     +42.0°C  (high = +60.0°C, hyst = +55.0°C)  sensor = thermistor
> CPU Temp:     +38.5°C  (high = +60.0°C, hyst = +55.0°C)  sensor = thermistor
>
> As you can see:
>
>     +5V:          +9.89 V  (min =  +2.98 V, max =  +3.65 V)  ALARM
>
> doesn't look right, and even the min and max values does not reflect the ones I set. Moreover, it looks as though in3 is really "+3.3V" in lm-sensors.
>
> But if I modify in4 in my configuration as follows:
>
> ##### in4 as +5V monitor
>
> label in4 "+5V"
> set in4_min 5 * 0.95
> set in4_max 5 * 1.05
> compute  in4  @*((20/10)+1), @/((20/10)+1)
>
> # sensors -s
> # sensors
> w83627dhg-isa-0290
> Adapter: ISA adapter
> Vcore:        +1.11 V  (min =  +1.07 V, max =  +1.18 V)
> AVcc:         +3.30 V  (min =  +2.98 V, max =  +3.63 V)
> +3.3V:        +3.30 V  (min =  +2.98 V, max =  +3.63 V)
> +5V:          +4.97 V  (min =  +4.75 V, max =  +5.26 V)
> Vram:         +1.90 V  (min =  +1.80 V, max =  +1.90 V)
> 3Vsb:         +3.50 V  (min =  +2.98 V, max =  +3.63 V)
> Vbat:         +3.33 V  (min =  +2.70 V, max =  +3.30 V)  ALARM
> CHA Fan:        0 RPM  (min =    0 RPM, div = 128)
> CPU Fan:     1654 RPM  (min =  902 RPM, div = 8)
> PSU Fan:        0 RPM  (min =    0 RPM, div = 128)
> N/B Temp:     +41.0°C  (high = +60.0°C, hyst = +55.0°C)  sensor = thermistor
> CPU Temp:     +37.5°C  (high = +60.0°C, hyst = +55.0°C)  sensor = thermistor
> intrusion0:  ALARM
>
> ##### in4 as +12V monitor
>
> label in4 "+12V"
> set in4_min 12 * 0.95
> set in4_max 12 * 1.05
> compute  in4  @*((60/10)+1), @/((60/10)+1)
>
> # sensors -s
> # sensors
> w83627dhg-isa-0290
> Adapter: ISA adapter
> Vcore:        +1.11 V  (min =  +1.07 V, max =  +1.18 V)
> AVcc:         +3.30 V  (min =  +2.98 V, max =  +3.63 V)
> +3.3V:        +3.30 V  (min =  +2.98 V, max =  +3.63 V)
> +12V:        +11.59 V  (min = +11.42 V, max = +12.60 V)
> Vram:         +1.90 V  (min =  +1.80 V, max =  +1.90 V)
> 3Vsb:         +3.50 V  (min =  +2.98 V, max =  +3.63 V)
> Vbat:         +3.34 V  (min =  +2.70 V, max =  +3.30 V)  ALARM
> CHA Fan:        0 RPM  (min =    0 RPM, div = 128)
> CPU Fan:     1854 RPM  (min =  902 RPM, div = 8)
> PSU Fan:        0 RPM  (min =    0 RPM, div = 128)
> N/B Temp:     +42.0°C  (high = +60.0°C, hyst = +55.0°C)  sensor = thermistor
> CPU Temp:     +38.5°C  (high = +60.0°C, hyst = +55.0°C)  sensor = thermistor
> intrusion0:  ALARM
>
> As you can see from above, I was able to successfully modify in4, and set min and max values for both +5V and +12V and showing the values as expected.
>
> So what is the reason for this behavior?
>
PDL, or Pure Damned Luck. You are using the fact that both in3 and in4
happen to report the same physical value to your favor. That doesn't
make it correct.

Guenter


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

Re: [lm-sensors] W83627DHG-P sensor shows a single voltage monitor for +5V and +12V on in4?

[Guenter Roeck]

On 02/18/2014 07:31 PM, ianp wrote:
> Minor correction:
>
>> You can see that in3 is "+3.3V". Of course I tried modifying in3 in my
>> configuration as follows:
>>
>> label in3 "+5V"
>> set in3_min 5 * 0.95
>> set in3_max 5 * 1.05
>> compute  in3  @*((20/10)+1), @/((20/10)+1) #### was in4
>
> Could this perhaps be a bug in the w83627ehf kernel module?
>
>

Theoretically yes, but I am quite sure that it is PBKC
(Problem Between Keyboard And Chair ;-).

Try sensors -u for raw values. That should help us determine
the correct compute statements.

As far as I can see from the driver, in3 has an automatic
built-in scaling factor of 2 for this chip, meaning it already
reports twice the voltage you would expect for other inputs,
and thus should not need scaling in the first place.
In other words, sensors -u should already report
the correct value for in3.

Guenter


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

Re: [lm-sensors] W83627DHG-P sensor shows a single voltage monitor for +5V and +12V on in4?

[ianp]

> On Wednesday, February 19, 2014 12:21 PM, Guenter Roeck <linux@roeck-us.net> wrote:

>
> Theoretically yes, but I am quite sure that it is PBKC
> (Problem Between Keyboard And Chair ;-).
> 

I do know about PEBKAC, and it would be unfortunate if that were to be the case.

Also,
 I am not using the fact, whether directly or indirectly stated, that 
"both in3 and in4 happen to report the same physical value," because 
they do not report the same physical value. Forgive me if I wasn't clear
 with my words, because English is not my native language.

For
 the record, what I have been stating since the start is that, 
apparently, I can scale the +5V and +12V monitors _only_ in in4. And 
they are not out of pure luck, because apart from researching the 
correct formula to use for the compute statements and a number of 
trial-and-error runs, the +5V and +12V values that I scaled from my 
formula just doesn't _happen_ to be correct -- they are corroborated as 
the same values that hwmonitor "sees" in Windows. I cannot scale +5V nor
 +12V from all the other inputs the kernel module provides, only in in4.

> Try sensors -u for raw values. That should help us determine
> the correct compute statements.
> 
> As far as I can see from the driver, in3 has an automatic
> built-in scaling factor of 2 for this chip, meaning it already
> reports twice the voltage you would expect for other inputs,
> and thus should not need scaling in the first place.
> In other words, sensors -u should already report
> the correct value for in3.
> 
> Guenter
>

I will defer to your understanding, because you know the code much better than I could hopefully ever understand.

For
 the sake of simplicity, I have disabled my custom configuration and 
deferred to the default values provided by lm-sensors, and here are the 
results:

$ sensors
w83627dhg-isa-0290
Adapter: ISA adapter
Vcore:        +1.11 V  (min =  +1.07 V, max =  +1.18 V)
in1:          +0.98 V  (min =  +0.91 V, max =  +1.44 V)
AVCC:         +3.30 V  (min =  +2.98 V, max =  +3.63 V)
+3.3V:        +3.30 V  (min =  +2.98 V, max =  +3.63 V)
in4:          +1.66 V  (min =  +1.63 V, max =  +1.80 V)
in5:          +1.69 V  (min =  +0.09 V, max =  +0.34 V)  ALARM
in6:          +1.90 V  (min =  +1.80 V, max =  +1.90 V)
3VSB:         +3.50 V  (min =  +2.98 V, max =  +3.63 V)
Vbat:         +3.34 V  (min =  +2.70 V, max =  +3.30 V)  ALARM
fan1:           0 RPM  (min =    0 RPM, div = 128)
fan2:        1854 RPM  (min =  902 RPM, div = 8)
fan3:           0 RPM  (min =    0 RPM, div = 128)
fan4:           0 RPM  (min = 2109 RPM, div = 128)  ALARM
fan5:           0 RPM  (min =  811 RPM, div = 128)  ALARM
temp1:        +41.0°C  (high = +60.0°C, hyst = +55.0°C)  sensor = thermistor
temp2:        +38.5°C  (high = +60.0°C, hyst = +55.0°C)  sensor = thermistor
temp3:        +45.5°C  (high = +80.0°C, hyst = +75.0°C)  sensor = thermistor
cpu0_vid:    +0.000 V
intrusion0:  ALARM

$ sensors -u
w83627dhg-isa-0290
Adapter: ISA adapter
Vcore:
  in0_input: 1.112
  in0_min: 1.072
  in0_max: 1.184
  in0_alarm: 0.000
in1:
  in1_input: 0.992
  in1_min: 0.912
  in1_max: 1.440
  in1_alarm: 0.000
AVCC:
  in2_input: 3.296
  in2_min: 2.976
  in2_max: 3.632
  in2_alarm: 0.000
+3.3V:
  in3_input: 3.296
  in3_min: 2.976
  in3_max: 3.632
  in3_alarm: 0.000
in4:
  in4_input: 1.656
  in4_min: 1.632
  in4_max: 1.800
  in4_alarm: 0.000 
  in5_input: 1.688
  in5_min: 0.088
  in5_max: 0.344
  in5_alarm: 1.000
in6:
  in6_input: 1.896
  in6_min: 1.800
  in6_max: 1.904
  in6_alarm: 0.000
3VSB:
  in7_input: 3.504
  in7_min: 2.976
  in7_max: 3.632
  in7_alarm: 0.000
Vbat:
  in8_input: 3.344
  in8_min: 2.704
  in8_max: 3.296
  in8_alarm: 1.000
fan1:
  fan1_input: 0.000
  fan1_min: 0.000
  fan1_alarm: 0.000
  fan1_div: 128.000
fan2:
  fan2_input: 2008.000
  fan2_min: 902.000
  fan2_alarm: 0.000
  fan2_div: 8.000
fan3:
  fan3_input: 0.000
  fan3_min: 0.000
  fan3_alarm: 0.000
  fan3_div: 128.000
fan4:
  fan4_input: 0.000
  fan4_min: 2109.000
  fan4_alarm: 1.000
  fan4_div: 128.000
fan5:
  fan5_input: 0.000
  fan5_min: 811.000
  fan5_alarm: 1.000
  fan5_div: 128.000
temp1:
  temp1_input: 41.000
  temp1_max: 60.000
  temp1_max_hyst: 55.000
  temp1_alarm: 0.000
  temp1_type: 4.000
  temp1_offset: 0.000
temp2:
  temp2_input: 39.000
  temp2_max: 60.000
  temp2_max_hyst: 55.000
  temp2_alarm: 0.000
  temp2_type: 4.000
  temp2_offset: 0.000
temp3:
  temp3_input: 46.000
  temp3_max: 80.000
  temp3_max_hyst: 75.000
  temp3_alarm: 0.000
  temp3_type: 4.000
  temp3_offset: 0.000
cpu0_vid:
  cpu0_vid: 0.000
intrusion0:
  intrusion0_alarm: 1.000

I appreciate your inputs regarding this inquiry and please advise on how to proceed from here.

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

Re: [lm-sensors] W83627DHG-P sensor shows a single voltage monitor for +5V and +12V on in4?

[Guenter Roeck]

On 02/18/2014 09:38 PM, ianp wrote:
>> On Wednesday, February 19, 2014 12:21 PM, Guenter Roeck <linux@roeck-us.net> wrote:
>
>>
>> Theoretically yes, but I am quite sure that it is PBKC
>> (Problem Between Keyboard And Chair ;-).
>>
>
> I do know about PEBKAC, and it would be unfortunate if that were to be the case.
>
> Also,
>   I am not using the fact, whether directly or indirectly stated, that
> "both in3 and in4 happen to report the same physical value," because
> they do not report the same physical value. Forgive me if I wasn't clear
>   with my words, because English is not my native language.
>
Actually, they do. Register values are 0xcf for both (bank 0,
registers 0x23 and 0x24).

> For
>   the record, what I have been stating since the start is that,
> apparently, I can scale the +5V and +12V monitors _only_ in in4. And
> they are not out of pure luck, because apart from researching the
> correct formula to use for the compute statements and a number of
> trial-and-error runs, the +5V and +12V values that I scaled from my
> formula just doesn't _happen_ to be correct -- they are corroborated as
> the same values that hwmonitor "sees" in Windows. I cannot scale +5V nor
>   +12V from all the other inputs the kernel module provides, only in in4.
>
Not sure if I I can follow that logic; see below.

>> Try sensors -u for raw values. That should help us determine
>> the correct compute statements.
>>
>> As far as I can see from the driver, in3 has an automatic
>> built-in scaling factor of 2 for this chip, meaning it already
>> reports twice the voltage you would expect for other inputs,
>> and thus should not need scaling in the first place.
>> In other words, sensors -u should already report
>> the correct value for in3.
>>
>> Guenter
>>
>
> I will defer to your understanding, because you know the code much better than I could hopefully ever understand.
>
> For
>   the sake of simplicity, I have disabled my custom configuration and
> deferred to the default values provided by lm-sensors, and here are the
> results:
>
> $ sensors
> w83627dhg-isa-0290
> Adapter: ISA adapter
> Vcore:        +1.11 V  (min =  +1.07 V, max =  +1.18 V)
> in1:          +0.98 V  (min =  +0.91 V, max =  +1.44 V)
> AVCC:         +3.30 V  (min =  +2.98 V, max =  +3.63 V)
> +3.3V:        +3.30 V  (min =  +2.98 V, max =  +3.63 V)
> in4:          +1.66 V  (min =  +1.63 V, max =  +1.80 V)
> in5:          +1.69 V  (min =  +0.09 V, max =  +0.34 V)  ALARM
> in6:          +1.90 V  (min =  +1.80 V, max =  +1.90 V)
> 3VSB:         +3.50 V  (min =  +2.98 V, max =  +3.63 V)
> Vbat:         +3.34 V  (min =  +2.70 V, max =  +3.30 V)  ALARM
> fan1:           0 RPM  (min =    0 RPM, div = 128)
> fan2:        1854 RPM  (min =  902 RPM, div = 8)
> fan3:           0 RPM  (min =    0 RPM, div = 128)
> fan4:           0 RPM  (min = 2109 RPM, div = 128)  ALARM
> fan5:           0 RPM  (min =  811 RPM, div = 128)  ALARM
> temp1:        +41.0°C  (high = +60.0°C, hyst = +55.0°C)  sensor = thermistor
> temp2:        +38.5°C  (high = +60.0°C, hyst = +55.0°C)  sensor = thermistor
> temp3:        +45.5°C  (high = +80.0°C, hyst = +75.0°C)  sensor = thermistor
> cpu0_vid:    +0.000 V
> intrusion0:  ALARM
>
> $ sensors -u
> w83627dhg-isa-0290
> Adapter: ISA adapter
> Vcore:
>    in0_input: 1.112
>    in0_min: 1.072
>    in0_max: 1.184
>    in0_alarm: 0.000
> in1:
>    in1_input: 0.992
>    in1_min: 0.912
>    in1_max: 1.440
>    in1_alarm: 0.000
> AVCC:
>    in2_input: 3.296
>    in2_min: 2.976
>    in2_max: 3.632
>    in2_alarm: 0.000
> +3.3V:
>    in3_input: 3.296
>    in3_min: 2.976
>    in3_max: 3.632
>    in3_alarm: 0.000

If we assume that hwmonitor is correct, this needs
to scale up 50%, which would make the value
3.296 * 1.5 = 4.944V.

The raw value reported by the driver in the hwmonitor dump
is 0xcf = 207, which is multiplied by the driver with 16,
resulting in 3.312V as originally seen, or scaled to 4.968V,
which is exactly the value that was reported by hwmonitor.

So your compute statement would be something like

compute  in3  @*(15/10), @/(15/10)

> in4:
>    in4_input: 1.656
>    in4_min: 1.632
>    in4_max: 1.800
>    in4_alarm: 0.000
>    in5_input: 1.688
>    in5_min: 0.088
>    in5_max: 0.344
>    in5_alarm: 1.000

The raw value reported by the driver is 0xcf = 207.
This is multiplied by the driver with 8, resulting
in a reported voltage of 1.656V. A scaling factor
of 7 (as you have) gets you to 11.592V, which
matches the voltage reported by hwmonitor quite closely.

compute in4 @*7, @/7

might be a bit simpler, though.

Hope this helps,
Guenter


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

Re: [lm-sensors] W83627DHG-P sensor shows a single voltage monitor for +5V and +12V on in4?

[ianp]

> On Wednesday, February 19, 2014 2:16 PM, Guenter Roeck <linux@roeck-us.net> wrote:
>
> Actually, they do. Register values are 0xcf for both (bank 0,
> registers 0x23 and 0x24).
>

Oh, you meant the raw dump physical value (0xCF). I was pertaining to the values reported back by sensors, which was an incorrect understanding on my part.

>> +3.3V:
>>     in3_input: 3.296
>>     in3_min: 2.976
>>     in3_max: 3.632
>>     in3_alarm: 0.000
>
> If we assume that hwmonitor is correct, this needs
> to scale up 50%, which would make the value
> 3.296 * 1.5 = 4.944V.
>
> The raw value reported by the driver in the hwmonitor dump
> is 0xcf = 207, which is multiplied by the driver with 16,
> resulting in 3.312V as originally seen, or scaled to 4.968V,
> which is exactly the value that was reported by hwmonitor.
>
> So your compute statement would be something like
>
> compute  in3  @*(15/10), @/(15/10)
>
>> in4:
>>     in4_input: 1.656
>>     in4_min: 1.632
>>     in4_max: 1.800
>>     in4_alarm: 0.000
>>     in5_input: 1.688
>>     in5_min: 0.088
>>     in5_max: 0.344
>>     in5_alarm: 1.000
>
> The raw value reported by the driver is 0xcf = 207.
> This is multiplied by the driver with 8, resulting
> in a reported voltage of 1.656V. A scaling factor
> of 7 (as you have) gets you to 11.592V, which
> matches the voltage reported by hwmonitor quite closely.
>
> compute in4 @*7, @/7
>
> might be a bit simpler, though.
>
> Hope this helps,
>
> Guenter
>

You sir have been very helpful, and I must admit that this is both the case of PEBKAC and PDL, but how could you blame me, an ordinary end user, for having only so limited an undesrtanding and resource at my disposal? ;-)

Committing your compute statements into my configuration:

$ sensors
Vcore:        +1.11 V  (min =  +1.07 V, max =  +1.18 V)
+3.3V:         +3.30 V  (min =  +2.98 V, max =  +3.63 V)
+5V:          +4.94 V  (min =  +2.98 V, max =  +3.62 V)  ALARM
+12V:        +11.59 V  (min = +11.42 V, max = +12.60 V)
Vram:         +1.90 V  (min =  +1.80 V, max =  +1.90 V)
3Vsb:         +3.50 V  (min =  +2.98 V, max =  +3.63 V)
Vbat:         +3.34 V  (min =  +2.70 V, max =  +3.30 V)  ALARM
CHA Fan:        0 RPM  (min =    0 RPM, div = 128)
CPU Fan:     2191 RPM  (min =  902 RPM, div = 8)
PSU Fan:        0 RPM  (min =    0 RPM, div = 128)
N/B Temp:     +43.0°C  (high = +60.0°C, hyst = +55.0°C)  sensor = thermistor
CPU Temp:     +40.0°C  (high = +60.0°C, hyst = +55.0°C)  sensor = thermistor
intrusion0:  ALARM

I will contribute my configuration into the http://lm-sensors.org/wiki/Configurations page for this board so that others may benefit as well.

There are still some observations I'd like to ask you about:

1. While +5V is now scaled from in3, if you will take notice the min and max values do not reflect the ones I have set in my configuration:

   set in3_min 5 * 0.95
   set in3_max 5 * 1.05

I do not believe that this is an expected behavior, so perhaps a bug then?

2. I have relied upon http://www.lm-sensors.org/wiki/VoltageLabelsAndScaling for scaling +5V and +12V values. But the way you derived the scaling factors from your explanation above, which I believe is much easier and faster than the one in the wiki that works on samples, does not seem to be covered there. How does one go about figuring out scaling factors like the way you did?

3. Regarding 3VSB, if this is the standby voltage, then shouldn't it be +5VSB? I don't think PSUs provide +3VSB, only +5VSB. So does this mean that the value needs to be scaled as well?

4. Same with VBAT, as I recall motherboard internal batteries are rated at +3V CR2032 coin-cell batteries.


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

Re: [lm-sensors] W83627DHG-P sensor shows a single voltage monitor for +5V and +12V on in4?

[Jean Delvare]

On Tue, 18 Feb 2014 20:11:40 -0800, Guenter Roeck wrote:
> On 02/18/2014 07:18 PM, ianp wrote:
> > I though about it too at first, that Voltage X corresponds to inX in lm-sensors. The problem is, if you look at the default configuration lm-sensors provide at /etc/sensors3.conf:
> >
> > chip "w83627ehf-*" "w83627dhg-*" "w83667hg-*" "nct6775-*" "nct6776-*"
> >
> >      label in0 "Vcore"
> >      label in2 "AVCC"
> >      label in3 "+3.3V"
> >      label in7 "3VSB"
> >      label in8 "Vbat"
> >
> >      set in2_min  3.3 * 0.90
> >      set in2_max  3.3 * 1.10
> >      set in3_min  3.3 * 0.90
> >      set in3_max  3.3 * 1.10
> >      set in7_min  3.3 * 0.90
> >      set in7_max  3.3 * 1.10
> >      set in8_min  3.0 * 0.90
> >      set in8_max  3.0 * 1.10
> >
> > You can see that in3 is "+3.3V". Of course I tried modifying in3 in my configuration as follows:
>
> That is just a generic description for settings which are
> often seen for those SuperIO chips. That doesn't mean they
> apply in any way to your board.

No, this isn't correct. We stopped with this long ago. Today the file
installed as /etc/sensors3.conf only contains statements which are
always correct. The comment at the top of the file says exactly that:

# This default configuration file only includes statements which do not
# differ from one mainboard to the next. Only label, compute and set
# statements for internal voltage and temperature sensors are included.

If you look at the W83627DHG-P datasheet, you'll see that in2, in3, in7
and in8 monitor the chips's own power sources (AVCC, 3VCC, 3VSB and
Vbat in this order.) The chip can monitor only 5 external voltages,
with Vcore always being in0 and in1, in4, in5 and in6 being the generic
inputs which can be used to monitor any other voltage.

So there's no way +5V is in3, sorry. +5V and +12V can only be amongst
in1, in4, in5 and in6. From there it's really only a matter of finding
the right mapping and scaling factors. Please follow my guide here to
get this right:

http://www.lm-sensors.org/wiki/VoltageLabelsAndScaling

Your chip's native voltage range is 2.04 V i.e. LSB = 8 mV.

-- 
Jean Delvare
Suse L3 Support
http://jdelvare.nerim.net/wishlist.html

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

Re: [lm-sensors] W83627DHG-P sensor shows a single voltage monitor for +5V and +12V on in4?

[ianp]

> On Wednesday, February 19, 2014 4:53 PM, Jean Delvare <jdelvare@suse.de> wrote:

> No, this isn't correct. We stopped with this long ago. Today the file
> installed as /etc/sensors3.conf only contains statements which are
> always correct. The comment at the top of the file says exactly that:
> 
> # This default configuration file only includes statements which do not
> # differ from one mainboard to the next. Only label, compute and set
> # statements for internal voltage and temperature sensors are included.
> 
> If you look at the W83627DHG-P datasheet, you'll see that in2, in3, in7
> and in8 monitor the chips's own power sources (AVCC, 3VCC, 3VSB and
> Vbat in this order.) The chip can monitor only 5 external voltages,
> with Vcore always being in0 and in1, in4, in5 and in6 being the generic
> inputs which can be used to monitor any other voltage.
> 
> So there's no way +5V is in3, sorry. +5V and +12V can only be amongst
> in1, in4, in5 and in6. From there it's really only a matter of finding
> the right mapping and scaling factors. Please follow my guide here to
> get this right:
> 
> http://www.lm-sensors.org/wiki/VoltageLabelsAndScaling
> 
> Your chip's native voltage range is 2.04 V i.e. LSB = 8 mV.
> 
> -- 
> Jean Delvare
> Suse L3 Support
> http://jdelvare.nerim.net/wishlist.html
>

And
 here I thought I could finalize my configuration for this board. 
Anyhow, keeping in mind that only one of in1, in4, in5, and in6 can be 
used for generic inputs, here's what I have done so far for +12V 
scaling, using the guide from 
http://www.lm-sensors.org/wiki/VoltageLabelsAndScaling.

I have removed my custom configuration at this point, so that I'm using the default configuration:

### unscaled sensors output:

# sensors -s
# sensors -u
w83627dhg-isa-0290
Adapter: ISA adapter
in1:
  in1_input: 0.984
  in1_min: 0.912
  in1_max: 1.440
  in1_alarm: 0.000
in4:
  in4_input: 1.656
  in4_min: 1.632
  in4_max: 1.800
  in4_alarm: 0.000
in5:
  in5_input: 1.688
  in5_min: 2.040
  in5_max: 2.040
  in5_alarm: 1.000
in6:
  in6_input: 1.896
  in6_min: 1.800
  in6_max: 1.904
  in6_alarm: 0.000

### computation:

+12V samples: 12.091 (screenshot from the manual), 12.460, 12.513 (these are the only two values I have observed in the bios)

12.460 - 12.091 = 0.369
12.513 - 12.460 = 0.053

From the above, it seems clear that 1 LSB of the ADC corresponds to 53 
mV after scaling. And I know that it corresponds to 8 mV before 
scaling. So I conclude that the scaling factor is 53/8. And I 
validate this conclusion as:

12.460 / (53/8) = 1.880754717

which
 is close enough to in6 (1.896). To test this out, I created a test 
configuration file (/etc/sensors.d/test.conf) as follows:

compute in6 @*(53/8), @/(53/8)
set in6_min 12 * 0.95
set in6_max 12 * 1.05

### scaled sensors output:

# sensors -s
# sensors -u
w83627dhg-isa-0290
Adapter: ISA adapter
Vcore:
  in0_input: 1.104
  in0_min: 1.072
  in0_max: 1.184
  in0_alarm: 0.000
in1:
  in1_input: 0.992
  in1_min: 0.912
  in1_max: 1.440
  in1_alarm: 0.000
in4:
  in4_input: 1.656
  in4_min: 1.632
  in4_max: 1.800
  in4_alarm: 0.000
in5:
  in5_input: 1.688
  in5_min: 2.040
  in5_max: 2.040
  in5_alarm: 1.000
in6:
  in6_input: 1.896
  in6_min: 1.800
  in6_max: 1.904
  in6_alarm: 0.000

Not only did in6 remained the same, but also the min and max values from my test configuration did not take effect.

Please advice on how to proceed from here.

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

Re: [lm-sensors] W83627DHG-P sensor shows a single voltage monitor for +5V and +12V on in4?

[ianp]

I'm really sorry for the noise, but I think I can finalize my configuration for this board and send my configuration file here for inclusion in the wiki.

Thank you Jean Delavare and Guenter Roeck for providing valuable inputs.


- ianp


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

Re: [lm-sensors] W83627DHG-P sensor shows a single voltage monitor for +5V and +12V on in4?

[Jean Delvare]

On Wed, 19 Feb 2014 03:47:50 -0800 (PST), ianp wrote:
> And
>  here I thought I could finalize my configuration for this board. 
> Anyhow, keeping in mind that only one of in1, in4, in5, and in6 can be 
> used for generic inputs, here's what I have done so far for +12V 
> scaling, using the guide from 
> http://www.lm-sensors.org/wiki/VoltageLabelsAndScaling.
> 
> I have removed my custom configuration at this point, so that I'm using the default configuration:
> 
> ### unscaled sensors output:
> 
> # sensors -s
> # sensors -u
> w83627dhg-isa-0290
> Adapter: ISA adapter
> in1:
>   in1_input: 0.984
>   in1_min: 0.912
>   in1_max: 1.440
>   in1_alarm: 0.000
> in4:
>   in4_input: 1.656
>   in4_min: 1.632
>   in4_max: 1.800
>   in4_alarm: 0.000
> in5:
>   in5_input: 1.688
>   in5_min: 2.040
>   in5_max: 2.040
>   in5_alarm: 1.000
> in6:
>   in6_input: 1.896
>   in6_min: 1.800
>   in6_max: 1.904
>   in6_alarm: 0.000
> 
> ### computation:
> 
> +12V samples: 12.091 (screenshot from the manual), 12.460, 12.513 (these are the only two values I have observed in the bios)
> 
> 12.460 - 12.091 = 0.369
> 12.513 - 12.460 = 0.053
> 
> From the above, it seems clear that 1 LSB of the ADC corresponds to 53 
> mV after scaling. And I know that it corresponds to 8 mV before 
> scaling. So I conclude that the scaling factor is 53/8. And I 
> validate this conclusion as:
> 
> 12.460 / (53/8) = 1.880754717
> 
> which
>  is close enough to in6 (1.896). To test this out, I created a test 
> configuration file (/etc/sensors.d/test.conf) as follows:
> 
> compute in6 @*(53/8), @/(53/8)

It turns out that a very frequent pair of scaling resistors is 10 Ohm
and 56 Ohm, which leads to:

compute in6 @*(1+56/10), @/(1+56/10)

This maps your raw reading (1.896) to exactly 12.513 which is one of
the values you saw in the BIOS, and also maps integer register values
to 12.091 and 12.460.

> set in6_min 12 * 0.95
> set in6_max 12 * 1.05
> 
> ### scaled sensors output:
> 
> # sensors -s
> # sensors -u
> w83627dhg-isa-0290
> Adapter: ISA adapter
> Vcore:
>   in0_input: 1.104
>   in0_min: 1.072
>   in0_max: 1.184
>   in0_alarm: 0.000
> in1:
>   in1_input: 0.992
>   in1_min: 0.912
>   in1_max: 1.440
>   in1_alarm: 0.000
> in4:
>   in4_input: 1.656
>   in4_min: 1.632
>   in4_max: 1.800
>   in4_alarm: 0.000
> in5:
>   in5_input: 1.688
>   in5_min: 2.040
>   in5_max: 2.040
>   in5_alarm: 1.000
> in6:
>   in6_input: 1.896
>   in6_min: 1.800
>   in6_max: 1.904
>   in6_alarm: 0.000
> 
> Not only did in6 remained the same, but also the min and max values from my test configuration did not take effect.
> 
> Please advice on how to proceed from here.

You must have changed the wrong file, or the wrong section in the right
file. It should work.

-- 
Jean Delvare
Suse L3 Support
http://jdelvare.nerim.net/wishlist.html

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

Re: [lm-sensors] W83627DHG-P sensor shows a single voltage monitor for +5V and +12V on in4?

[ianp]

> On Wednesday, February 19, 2014 9:10 PM, Jean Delvare <jdelvare@suse.de> wrote:

>
> It turns out that a very frequent pair of scaling resistors is 10 Ohm
> and 56 Ohm, which leads to:
> 
> compute in6 @*(1+56/10), @/(1+56/10)
> 
> This maps your raw reading (1.896) to exactly 12.513 which is one of
> the values you saw in the BIOS, and also maps integer register values
> to 12.091 and 12.460.
> 

Ah, I see. Thank you for that input. Now it maps exactly with the BIOS values that I have observed.

> You must have changed the wrong file, or the wrong section in the right
> file. It should work.
>

Yes, it works now.

I'm almost ready with my configuration. Now here's my +5V scaling computation:

+5V BIOS samples: 5.040, 5.064, 5.136

5.064 - 5.040 = 0.024
5.136 - 5.064 = 0.072

5.136 / (24/8) = 1.712

1.712 is close enough to in5 (1.688). So my compute statement is:

compute in5 @*3, @/3

Apparently, the scaling factor I use above maps exactly with the BIOS values I have seen. So if everything checks out and you concur with my computation, then I can send in my configuration.


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

Re: [lm-sensors] W83627DHG-P sensor shows a single voltage monitor for +5V and +12V on in4?

[Jean Delvare]

On Wed, 19 Feb 2014 05:52:54 -0800 (PST), ianp wrote:
> I'm almost ready with my configuration. Now here's my +5V scaling computation:
> 
> +5V BIOS samples: 5.040, 5.064, 5.136

And I've found 5.088 on the web (G41M-GS but hopefully it's the same):
http://www.3dnews.ru/582775/page-2.html

> 5.064 - 5.040 = 0.024
> 5.136 - 5.064 = 0.072

5.088 - 5.064 = 0.024
5.136 - 5.088 = 0.048
(just to confirm your findings)

> 5.136 / (24/8) = 1.712
> 
> 1.712 is close enough to in5 (1.688). So my compute statement is:

I'd even say that 5.064 / (24/8) = 1.688 is close enough to your in5 ;-)

> compute in5 @*3, @/3
> 
> Apparently, the scaling factor I use above maps exactly with the BIOS values I have seen. So if everything checks out and you concur with my computation, then I can send in my configuration.

Yes, I completely agree with your computations. Great job! Glad to see
my guide working in practice :-)

-- 
Jean Delvare
Suse L3 Support
http://jdelvare.nerim.net/wishlist.html

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

Re: [lm-sensors] W83627DHG-P sensor shows a single voltage monitor for +5V and +12V on in4?

[Guenter Roeck]

On 02/19/2014 06:14 AM, Jean Delvare wrote:
> On Wed, 19 Feb 2014 05:52:54 -0800 (PST), ianp wrote:
>> I'm almost ready with my configuration. Now here's my +5V scaling computation:
>>
>> +5V BIOS samples: 5.040, 5.064, 5.136
>
> And I've found 5.088 on the web (G41M-GS but hopefully it's the same):
> http://www.3dnews.ru/582775/page-2.html
>
>> 5.064 - 5.040 = 0.024
>> 5.136 - 5.064 = 0.072
>
> 5.088 - 5.064 = 0.024
> 5.136 - 5.088 = 0.048
> (just to confirm your findings)
>
>> 5.136 / (24/8) = 1.712
>>
>> 1.712 is close enough to in5 (1.688). So my compute statement is:
>
> I'd even say that 5.064 / (24/8) = 1.688 is close enough to your in5 ;-)
>
>> compute in5 @*3, @/3
>>
>> Apparently, the scaling factor I use above maps exactly with the BIOS values I have seen. So if everything checks out and you concur with my computation, then I can send in my configuration.
>
> Yes, I completely agree with your computations. Great job! Glad to see
> my guide working in practice :-)
>

... and sorry for my misleading advice earlier.

Guenter


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

Re: [lm-sensors] W83627DHG-P sensor shows a single voltage monitor for +5V and +12V on in4?

[ianp]

> On Wednesday, February 19, 2014 10:14 PM, Jean Delvare <jdelvare@suse.de> wrote:

>
> I'd even say that 5.064 / (24/8) = 1.688 is close enough to your in5 ;-)
> 

Now 5.064 is the perfect choice. ;-) 

> 
> Yes, I completely agree with your computations. Great job! Glad to see
> my guide working in practice :-)
> 

Indeed. Many thanks for your well-written guide.

If I may make some suggestions to further improve the guide:

* It wasn't obvious nor clear, at least to me, that one needs to arbitrarily choose, by means of trial-and-error, from the set of voltage samples the value that will produce the closest, if not exact, match to one of the unscaled sensor inputs when validating the scaling factor.

If you could specify that then I think it would really be a big help. When I first tried following your guide I didn't know this so that I was skeptical of the results I was getting and couldn't make a definitive map to one of the unscaled sensor inputs.

* It should be noted that it is recommended to have at least 3 voltage samples to facilitate an accurate computation. More importantly, the samples must be taken from the BIOS, whether seen from a screenshot or personally observed, and not from some monitoring software.

When I was computing for the +5V scale I had a hard time collecting samples because the +5V monitor from the BIOS rarely fluctuated -- my PSU must be that stable -- so that I only got values that I had observed and the other from the screenshot in the manual. I found it difficult scouring the web for BIOS voltage screenshots with the exact motherboad model as mine. With just two samples, it was hard to infer on the number of possible scaling factor steps.

I tried using the value I got from hwmonitor in Windows, but the results didn't make any sense when computed together with the other two values from the BIOS.

---------

All in all, this has been a very educating experience, and I really appreciate the inputs and patience that you and Guenter Roeck have given me.

Moreover, I have gained an appreciation of the sensors in my system that I was quick to disregard as being inaccurate, and it looks as though there's a problem with hwmonitor because I have now corroborated in Linux, via lm-sensors, values that I am seeing in the BIOS.

I will post my configuration file in a short while, and I hope you or some one could add it to the wiki.

Many thanks once again,

Ian Pangilinan


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

Re: [lm-sensors] W83627DHG-P sensor shows a single voltage monitor for +5V and +12V on in4?

[ianp]

> On Wednesday, February 19, 2014 10:23 PM, Guenter Roeck <linux@roeck-us.net> wrote:

> 
> ... and sorry for my misleading advice earlier.
> 

Not a problem. :-) You helped me identify the misunderstanding I had and set me on the right path.


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

Re: [lm-sensors] W83627DHG-P sensor shows a single voltage monitor for +5V and +12V on in4?

[Jean Delvare]

Hi,

On Wed, 19 Feb 2014 07:05:36 -0800 (PST), ianp wrote:
> Indeed. Many thanks for your well-written guide.
> 
> If I may make some suggestions to further improve the guide:
> 
> * It wasn't obvious nor clear, at least to me, that one needs to arbitrarily choose, by means of trial-and-error, from the set of voltage samples the value that will produce the closest, if not exact, match to one of the unscaled sensor inputs when validating the scaling factor.

Indeed. In my example the BIOS displayed only one value so the problem
did not exist. And you are right, the values do not have to match
exactly as "sensors" may be displaying the value for a slightly
different register value than the BIOS was.

> If you could specify that then I think it would really be a big help. When I first tried following your guide I didn't know this so that I was skeptical of the results I was getting and couldn't make a definitive map to one of the unscaled sensor inputs.
> 
> * It should be noted that it is recommended to have at least 3 voltage samples to facilitate an accurate computation. More importantly, the samples must be taken from the BIOS, whether seen from a screenshot or personally observed, and not from some monitoring software.

Monitoring software provided by the vendor is good. What's not good is
3rd party software.

> When I was computing for the +5V scale I had a hard time collecting samples because the +5V monitor from the BIOS rarely fluctuated -- my PSU must be that stable

Yeah, I had the same problem. Ironically, having a good, stable PSU
makes the job harder. A crappy PSU oscillating between 5 different
values in the BIOS would be much better ;-)

> -- so that I only got values that I had observed and the other from the screenshot in the manual. I found it difficult scouring the web for BIOS voltage screenshots with the exact motherboad model as mine. With just two samples, it was hard to infer on the number of possible scaling factor steps.

Well it really depends on the motherboard brand and model. In my
example it was relatively easy, while I admit I had a hard time finding
screenshots for yours (for only one and then realized it wasn't even
exactly the same as yours.)

> 
> I tried using the value I got from hwmonitor in Windows, but the results didn't make any sense when computed together with the other two values from the BIOS.

Thanks for your suggestions, I have updated my guide to clarify the
points you mentioned, hopefully it's better now.

> ---------
> 
> All in all, this has been a very educating experience, and I really appreciate the inputs and patience that you and Guenter Roeck have given me.

You're welcome :-)

> 
> Moreover, I have gained an appreciation of the sensors in my system that I was quick to disregard as being inaccurate, and it looks as though there's a problem with hwmonitor because I have now corroborated in Linux, via lm-sensors, values that I am seeing in the BIOS.
> 
> I will post my configuration file in a short while, and I hope you or some one could add it to the wiki.

I will do.

-- 
Jean Delvare
Suse L3 Support
http://jdelvare.nerim.net/wishlist.html

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

Re: [lm-sensors] W83627DHG-P sensor shows a single voltage monitor for +5V and +12V on in4?

[ianp]

> On Thursday, February 20, 2014 12:35 AM, Jean Delvare <jdelvare@suse.de> wrote:

>
>>  * It should be noted that it is recommended to have at least 3 voltage 
> samples to facilitate an accurate computation. More importantly, the samples 
> must be taken from the BIOS, whether seen from a screenshot or personally 
> observed, and not from some monitoring software.
> 
> Monitoring software provided by the vendor is good. What's not good is
> 3rd party software.
> 

I don't have much experience on using vendor-provided monitoring software, so I think that can be an exception.

>>  When I was computing for the +5V scale I had a hard time collecting samples 
> because the +5V monitor from the BIOS rarely fluctuated -- my PSU must be that 
> stable
> 
> Yeah, I had the same problem. Ironically, having a good, stable PSU
> makes the job harder. A crappy PSU oscillating between 5 different
> values in the BIOS would be much better ;-)
> 

Almost twenty minutes into just staring at the monitor, I thought about replacing the PSU with a generic unit that I have lying around here just to get it moving. But then I had an idea that maybe I could introduce a tiny ripple if I open and close my optical drive's tray. And that did the trick and gave me a quick 5.040 reading. :-)

> 
> Thanks for your suggestions, I have updated my guide to clarify the
> points you mentioned, hopefully it's better now.
> 

Yes it is. It bridges the gap I encountered while following the guide, i.e. what recommended voltage to use when validating the scaling factor.


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

Re: [lm-sensors] W83627DHG-P sensor shows a single voltage monitor for +5V and +12V on in4?

[Jean Delvare]

On Wed, 19 Feb 2014 10:20:16 -0800 (PST), ianp wrote:
> > On Thursday, February 20, 2014 12:35 AM, Jean Delvare <jdelvare@suse.de> wrote:
> > Yeah, I had the same problem. Ironically, having a good, stable PSU
> > makes the job harder. A crappy PSU oscillating between 5 different
> > values in the BIOS would be much better ;-)
> 
> Almost twenty minutes into just staring at the monitor, I thought about replacing the PSU with a generic unit that I have lying around here just to get it moving. But then I had an idea that maybe I could introduce a tiny ripple if I open and close my optical drive's tray. And that did the trick and gave me a quick 5.040 reading. :-)

This is a good trick, I've added it to the guide :) Thanks!

-- 
Jean Delvare
SUSE L3 Support

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