[Bug 194718] New: vt(4): Keyboard not working properly when not using kbdmux(4)

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194718

            Bug ID: 194718
           Summary: vt(4): Keyboard not working properly when not using
                    kbdmux(4)
           Product: Base System
           Version: 11.0-CURRENT
          Hardware: Any
                OS: Any
            Status: Needs Triage
          Severity: Affects Only Me
          Priority: ---
         Component: kern
          Assignee: freebsd-bugs at FreeBSD.org
          Reporter: dumbbell at FreeBSD.org

When using kbdmux(4), which is the default in all supported versions of
FreeBSD, the keyboard is working properly in the console and in an X session:

$ kbdcontrol -i < /dev/ttyv0 
kbd1:
    kbdmux0, type:AT 101/102 (2)

$ xev
(...)
KeyPress event, serial 30, synthetic NO, window 0x2600001,
    root 0x2c3, subw 0x0, time 25050869, (525,686), root:(1486,706),
    state 0x10, keycode 45 (keysym 0x6b, k), same_screen YES,
    XLookupString gives 1 bytes: (6b) "k"
    XmbLookupString gives 1 bytes: (6b) "k"
    XFilterEvent returns: False

KeyRelease event, serial 33, synthetic NO, window 0x2600001,
    root 0x2c3, subw 0x0, time 25050973, (525,686), root:(1486,706),
    state 0x10, keycode 45 (keysym 0x6b, k), same_screen YES,
    XLookupString gives 1 bytes: (6b) "k"
    XFilterEvent returns: False

However, when kbdmux is disabled through "hint.kbdmux.0.disabled=1" in
/boot/loader.conf, the keyboard isn't reported correctly by kbdcontrol:

$ kbdcontrol -i < /dev/ttyv0 
kbd0:
    0, type:generic (0)

And under X, the keyboard doesn't work at all. After the first keystroke,
xev(1) receives invalid keyboard events in an infinite loop:
KeyPress event, serial 30, synthetic NO, window 0x1200001,
    root 0x80, subw 0x0, time 81112, (639,380), root:(640,400),
    state 0x0, keycode 203 (keysym 0x0, NoSymbol), same_screen YES,
    XLookupString gives 0 bytes: 
    XmbLookupString gives 0 bytes: 
    XFilterEvent returns: False

KeyRelease event, serial 33, synthetic NO, window 0x1200001,
    root 0x80, subw 0x0, time 81804, (639,380), root:(640,400),
    state 0x0, keycode 203 (keysym 0x0, NoSymbol), same_screen YES,
    XLookupString gives 0 bytes: 
    XFilterEvent returns: False

KeyPress event, serial 33, synthetic NO, window 0x1200001,
    root 0x80, subw 0x0, time 81804, (639,380), root:(640,400),
    state 0x0, keycode 203 (keysym 0x0, NoSymbol), same_screen YES,
    XLookupString gives 0 bytes: 
    XmbLookupString gives 0 bytes: 
    XFilterEvent returns: False

KeyRelease event, serial 33, synthetic NO, window 0x1200001,
    root 0x80, subw 0x0, time 81845, (639,380), root:(640,400),
    state 0x0, keycode 203 (keysym 0x0, NoSymbol), same_screen YES,
    XLookupString gives 0 bytes: 
    XFilterEvent returns: False

Even the first keystroke is incorrect (here, it should be 'k').

The same situation tested with syscons works. kbdcontrol reports that atkbd0 is
connected.

-- 
You are receiving this mail because:
You are the assignee for the bug.