From: Helge Hafting <helgehaf@aitel.hist.no>
To: Zoltan Szecsei <zoltans@geograph.co.za>
Cc: linux-kernel@vger.kernel.org
Subject: Re: multiple independent keyboard kernel support
Date: Wed, 19 Oct 2005 21:23:18 +0200 [thread overview]
Message-ID: <20051019192318.GA21589@aitel.hist.no> (raw)
In-Reply-To: <43566DCE.5040705@geograph.co.za>
On Wed, Oct 19, 2005 at 06:01:18PM +0200, Zoltan Szecsei wrote:
> Hi Helga (et al),
>
> I'm just back on this issue and am trying to make changes to the basic
> xorg.conf without yet connecting the 2nd VGA,Kyb & mouse.
>
> I thought if I set up a template for the config then it would be easier
> to copy & make changes for when I connect the 2nd KVM devices.
>
> I'm having a problem with the "Dev Phys" option as I keep getting:
> (EE) Generic Keyboard: cannot register with evdev brain
> No core keyboard.
>
> (man xorg.conf does not show "Dev Phys" - should it not be "Device" ??
>
> The real issue is that I cannot find the keyboard device in /dev/input
> (Ubuntu 5.04 )
> In /dev/input I only have 6 devices: event0, 1 and 2; mice, mouse0 and ts0
>
> Are you able to tell me what parameter to put in this Option "Dev Phys" ?
>
> TIA,
> Zoltan
>
(USe a 2.6 kernel)
$ cat /proc/bus/input/devices
On my machine:
I: Bus=0003 Vendor=09da Product=001a Version=0001
N: Name="A4Tech RF USB Mouse"
P: Phys=usb-0000:00:10.2-2/input0
H: Handlers=mouse0 event0
B: EV=7
B: KEY=ff0000 0 0 0 0
B: REL=303
I: Bus=0011 Vendor=0001 Product=0002 Version=ab83
N: Name="AT Raw Set 2 keyboard"
P: Phys=isa0060/serio1/input0
H: Handlers=kbd event1
B: EV=120013
B: KEY=402000000 3802078f840d001 f2ffffdfffefffff fffffffffffffffe
B: MSC=10
B: LED=7
I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
N: Name="AT Translated Set 2 keyboard"
P: Phys=isa0060/serio0/input0
H: Handlers=kbd event2
B: EV=120013
B: KEY=402000000 3802078f840d001 f2ffffdfffefffff fffffffffffffffe
B: MSC=10
B: LED=7
Look for lines saying Handlers=kbd eventX
In the same block, you find Phys=<something>
Copy this into xorg.conf, yielding Dev Phys=<something>
The proc/bus/input/devices file tells you about all input devices,
such as keyboards, mice, joysticks... Take care not trying to
interpret a mouse as a keyboard.. :-)
Helge Hafting
next prev parent reply other threads:[~2005-10-19 19:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-01 11:28 Zoltan Szecsei
2005-09-01 12:22 ` Vojtech Pavlik
2005-09-01 13:07 ` Zoltan Szecsei
2005-09-01 13:24 ` Vojtech Pavlik
2005-09-01 14:48 ` Martin Mares
2005-09-01 16:38 ` Vojtech Pavlik
2005-09-11 22:36 ` Helge Hafting
2005-09-12 16:03 ` Bjorn Helgaas
2005-09-12 20:47 ` Kyle Moffett
2005-09-13 16:20 ` Bjorn Helgaas
2005-09-11 22:34 ` Helge Hafting
2005-09-12 7:01 ` Zoltan Szecsei
2005-10-19 16:01 ` Zoltan Szecsei
2005-10-19 19:23 ` Helge Hafting [this message]
2005-09-01 13:35 Svetoslav Slavtchev
2005-09-01 14:06 ` Zoltan Szecsei
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=20051019192318.GA21589@aitel.hist.no \
--to=helgehaf@aitel.hist.no \
--cc=linux-kernel@vger.kernel.org \
--cc=zoltans@geograph.co.za \
/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®