Date: Tue, 12 Aug 2025 20:27:47 +0000 From: Jordan Gordeev <jgopensource@proton.me> To: 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) [reproduces again] Message-ID: <4JnDBHlYaAjDciQ_DeelqZkjMkWgG5MTgbLJvZZgppOhKm5CLLmkbN3xCHRb9gVBJi1jYIeSR-QzcZ0yhluPKQr7jC2HMZ4_2ck_k1JbpHQ=@proton.me> In-Reply-To: <67BA742F-CEBA-4AB3-B088-22771C20FF8A@yahoo.com> References: <BBB8EBC8-2A38-468D-B968-FE8C4BDA6DCD.ref@yahoo.com> <BBB8EBC8-2A38-468D-B968-FE8C4BDA6DCD@yahoo.com> <rB59TnyXd_btyd0Lp5E63bTpiSZ9eY-JIJ0Nod63UBUch6gBiumHvc5VL2s1UhLsGOecmBUv8bAu2bv2VoWkPDkC3phbRYeRjAUl-cROagk=@proton.me> <A5B712C4-7ECE-45BC-806C-E7B2532E1F8C@yahoo.com> <67BA742F-CEBA-4AB3-B088-22771C20FF8A@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Monday, 11 August 2025 at 03:31, Mark Millard <marklmi@yahoo.com> wrote:
>=20
> After the updates I'm back to the "serial console"
> is not getting/taking keyboard input (without
> hw.usb.usbhid.enable=3D0 involved).
>=20
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 c=
onfusing 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 t=
he following to /boot/loader.conf will enable debug output from the driver:
hw.hid.hkbd.debug=3D"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.=20
> # usbconfig -l
> ugen1.3: <Virtual Keyboard PARALLELS> at usbus1, cfg=3D0 md=3DHOST spd=3D=
SUPER (5.0Gbps) pwr=3DON (0mA)
>=20
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4JnDBHlYaAjDciQ_DeelqZkjMkWgG5MTgbLJvZZgppOhKm5CLLmkbN3xCHRb9gVBJi1jYIeSR-QzcZ0yhluPKQr7jC2HMZ4_2ck_k1JbpHQ=>