public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Lincoln Baxter, III" <lincolnbaxter@gmail.com>
To: linux-acpi@vger.kernel.org
Subject: Re: HP nc6400 v.03 or v.05 laptop ACPI fails after reboot, works again after booting windows
Date: Sun, 17 Dec 2006 13:51:06 -0500	[thread overview]
Message-ID: <4585919A.9060907@gmail.com> (raw)
In-Reply-To: <20061216081757.GA3571@invalid.invalid>


> As far as i know, the humming appears in windows too. I tested it with
> the RMClock utility and on my laptop, switching to C4 was making the
> humming. But every other C-State was quite. You should tune the timing
> frquencies, like Pavel pointed out.
>
> But i'm curios, why on linux the C4-State does not show up. The maximum
> working C-State on my system, on AC or battery is C3. Is there any
> hidden switch to enable it?
>
> with regards, frank
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
Ok, thank you. With regard to the timing frequencies Is that in 
reference to the Kernel Frequency for Latency?
Eg. 1000 / 250 / 100 ?

There's nothing that I've found the enable the C4 state. It would be 
nice, since that is definitely the most power saving state. And do you 
have any ideas why the sound would not occur in windows? I'm pretty sure 
it's using the lower power states, because battery lasts a heck of a lot 
longer than in gentoo.

I'm not sure if I was using RMClock correctly, but it seems like the 
humming did not occur in windows. Perhaps you could give me a little 
guidance on how to use the tool properly?

Thanks.
Lincoln

  reply	other threads:[~2006-12-17 18:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-12 23:14 HP nc6400 v.03 or v.05 laptop ACPI fails after reboot, works again after booting windows Lincoln Baxter, III
2006-12-12 23:42 ` Peter Clifton
2006-12-13  7:54   ` Lincoln Baxter, III
2006-12-13 12:25     ` Peter Clifton
2006-12-15 13:41       ` Lincoln Baxter, III
2006-12-15 14:10         ` Peter Clifton
2006-12-15 14:38           ` Lincoln Baxter, III
2006-12-15 22:35           ` Lincoln Baxter, III
2006-12-16  4:30             ` Pavel Troller
2006-12-16  7:59               ` Lincoln Baxter, III
2006-12-16  8:17                 ` Frank Ursel
2006-12-17 18:51                   ` Lincoln Baxter, III [this message]
2006-12-21 21:44                   ` Lincoln Baxter, III
2006-12-21 22:40                     ` Peter Clifton
2007-01-05 14:18                       ` Thomas Renninger
2007-01-12  5:51       ` Luming Yu

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=4585919A.9060907@gmail.com \
    --to=lincolnbaxter@gmail.com \
    --cc=linux-acpi@vger.kernel.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