public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Lars Tobias Børsting" <larstobi-zs2scLodJVNRyvKAgBWctw@public.gmane.org>
To: ACPI Devel Mailing List
	<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: ACPI Hotkeys don't work with latest ACPI release
Date: Sat, 05 Feb 2005 13:19:05 +0100	[thread overview]
Message-ID: <8jf8y63fbd2.fsf@panter.stud.ntnu.no> (raw)
In-Reply-To: <1107564000.7783.2.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org> (Andrew Barr's message of "Fri, 04 Feb 2005 19:39:59 -0500")

Andrew Barr <barr.156-ZbGKxL/pcrQ@public.gmane.org> writes:

> I have a 2.6.10 kernel with ACPI 20050125. If my fixed DSDT is compiled
> into the kernel (Dell Inspiron 300m BIOS A07--
> http://acpi.sourceforge.net/dsdt/view.php?id=218), the ACPI hotkeys
> don't work. These are all Fn+* keys--brightness, CRT/LCD switching,
> wireless RF kill. Can anyone tell me why this is?

This is common on the X300 when you use a fixed DSDT with wrong present
memory amount settings. This can easily be fixed by using the correct
values of present memory on the X300, and I think the BIOS on 300m is
quite the same.

Regards,

-- 
Lars Tobias Børsting



-------------------------------------------------------
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-05 12:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-05  0:39 ACPI Hotkeys don't work with latest ACPI release Andrew Barr
     [not found] ` <1107564000.7783.2.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2005-02-05 12:19   ` Lars Tobias Børsting [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-02-05  6:08 Yu, Luming
2005-02-05  6:17 Yu, Luming
2005-02-05 14:58 ` Andrew Barr

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=8jf8y63fbd2.fsf@panter.stud.ntnu.no \
    --to=larstobi-zs2sclodjvnryvkagbwctw@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