Date: Sun, 17 Aug 2025 18:40:37 +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: <Bz8ulI1In9JCMZ0uzuAoTYTIZpZJsZKzMA752nO42nG9DP4iXK_nm1CKiNhg5mfO9gErfPsM0HAE0zjF4gKHIo4NnvWv7_5VruuvABOgKkE=@proton.me> In-Reply-To: <7C8C2BE0-828E-494D-AF51-AA026CA000C5@yahoo.com> References: <7C8C2BE0-828E-494D-AF51-AA026CA000C5.ref@yahoo.com> <7C8C2BE0-828E-494D-AF51-AA026CA000C5@yahoo.com>
index | next in thread | previous in thread | raw e-mail
On Thursday, 14 August 2025 at 21:51, Mark Millard <marklmi@yahoo.com> wrote: > Have you been implicitly expecting a debug kernel instead of > kernel.GENERIC-NODEBUG ? I had previously provided the text > (note the "GENRIC-NODEBUG"): > I was unaware that the -NODEBUG kernel also disables the hkbd(4) debugging output. > Now testing the debug kernel with hw.hid.hkbd.debug="100" : > It now provides the dmesg -a text you have been > looking for all along. Sorry for the previously bad test > context. > What you get in dmesg from the hkbd(4) driver looks very very normal. It's what you would expect from a fully functioning keyboard. Can you try booting from an install image of FreeBSD 14.3-RELEASE with usbhid enabled? You have to escape to the loader prompt and execute "set hw.usb.usbhid.enable=1". Report whether the keyboard works in the installer. Also try an install image for CURRENT such as FreeBSD-15.0-CURRENT-arm64-aarch64-20250807-02f394281fd6-279407-bootonly.iso where you don't have to manually enable usbhid as it is already enabled by default. Best regards, Jordan Gordeevhelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Bz8ulI1In9JCMZ0uzuAoTYTIZpZJsZKzMA752nO42nG9DP4iXK_nm1CKiNhg5mfO9gErfPsM0HAE0zjF4gKHIo4NnvWv7_5VruuvABOgKkE=>