Input problem with kdrive/ Xvesa

[Steve Kreyer]

Daniel Stone wrote:
> On Mon, Apr 16, 2007 at 12:51:50AM +0200, Steve Kreyer wrote:
>   
>> Daniel Stone wrote:
>>     
>>> That should work just fine (does for me with Xomap), but you might need
>>> to pass '-keybd keyboard'.
>>>       
>> Hm, there's no such option. The only options I've found are +kb to
>> enable X keyboard extension and -kb to disable it. But +kb has no
>> effect. Is it possible that Xvesa /kdrive uses an input device such as
>> /dev/input/event0 for keyboard events? I ask, because at the target
>> system there's no such device file for the keyboard ...
>>     
>
> There is such an option, I just forgot to add it to the help. :)
>   
Ok, I see.
I've try to start Xvesa via

Xvesa -mouse mouse,/dev/mouse,3button -keybd keyboard

but with the same result, that the keyboard does not react. I wonder
because I can't even enable/disable the "Num-lock" key of the keyboard,
when Xvesa is running. So maybe the source of the problem is located
somewhere else?
> The evdev driver is currently non-functional (for those who care, I've
> rewritten it, and will release it when this throat infection decides
> it's had enough --- two weeks and counting thus far -- and I can get
> back to work), so right now it just uses the standard keyboard input
> layer.
>
> There's code in Xvesa to add a default keyboard, but I assume that it's
> broken.
>
> Cheers,
> Daniel
<http://dict.leo.org/ende?lp=ende&p=/gQPU.&search=soon>
Regards,
Steve
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3245 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.x.org/archives/xorg/attachments/20070416/65622c7e/attachment.bin>