public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Barr <barr.156-ZbGKxL/pcrQ@public.gmane.org>
To: "Yu, Luming" <luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: [SOLVED] RE: ACPI Hotkeys don't work with latest ACPI release
Date: Sun, 06 Feb 2005 13:23:33 -0500	[thread overview]
Message-ID: <1107714213.22960.3.camel@localhost.localdomain> (raw)
In-Reply-To: <3ACA40606221794F80A5670F0AF15F84071415C1@pdsmsx403>

It seems that the DSDT for my laptop has changed. I had been using the
copy I posted to the DSDT pages at acpi.sourceforge.net, but I
discovered that a disassembled copy from /proc/acpi/dsdt was several
dozen kilobytes larger. Fixing this one (same modification as before)
and recompiling and inserting it into my kernel fixed this issue.

My best guess as to why this is is that I replaced the Intel
PRO/Wireless 2100 card in the notebook with an Intel PRO/Wireless
2915ABG card. Interestingly, the new DSDT seems to cure the kernel panic
that I saw using that card with NDISwrapper and WPA-PSK.

Andrew

On Sat, 2005-02-05 at 14:17 +0800, Yu, Luming wrote:
> I mean the original one, and the modified one.




-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl

      parent reply	other threads:[~2005-02-06 18:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-05  6:17 ACPI Hotkeys don't work with latest ACPI release Yu, Luming
2005-02-05 14:58 ` Andrew Barr
2005-02-06 18:23 ` Andrew Barr [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=1107714213.22960.3.camel@localhost.localdomain \
    --to=barr.156-zbgkxl/pcrq@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=luming.yu-ral2JQCrhuEAvxtiuMwx3w@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