From: William Park <opengeometry@yahoo.ca>
To: Boszormenyi Zoltan <zboszor@freemail.hu>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Multiple keyboard/monitor vs linux-2.6?
Date: Fri, 12 Dec 2003 16:43:10 -0500 [thread overview]
Message-ID: <20031212214310.GA744@node1.opengeometry.net> (raw)
In-Reply-To: <fa.da53dsa.dho216@ifi.uio.no>
On Fri, Dec 12, 2003 at 09:13:28AM +0000, Boszormenyi Zoltan wrote:
> Hi,
>
> is there a way to assign different keyboards to different vcs?
> I would like to set up a machine that has 2 keyboards, 2 mice and
> 2 videocards and run XFree-4.x on both heads. The videocard/monitor and
> mouse settings are easy to set up but I cannot find a device setting
> for the keyboard in man XF86Config. How can I do it with mainline kerne=
> ls?
>
> After some googleing I found something called "backstreet ruby"
> http://startx.times.lv/eng-faq.html
> This gave me this info (howto in a nutshell):
>
> 1. Boot with kernel option "dumbcon=N" to activate N dummy console.
> 2. cat /proc/bus/input/devices gives the input devices, search for keyb=
> oard
> entries.
> 3. To assign a keyboard to a VT, feed the keyboard Phys= entry into
> a VT, e.g. echo "isa0060/serio0/input0" > /proc/bus/console/00/keyb=
> oard
> 4. Start the X server on the proper VT.
>
> The functionality can be found at linuxconsole.sourceforge.net.
> Will this be included into mainline near term? Say 2.6.[12]?
> The ruby-2.6 is against 2.6.0-test9 so it's almost uptodate.
Does it work?
I have 2 keyboard/mouse/video setup as well, but I followed
http://cambuca.ldhs.cetuc.puc-rio.br/multiuser/
by Miguel Freitas with 2.4.23 kernel, because you have to unload
'keybdev' USB module. Kernel-2.6.0 doesn't seem to give me that choice.
In my XF86Config, I had to use
Section "InputDevice"
Identifier "USB Keyboard"
Driver "keyboard"
Option "Protocol" "usbev"
Option "Device" "/dev/input/event2"
Option "XkbRules" "xfree86"
Option "XkbModel" "pc104"
Option "XkbLayout" "us"
EndSection
for the USB keyboard. Note the /dev/input/event2 and "Xkb*" lines --
they were necessary.
Both are mentioned in XFree-Local-multi-user-HOWTO. Even though the
HOWTO is more for Backstreet Ruby, I couldn't make head or tail of it.
--
William Park, Open Geometry Consulting, <opengeometry@yahoo.ca>
Linux solution for data management and processing.
next parent reply other threads:[~2003-12-12 21:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.da53dsa.dho216@ifi.uio.no>
2003-12-12 21:43 ` William Park [this message]
2003-12-13 13:14 ` Multiple keyboard/monitor vs linux-2.6? Helge Hafting
2003-12-13 21:12 ` William Park
2003-12-15 12:18 ` Helge Hafting
2003-12-15 20:38 ` William Park
2003-12-15 17:18 ` Pavel Machek
2003-12-12 22:27 Svetoslav Slavtchev
2003-12-12 22:45 ` William Park
2003-12-12 23:09 ` Svetoslav Slavtchev
2003-12-12 23:46 ` William Park
2003-12-13 1:05 ` Svetoslav Slavtchev
2003-12-13 10:20 ` John Bradford
2003-12-13 10:28 ` Svetoslav Slavtchev
-- strict thread matches above, loose matches on Subject: below --
2003-12-12 10:03 Svetoslav Slavtchev
2003-12-12 9:12 Boszormenyi Zoltan
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=20031212214310.GA744@node1.opengeometry.net \
--to=opengeometry@yahoo.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=zboszor@freemail.hu \
/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