public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: fire-eyes <sgtphou@fire-eyes.dynup.net>
To: linux-kernel@vger.kernel.org
Subject: 2.6.1: atkbd.c errors + mouse errors with a belkin KVM
Date: Mon, 19 Jan 2004 13:08:47 -0500	[thread overview]
Message-ID: <400C1D2F.7020503@fire-eyes.dynup.net> (raw)

I'm seeing some strange behavior using kernel 2.6.1 and a Belkin KVM. I 
have talked to two others who have seen the same problem. This did not 
happen in 2.6.0 or any 2.4 kernel.

When switching ports using the keyboard, that is hitting scroll lock 
twice and then the port # I want ( 1 - 16), then coming back the same 
way, I often get the following error:

kernel: atkbd.c: Unknown key released (translated set 2, code 0x7a on 
isa0060/serio0).

I have also seen this same error while switching from X11 to console, 
but only once. In that one case, I lost mouse control, and keyboard 
control, and was unable to regain either. I had to reboot to rectify the 
situation.

I'm not sure if this happens when pushing the buttons on the front of 
the kvm.

KVM Information:

Belkin Omniview Matrix2 , Model F1DM216T
Maufacturer URL: 
http://catalog.belkin.com/IWCatProductPage.process?Merchant_Id=1&Product_Id=122933

Is there any further information I can submit to help solve this?

             reply	other threads:[~2004-01-19 18:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-19 18:08 fire-eyes [this message]
2004-01-19 19:29 ` 2.6.1: atkbd.c errors + mouse errors with a belkin KVM Andries Brouwer
2004-01-19 20:43   ` Vojtech Pavlik
2004-01-19 21:40     ` Andries Brouwer
2004-01-19 21:50       ` Vojtech Pavlik

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=400C1D2F.7020503@fire-eyes.dynup.net \
    --to=sgtphou@fire-eyes.dynup.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