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

Jordan Gordeev <jgopensource_at_proton.me> wrote on
Date: Sun, 17 Aug 2025 18:40:37 UTC :

> 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.

I'll try such and report back.

But first I'll report that I for this Parallels under
macOS context I use:

# cat /boot/device.hints 
# This is for virtio_gpu --for avoiding its use under Parallels:
# dmesg -a | grep -i "virtio.*gpu"
# virtio_pci1: <VirtIO PCI (modern) GPU adapter> mem 0x10000000-0x17ffffff,0x18008000-0x18008fff,0x18000000-0x18003fff at device 10.0 on pci0
hint.virtio_pci.1.disabled="1"

This was to get the simple text console. I never got
virtio_gpu to work when I was first trying to get the
context working and was not directly interested in
it at all.

I'm not sure how this issue might mix with your
requested tests. I might need to do the disable.

===
Mark Millard
marklmi at yahoo.com