From: pyther <pyther@pyther.net>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Corentin Chary <corentincj@iksaif.net>,
Matthew Garrett <mjg59@srcf.ucam.org>,
bugme-daemon@bugzilla.kernel.org, patrick.bregman@gmail.com,
linux-acpi@vger.kernel.org
Subject: Re: [Bugme-new] [Bug 12831] New: Hot/Fn Keys do not work EEEPC 1000HE (eeepc_laptop)
Date: Mon, 09 Mar 2009 16:32:45 -0400 [thread overview]
Message-ID: <94855ae5f6d072e7c9b5920b67fc4c1d@localhost> (raw)
In-Reply-To: <20090309125142.54f707dd.akpm@linux-foundation.org>
On Mon, 9 Mar 2009 12:51:42 -0700, Andrew Morton
<akpm@linux-foundation.org>
wrote:
> (switched to email. Please respond via emailed reply-to-all, not via the
> bugzilla web interface).
>
>
> On Sat, 7 Mar 2009 10:05:56 -0800 (PST)
> bugme-daemon@bugzilla.kernel.org wrote:
>
>> http://bugzilla.kernel.org/show_bug.cgi?id=12831
>>
>> Summary: Hot/Fn Keys do not work EEEPC 1000HE (eeepc_laptop)
>> Product: Drivers
>> Version: 2.5
>> KernelVersion: 2.6.29-rc7
>> Platform: All
>> OS/Version: Linux
>> Tree: Mainline
>> Status: NEW
>> Severity: normal
>> Priority: P1
>> Component: Other
>> AssignedTo: drivers_other@kernel-bugs.osdl.org
>> ReportedBy: pyther@pyther.net
>>
>>
>> Latest working kernel version: 2.6.28.7
>> Earliest failing kernel version: 2.6.29-rc7 (may have been eailier, I
>> haven't
>> tested older rcs)
>> Distribution: Archlinux
>> Hardware Environment: EEEPC 1000HE
>>
>> Problem Description:
>>
>> The function keys on the Asus EEEPC 1000HE do not register any keycodes
/
>> acpi
>> code. However, Fn+F1 (Sleep) and the Power Button register keycodes and
>> work as
>> expected. Another note is that the Fn+F5 and Fn+F6 keys work as expected
>> (brighten and dims the display), but do not give any acpi codes.
>>
>> Here is a copy of my kernel config: http://rafb.net/p/GTQiS467.html
>>
>> If you need any extra information, I'll be more than happy to provide
it.
>> I do
>> not have a good grasp on how acpi works, so please forgive me if I used
>> the
>> wrong terminology.
>>
>>
>> Steps to reproduce:
>> 1. Compile 2.6.29-rc7
>> 2. Run acpi_listen
>> 3. Press Fn+F2-F10 or anyother special key
>>
>> Expected results output of acpi keycode. Actual results no output.
>>
>
> Two people (Patrick and Matthew) are reporting this post-2.6.28
> regression.
>
> Could someone please recategorise the report to something more
> appropriate than drivers_other?
>
> Thanks.
I realized you were talking to Patrick, but I just wanted to say I do not
have pciehp compiled in. Here is my 2.6.29-rc7 kernel config:
http://world.pyther.net/kernel.2.6.29-rc7_config.txt (The rafb.net/paste
one got deleted)
Cheers!
next prev parent reply other threads:[~2009-03-09 20:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-12831-10286@http.bugzilla.kernel.org/>
2009-03-09 19:51 ` [Bugme-new] [Bug 12831] New: Hot/Fn Keys do not work EEEPC 1000HE (eeepc_laptop) Andrew Morton
2009-03-09 20:04 ` Matthew Garrett
2009-03-09 20:32 ` pyther [this message]
2009-03-09 20:37 ` Matthew Garrett
2009-03-09 21:13 ` pyther
2009-03-09 21:14 ` Matthew Garrett
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=94855ae5f6d072e7c9b5920b67fc4c1d@localhost \
--to=pyther@pyther.net \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=corentincj@iksaif.net \
--cc=linux-acpi@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=patrick.bregman@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).