NetBSD-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: netbsd (i386 9.0) vs. USB Keyboard/Video/Mouse switches (and X11) ("Greg A. Woods") writes:

>not on these old machines, and I don't know how to type function keys
>via the serial console either, something that's necessary to drive some
>firmware UIs).

Dell and most others use the convention

ESC 1 -> F1 .. ESC 9 -> F9
ESC 0 -> F10
ESC ! -> F11
ESC @ -> F12

>However things got worse when I cycled the KVM to another server and
>back.  Suddenly it seemed as if a key was held down and repeating in the
>login window.  Pressing other keys changed which key was repeating, but
>didn't stop the repeating.

Yes, I've seen KVM servers that send a keypress when switching sources
but never the keyrelease and that can confuse the repeat logic. The
only solution I found was to turn off keyrepeat.

>The following kernel messages appear when cycling the KVM and look
>"normal"/OK (to me):

>[ 96163.108666] wsmouse0: detached
>[ 96163.108666] ums0: detached
>[ 96163.108666] uhidev0: detached
>[ 96163.108666] uhidev0: at uhub0 port 1 (addr 2) disconnected
>[ 96163.208734] wskbd0: disconnecting from wsdisplay0
>[ 96163.208734] wskbd0: detached
>[ 96163.208734] ukbd0: detached
>[ 96163.208734] uhidev1: detached
>[ 96163.208734] uhidev1: at uhub0 port 2 (addr 3) disconnected
>[ 96170.263343] uhidev0 at uhub0 port 1 configuration 1 interface 0
>[ 96170.263343] uhidev0: ELAN Microelectronics (0x4f3) USB+PS/2 Optical Mouse (0x230), rev 1.10/24.58, addr 2, iclass 3/1
>[ 96170.273352] ums0 at uhidev0: 3 buttons and Z dir
>[ 96170.273352] wsmouse0 at ums0 mux 0
>[ 96171.824385] uhidev1 at uhub0 port 2 configuration 1 interface 0
>[ 96171.824385] uhidev1: CHICONY (0x4b3) USB NetVista Full Width Keyboard (0x3025), rev 1.10/1.02, addr 3, iclass 3/1
>[ 96171.824385] ukbd0 at uhidev1
>[ 96172.234655] wskbd0 at ukbd0 mux 1
>[ 96172.234655] wskbd0: connecting to wsdisplay0

If the X server is configured for wsmux (not wsmouse0), then it
shouldn't see anything of this.

>Getting X stable with the built-in video card and the monitor I have
>doesn't seem worthwhile until the keyboard issue is fixed, but just for
>fun, as promised, the xdm, Xserver, and dmesg logs follow.

It might be helpful to configure X for the modesetting driver or wsfb.

                                Michael van Elst
                                "A potential Snark may lurk in every tree."

Home | Main Index | Thread Index | Old Index