* Re: [lm-sensors] 5VSB computing on it87
2009-05-11 8:07 [lm-sensors] 5VSB computing on it87 Mr. Tux
@ 2009-05-11 8:55 ` Jean Delvare
2009-05-12 17:55 ` Mr. Tux
` (4 subsequent siblings)
5 siblings, 0 replies; 7+ messages in thread
From: Jean Delvare @ 2009-05-11 8:55 UTC (permalink / raw)
To: lm-sensors
On Mon, 11 May 2009 10:07:30 +0200, Mr. Tux wrote:
> My Foxconn A7GM-S keep showing the wrong Voltage of 5VSB sensor.
>
> This one shows up in BIOS as well, so it is connected and should indicate about 5.02V
>
> But 'sensors' with it87 module loaded keeps showing 6.85V - how to change the compute
> line in order to get the 5.02V?
>
> At the moment the compute line is the default:
>
> compute in7 ((6.8/10)+1)*@ , @/((6.8/10)+1)
I can't help but notice that 6.85 = ((6.8/10)+1)*4.08. The IT87xxF
chips have a 4.08V DAC, meaning that this input channel is saturated.
Thus I pretty much doubt it corresponds to your 5VSB line.
--
Jean Delvare
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 7+ messages in thread* Re: [lm-sensors] 5VSB computing on it87
2009-05-11 8:07 [lm-sensors] 5VSB computing on it87 Mr. Tux
2009-05-11 8:55 ` Jean Delvare
@ 2009-05-12 17:55 ` Mr. Tux
2009-05-12 18:57 ` Mark E. Hansen
` (3 subsequent siblings)
5 siblings, 0 replies; 7+ messages in thread
From: Mr. Tux @ 2009-05-12 17:55 UTC (permalink / raw)
To: lm-sensors
[-- Attachment #1.1: Type: text/plain, Size: 2002 bytes --]
Thank you Jean
So, this sensor is not assigned correctly, I could life with that for the moment, but my problem
is the alarm flag this sensors is causing, since the value for some reason is saturated.
I'd like to put this sensor on ignore for the moment, but I don't know how to do that:
*) ignore in7 - only prevents the sensor to be listed using the 'sensors' command
*) comment every line mentioning in7 in sensors3.conf - makes it appear under
/sys/devices/plattform/[...]/ anyway ! With the alarm flag in "in7_alarm" set to 1 - I need to get rid
of that...
*) trying to set in7 to value 0 (= unused): 'set in7_type 0' causes a parse error with 'sensors -s'
*) trying to raise the max_value barrier switching on the alarm: 'set in7_max 7 * 1.05'
this does not have an effect - the max limit stays at 6,.85, triggering the alarm!
What else can I try? I need the alarm flag in /sys/devices/plattform/[...]/in7_alarm to
be set to '0' - since I'm writing a small daemon who will parse for alarm values
only, starting a speaker beep when a alarm is discovered.
Thanks in advance for any help.
Mr Tux
> On Mon, 11 May 2009 10:07:30 +0200, Mr. Tux wrote:
> > My Foxconn A7GM-S keep showing the wrong Voltage of 5VSB sensor.
> >
> > This one shows up in BIOS as well, so it is connected and should indicate about 5.02V
> >
> > But 'sensors' with it87 module loaded keeps showing 6.85V - how to change the compute
> > line in order to get the 5.02V?
> >
> > At the moment the compute line is the default:
> >
> > compute in7 ((6.8/10)+1)*@ , @/((6.8/10)+1)
>
> I can't help but notice that 6.85 == ((6.8/10)+1)*4.08. The IT87xxF
> chips have a 4.08V DAC, meaning that this input channel is saturated.
> Thus I pretty much doubt it corresponds to your 5VSB line.
>
> --
> Jean Delvare
_________________________________________________________________
http://redirect.gimas.net/?n=M0905xIE8_MSN4
Internet Explorer 8 jetzt für MSN - kostenlos!
[-- Attachment #1.2: Type: text/html, Size: 2407 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
^ permalink raw reply [flat|nested] 7+ messages in thread* Re: [lm-sensors] 5VSB computing on it87
2009-05-11 8:07 [lm-sensors] 5VSB computing on it87 Mr. Tux
2009-05-11 8:55 ` Jean Delvare
2009-05-12 17:55 ` Mr. Tux
@ 2009-05-12 18:57 ` Mark E. Hansen
2009-05-12 19:06 ` Jean Delvare
` (2 subsequent siblings)
5 siblings, 0 replies; 7+ messages in thread
From: Mark E. Hansen @ 2009-05-12 18:57 UTC (permalink / raw)
To: lm-sensors
On 05/12/09 10:55, Mr. Tux wrote:
> Thank you Jean
>
> So, this sensor is not assigned correctly, I could life with that for the moment, but my problem
> is the alarm flag this sensors is causing, since the value for some reason is saturated.
>
> I'd like to put this sensor on ignore for the moment, but I don't know how to do that:
>
> *) ignore in7 - only prevents the sensor to be listed using the 'sensors' command
> *) comment every line mentioning in7 in sensors3.conf - makes it appear under
> /sys/devices/plattform/[...]/ anyway ! With the alarm flag in "in7_alarm" set to 1 - I need to get rid
> of that...
> *) trying to set in7 to value 0 (= unused): 'set in7_type 0' causes a parse error with 'sensors -s'
> *) trying to raise the max_value barrier switching on the alarm: 'set in7_max 7 * 1.05'
> this does not have an effect - the max limit stays at 6,.85, triggering the alarm!
>
> What else can I try? I need the alarm flag in /sys/devices/plattform/[...]/in7_alarm to
> be set to '0' - since I'm writing a small daemon who will parse for alarm values
> only, starting a speaker beep when a alarm is discovered.
>
> Thanks in advance for any help.
>
> Mr Tux
Sir,
If you don't come up with a better solution, I parse the output of the
'sensors' command and look for alarms. I just run the command once a minute
(I think that's the current rate) and send an e-mail when an alarm is
detected.
I just 'ignore' (in7 in your case) in the sensors.conf file, by the way,
for any inputs I don't want to see in the 'sensors' output.
YMMV.
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 7+ messages in thread* Re: [lm-sensors] 5VSB computing on it87
2009-05-11 8:07 [lm-sensors] 5VSB computing on it87 Mr. Tux
` (2 preceding siblings ...)
2009-05-12 18:57 ` Mark E. Hansen
@ 2009-05-12 19:06 ` Jean Delvare
2009-05-12 19:07 ` Mark E. Hansen
2009-05-14 9:09 ` Mr. Tux
5 siblings, 0 replies; 7+ messages in thread
From: Jean Delvare @ 2009-05-12 19:06 UTC (permalink / raw)
To: lm-sensors
On Tue, 12 May 2009 19:55:10 +0200, Mr. Tux wrote:
>
> Thank you Jean
>
> So, this sensor is not assigned correctly, I could life with that for the moment, but my problem
> is the alarm flag this sensors is causing, since the value for some reason is saturated.
>
> I'd like to put this sensor on ignore for the moment, but I don't know how to do that:
>
> *) ignore in7 - only prevents the sensor to be listed using the 'sensors' command
Not just the "sensors" command, but all problems using libsensors. And
all monitoring programs should use it.
> *) comment every line mentioning in7 in sensors3.conf - makes it appear under
> /sys/devices/plattform/[...]/ anyway ! With the alarm flag in "in7_alarm" set to 1 - I need to get rid
> of that...
This doesn't make any sense. Statements mentioning in7 for other chips
you do not have on your board have no effect for you in the first place.
> *) trying to set in7 to value 0 (= unused): 'set in7_type 0' causes a parse error with 'sensors -s'
You can't invent symbols like that. Only a few sensors have a
selectable type, thermal sensors mostly.
> *) trying to raise the max_value barrier switching on the alarm: 'set in7_max 7 * 1.05'
> this does not have an effect - the max limit stays at 6,.85, triggering the alarm!
Some chips to strict comparisons on limits and some do loose
comparisons. Apparently the IT87xxF chips do loose comparisons on upper
limits, so you're doomed. That's the reason why chip manufacturer
recommend to connect unused voltage inputs to the ground, a
recommendation your motherboard vendor did not follow - blame them!
> What else can I try? I need the alarm flag in /sys/devices/plattform/[...]/in7_alarm to
> be set to '0' - since I'm writing a small daemon who will parse for alarm values
> only, starting a speaker beep when a alarm is discovered.
Your small daemon should link with libsensors and use it's API, instead
of accessing /sys files directly. That way you can ignore faulty inputs
through /etc/sensors3.conf.
--
Jean Delvare
http://khali.linux-fr.org/wishlist.html
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 7+ messages in thread* Re: [lm-sensors] 5VSB computing on it87
2009-05-11 8:07 [lm-sensors] 5VSB computing on it87 Mr. Tux
` (3 preceding siblings ...)
2009-05-12 19:06 ` Jean Delvare
@ 2009-05-12 19:07 ` Mark E. Hansen
2009-05-14 9:09 ` Mr. Tux
5 siblings, 0 replies; 7+ messages in thread
From: Mark E. Hansen @ 2009-05-12 19:07 UTC (permalink / raw)
To: lm-sensors
On 05/12/09 11:57, Mark E. Hansen wrote:
> On 05/12/09 10:55, Mr. Tux wrote:
>> Thank you Jean
>>
>> So, this sensor is not assigned correctly, I could life with that for the moment, but my problem
>> is the alarm flag this sensors is causing, since the value for some reason is saturated.
>>
>> I'd like to put this sensor on ignore for the moment, but I don't know how to do that:
>>
>> *) ignore in7 - only prevents the sensor to be listed using the 'sensors' command
>> *) comment every line mentioning in7 in sensors3.conf - makes it appear under
>> /sys/devices/plattform/[...]/ anyway ! With the alarm flag in "in7_alarm" set to 1 - I need to get rid
>> of that...
>> *) trying to set in7 to value 0 (= unused): 'set in7_type 0' causes a parse error with 'sensors -s'
>> *) trying to raise the max_value barrier switching on the alarm: 'set in7_max 7 * 1.05'
>> this does not have an effect - the max limit stays at 6,.85, triggering the alarm!
>>
>> What else can I try? I need the alarm flag in /sys/devices/plattform/[...]/in7_alarm to
>> be set to '0' - since I'm writing a small daemon who will parse for alarm values
>> only, starting a speaker beep when a alarm is discovered.
>>
>> Thanks in advance for any help.
>>
>> Mr Tux
>
> Sir,
>
> If you don't come up with a better solution, I parse the output of the
> 'sensors' command and look for alarms. I just run the command once a minute
> (I think that's the current rate) and send an e-mail when an alarm is
> detected.
Heh, ok - I do it every 5 minutes, not every minute. Of course, every 5
minutes may be too often as well, but the machine is not doing much
otherwise :-)
>
> I just 'ignore' (in7 in your case) in the sensors.conf file, by the way,
> for any inputs I don't want to see in the 'sensors' output.
>
> YMMV.
>
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 7+ messages in thread* Re: [lm-sensors] 5VSB computing on it87
2009-05-11 8:07 [lm-sensors] 5VSB computing on it87 Mr. Tux
` (4 preceding siblings ...)
2009-05-12 19:07 ` Mark E. Hansen
@ 2009-05-14 9:09 ` Mr. Tux
5 siblings, 0 replies; 7+ messages in thread
From: Mr. Tux @ 2009-05-14 9:09 UTC (permalink / raw)
To: lm-sensors
_________________________________________________________________
http://redirect.gimas.net/?n=M0905xIE8_MSN3
Hol Dir den neuen Internet Explorer 8 mit MSN-Toolbar
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 7+ messages in thread