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

On Sunday, 10 August 2025 at 12:16, Mark Millard <marklmi@yahoo.com> wrote:

> Until I added the line shown by:
> 
> # grep hw.usb.usbhid.enable /boot/loader.conf
> hw.usb.usbhid.enable=0
> 
> I did not any more get:
> 
> ugen1.3: <Parallels Virtual Keyboard> at usbus1
> 
> ukbd0 on uhub1
> ukbd0: <Parallels Virtual Keyboard, class 0/0, rev 3.00/1.10, addr 2> on usbus1
> 
> kbd1 at ukbd0
> ukbd1 on uhub1
> ukbd1: <Parallels Virtual Keyboard, class 0/0, rev 3.00/1.10, addr 2> on usbus1
> 
> 
> running FreeBSD main under Parallels --but got instead:
> 
> hcons0: <Parallels Virtual Keyboard Consumer Control> on hidbus3
> 
> 
> The input to the console window in Parallels
> did not work for the hidbus3 one.
> 

When usbhid is enabled USB keyboards should appear as hkbd(4) devices. Do you see any lines mentioning hkbd in dmesg? If not, try adding "hw.hid.hkbd.debug=100" to /boot/loader.conf in the hope that hkbd will produce some debug messages. Try also loading the hkbd module and any modules on which it depends via loader.conf because that might affect the outcome.

When reporting problems such as this, you should provide the version number of FreeBSD (exact commit ID), version number of Parallels, whether you have any VM tools installed for better integration between FreeBSD and Parallels, and because this is a USB problem, the output of "usbconfig -v" (at least the part describing the keyboard).

Best regards,
Jordan Gordeev