From: Anders Persson <anders.persson-sT6loi8rTDSci/EUP2OQSw@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Compaq evo n800v
Date: 08 Mar 2003 13:07:03 +0100 [thread overview]
Message-ID: <1047125223.5077.28.camel@localhost.localdomain> (raw)
I have problems with CPU-throttling on my Compaq Evo n800v.
To get ACPI working I compiled the following kernel+patches and applied
a modified dsdt-table.
2.4.20 kernel +
patch-2.4.21-pre4.gz +
acpi-20030218-2.4.21-pre4.diff.gz +
linux-2.4.18-acpi-20020709-dsdt.patch +
custom dsdt
AC- and battery-status works just fine, as well as the Fn-combinations
for screen-brightness.
But no matter how low the CPU-load, the clock frequency is always at
max. Also, the fan(s?) are always on making noise (at relatively low
speed but still too high compared to under Win-XPP).
I am not really familiar with how this is supposed to work. Can I force
the CPU to run on the low clock-frequency when, e.g., running on
batteries? Can I set load-thresholds when the speed-step functionality
should take action? Grateful for any help on this!
Some data available below!
$ cd /proc/acpi/processor/C000
$ cat throttling
state count: 8
active state: T0
states:
*T0: 00%
T1: 12%
T2: 25%
T3: 37%
T4: 50%
T5: 62%
T6: 75%
T7: 87%
$ cat limit
active limit: P0:T0
platform limit: P0:T0
user limit: P0:T0
thermal limit: P0:T0
$ cat info
processor id: 0
acpi id: 1
bus mastering control: yes
power management: yes
throttling control: yes
performance management: yes
limit interface: yes
$ cat performance
state count: 2
active state: P0
states:
*P0: 1900 MHz, 20000 mW, 500 uS
P1: 1200 MHz, 10000 mW, 500 uS
$ cat power
active state: C2
default state: C1
bus master activity: 04082fff
states:
C1: promotion[C2] demotion[--] latency[000]
usage[00001020]
*C2: promotion[C3] demotion[C1] latency[002]
usage[00348077]
C3: promotion[--] demotion[C2] latency[085]
usage[00002681]
-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger
for complex code. Debugging C/C++ programs can leave you feeling lost and
disoriented. TotalView can help you find your way. Available on major UNIX
and Linux platforms. Try it free. www.etnus.com
next reply other threads:[~2003-03-08 12:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-08 12:07 Anders Persson [this message]
[not found] ` <1047125223.5077.28.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2003-03-08 19:59 ` Compaq evo n800v Daniele Boffi
2003-03-10 9:19 ` Stephan Krings
[not found] ` <15980.22695.764082.140067-/D6BEnooUbBSBwh6+m2SNzw7hsPlABbXrfATN7qnIZ4@public.gmane.org>
2003-03-10 10:08 ` Karol Kozimor
[not found] ` <20030310100824.GB32516-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
2003-03-10 20:37 ` Stephan Krings
[not found] ` <15980.63370.956274.280152-/D6BEnooUbBSBwh6+m2SNzw7hsPlABbXrfATN7qnIZ4@public.gmane.org>
2003-03-10 20:45 ` Karol Kozimor
[not found] ` <15981.52449.352495.551945@stephan.convergence.de>
[not found] ` <15981.52449.352495.551945-i6UgHu6VvmYwLeuMs8dnSMnRjscXObHh@public.gmane.org>
2003-03-12 13:12 ` Karol Kozimor
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=1047125223.5077.28.camel@localhost.localdomain \
--to=anders.persson-st6loi8rtdsci/eup2oqsw@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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