From: "Kevin P. Fleming" <kevin@labsysgrp.com>
To: <pogosyan@phys.ualberta.ca>, <whitney@math.berkeley.edu>
Cc: "Rasmus Bøg Hansen" <moffe@amagerkollegiet.dk>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: ACPI trouble (Was: Re: [patch] amd athlon cooling on kt266/266a chipset)
Date: Thu, 24 Jan 2002 12:49:42 -0700 [thread overview]
Message-ID: <034501c1a510$44422590$6caaa8c0@kevin> (raw)
In-Reply-To: <20020124155853Z287177-13996+11274@vger.kernel.org> <Pine.LNX.4.44.0201241803540.1345-100000@grignard.amagerkollegiet.dk> <200201241749.g0OHnbG02468@adsl-209-76-109-63.dsl.snfc21.pacbell.net> <3C505702.7B665083@phys.ualberta.ca>
Actually, I used a separate temperature sensor to come up with proper values
for lm_sensors to read the CPU temperature on my A7V (ver 1.01). After
testing lowest and highest temperatures, this what I came up with:
compute temp2 28.2+((@-18)*2), ((@-28.2)/2)+18
I know it looks weird, but it makes the "sensors" value for CPU temperate
match (within .5 degrees C) across the entire range I can test (which is
from full load on a 1GHz Thunderbird down to idle and using the old "lvcool"
patch).
----- Original Message -----
From: <pogosyan@phys.ualberta.ca>
To: <whitney@math.berkeley.edu>
Cc: "Rasmus Bøg Hansen" <moffe@amagerkollegiet.dk>; "LKML"
<linux-kernel@vger.kernel.org>
Sent: Thursday, January 24, 2002 11:48 AM
Subject: Re: ACPI trouble (Was: Re: [patch] amd athlon cooling on kt266/266a
chipset)
> > Note that on this motherboard (and perhaps all ASUS Via chipset
> > motherboards, including the A7V133), one needs the following line in
> > /etc/sensors.conf to get reasonable lm_sensors CPU temperatures:
> > compute temp2 @*2, @/2
> > This is as described at http://www2.lm-sensors.nu/~lm78/support.html
> > in Ticket 775.
> >
>
> I have ASUS A7V266-E (AS99127F chip) and lm_sensors 2.6.2
> shows 43 C for CPU without any additional lines in /etc/sensors.conf
>
> Which sounds reasonable. However this temperature is rarely ever change
!
> I typically have 43.1, sometimes 42.8 and that's it. Even after 2-3
min
>
> compiles. So something is wrong
>
> Dmitri
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
>
>
next prev parent reply other threads:[~2002-01-27 2:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-24 15:58 [patch] amd athlon cooling on kt266/266a chipset Dieter Nützel
2002-01-24 17:22 ` ACPI trouble (Was: Re: [patch] amd athlon cooling on kt266/266a chipset) Rasmus Bøg Hansen
2002-01-24 17:49 ` Wayne Whitney
2002-01-24 18:40 ` Petr Vandrovec
2002-01-25 0:47 ` Wayne Whitney
2002-01-25 9:48 ` Rasmus Bøg Hansen
2002-01-25 18:47 ` Pavel Machek
2002-01-24 18:48 ` pogosyan
2002-01-24 19:49 ` Kevin P. Fleming [this message]
2002-01-24 21:39 ` Daniel Nofftz
2002-01-24 19:27 ` Rasmus Bøg Hansen
2002-01-24 21:29 ` Daniel Nofftz
2002-01-24 22:24 ` Craig Knox
2002-01-24 21:15 ` Dieter Nützel
2002-01-24 23:28 ` Rasmus Bøg Hansen
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='034501c1a510$44422590$6caaa8c0@kevin' \
--to=kevin@labsysgrp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=moffe@amagerkollegiet.dk \
--cc=pogosyan@phys.ualberta.ca \
--cc=whitney@math.berkeley.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.