public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Luming Yu" <luming.yu@gmail.com>
To: Peter Clifton <pcjc2@cam.ac.uk>
Cc: linux-acpi@vger.kernel.org, "Lincoln Baxter,
	III" <lincolnbaxter@gmail.com>
Subject: Re: HP nc6400 v.03 or v.05 laptop ACPI fails after reboot, works again after booting windows
Date: Fri, 12 Jan 2007 13:51:50 +0800	[thread overview]
Message-ID: <3877989d0701112151m6816cd4fl4f2a2bdf309d51ac@mail.gmail.com> (raw)
In-Reply-To: <1166012707.22903.4.camel@pcjc2lap>

Since it is somewhat related to ACPI, please open a bug in ACPI
category on bugzilla.kernel.org. It is a great place to track this
kind of issues.

On 12/13/06, Peter Clifton <pcjc2@cam.ac.uk> wrote:
> On Wed, 2006-12-13 at 02:54 -0500, Lincoln Baxter, III wrote:
> > Wow. You're completely right... so this isn't an ACPI issue (directly.)
> >
> > I don't seem to experience any of the other problems you describe, but I
> > do have a different model. I don't have an external lid-switch sensor.
> > Hm.. Suspend doesn't quite work for me either, I'll look into this
> > farther and get back to you.
> >
> > The battery meters and other ACPI functionality is working now with your
> > workaround. Should this be a bug report? Which group should get the
> > report if this is the case?
> >
> > Thanks so much!
> > Lincoln
>
> It was suggested to me to open a kernel bug (possibly starting under
> ACPI), however I never got to it.. I don't know where kernel bugs are
> reported officially, and was busy at the time. (still am). I do try and

bugzilla.kernel.org

> reply to others with the same problems though... finding the webpage
> which suggested that fix was not trivial!

It is not easy to track it in emals.

>
> My lid switch is just above the keyboard, on the right hand side of the
> left hand screen hinge. It is just a tiny piece of plastic protruding
> from the case. Push it, and the screen goes off. Hold it, and wiggle the
> mouse (touchpad), and the naughty screen comes back on.
>
> Most importantly for me, the workaround brings the max CPU speed
> available with speed step back to what it is supposed to be on my
> laptop, and the BIOS actually boots much faster.
>

      parent reply	other threads:[~2007-01-12  5: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
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 [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=3877989d0701112151m6816cd4fl4f2a2bdf309d51ac@mail.gmail.com \
    --to=luming.yu@gmail.com \
    --cc=lincolnbaxter@gmail.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=pcjc2@cam.ac.uk \
    /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