Re: keyboard

[James S. <jsi...@ac...>]

> > This is for a single PS/2 keyboard. What do you see for your setup?
> 
> similar stuff. I'll send the logs later if needed.
> but from what you said below, I understand it means that my primary
> keyboard (ps2) is bound to the console and won't be in /dev/input/event,
> is this correct?

No. For every input device a /dev/input/event should appear if you
are using devfs. Otherwise you have to create the device file yourself
(man mknod). The console system behave indpendent of the userland input
interface. This is a more powerful approach. 

> Actually, I have 2 displays (rage128 agp and g200 pci), 2 keyboards (ps2
> and usb) and 2 rodents (ps2 and usb).

Cool. 

> And I wouldn't mind running concurrently 2 full X desktops off 1 box...
> (could even run q3 multiplayer off that box!?)
> When I start 2 X servers (both using the ps2 keyboard since I couldn't
> work it out) I need to VT switch to change which X is active, I guess
> tha's because they share the same keyboard. If I get one of the Xs to use
> the usb keyboard, will they both be running concurrently then? Or do I need
> something extra...

Well that is a little more complex. I seen another posting about this.

> Also, when using ruby, it boots off the g200 (usually boots off the r128)
> and the kernel boot messages in dmesg do not contain whatever was
> on the console before it switched to the g200, where can I get these early
> messages? And why did they disappear!?

Right now with ruby only vgacon, mdacon, and nvida text mode are
supported. The fbdev layer is incomplete. I have found matrox cards
usually like to be booted first. I know of no way to make one card boot
before another. Petr, you have any ideas ?

> Then, if I try to con2fb to the r128, it does not come on (but it works on
> test7).
> Framebuffer tools (fbset, fbi or fbtv...) all go to the g200, even when I
> specify
> -c /dev/fb1 (the r128), now that's scary! 
> Also, on test7 I need to con2fb to the r128 before I can use it as a
> framebuffer
> device (all modules already loaded...), otherwise the fb mode that gets set is

  How do you get the fbcon layer to even compile for ruby? I didn't think
it compiled. Also alot of the fbcon layer has global variables meaning it
not really multihead safe. I'm rewriting that code to make it really
multihead safe but I'm not finished. 
   The reason con2fb doesn't work is because with the new console
system it automatically allocates 16 VCs to each head. You don't need to
do con2fb because it should be done automatically for you. With your setup
with the fbcon layer you should have 2 consoles come up for you automatically.
The console code also prevents things like VC switching to a different
head than your on.

> > Look at ruby CVS code for xfree86.
> 
> Where is this tree?

Grab the ruby tree and right at the top you see a xfree86 directory.

> > looked it didn't support USB keyboards or /dev/input. Which X server are
> > you running.
> 
> 4.0.1 from CVS (but I must have an old 3.3.6 tree somewhere)
> > XF4.0. With XFree86 it usually takes them 6 months to support something.
> 
> what about doing it myself?
> I was looking around for docs on xinput and the whole input stuff in X4...
> and I didn't find much info.

Go for it. I noticed the lack of docs myself. I atempted to read their
code but it was such a mess I gave up.

MS: (n) 1. A debilitating and surprisingly widespread affliction that
renders the sufferer barely able to perform the simplest task. 2. A disease.

James Simmons  [jsi...@li...]               ____/| 
fbdev/console/gfx developer                             \ o.O| 
http://www.linux-fbdev.org                               =(_)= 
http://linuxgfx.sourceforge.net                            U
http://linuxconsole.sourceforge.net