Re: Example context needing use of hw.usb.usbhid.enable=0 : serial console keyboard input under Parallels (aarch64) [reproduces again]

On Monday, 11 August 2025 at 03:31, Mark Millard <marklmi@yahoo.com> wrote:
> 
> After the updates I'm back to the "serial console"
> is not getting/taking keyboard input (without
> hw.usb.usbhid.enable=0 involved).
> 
Serial console is typically understood to mean a console over a serial link like RS-232. If you end up reporting this bug to the bug database, using confusing terminology should be avoided.

> # dmesg -a | grep -e eybo -e kbd
> hkbd0: <Parallels Virtual Keyboard> on hidbus2
> hkbd1: <Parallels Virtual Keyboard> on hidbus3

The hkbd(4) driver detects the keyboard and attaches successfully. Adding the following to /boot/loader.conf will enable debug output from the driver:
    hw.hid.hkbd.debug="100"

Please provide the output if you can't analyze it yourself. Initial output from device probing and output when pressing keys are both relevant. 

> # usbconfig -l
> ugen1.3: <Virtual Keyboard PARALLELS> at usbus1, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=ON (0mA)
> 

The keyboard seems to be attached to the XHCI USB controller (USB 3.0). If Parallels offers such a choice, as an experiment try to force it to use the EHCI USB controller (USB 2.0) instead.

If you have the dmesg output from when the keyboard worked, you can compare to dmesg when the keyboard doesn't work.

Also, when the keyboard doesn't work does the mouse work?

Best regards,
Jordan Gordeev