From: Sergey Vlasov <vsu-u2l5PoMzF/Uox3rIn2DAYQ@public.gmane.org>
To: Hamie <hamish-CM5YN7r2dWBr4tq51QLIbdBPR1lH4CV8@public.gmane.org>
Cc: gentoo-amd64-cnFmAm88PdgLnqt3yJz4RQ@public.gmane.org,
acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: ACPI vs Asus A8v
Date: Sat, 5 Mar 2005 14:22:45 +0300 [thread overview]
Message-ID: <20050305142245.40c8914a.vsu@altlinux.ru> (raw)
In-Reply-To: <42289943.6030303-CM5YN7r2dWBr4tq51QLIbdBPR1lH4CV8@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 944 bytes --]
On Fri, 04 Mar 2005 17:22:11 +0000 Hamie wrote:
> I have an athlon64 in an Asus A8V motherboard, running gentoo with
> kernel 2.6.11 (Also tried with 2.6.9 and 2.6.10). Although it works, and
> cool&quiet kicks in before boot, I can get no thermal or fan information
> from acpi...
[skip]
> What sort of info & control SHOULD I be able to see out of this
> motherboard? How can I get the level of control that Asus offer with
> their windoze applications?
You should try to use lm_sensors - there are some success reports
about this board:
http://archives.andrew.net.au/lm-sensors/msg29514.html
In fact, most desktop machines do not support access to thermal or fan
information via ACPI (because the code for this is not present in
DSDT); and even if it is supported, the capabilities compared to
lm_sensors are reduced (e.g., most hardware monitoring chips support
voltage monitoring, which is not available through ACPI interfaces).
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-03-05 11:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-04 17:22 ACPI vs Asus A8v Hamie
[not found] ` <42289943.6030303-CM5YN7r2dWBr4tq51QLIbdBPR1lH4CV8@public.gmane.org>
2005-03-05 11:22 ` Sergey Vlasov [this message]
2005-03-05 22:51 ` [ACPI] " Hamie
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=20050305142245.40c8914a.vsu@altlinux.ru \
--to=vsu-u2l5pomzf/uox3rin2dayq@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=gentoo-amd64-cnFmAm88PdgLnqt3yJz4RQ@public.gmane.org \
--cc=hamish-CM5YN7r2dWBr4tq51QLIbdBPR1lH4CV8@public.gmane.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