From: Guest section DW <dwguest@win.tue.nl>
To: Andrzej Krzysztofowicz <ankry@green.mif.pg.gda.pl>
Cc: marekm@amelek.gda.pl, linux-kernel@vger.kernel.org (kernel list)
Subject: Re: PC keyboard unknown scancodes (Power, Sleep, Wake)
Date: Sun, 12 Aug 2001 15:26:25 +0200 [thread overview]
Message-ID: <20010812152625.A15275@win.tue.nl> (raw)
In-Reply-To: <200108120721.JAA05389@green.mif.pg.gda.pl>
In-Reply-To: <200108120721.JAA05389@green.mif.pg.gda.pl>; from Andrzej Krzysztofowicz on Sun, Aug 12, 2001 at 09:21:02AM +0200
On Sun, Aug 12, 2001 at 09:21:02AM +0200, Andrzej Krzysztofowicz wrote:
> > On Sat, Aug 11, 2001 at 08:51:46PM +0200, Marek Michalkiewicz wrote:
> >
> > > these three keys (on a cheap no-name "Designed for Win*" keyboard ;)
> > > produce "unknown scancode" kernel messages when pressed or released.
> > >
> > > Power - e0 5e
> > > Sleep - e0 5f
> > > Wake - e0 63
> >
> > You can use the setkeycodes command to tell the kernel about them.
>
> It doesn't seem to fix the problem:
>
> # dmesg -c
> # setkeycodes e05f 127
> # setkeycodes e05e 127
> # dmesg -c
> [ pressing some keys here ]
> # dmesg -c
> keyboard: unknown scancode e0 5e
> keyboard: unknown scancode e0 5e
> keyboard: unknown scancode e0 5f
> keyboard: unknown scancode e0 5f
>
> Am I doing something wrong ?
Maybe you are using console-tools instead of kbd?
Check with strace that it does the KDSETKEYCODE ioctl.
next prev parent reply other threads:[~2001-08-12 13:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-12 7:21 Andrzej Krzysztofowicz
2001-08-12 13:26 ` Guest section DW [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-08-11 18:51 Marek Michalkiewicz
2001-08-11 21:36 ` Guest section DW
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=20010812152625.A15275@win.tue.nl \
--to=dwguest@win.tue.nl \
--cc=ankry@green.mif.pg.gda.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=marekm@amelek.gda.pl \
/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®