Re: keyboard bound to [dummy device]

[Helge H. <hel...@hi...>]

Hugo Vanwoerkom wrote:

>Hi List!!!
>
>With Helge's help I got 2.6.7 + framebuffers +vc's
>running. Looks great.
>
>Have 2 X's running framebuffer vc's also on primary
>display.
>
>However: 2nd X on PCI card shows the login screen but
>the keyboard doesn't work. (It does on 2.4.x)
>  
>
You usually have to tell X to use the appropriate vt. If you don't,
X grabs the next free vt which is likely bound to the first keyboard.
(Std. linux setup runs gettys at vt1 through vt6, and first X on vt7.
Another X will then grab vt8, which is bound to the first keyboard.
Press ctrl+alt+f8 and the first keyboard brobably works on the
second display.   This is not what you want.

A command line for starting X, taken from /etc/X11/xdm/Xservers:
/usr/X11R6/bin/X vt7 -dpi 100 -nolisten tcp -deferglyphs 16
Note the explicit "vt7" in there.
Ruby 2.6 allocate vt1 through vt16 to the first keyboard,
and vt17 through vt32 to the second.

So, specify "vt17" for the second xserver, and it will use
the second keyboard.  You may also want to
specify a different xf86config file, but I guess you
already figured that out, considering that X came up at all.

Don't specify "vt17" if you're running a getty there, if so,
specify vt18 or whatever higher number you have that
isn't in use.  Note that console switching can be troublesome
on the second console, so I recommendrunning only X on it,
at least in the beginning.

>Dmesg shows this:
>keyboard: [AT Raw Set 2 keyboard] bound to [dummy
>device] vc:17-17
>keyboard: [AT Translated Set 2 keyboard] bound to
>[VESA VGA] vc:1-16
>
>Those messages come out of vt_proc.c, which...
>has Aivils' name on it!
>
>Aivils, what am I doing wrong? Why doesn't he say "AT
>Translated Set 2 keyboard" and VESA VGA for vc:17-17?
>
>Thanks! Getting closer!
>
Are you using a "dumbcon=1" parameter on the kernel command line?
That is ok with X, but not with fbcon.  (vt17 works either way, but
a vt17 bound to dumbcon isn't displayed anywhere.  So it is
unusable for gettys and other console uses.)
If you have two framebuffers, one for each card, then I recommend
using framebuffer console and no dumbcon for ruby 2.6.7.

"dumbcon=1" is the solution for those without fbcon, because
plain vgacon will only grab one keyboard and something (i.e. dumbcon)
mus grab the second keyboard and assign VT numbers to it.

Helge Hafting