mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ken Moffat <ken@kenmoffat.uklinux.net>
To: Jurriaan <thunder7@xs4all.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: KVM issues with recent 2.6 kernels
Date: Mon, 19 Apr 2004 21:14:41 +0100 (BST)	[thread overview]
Message-ID: <Pine.LNX.4.58.0404192104590.1572@ppg_penguin> (raw)
In-Reply-To: <20040419181159.GA10708@middle.of.nowhere>

On Mon, 19 Apr 2004, Jurriaan wrote:

> Does your KVM also have keys on the kvm to switch? If so, does the
> problem go away if you use those?
>

 I was about to say the problem doesn't appear like that (it just takes
an age to cycle through all 4 boxes), but I thought I'd better try it -
guess what, the alt key is no longer functioning on the duron/2.6.5 box
when I go to it like that.  I've now gone back to it using key presses
and it sorted itself out after I threw in an extra press of the scroll
lock (the xterm was responding, unlike console sessions, it was only the
alt key that seemed to be swallowed).  At least I've now found out a way
to fix the immediate "loss of alt key" problem - thanks !

> Otherwise, perhaps hack drivers/input/keyboard/atkbd.c (dunno if that is
> the correct path) to log when a scroll-lock is received) and then throw
> away that keypress?
>

 Interesting idea, but I've got enough trouble with userspace apps
without hacking the kernel, and anyway /some/ of the scroll-lock
keypresses are needed to get directly to the desired session.

> Good luck,
> Jurriaan
>

-- 
 das eine Mal als Tragödie, das andere Mal als Farce


      reply	other threads:[~2004-04-19 20:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-19 11:36 Ken Moffat
2004-04-19 18:11 ` Jurriaan
2004-04-19 20:14   ` Ken Moffat [this message]

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=Pine.LNX.4.58.0404192104590.1572@ppg_penguin \
    --to=ken@kenmoffat.uklinux.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thunder7@xs4all.nl \
    /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®