From: sven kissner <sven.kissner@consistencies.net>
To: linux-kernel@vger.kernel.org
Subject: logitech cordless desktop deluxe optical keyboard issues
Date: Sat, 10 Jan 2004 22:30:41 +0100 [thread overview]
Message-ID: <200401102230.54966.sven.kissner@consistencies.net> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
hello,
i use the keyboard mentioned in the topic attached to the ps/2 keyboard port.
most keys can be mapped using lineak or appropriate applications but i have
problems getting some keys to work. i tested this with 2.6.0 and 2.6.1 as
well as with some of the 2.4 series. with wintendo xp, all keys are working
fine using logitech's itouch software.
xev is not displaying keycodes for the special keys not working but i get
various messages by dmesg when pressing them:
<-- snip -->
atkbd.c: Unknown key pressed (translated set 2, code 0x91 on isa0060/serio0).
atkbd.c: Unknown key released (translated set 2, code 0x91 on isa0060/serio0).
atkbd.c: Unknown key pressed (translated set 2, code 0x92 on isa0060/serio0).
atkbd.c: Unknown key released (translated set 2, code 0x92 on isa0060/serio0).
<-- snap -->
on startup, i get the following:
with 2.6.x:
<-- snip -->
serio: i8042 KBD port at 0x60,0x64 irq 1
input: AT Translated Set 2 keyboard on isa0060/serio0
[..]
INIT: version 2.85
Loading /etc/console/boottime.kmap.gz
KDSKBENT: Invalid argument
failed to bind key 265 to value 638
KDSKBENT: Invalid argument
failed to bind key 265 to value 638
<-- snap -->
with 2.4.20 & 2.4.22-ck2 the value is increasing from 128 to 511, restarting
~10 times(!):
<-- snip -->
INIT: version 2.85
Loading /etc/console/boottime.kmap.gz
KDSKBENT: Invalid argument
failed to bind key 128 to value 512
[..]
failed to bind key 511 to value 512
<-- snap -->
if i connect the kb to usb, there are slightly different issues, but let's do
it step-by-step ;). any ideas how to get this working? if you require
additional information, just let me know.
if answering, please put me on cc for i'm not subscribed to the list.
keep on rockin,
sven
- --
..never argue with idiots. they drag you down to their level and beat you with
experience..
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFAAG8MPV/e7f4i4AERAm2aAKCXkcngzoaoVI0caZ9qCnzIx8qSxACdEJtx
VmFnQRAFUhCckPWPbf0PKD8=
=AaJH
-----END PGP SIGNATURE-----
next reply other threads:[~2004-01-10 21:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-10 21:30 sven kissner [this message]
2004-01-11 0:28 Andries.Brouwer
2004-01-11 1:53 ` logitech cordless desktop deluxe optical keyboard issues sven kissner
2004-01-11 4:05 Andries.Brouwer
2004-01-11 8:27 ` sven kissner
2004-01-11 13:58 Andries.Brouwer
2004-01-11 16:05 ` sven kissner
2004-01-11 16:32 ` Andries Brouwer
2004-01-11 18:37 ` sven kissner
2004-01-11 19:03 Andries.Brouwer
2004-01-11 19:35 ` sven kissner
2004-01-11 19:46 ` Andries Brouwer
2004-01-22 22:49 ` sven kissner
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=200401102230.54966.sven.kissner@consistencies.net \
--to=sven.kissner@consistencies.net \
--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®