From: Warren Turkal <wturkal@cbu.edu>
To: linux-kernel@vger.kernel.org
Subject: [BUG] laptop keyboard, more info
Date: Sun, 23 Mar 2003 20:56:06 -0600 [thread overview]
Message-ID: <200303232056.06284.wturkal@cbu.edu> (raw)
In-Reply-To: <200303220605.54478.wturkal@cbu.edu>
I am not subscribed. Please cc on reply. Thanks.
A terrible description of this bug is included below.
I have successfully narrowed the revisions that could have introduced this
bug. I managed to build a 1.889.289.3 bk revision kernel. This appears to be
the minimum revision which fixes the build bug I experienced in 2.5.64. The
bug exists in this kernel, meaning that the bug was introduces somewhere
between the 2.5.63 (1.889.1.133 bk revision) kernel and the 1.889.289.3 bk
revision kernel. These revisions cover about 1 week of time. I am trying to
build some in between revisions to see if I can narrow even more. Does anyone
know of any craziness that went in between 2.5.63 and 2.5.64 that would have
broken the way my computer reads these keys?
Thanks, Warren Turkal
On Sunday 23 March 2003 08:36 pm, Warren Turkal wrote:
> I am not subscribed. Please cc on replies.
>
> I have a Gateway 600 series notebook. I have been using and testing the
> developmental kernel for some time now. I have just noticed that my
> keyboard''s "fn" key combinations stop working upon booting 2.5.65. They
> worked as recently as 2.5.63 and I could not get 2.5.64 to compile cleanly.
> These key combinations are supposed to make various things happen on my
> laptop. I believe that they are controlled by the bios, as I can see
> results of some while on the bios load screen.
>
> Fn-F1 - Labeled "Help"; don't know what it does
> Fn-F2 - Labeled "Status"; used to show battery status in upper left
> Fn-F3 - Labeled "LCD/CRT"; switch montior output among built in LCD, back
> monitor port, and both
> Fn-F4 - Labeled "Standby"; used to function as the ACPI standby button
> Fn-F9 - Labeled "Pad Lock"; think num lock; strangely, this one still
> work in 2.5.65
> Fn-F10 - Labeled "Scroll Lock"
> Fn-F11 - Labeled "Pause"
> Fn-F12 - Labeled "Break"
>
> I have tested that the Fn-F2 combination works in bios and grub and
> continues to work until the 2.5.65 kernel is loaded.
>
> I think this is a regression in the keyboard handling for the 2.5.65
> kernel.
>
> Like I said before, all of the Fn combinations work in 2.5.63. If anyone
> has a patch from 2.5.63 to something after 2.5.64 that compiles, I would be
> happy to try it. I setup a bitkeeper clone of Linus's latest, so if someone
> could give me some bitkeeper magic to export diffs from 2.5.63 to 2.5.64 in
> a relavant directory (probably drivers/input/keyboard) maybe I could look
> to see what changed, although I don't know if I am skilled enough to find
> errors in the code.
>
next prev parent reply other threads:[~2003-03-24 2:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-22 12:05 [BUG] laptop keyboard Warren Turkal
2003-03-24 2:56 ` Warren Turkal [this message]
2003-03-28 9:05 ` [BUG] laptop keyboard, even more info Arne Koewing
2003-03-28 19:36 ` Felipe Alfaro Solana
2003-03-28 21:50 ` Warren Turkal
2003-03-28 10:41 ` Felipe Alfaro Solana
[not found] ` <200303280828.20070.felix.seeger@gmx.de>
2003-03-29 7:42 ` [BUG] laptop keyboard, tracked to ACPI Warren Turkal
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=200303232056.06284.wturkal@cbu.edu \
--to=wturkal@cbu.edu \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®