From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: xserver-kdrive 1.4 and USB keyboard
Date: Wed, 17 Sep 2008 12:09:53 +0200 [thread overview]
Message-ID: <gaql1h$b9$1@ger.gmane.org> (raw)
In-Reply-To: <f96d234e0809161439tc0ed410jad0ae837edd24e29@mail.gmail.com>
Cliff Brake wrote:
> On Tue, Sep 16, 2008 at 4:53 PM, Koen Kooi<k.kooi@student.utwente.nl> wrote:
>> Cliff Brake wrote:
>>> Does anyone have this combination working yet?
>>>
>>> On my system, ctrl-alt-f1 does not work, and caps/num lock lights do
>>> not work when X is running. Keyboard works fine at the console.
>> I suspect that's because kdrive 1.4 lacks a default keymap. Graeme provided
>> a really bare-bones one that makes X access keys (e.g. xkbd,
>> matchbox-keyboard). Making USB keyboards work properly proved to be too much
>> work, so I am now using full-blown Xorg on anything with a usb-keyboard.
>> Having said that, the A-z keys did work on beagle, the fact that left-mouse
>> button clicks produced a 'q' was the final straw (clock on window running
>> powertop - boom).
>> Something is very broken in kdrive, which might be due to people working on
>> it only care for tablets from a certain scandinavian company.
>
> Thanks. Yes, you are correct. I can get arrow keys, and enter to
> work, but not cap/num lock or Ctrl-Alt-F1.
In that case fixing the keymap would be the way to go. You'll need to
poke the resident X exports on how to do that properly, though :)
regards,
Koen
>
> Cliff
>
next prev parent reply other threads:[~2008-09-17 10:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-16 20:27 xserver-kdrive 1.4 and USB keyboard Cliff Brake
2008-09-16 20:53 ` Koen Kooi
2008-09-16 21:39 ` Cliff Brake
2008-09-17 10:09 ` Koen Kooi [this message]
2008-09-17 16:25 ` Cliff Brake
2008-09-17 16:33 ` Graeme Gregory
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='gaql1h$b9$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.