[lm-sensors] Can someone give me some help? thanks

[lm-sensors] Can someone give me some help? thanks

[he liang]

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

# sensors-detect revision 5016 (2007-11-11 22:20:16 +0100)

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.

We can start with probing for (PCI) I2C or SMBus adapters.
Do you want to probe now? (YES/no): y
Probing for PCI bus adapters...
Use driver `i2c-i801' for device 0000:00:1f.3: Intel 82801H ICH8

We will now try to load each adapter module in turn.
Module `i2c-i801' already loaded.
If you have undetectable or unsupported adapters, you can have them
scanned by manually loading the modules before running this script.

We are now going to do the I2C/SMBus adapter probings. Some chips may
be double detected; we choose the one with the highest confidence
value in that case.
If you found that the adapter hung after probing a certain address,
you can specify that address to remain unprobed.

Next adapter: NVIDIA i2c adapter  (i2c-0)
Do you want to scan it? (YES/no/selectively): yes

Next adapter: NVIDIA i2c adapter  (i2c-1)
Do you want to scan it? (YES/no/selectively): yes

Next adapter: NVIDIA i2c adapter  (i2c-2)
Do you want to scan it? (YES/no/selectively): yes

Next adapter: SMBus I801 adapter at 0400 (i2c-3)
Do you want to scan it? (YES/no/selectively): yes
Client found at address 0x50
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 Yes
    (confidence 8, not a hardware monitoring chip)
Probing for `EDID EEPROM'...                                No
Client found at address 0x51
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 Yes
    (confidence 8, not a hardware monitoring chip)
Probing for `EDID EEPROM'...                                No
Client found at address 0x52
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 Yes
    (confidence 8, not a hardware monitoring chip)
Probing for `EDID EEPROM'...                                No
Client found at address 0x53
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 Yes
    (confidence 8, not a hardware monitoring chip)
Probing for `EDID EEPROM'...                                No

