Re: problem with XFree86 keyboard

[dave g. <giv...@ya...>]

I connected a 2nd PS2 keyboard in place of my PS2
mouse, so I now have 2 PS2 keyboards. I configured
hotplug and input.rc/input.agent, and using input.rc I
can control which of my 2 keyboards goes on VT0 or
VT1.

I start my first X on vt06, and it runs just
fine(though temporarily w/o a mouse). The first X is
set to use the keyboard assigned to VT0, and it does.

I set my second X to use the VT1 keyboard by using the
"Dev Phys" option and setting it to
isa0060/serio1/input0. I set it to use the evdev
driver. From what I've read, doing that would normally
require applying a patch to XFree86, but apparently
that is already applied to the XFree86 shipped with
debian? though I'm not sure if that applies to debian
woody, the distribution I'm running.

Then I try starting my second X on vt08, which I've
set to use the keyboard assigned to VT1. I've tried
starting the second X either by running the server
directly (ie 'X :1 -xf86config /etc/X11/XFC_1 vt08')
and by running a modified startx script (startx1).
Now, with either one, I don't see anything on the
screen, its just black, no cursor, the monitor did
come out of sleep mode, though. Also, I can press CAPS
lock and NUM lock on the VT1 keyboard and the
appropriate light does appear on the VT1 Keyboard.

But, also as before, the VT0 keyboard doesn't work.
When I type, nothing appears on 1st screen, nor does
pressing CAPS lock or NUM lock cause a light to come
on.

My first X is running KDE which I have set to display
a clock in the lower right corner. Once I start my
second X, the clock on the first X doesn't update,
even after several minutes. I sshed into the machine
from another and tried loading konsole on the 2nd X,
but got an error message that it couldn't connect to
it. I then tried loading konsole onto the first X, it
seemed to be running, but nothing appeared on that
screen(much like the clock not updating).

I have also tried using the "Dev Phys" option with the
'evdev' driver on my first X, which also causes the
same problem (screen goes black, can't be contacted by
an X client). Is it possible there is something wrong
w/ evdev or that it is not installed?

Even though I continue to have these problems with X,
my keyboards ONLY work on the second X I start, why?
Why does the screen on my first X not update?

I started my kernel with 'dumbcon=2'

In the event I do have to apply the 'evdev' patch
mentioned in the 'how to', do I apply that to the
XFree86 source code? which version?

:)

--- Aivils Stoss <Aiv...@un...> wrote:
> 
> >I appreciate your help, but I still haven't been
> able
> >to get this to work. I've tried a number of things,
> >which I've detailed below.
> >
> >When starting the secondary (keyboardless) X
> windows
> >on vt08 or above having started the first
> (keyboard) X
> >windows on vt07 or below, the second X grabs my
> >keyboard and mouse and pressing CTRL+ALT+Fx doesn't
> >get me back to the first (keyboard) X.
> >
> >Or, I start the secondary (keyboardless) X windows
> on
> >vt07 or below and then switch to a console tty
> running
> >mingetty, then start the primary (keyboard) X but
> then
> >have to press CTRL+ALT+F7 to get the secondary X to
> >appear, at which point, I can no longer access the
> >first X.
> >
> >Or I can start both, one on vt07 and one on vt06,
> but
> >they won't appear at the same time.
> 
> This is normal linus tree kernel feature :)
> Same hapen under vanilla linux.
> 
> >This seems to be something that could be fixed in
> your
> >backstreet ruby patch to prevent the secondary
> >(keyboardless) X windows from grabbing my keyboard
> &
> >mouse. But, I don't understand how it works at all,
> so
> >I was hoping that maybe you could fix this. It
> would
> >really, really help me!
> 
> I michmatch my own versions.
> 2.4.22-20030910
> Use vt8 for secondary xf86. This one mean,
> You should start 1st xf86
> startx -- vt7
> after open xterm, konsole or similar and run 2nd
> startx -- :1 -xf86config XF86Config-1 vt8
> where kernel commandline dumbcon=1, and
> /etc/X11/XF86Config-1 contain config for 2nd xf86
> 
> >tried using vt08/9(dumb1), vt16/17(dumb2)
> >
> >won't work when both are on separate dumbs
> >won't work when both are on the same vga
> >
> >keyboard doesn't work when 2nd X is on vt09
> 
> Truth. Right! This one is Your solution!
> 
> Range of ttys /dev/tty0-/dev/tty7 works as vanilla
> linux
> Another range /dev/tty8-/dev/tty15 again works as
> vanilla
> linux. This is ruby ploy. If You start xf86 on
> secondary
> range of tty, then You cannot manipulate with
> primary range
> of tty.
> This feature You describe mulptiple times. You
> should start
> 1st normal xf86 with keyboard and after 1st xf86
> init start
> 2nd keyboardless xf86 from xterm. You can use
> xdm,gdm to
> start 1st xf86 - this one show login. And You can
> start 2nd
> from system init script.
> su ultraman -c "startx -- :1 -xf86config
> XF86Config-1 vt8"
> where ultraman is username, which exists in Your
> system.
> Please do not try switch to text mode console to
> start 2nd xf86.
> This is wrong way. Use 1st xf86 to start 2nd xf86 or
> 2nd xf86
> will be started by script. I recommend script,
> because You can
> choose user for 2nd xf86. 2nd xf86 user homedir
> contain right
> file for programs under 2nd xf86
> /home/ultraman/.xinitrc
> Your main homedir contain other .xinitrc
> 
> Text mode console will be available only after both
> xf86 server
> start. This is rule. If runs 2 xf86, then text mode
> console
> may show garbage. If You press Ctrl-Alt-Fx on 2nd
> xf86 should
> not happen anything, of course Your 2nd xf86 is
> keyboardless,
> but You might borrow PS/2 keyboard for first time.
> Ruby works nice with 2 PS/2 keyboards.
> 
> >tried:
> >    loading keyboardless X on vt07
> >    was able to get to a command-line tty,
> >keyboardless-X dissappears
> >    then loading keyboard X on vt10
> >    brought keyboardless X back on screen by
> pressing
> >CTRL+ALT+F7
> >    wasn't able to switch back to keyboard-X on
> vt10
> >b/c CTRL+ALT+Fx
> >        key sequence won't reach DUMBx
> 
> Afresh truth!!!
> 
> >My hardware is:
> >i686 debian-woody
> >kernel-2.4.22 w/ backstreet ruby path
> 2.4.22-20030910
> >nvidia GeForce4 for the secondary X
> >ATI radeon 7000 for the primary X
> 
> Should work.
> 
> Aivils
> 
> --- Aivils Stoss <Aiv...@un...> wrote:
> I wrote bullshit
> 




__________________________________
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com