mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: sven kissner <sven.kissner@consistencies.net>
To: Andries.Brouwer@cwi.nl
Cc: linux-kernel@vger.kernel.org
Subject: Re: logitech cordless desktop deluxe optical keyboard issues
Date: Sun, 11 Jan 2004 02:53:03 +0100	[thread overview]
Message-ID: <200401110253.25040.sven.kissner@consistencies.net> (raw)
In-Reply-To: <UTC200401110028.i0B0SpL08329.aeb@smtp.cwi.nl>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

hi andries, 

thanks for your reply.

On Sunday 11 January 2004 01:28, Andries.Brouwer@cwi.nl wrote:
> I have seen patches by Vojtech somewhere that already did this,
> but looking at current bk source it seems that they have not been
> applied yet.

where can i find those patches? kml?

> Anyway, I released kbd-1.10 last week or so, and it ignores the
> kernel NR_KEYS but tries to adapt dynamically to the kernel.
> It would not come with this error message, I suppose.

the message doesn't appear anymore, but installing is giving me the following:
<-- snip -->
Setting up kbd (1.10-1) ...
Looking for keymap to install:
de-latin1-nodeadkeys
cannot open file de-latin1-nodeadkeys
Loading /etc/console/boottime.kmap.gz
<-- snap -->
i guess i just screwed up the paths ;)

> : 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)
>
> This is something different, a key without associated keycode.
> That is normal. If it really has high bit set it is a bit unusual.
> (What does showkey -s show?)

showkey -s is giving me exactly the same:
<-- snip -->
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 -->

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)

iD8DBQFAAKySPV/e7f4i4AERAm0FAJ97N/CT3PfUcJZK2+4gXy7e3lDFgwCgl/T2
qRVMrl5ik2NZ3dtGdxounJQ=
=8I8H
-----END PGP SIGNATURE-----

  reply	other threads:[~2004-01-11  1:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-11  0:28 Andries.Brouwer
2004-01-11  1:53 ` sven kissner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-01-11 19:03 logitech cordless desktop deluxe optical keyboard issues Andries.Brouwer
2004-01-11 19:35 ` sven kissner
2004-01-11 19:46   ` Andries Brouwer
2004-01-22 22:49     ` 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  4:05 Andries.Brouwer
2004-01-11  8:27 ` sven kissner
2004-01-10 21:30 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=200401110253.25040.sven.kissner@consistencies.net \
    --to=sven.kissner@consistencies.net \
    --cc=Andries.Brouwer@cwi.nl \
    --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®