Date: Sun, 10 Aug 2025 10:32:37 -0700 From: Mark Millard <marklmi@yahoo.com> To: Jordan Gordeev <jgopensource@proton.me> Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: Example context needing use of hw.usb.usbhid.enable=0 : serial console keyboard input under Parallels (aarch64) [no longer reproduces] Message-ID: <A5B712C4-7ECE-45BC-806C-E7B2532E1F8C@yahoo.com> In-Reply-To: <rB59TnyXd_btyd0Lp5E63bTpiSZ9eY-JIJ0Nod63UBUch6gBiumHvc5VL2s1UhLsGOecmBUv8bAu2bv2VoWkPDkC3phbRYeRjAUl-cROagk=@proton.me> References: <BBB8EBC8-2A38-468D-B968-FE8C4BDA6DCD.ref@yahoo.com> <BBB8EBC8-2A38-468D-B968-FE8C4BDA6DCD@yahoo.com> <rB59TnyXd_btyd0Lp5E63bTpiSZ9eY-JIJ0Nod63UBUch6gBiumHvc5VL2s1UhLsGOecmBUv8bAu2bv2VoWkPDkC3phbRYeRjAUl-cROagk=@proton.me>
next in thread | previous in thread | raw e-mail | index | archive | help
On Aug 10, 2025, at 07:51, Jordan Gordeev <jgopensource@proton.me> = wrote: > On Sunday, 10 August 2025 at 12:16, Mark Millard <marklmi@yahoo.com> = wrote: >=20 >> Until I added the line shown by: >>=20 >> # grep hw.usb.usbhid.enable /boot/loader.conf >> hw.usb.usbhid.enable=3D0 >>=20 >> I did not any more get: >>=20 >> ugen1.3: <Parallels Virtual Keyboard> at usbus1 >>=20 >> ukbd0 on uhub1 >> ukbd0: <Parallels Virtual Keyboard, class 0/0, rev 3.00/1.10, addr 2> = on usbus1 >>=20 >> kbd1 at ukbd0 >> ukbd1 on uhub1 >> ukbd1: <Parallels Virtual Keyboard, class 0/0, rev 3.00/1.10, addr 2> = on usbus1 >>=20 >>=20 >> running FreeBSD main under Parallels --but got instead: >>=20 >> hcons0: <Parallels Virtual Keyboard Consumer Control> on hidbus3 >>=20 >>=20 >> The input to the console window in Parallels >> did not work for the hidbus3 one. >>=20 >=20 > 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=3D100" 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. >=20 > 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). I'm now unable to reproduce the issue. I had reproduced it multiple times before sending to the list, mostly to note a type of context with observed lack of operation. (I've no problem with using hw.usb.usbhid.enable=3D0 for my context.) I'm to be updating FreeBSD and I see Parallels has a new version. So it looks like gathering and reporting more about how things are would not be of much use. I'll report more if I get the problem again. =3D=3D=3D Mark Millard marklmi at yahoo.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?A5B712C4-7ECE-45BC-806C-E7B2532E1F8C>