Ticket #2091 (closed defect: worksforme)

Opened 6 years ago

Last modified 5 years ago

w83627hf-isa in6 reading changed from -5V line to something +3.5V between kernels 2.6.14.5 and 2.6.17.4 on MSI K7D MS-6501

Reported by: ej@… Owned by: khali
Priority: minor Milestone:
Component: kernel Version: kernel
Keywords: w83627hf Cc:

Description (last modified by khali) (diff)

My w83627hf-isa in6 reading from my MSI K7D Master (MS-6501) motherboard changed from its previous -5V line to something measuring +3.5V when I upgraded from kernel 2.6.14.5 to 2.6.17.4.

Also, I've been wondering for a while if the temp3 (bottom CPU) reading is correct cause it's always about 20 degrees Celsius hotter than the top one, but when I touch both of them in my case they feel about the same.

Also, but unrelated, the instructions for adding motherboard specific configs to the wiki don't work. Here's mine:

chip "w83627hf-*"
# -------------------
# +++ MSI K7D Master (MS-6501) +++
    
# VOLTAGES
    label in0 "V_Core"
    label in1 "V_+2.5V"
    label in2 "V_+3.3V"
    label in3 "V_+5V"
    label in4 "V_+12V"
    label in5 "V_-12V"
# changed to something measuring around +3.5 b/w 2.6.14.5 and 2.6.17.4
#    label in6 "V_-5V"
    label in7 "V_5VSB"
    label in8 "V_Bat"
    label vid "V_ID"
# conversion formulae taken from chip docs pp. 28-29
    compute in3 ((34/50)+1)*@ ,  @/((34/50)+1)
    compute in4 ((28/10)+1)*@  ,  @/((28/10)+1)
#    compute in5 (5.14*@) - 14.91  ,  (@ + 14.91) / 5.14
    compute in5 ((232+56)/56)*@-3.6*232/56  ,  (@+3.6*232/56)/((232+56)/56)
#    compute in6 (3.14*@) -  7.71  ,  (@ +  7.71) / 3.14
    compute in6 ((120+56)/56)*@-3.6*120/56  ,  (@+3.6*120/56)/((120+56)/56)
    compute in7 ((17/33)+1)*@ ,  @/((17/33)+1)
#    ignore in7
#    ignore in8
# adjust this if your vid is wrong; see doc/vid
   set vrm 9.0
# set limits to  5% for the critical voltages
# set limits to 10% for the non-critical voltages
# set limits to 20% for the battery voltage
##    set in0_min vid*0.95
##    set in0_max vid*1.05
# why are the VCores always giving alarms?
# these are someone else's
#set in0_min vid*0.90 (or below is 0.95)
#set in0_max vid*1.05
    set in0_min vid-0.150 # corresponds to vid*0.94
    set in0_max       vid+0.100 # corresponds to vid*1.06
    set in1_min 2.5*0.95
    set in1_max 2.5*1.05
    set in2_min 3.3*0.95
    set in2_max 3.3*1.05
    set in3_min 5.0*0.95
    set in3_max 5.0*1.05
    set in4_min 12*0.95
    set in4_max 12*1.05
    set in5_max -12*0.90
    set in5_min -12*1.10
# changed to +3.5
#    set in6_max -5*0.90
#    set in6_min -5*1.10
    set in7_min 5*0.90
    set in7_max 5*1.10
    set in8_min 3.3*0.90
    set in8_max 3.3*1.10

# TEMPERATURES
# don't set sensor1
# sensors set to 1 (diode) would give values 25K too high; 3435 gives +40K
    set sensor2 2
    set sensor3 2
    label temp1 "T_IN_CASE"
    label temp2 "T_TOP_CPU"
    label temp3 "T_BOT_CPU"
# limits
#    set temp1_over 50
    set temp1_over 40
    set temp1_hyst 49
    set temp2_over 67
    set temp2_hyst 127
# why is this 10 hotter all the time?
#    set temp3_over 67
#    set temp3_over 75
#    set temp3_over 80
    set temp3_over 85
    set temp3_hyst 127

# FANS
    label fan1 "F_FR_CASE"
    label fan2 "F_BOT_CPU"
    label fan3 "F_TOP_CPU"

    set fan1_div 4
    set fan2_div 4
    set fan3_div 4
    set fan1_min 1500
    set fan2_min 3000
    set fan3_min 3000
    
# BEEPS on
    set beeps 1
    set beep_enable 1

Change History

Changed 5 years ago by khali

  • owner changed from somebody to khali
  • priority changed from major to minor
  • status changed from new to assigned
  • description modified (diff)

I don't see anything between 2.6.14 and 2.6.17 which could have caused the problem you describe. Please double check that the BIOS still displays a valid value for -5V. Please also try again with the old kernel and confirm that the -5V value is OK there - I would like to rule out any user-space change.

If you are certain this is a kernel issue, please try 2.6.15 and 2.6.16 and report results.

Changed 5 years ago by khali

  • status changed from assigned to closed
  • resolution set to worksforme

No news for 7 months, closing.

Note: See TracTickets for help on using tickets.