On Thursday, 14 August 2025 at 00:01, Mark Millard <[email protected]> wrote:
> Jordan Gordeev <jgopensource_at_proton.me> wrote on > > Date: Wed, 13 Aug 2025 18:14:41 UTC : > > > On Wednesday, 13 August 2025 at 08:30, Mark Millard [email protected] wrote: > > > > > Jordan Gordeev <jgopensource_at_proton.me> wrote on > > > > > Okay, you've enabled the generation of debugging output by hkbd(4). What > > did you do with the generated output? > > > Other than the diff's I'd provided (as referenced below)? If usbhid is enabled and you put hw.hid.hkbd.debug="100" in /boot/loader.conf, after rebooting you will see messages like these in dmesg: hkbd_probe: hkbd_probe: hkbd_probe: hkbd_probe: hkbd0: <VMware VMware Virtual USB Keyboard> on hidbus2 hkbd_attach: Parsing HID descriptor of 65 bytes hkbd_parse_hid: Found keyboard event array hkbd_parse_hid: Found key 0xe0 hkbd_parse_hid: Found key 0xe1 hkbd_parse_hid: Found key 0xe2 hkbd_parse_hid: Found key 0xe3 hkbd_parse_hid: Found key 0xe4 hkbd_parse_hid: Found key 0xe5 hkbd_parse_hid: Found key 0xe6 hkbd_parse_hid: Found key 0xe7 hkbd_parse_hid: Found keyboard numlock hkbd_parse_hid: Found keyboard capslock hkbd_parse_hid: Found keyboard scrolllock hkbd_set_leds: leds=0x00 hkbd_set_leds: len=1, id=0 hkbd_set_leds: leds=0x00 hkbd_set_leds: len=1, id=0 If you start typing on the keyboard, the messages will look like these: hkbd_intr_callback: actlen=8 bytes hkbd_intr_callback: modifiers = 0x0000 hkbd_intr_callback: Key 0x28 pressed hkbd_put_key: 0x28 (40) pressed If you see too many of these messages on your first virtual terminal to the point of being unable to use it, switch to the second or subsequent virtual terminals (e.g. Alt+F2). The first one is the kernel's console while the others are not. You could also ssh into the system. Best regards, Jordan Gordeev