Some chips are also accessible through the ISA I/O ports. We have to
write to arbitrary I/O ports to probe them. This is usually safe though.
Yes, you do have ISA I/O ports even if you do not have any ISA slots!
Do you want to scan the ISA I/O ports? (YES/no): yes
Probing for `National Semiconductor LM78' at 0x290...       No
Probing for `National Semiconductor LM78-J' 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
Probing for `Silicon Integrated Systems SIS5595'...         No
Probing for `VIA VT82C686 Integrated Sensors'...            No
Probing for `VIA VT8231 Integrated Sensors'...              No
Probing for `IPMI BMC KCS' at 0xca0...                      No
Probing for `IPMI BMC SMIC' at 0xca8...                     No

Some Super I/O chips may also contain 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): yes
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor'...                   No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Fintek'...                       Yes
Found `Winbond W83627DHG Super IO Sensors'                  Success!
    (address 0x290, driver `w83627ehf')
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 CPUs or memory controllers may also contain embedded sensors.
Do you want to scan for them? (YES/no): yes
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

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

Driver `w83627ehf' (should be inserted):
  Detects correctly:
  * ISA bus, address 0x290
    Chip `Winbond W83627DHG Super IO Sensors' (confidence: 9)

Driver `coretemp' (should be inserted):
  Detects correctly:
  * Chip `Intel Core family thermal sensor' (confidence: 9)

I will now generate the commands needed to load the required modules.
Just press ENTER to continue:

To load everything that is needed, add this to /etc/modules:

#----cut here----
# Chip drivers
w83627ehf
coretemp
#----cut here----

Do you want to add these lines automatically? (yes/NO)yes
psy@psy-desktop:~$ sudo sensors
No sensors found!
Make sure you loaded all the kernel drivers you need.
Try sensors-detect to find out which these are.

[-- Attachment #1.2: Type: text/html, Size: 6245 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] Can someone give me some help? thanks

[Martyn Welch]

he liang wrote:
>
> Just press ENTER to continue:
>
> I will now generate the commands needed to load the required modules.
>
> To load everything that is needed, add this to /etc/modules:
>
> #----cut here----
> # Chip drivers
> w83627ehf
> coretemp
> #----cut here----
>
> Do you want to add these lines automatically? (yes/NO)yes
> psy@psy-desktop:~$ <mailto:psy@psy-desktop:%7E$> sudo sensors
> No sensors found!
> Make sure you loaded all the kernel drivers you need.
> Try sensors-detect to find out which these are.
>
Have you tried rebooting? Adding those lines to "/etc/modules" should 
take effect after a reboot.

Try rebooting or issuing the following commands to load the modules:

  sudo modprobe w83627ehf
  sudo modprobe coretemp

Hope that helps,

Martyn

-- 
Martyn Welch MEng MPhil MIET (Principal Software Engineer)   T:+44(0)1327322748
GE Fanuc Intelligent Platforms Ltd,        |Registered in England and Wales
Tove Valley Business Park, Towcester,      |(3828642) at 100 Barbirolli Square,
Northants, NN12 6PF, UK T:+44(0)1327359444 |Manchester,M2 3AB  VAT:GB 927559189

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

Re: [lm-sensors] Can someone give me some help? thanks

[Mark E. Hansen]

On 07/13/09 03:52, Martyn Welch wrote:
> he liang wrote:
>>
>> Just press ENTER to continue:
>>
>> I will now generate the commands needed to load the required modules.
>>
>> To load everything that is needed, add this to /etc/modules:
>>
>> #----cut here----
>> # Chip drivers
>> w83627ehf
>> coretemp
>> #----cut here----
>>
>> Do you want to add these lines automatically? (yes/NO)yes
>> psy@psy-desktop:~$ <mailto:psy@psy-desktop:%7E$> sudo sensors
>> No sensors found!
>> Make sure you loaded all the kernel drivers you need.
>> Try sensors-detect to find out which these are.
>>
> Have you tried rebooting? Adding those lines to "/etc/modules" should 
> take effect after a reboot.
> 
> Try rebooting or issuing the following commands to load the modules:
> 
>   sudo modprobe w83627ehf
>   sudo modprobe coretemp
> 
> Hope that helps,
> 
> Martyn
> 

Also, the OP should try 'sensors -s' as root (in /etc/rc.local) to
upload the sensors configuration to the sensors chips.


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

Re: [lm-sensors] Can someone give me some help? thanks

[Mark E. Hansen]

On 07/13/09 20:53, he liang wrote:
> it can works
> THanks very much!
> the result as follows
> I want to ask why so many ALARM?
> need i to check something?

First, you should make sure you always include the lm-sensors mailing
list on all messages, so the entire list can participate.

You're getting the alarms because your configuration, for in1 for
example, shows a min voltage of +9.03 and a max voltage of +5.17,
while the sensed voltage is +12.20 - well above the defined max:

> in1:        +12.20 V  (min =  +9.03 V, max =  +5.17 V)   ALARM


Note that although the sensors-detect script can detect which sensor
chips are used by your motherboard and install the proper drivers,
it can't really set up the configuration file, as each motherboard
manufacturer "wires-up" the chips differently.

I'm not an expert at setting up a configuration file, so I'll let
someone else answer here.

Best Regards,


> -------------------------------------------------------------------------------------------
> Adapter: ISA adapter
> VCore:       +1.12 V  (min =  +0.00 V, max =  +1.74 V)
> in1:        +12.20 V  (min =  +9.03 V, max =  +5.17 V)   ALARM
> AVCC:        +3.17 V  (min =  +3.14 V, max =  +2.98 V)   ALARM
> 3VCC:        +3.17 V  (min =  +2.66 V, max =  +2.82 V)   ALARM
> in4:         +0.00 V  (min =  +0.13 V, max =  +1.39 V)   ALARM
> in5:         +1.58 V  (min =  +1.18 V, max =  +0.22 V)   ALARM
> in6:         +0.13 V  (min =  +4.35 V, max =  +6.35 V)   ALARM
> VSB:         +3.17 V  (min =  +1.14 V, max =  +2.61 V)   ALARM
> VBAT:        +3.17 V  (min =  +2.40 V, max =  +2.53 V)   ALARM
> Case Fan:      0 RPM  (min = 21093 RPM, div = 64)  ALARM
> CPU Fan:    1394 RPM  (min = 2678 RPM, div = 8)  ALARM
> Aux Fan:       0 RPM  (min = 21093 RPM, div = 64)  ALARM
> fan4:          0 RPM  (min = 42187 RPM, div = 32)  ALARM
> fan5:          0 RPM  (min = 10546 RPM, div = 128)  ALARM
> Sys Temp:    +37.0°C  (high = +15.0°C, hyst = +68.0°C)  sensor = thermistor
> CPU Temp:    +14.0°C  (high = +80.0°C, hyst = +75.0°C)  sensor = diode
> AUX Temp:   +111.5°C  (high = +80.0°C, hyst = +75.0°C)  ALARM  sensor > thermistor
> cpu0_vid:   +1.550 V
> coretemp-isa-0000
> Adapter: ISA adapter
> Core 0:      +36.0°C  (crit = +100.0°C)
> coretemp-isa-0001
> Adapter: ISA adapter
> Core 1:      +36.0°C  (crit = +100.0°C)
> coretemp-isa-0002
> Adapter: ISA adapter
> Core 2:      +34.0°C  (crit = +100.0°C)
> coretemp-isa-0003
> Adapter: ISA adapter
> Core 3:      +34.0°C  (crit = +100.0°C)
> 2009/7/13 Mark E. Hansen <meh@winfirst.com>
> 
>> On 07/13/09 03:52, Martyn Welch wrote:
>> > he liang wrote:
>> >>
>> >> Just press ENTER to continue:
>> >>
>> >> I will now generate the commands needed to load the required modules.
>> >>
>> >> To load everything that is needed, add this to /etc/modules:
>> >>
>> >> #----cut here----
>> >> # Chip drivers
>> >> w83627ehf
>> >> coretemp
>> >> #----cut here----
>> >>
>> >> Do you want to add these lines automatically? (yes/NO)yes
>> >> psy@psy-desktop:~$ <mailto:psy@psy-desktop:%7E$> sudo sensors
>> >> No sensors found!
>> >> Make sure you loaded all the kernel drivers you need.
>> >> Try sensors-detect to find out which these are.
>> >>
>> > Have you tried rebooting? Adding those lines to "/etc/modules" should
>> > take effect after a reboot.
>> >
>> > Try rebooting or issuing the following commands to load the modules:
>> >
>> >   sudo modprobe w83627ehf
>> >   sudo modprobe coretemp
>> >
>> > Hope that helps,
>> >
>> > Martyn
>> >
>>
>> Also, the OP should try 'sensors -s' as root (in /etc/rc.local) to
>> upload the sensors configuration to the sensors chips.
>>
>>
>> _______________________________________________
>> lm-sensors mailing list
>> lm-sensors@lm-sensors.org
>> http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
>>
> 


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

Re: [lm-sensors] Can someone give me some help? thanks

[he liang]

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

ok,I know.
This time  I send my question to  the  lm-sensors mailing address
 thanks for your advice.

my result is as follow,so why it has so many ALARM?
need I to modify or check something?

Processor 4x Intel(R) Core(TM)2 Quad CPU @ 2.40GHz
Operating System Ubuntu 8.04.3 LTS
Kernel Linux 2.6.24-24-generic (i686)
mainboard: asus p5b plus

Adapter: ISA adapter
VCore:       +1.12 V  (min =  +0.00 V, max =  +1.74 V)
in1:        +12.20 V  (min =  +9.03 V, max =  +5.17 V)   ALARM
AVCC:        +3.17 V  (min =  +3.14 V, max =  +2.98 V)   ALARM
3VCC:        +3.17 V  (min =  +2.66 V, max =  +2.82 V)   ALARM
in4:         +0.00 V  (min =  +0.13 V, max =  +1.39 V)   ALARM
in5:         +1.58 V  (min =  +1.18 V, max =  +0.22 V)   ALARM
in6:         +0.13 V  (min =  +4.35 V, max =  +6.35 V)   ALARM
VSB:         +3.17 V  (min =  +1.14 V, max =  +2.61 V)   ALARM
VBAT:        +3.17 V  (min =  +2.40 V, max =  +2.53 V)   ALARM
Case Fan:      0 RPM  (min = 21093 RPM, div = 64)  ALARM
CPU Fan:    1394 RPM  (min = 2678 RPM, div = 8)  ALARM
Aux Fan:       0 RPM  (min = 21093 RPM, div = 64)  ALARM
fan4:          0 RPM  (min = 42187 RPM, div = 32)  ALARM
fan5:          0 RPM  (min = 10546 RPM, div = 128)  ALARM
Sys Temp:    +37.0°C  (high = +15.0°C, hyst = +68.0°C)  sensor = thermistor
CPU Temp:    +14.0°C  (high = +80.0°C, hyst = +75.0°C)  sensor = diode
AUX Temp:   +111.5°C  (high = +80.0°C, hyst = +75.0°C)  ALARM  sensor =
thermistor
cpu0_vid:   +1.550 V
coretemp-isa-0000
Adapter: ISA adapter
Core 0:      +36.0°C  (crit = +100.0°C)
coretemp-isa-0001
Adapter: ISA adapter
Core 1:      +36.0°C  (crit = +100.0°C)
coretemp-isa-0002
Adapter: ISA adapter
Core 2:      +34.0°C  (crit = +100.0°C)
coretemp-isa-0003
Adapter: ISA adapter
Core 3:      +34.0°C  (crit = +100.0°C)

2009/7/14 Mark E. Hansen <meh@winfirst.com>

> On 07/13/09 20:53, he liang wrote:
> > it can works
> > THanks very much!
> > the result as follows
> > I want to ask why so many ALARM?
> > need i to check something?
>
> First, you should make sure you always include the lm-sensors mailing
> list on all messages, so the entire list can participate.
>
> You're getting the alarms because your configuration, for in1 for
> example, shows a min voltage of +9.03 and a max voltage of +5.17,
> while the sensed voltage is +12.20 - well above the defined max:
>
> > in1:        +12.20 V  (min =  +9.03 V, max =  +5.17 V)   ALARM
>
>
> Note that although the sensors-detect script can detect which sensor
> chips are used by your motherboard and install the proper drivers,
> it can't really set up the configuration file, as each motherboard
> manufacturer "wires-up" the chips differently.
>
> I'm not an expert at setting up a configuration file, so I'll let
> someone else answer here.
>
> Best Regards,
>
>
> >
> -------------------------------------------------------------------------------------------
> > Adapter: ISA adapter
> > VCore:       +1.12 V  (min =  +0.00 V, max =  +1.74 V)
> > in1:        +12.20 V  (min =  +9.03 V, max =  +5.17 V)   ALARM
> > AVCC:        +3.17 V  (min =  +3.14 V, max =  +2.98 V)   ALARM
> > 3VCC:        +3.17 V  (min =  +2.66 V, max =  +2.82 V)   ALARM
> > in4:         +0.00 V  (min =  +0.13 V, max =  +1.39 V)   ALARM
> > in5:         +1.58 V  (min =  +1.18 V, max =  +0.22 V)   ALARM
> > in6:         +0.13 V  (min =  +4.35 V, max =  +6.35 V)   ALARM
> > VSB:         +3.17 V  (min =  +1.14 V, max =  +2.61 V)   ALARM
> > VBAT:        +3.17 V  (min =  +2.40 V, max =  +2.53 V)   ALARM
> > Case Fan:      0 RPM  (min = 21093 RPM, div = 64)  ALARM
> > CPU Fan:    1394 RPM  (min = 2678 RPM, div = 8)  ALARM
> > Aux Fan:       0 RPM  (min = 21093 RPM, div = 64)  ALARM
> > fan4:          0 RPM  (min = 42187 RPM, div = 32)  ALARM
> > fan5:          0 RPM  (min = 10546 RPM, div = 128)  ALARM
> > Sys Temp:    +37.0°C  (high = +15.0°C, hyst = +68.0°C)  sensor =
> thermistor
> > CPU Temp:    +14.0°C  (high = +80.0°C, hyst = +75.0°C)  sensor = diode
> > AUX Temp:   +111.5°C  (high = +80.0°C, hyst = +75.0°C)  ALARM  sensor =
> > thermistor
> > cpu0_vid:   +1.550 V
> > coretemp-isa-0000
> > Adapter: ISA adapter
> > Core 0:      +36.0°C  (crit = +100.0°C)
> > coretemp-isa-0001
> > Adapter: ISA adapter
> > Core 1:      +36.0°C  (crit = +100.0°C)
> > coretemp-isa-0002
> > Adapter: ISA adapter
> > Core 2:      +34.0°C  (crit = +100.0°C)
> > coretemp-isa-0003
> > Adapter: ISA adapter
> > Core 3:      +34.0°C  (crit = +100.0°C)
> > 2009/7/13 Mark E. Hansen <meh@winfirst.com>
> >
> >> On 07/13/09 03:52, Martyn Welch wrote:
> >> > he liang wrote:
> >> >>
> >> >> Just press ENTER to continue:
> >> >>
> >> >> I will now generate the commands needed to load the required modules.
> >> >>
> >> >> To load everything that is needed, add this to /etc/modules:
> >> >>
> >> >> #----cut here----
> >> >> # Chip drivers
> >> >> w83627ehf
> >> >> coretemp
> >> >> #----cut here----
> >> >>
> >> >> Do you want to add these lines automatically? (yes/NO)yes
> >> >> psy@psy-desktop:~$ <mailto:psy@psy-desktop:%7E$> sudo sensors
> >> >> No sensors found!
> >> >> Make sure you loaded all the kernel drivers you need.
> >> >> Try sensors-detect to find out which these are.
> >> >>
> >> > Have you tried rebooting? Adding those lines to "/etc/modules" should
> >> > take effect after a reboot.
> >> >
> >> > Try rebooting or issuing the following commands to load the modules:
> >> >
> >> >   sudo modprobe w83627ehf
> >> >   sudo modprobe coretemp
> >> >
> >> > Hope that helps,
> >> >
> >> > Martyn
> >> >
> >>
> >> Also, the OP should try 'sensors -s' as root (in /etc/rc.local) to
> >> upload the sensors configuration to the sensors chips.
> >>
> >>
> >> _______________________________________________
> >> lm-sensors mailing list
> >> lm-sensors@lm-sensors.org
> >> http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
> >>
> >
>
>

[-- Attachment #1.2: Type: text/html, Size: 7442 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] Can someone give me some help? thanks

[Mark E. Hansen]

On 07/14/09 08:02, he liang wrote:
> ok,I know.
> This time  I send my question to  the  lm-sensors mailing address
>  thanks for your advice.
> 
> my result is as follow,so why it has so many ALARM?
> need I to modify or check something?
> 
> Processor 4x Intel(R) Core(TM)2 Quad CPU @ 2.40GHz
> Operating System Ubuntu 8.04.3 LTS
> Kernel Linux 2.6.24-24-generic (i686)
> mainboard: asus p5b plus
> 
> Adapter: ISA adapter
> VCore:       +1.12 V  (min =  +0.00 V, max =  +1.74 V)
> in1:        +12.20 V  (min =  +9.03 V, max =  +5.17 V)   ALARM

Let's look at in1. You have min for in1 set to +9.03 and max set
to +5.17 (these are set in your configuration file). However, the
value read from the sensor chip is +12.20. This is outside your
configured range, so you get an alarm.

Also, your range is backwards. How can you have a configured Min
value that is larger than your configured Max value?

As I said in my previous response (perhaps you missed that?), you
need to correct your configuration file. I'm not an expert at this,
so I'll leave it for others to answer.

Best Regards,

> AVCC:        +3.17 V  (min =  +3.14 V, max =  +2.98 V)   ALARM
> 3VCC:        +3.17 V  (min =  +2.66 V, max =  +2.82 V)   ALARM
> in4:         +0.00 V  (min =  +0.13 V, max =  +1.39 V)   ALARM
> in5:         +1.58 V  (min =  +1.18 V, max =  +0.22 V)   ALARM
> in6:         +0.13 V  (min =  +4.35 V, max =  +6.35 V)   ALARM
> VSB:         +3.17 V  (min =  +1.14 V, max =  +2.61 V)   ALARM
> VBAT:        +3.17 V  (min =  +2.40 V, max =  +2.53 V)   ALARM
> Case Fan:      0 RPM  (min = 21093 RPM, div = 64)  ALARM
> CPU Fan:    1394 RPM  (min = 2678 RPM, div = 8)  ALARM
> Aux Fan:       0 RPM  (min = 21093 RPM, div = 64)  ALARM
> fan4:          0 RPM  (min = 42187 RPM, div = 32)  ALARM
> fan5:          0 RPM  (min = 10546 RPM, div = 128)  ALARM
> Sys Temp:    +37.0°C  (high = +15.0°C, hyst = +68.0°C)  sensor = thermistor
> CPU Temp:    +14.0°C  (high = +80.0°C, hyst = +75.0°C)  sensor = diode
> AUX Temp:   +111.5°C  (high = +80.0°C, hyst = +75.0°C)  ALARM  sensor > thermistor
> cpu0_vid:   +1.550 V
> coretemp-isa-0000
> Adapter: ISA adapter
> Core 0:      +36.0°C  (crit = +100.0°C)
> coretemp-isa-0001
> Adapter: ISA adapter
> Core 1:      +36.0°C  (crit = +100.0°C)
> coretemp-isa-0002
> Adapter: ISA adapter
> Core 2:      +34.0°C  (crit = +100.0°C)
> coretemp-isa-0003
> Adapter: ISA adapter
> Core 3:      +34.0°C  (crit = +100.0°C)
> 
> 2009/7/14 Mark E. Hansen <meh@winfirst.com>
> 
>> On 07/13/09 20:53, he liang wrote:
>> > it can works
>> > THanks very much!
>> > the result as follows
>> > I want to ask why so many ALARM?
>> > need i to check something?
>>
>> First, you should make sure you always include the lm-sensors mailing
>> list on all messages, so the entire list can participate.
>>
>> You're getting the alarms because your configuration, for in1 for
>> example, shows a min voltage of +9.03 and a max voltage of +5.17,
>> while the sensed voltage is +12.20 - well above the defined max:
>>
>> > in1:        +12.20 V  (min =  +9.03 V, max =  +5.17 V)   ALARM
>>
>>
>> Note that although the sensors-detect script can detect which sensor
>> chips are used by your motherboard and install the proper drivers,
>> it can't really set up the configuration file, as each motherboard
>> manufacturer "wires-up" the chips differently.
>>
>> I'm not an expert at setting up a configuration file, so I'll let
>> someone else answer here.
>>
>> Best Regards,
>>
>>
>> >
>> -------------------------------------------------------------------------------------------
>> > Adapter: ISA adapter
>> > VCore:       +1.12 V  (min =  +0.00 V, max =  +1.74 V)
>> > in1:        +12.20 V  (min =  +9.03 V, max =  +5.17 V)   ALARM
>> > AVCC:        +3.17 V  (min =  +3.14 V, max =  +2.98 V)   ALARM
>> > 3VCC:        +3.17 V  (min =  +2.66 V, max =  +2.82 V)   ALARM
>> > in4:         +0.00 V  (min =  +0.13 V, max =  +1.39 V)   ALARM
>> > in5:         +1.58 V  (min =  +1.18 V, max =  +0.22 V)   ALARM
>> > in6:         +0.13 V  (min =  +4.35 V, max =  +6.35 V)   ALARM
>> > VSB:         +3.17 V  (min =  +1.14 V, max =  +2.61 V)   ALARM
>> > VBAT:        +3.17 V  (min =  +2.40 V, max =  +2.53 V)   ALARM
>> > Case Fan:      0 RPM  (min = 21093 RPM, div = 64)  ALARM
>> > CPU Fan:    1394 RPM  (min = 2678 RPM, div = 8)  ALARM
>> > Aux Fan:       0 RPM  (min = 21093 RPM, div = 64)  ALARM
>> > fan4:          0 RPM  (min = 42187 RPM, div = 32)  ALARM
>> > fan5:          0 RPM  (min = 10546 RPM, div = 128)  ALARM
>> > Sys Temp:    +37.0°C  (high = +15.0°C, hyst = +68.0°C)  sensor >> thermistor
>> > CPU Temp:    +14.0°C  (high = +80.0°C, hyst = +75.0°C)  sensor = diode
>> > AUX Temp:   +111.5°C  (high = +80.0°C, hyst = +75.0°C)  ALARM  sensor >> > thermistor
>> > cpu0_vid:   +1.550 V
>> > coretemp-isa-0000
>> > Adapter: ISA adapter
>> > Core 0:      +36.0°C  (crit = +100.0°C)
>> > coretemp-isa-0001
>> > Adapter: ISA adapter
>> > Core 1:      +36.0°C  (crit = +100.0°C)
>> > coretemp-isa-0002
>> > Adapter: ISA adapter
>> > Core 2:      +34.0°C  (crit = +100.0°C)
>> > coretemp-isa-0003
>> > Adapter: ISA adapter
>> > Core 3:      +34.0°C  (crit = +100.0°C)
>> > 2009/7/13 Mark E. Hansen <meh@winfirst.com>
>> >
>> >> On 07/13/09 03:52, Martyn Welch wrote:
>> >> > he liang wrote:
>> >> >>
>> >> >> Just press ENTER to continue:
>> >> >>
>> >> >> I will now generate the commands needed to load the required modules.
>> >> >>
>> >> >> To load everything that is needed, add this to /etc/modules:
>> >> >>
>> >> >> #----cut here----
>> >> >> # Chip drivers
>> >> >> w83627ehf
>> >> >> coretemp
>> >> >> #----cut here----
>> >> >>
>> >> >> Do you want to add these lines automatically? (yes/NO)yes
>> >> >> psy@psy-desktop:~$ <mailto:psy@psy-desktop:%7E$> sudo sensors
>> >> >> No sensors found!
>> >> >> Make sure you loaded all the kernel drivers you need.
>> >> >> Try sensors-detect to find out which these are.
>> >> >>
>> >> > Have you tried rebooting? Adding those lines to "/etc/modules" should
>> >> > take effect after a reboot.
>> >> >
>> >> > Try rebooting or issuing the following commands to load the modules:
>> >> >
>> >> >   sudo modprobe w83627ehf
>> >> >   sudo modprobe coretemp
>> >> >
>> >> > Hope that helps,
>> >> >
>> >> > Martyn
>> >> >
>> >>
>> >> Also, the OP should try 'sensors -s' as root (in /etc/rc.local) to
>> >> upload the sensors configuration to the sensors chips.
>> >>
>> >>
>> >> _______________________________________________
>> >> lm-sensors mailing list
>> >> lm-sensors@lm-sensors.org
>> >> http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
>> >>
>> >
>>
>>
> 


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