From: Andreas Leppert <wudmx-S0/GAf8tV78@public.gmane.org>
To: Bruno Ducrot <ducrot-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
Cc: ML ACPI-devel
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: About DSDT fixing and debugging
Date: Thu, 23 Sep 2004 16:59:05 +0200 [thread overview]
Message-ID: <20040923145905.GA14360@laptop> (raw)
In-Reply-To: <20040923123751.GA29424-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 948 bytes --]
On Thu, Sep 23, 2004 at 02:37:51PM +0200, Bruno Ducrot wrote:
> > Hello,
> >
> > on 09/23/04 14:55, Andreas Leppert wrote:
> > > just want to say that these are exactly the same problems i have with my fujitsu amilo D 7830!
> > > no throttling (always C1 = 12%), no cooling (always 75° C). i have already disassembled with a few
> > > errors, but couldn't fix it correctly.
> > about the C1 states: does your DSDT have a PBLK_lenght != [0|6]? Please
> > see post [1] on ACPI-devel (sorry, I don't know how you can see the
> > whole thread with gmane.com) and the first integration _CST method [2].
didn't find PBLK_length in my dsdt.dsl because...
> >
>
> I think OP meant s/C1/T1 ;)
>
yes, i've really meant T1 = 12%... i was talking about the throttling
state.
question: does a pentium 4 (not mobile) in a laptop support C2/C3? (i
mean the processor states when the cpu doesn't have much work!)
thank you guys
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2004-09-23 14:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-23 8:38 About DSDT fixing and debugging Gaetano Sferra
[not found] ` <I4HK00$27530FB661DF79A95160CDA9EDFBAE18-VGgt2q2+T+FeoWH0uzbU5w@public.gmane.org>
2004-09-23 12:55 ` Andreas Leppert
2004-09-23 11:50 ` Luca Capello
[not found] ` <4152B880.6050001-wlebWZzHoyE@public.gmane.org>
2004-09-23 12:37 ` Bruno Ducrot
[not found] ` <20040923123751.GA29424-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2004-09-23 14:59 ` Andreas Leppert [this message]
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=20040923145905.GA14360@laptop \
--to=wudmx-s0/gaf8tv78@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=ducrot-kk6yZipjEM5g9hUCZPvPmw@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 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.