From: Felipe Alfaro Solana <felipe_alfaro@linuxmail.org>
To: Arne Koewing <ark@gmx.net>
Cc: Warren Turkal <wturkal@cbu.edu>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] laptop keyboard, even more info
Date: 28 Mar 2003 20:36:50 +0100 [thread overview]
Message-ID: <1048880210.598.1.camel@teapot> (raw)
In-Reply-To: <87y92zr57o.fsf@localhost.i-did-not-set--mail-host-address--so-tickle-me>
On Fri, 2003-03-28 at 10:05, Arne Koewing wrote:
> >> 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....
>
> I don't think this is caused by the input-layer. Linux is not passing
> Fn-X keypresses to your BIOS. If you've enabled ACPI that ought to be
> the reason for this.
Also, XFree86 4.3.0 seems to inhibit Fn key combinations on some
scenarios. On my laptop, I can't use Fn+F3 to switch between LCD and CRT
while running X.
________________________________________________________________________
Felipe Alfaro Solana
Linux Registered User #287198
http://counter.li.org
next prev parent reply other threads:[~2003-03-28 19:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-22 12:05 [BUG] laptop keyboard Warren Turkal
2003-03-24 2:56 ` [BUG] laptop keyboard, more info Warren Turkal
2003-03-28 9:05 ` [BUG] laptop keyboard, even " Arne Koewing
2003-03-28 19:36 ` Felipe Alfaro Solana [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2003-03-28 14:00 [BUG] laptop keyboard, even more info wturkal
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=1048880210.598.1.camel@teapot \
--to=felipe_alfaro@linuxmail.org \
--cc=ark@gmx.net \
--cc=linux-kernel@vger.kernel.org \
--cc=wturkal@cbu.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.