From nobody Wed Aug 13 18:14:41 2025 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4c2Gk62nRLz64JjX for ; Wed, 13 Aug 2025 18:14:54 +0000 (UTC) (envelope-from jgopensource@proton.me) Received: from mail-24418.protonmail.ch (mail-24418.protonmail.ch [109.224.244.18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "protonmail.com", Issuer "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4c2Gk35syNz46lW for ; Wed, 13 Aug 2025 18:14:51 +0000 (UTC) (envelope-from jgopensource@proton.me) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=proton.me header.s=protonmail header.b=ErNgzUNF; spf=pass (mx1.freebsd.org: domain of jgopensource@proton.me designates 109.224.244.18 as permitted sender) smtp.mailfrom=jgopensource@proton.me; dmarc=pass (policy=quarantine) header.from=proton.me DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=proton.me; s=protonmail; t=1755108887; x=1755368087; bh=B8PY1ehLVenDLBBFQO+5LQUVg67EgaeLxg39H9HPkFY=; h=Date:To:From:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector; b=ErNgzUNFNfJJsv8EjygYrHPnOHrTWO0EYC6SlN6e32CEI9hmQn+bbMnSjTD/cbWr5 RGe9tmMgZLIYsEY8CQZU9qE93npk59dZ4keh3ZHcq+AKegG8qhC+GRx6P1cQmkXLhb pNdgjxXDEYNgCjvfp4NlDOxbjj6cRr6k10me6ootD2CpmMzrDjnewQswoqLaxsYxN0 VnSPYrR5pXgKGeWBL9tO7SHrY76FWEO6im20J0mwLR4z9DQ13bf50+HfzdhHJ1DGz+ Qa+8P7Ab3ivTcPfyIkueyhqF838aBaBhH7+FQ7Z4dNzWh+VO6fsXrHA99M66i2GuC5 hL71qziULeo/A== Date: Wed, 13 Aug 2025 18:14:41 +0000 To: FreeBSD Current From: Jordan Gordeev Subject: Re: Example context needing use of hw.usb.usbhid.enable=0 : serial console keyboard input under Parallels (aarch64) [reproduces again] Message-ID: In-Reply-To: References: Feedback-ID: 125078299:user:proton X-Pm-Message-ID: eae9759667fff3c1af9916ffc1ffb5ba49e05c8d List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spamd-Result: default: False [-4.40 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.999]; DMARC_POLICY_ALLOW(-0.50)[proton.me,quarantine]; RWL_MAILSPIKE_EXCELLENT(-0.40)[109.224.244.18:from]; R_DKIM_ALLOW(-0.20)[proton.me:s=protonmail]; R_SPF_ALLOW(-0.20)[+ip4:109.224.244.0/24]; MIME_GOOD(-0.10)[text/plain]; RCPT_COUNT_ONE(0.00)[1]; ARC_NA(0.00)[]; DKIM_TRACE(0.00)[proton.me:+]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_ALL(0.00)[]; ASN(0.00)[asn:62371, ipnet:109.224.244.0/24, country:CH]; MIME_TRACE(0.00)[0:+]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; MISSING_XM_UA(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; RCVD_COUNT_ZERO(0.00)[0]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[109.224.244.18:from] X-Rspamd-Queue-Id: 4c2Gk35syNz46lW X-Spamd-Bar: ---- On Wednesday, 13 August 2025 at 08:30, Mark Millard wro= te: > Jordan Gordeev wrote on >=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, usi= ng confusing terminology should be avoided. >=20 >=20 > "Text console"? Some other suggestion to avoid misleading? It is not emul= ating any general graphics console as far as I can tell. "Text console" is fine. > > The hkbd(4) driver detects the keyboard and attaches successfully. Addi= ng the following to /boot/loader.conf will enable debug output from the dri= ver: > > hw.hid.hkbd.debug=3D"100" >=20 >=20 > Added for now. Okay, you've enabled the generation of debugging output by hkbd(4). What di= d you do with the generated output? It's the most important piece of inform= ation in this situation. > dmsg -a output capture differences from different boots follow. There are three cases here: Case A: usbhid is disabled; the keyboard works Case B: usbhid is enabled; the keyboard works Case C: usbhid is enabled; the keyboard doesn't work You recently observed Case B. The difference in dmesg between Case B and Ca= se C is what is of interest. > > Also, when the keyboard doesn't work does the mouse work? >=20 >=20 > This is not a graphics window context. Clicking in that window captures t= he mouse/cursor and stops displaying it until Ctrl+Alt are both pressed at = the same time "too free the cursor", as it says. >=20 If you start moused, you would get a mouse cursor in the text console. Howe= ver, with usbhid enabled, the mouse will always not work (the cursor won't = move at all) because the current version of moused does not support hms(4) = devices. Forget about the mouse for a while. One extra thing to try is resetting the keyboard with a command such as thi= s: usbconfig -d /dev/ugen1.3 reset If the keyboard doesn't work, the command might make it work. Perhaps the o= pposite is also possible. Best regards, Jordan Gordeev