mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Oliver Pinter" <oliver.pntr@gmail.com>
To: "Jean Delvare" <khali@linux-fr.org>
Cc: "LM Sensors" <lm-sensors@lm-sensors.org>, linux-kernel@vger.kernel.org
Subject: Re: Bad value with w83627thf
Date: Fri, 16 May 2008 15:45:01 +0200	[thread overview]
Message-ID: <6101e8c40805160645x5982d5ads61a422f5600f7507@mail.gmail.com> (raw)
In-Reply-To: <20080516152712.629606bf@hyperion.delvare>

Hi Jean!

sorry for the bad ML.

the battery is CR2032, and it is 3V, im older kernel alway reported
bad value 0,02V or 2,4V (i think it is a possible value), after i
inserted new battery, show 2,4V.
from the 2.6.26-rcX kernel showed the 3+ V. when i reboot to older
kernel, the this state remained, but when turned off the pc, then not.


On 5/16/08, Jean Delvare <khali@linux-fr.org> wrote:
> Hi Oliver,
>
> You are writing to the wrong mailing list (i2c instead of lm-sensors)
> so I am redirecting.
>
> On Fri, 16 May 2008 14:59:21 +0200, Oliver Pinter wrote:
>> linux-2.6 - git HEAD on: 9662369
>> lm-sensors: 1:3.0.1-5
>> libsensors4: 1:3.0.1-5
>> os: debian lenny
>> sernsor: w83627thf on asus p4c800 MB
>>
>> with 2.6.26-rcX kernel, reported false Battery values,
>> -------------------------------------->
>> VBat:        +3.26 V  (min =  +0.02 V, max =  +3.01 V)   ALARM
>> <-------------------------------------
>
> There is nothing wrong here. +3.26V sounds possible and correct for the
> battery voltage. If you are worried about the min and max values: it is
> up to you to edit your sensors3.conf file to set them properly if the
> BIOS of your motherboard did not (apply the changes with "sensors -s").
> The alarm will go away when you do.
>
>> lspci -xxx
>> 00:1f.3 SMBus: Intel Corporation 82801EB/ER (ICH5/ICH5R) SMBus
>> Controller (rev 02)
>> 00: 86 80 d3 24 01 00 80 02 02 00 05 0c 00 00 00 00
>> 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 20: 01 04 00 00 00 00 00 00 00 00 00 00 43 10 a6 80
>> 30: 00 00 00 00 00 00 00 00 00 00 00 00 03 02 00 00
>> 40: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> f0: 00 00 00 00 00 00 00 00 66 0f 04 00 00 00 00 00
>
> Completely irrelevant here, the Winbond W83627THF is an LPC chip, it
> doesn't have an I2C/SMBus interface, so the SMBus controller doesn't
> matter at all.
>
> --
> Jean Delvare
>


-- 
Thanks,
Oliver

  reply	other threads:[~2008-05-16 13:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-16 12:59 Oliver Pinter
2008-05-16 13:27 ` Jean Delvare
2008-05-16 13:45   ` Oliver Pinter [this message]
2008-05-16 14:26     ` Jean Delvare
2008-05-16 14:34       ` Oliver Pinter

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6101e8c40805160645x5982d5ads61a422f5600f7507@mail.gmail.com \
    --to=oliver.pntr@gmail.com \
    --cc=khali@linux-fr.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm-sensors@lm-sensors.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®