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

Hello Mark,

Not sure if I understood correctly but lets take a look at UPDATING entry:

```
20250730:
        The usbhid(4) USB HID driver is now enabled by default, and will be
        used in preference to other USB HID drivers like ukbd(4), ums(4),
and
        uhid(4).  Work on a FIDO/U2F driver and moused(8) is in progress.
        The default is being switched now so that we can find and fix any
        additional issues prior to FreeBSD 15.0.

        To revert to the previous USB HID driver behavior, set the loader
        tunable hw.usb.usbhid.enable=0.
```

In my context, on a laptop, I need to use `tunable hw.usb.usbhid.enable=0`
to get console mouse working.
There are some moused changes to support usbhid as work in progress.

Cheers,

Mark Millard <marklmi@yahoo.com> escreveu (domingo, 10/08/2025 à(s) 07:33):

> 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.
>
> It may be that something else needs to be changed
> or reverted. I'm just noting the delta from the
> preexisting context that I'd previously
> established.
>
> With the line in place, it reverted back to
> what I'd previously established as a working
> context.
>
>
> ===
> Mark Millard
> marklmi at yahoo.com
>
>
>

-- 
Nuno Teixeira
FreeBSD UNIX:  <eduardo@FreeBSD.org>   Web:  https://FreeBSD.org