From nobody Wed Dec 6 19:09:03 2023 X-Original-To: freebsd-arm@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 4Sln566FdFz53pn7 for ; Wed, 6 Dec 2023 19:09:14 +0000 (UTC) (envelope-from mike@karels.net) Received: from mail2.karels.net (mail2.karels.net [3.19.118.201]) (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 (2048 bits) client-digest SHA256) (Client CN "freebsd", Issuer "freebsd" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Sln564Mg1z3HZg for ; Wed, 6 Dec 2023 19:09:14 +0000 (UTC) (envelope-from mike@karels.net) Authentication-Results: mx1.freebsd.org; none Received: from mail2.karels.net (localhost [IPv6:0:0:0:0:0:0:0:1]) by mail2.karels.net (8.17.1/8.17.1) with ESMTP id 3B6J94UG081559; Wed, 6 Dec 2023 13:09:04 -0600 (CST) (envelope-from mike@karels.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=karels.net; s=mail2; t=1701889744; bh=KNrEEs3uvUPK2kPKqWAnJbjv/eA1kELhz21XANJv1Dw=; h=From:To:Cc:Subject:Date:In-Reply-To:References; b=lP0ET9AamNr6E6Cu67VR385hL9hxP8eO54kBqg7szGUjQV8/IbCipsr/H6EVMhxrb F7wnmfYH1XPjtE6IgA5nIsarNGM7t6QhSBV5bG0pgNEaaDE5uImOdDgQOEH+JtkT/9 8PPD9ex5EIh2K91umeEQO8vf9jJtosfPFceDA2NMRNbg2oxWxsSoACRCbCMUkVRwKW EVkUfenmBcyMnJ2uLjVmYMmIKPNqLbV52HQ0oZETKcsH2wlaE0j1qry7M0SJr/2PpA n597VTr1NjYHJQXQggnKBJMyvDd8o8/2HY44nndxn4l4/kyHL4jO4qqAdluPq1/DEr JoQDA2MSMP6gw== Received: from [10.0.2.130] ([73.62.165.147]) by mail2.karels.net with ESMTPSA id Zc9iFNDGcGWVPgEAs/W3XQ (envelope-from ); Wed, 06 Dec 2023 13:09:04 -0600 From: Mike Karels To: "Elmar K. Bins" Cc: freebsd-arm@freebsd.org Subject: Re: [Raspi4 13.2] Keyboard woes Date: Wed, 06 Dec 2023 13:09:03 -0600 X-Mailer: MailMate (1.14r5964) Message-ID: In-Reply-To: References: List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org MIME-Version: 1.0 Content-Type: text/plain X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:16509, ipnet:3.16.0.0/14, country:US] X-Spamd-Bar: ---- X-Rspamd-Queue-Id: 4Sln564Mg1z3HZg On 6 Dec 2023, at 8:10, Elmar K. Bins wrote: > Re Nuno, > > thanks for looking at this. > > eduardo@freebsd.org (Nuno Teixeira) wrote: > >>> Is keyboard original from raspberry? >> https://lists.freebsd.org/archives/freebsd-arm/2023-July/002810.html > > I didn't even know they sold a keyboard. This looks like a generic rebrand. > I concur with Mark, I don't think this makes any difference. > > Because you asked; I've tested a whole bunch of keyboards.. > > - original IBM Model M from 1983 > - Replica Model F from 2022 > - Korean generic USB keyboard > - Apple M0115 on an ADB->USB converter > - Apple M3501 on an ADB->USB converter > - HHKB > - Das Keyboard 4 > - really old Olivetti on a PS2->USB converter > - Cherry G80-3000 from 2018 > - some generic more or less ancient ones lying around > > *All* of them work in U-Boot and after FBSD is way into the boot process. > *None* of them do anything in between (i.e. beastie). > Changing the physical port used makes no difference. > > Note: There is nothing on the screen to either indicate a problem or > recognition of the keyboard. > > To me it appears that the drivers (maybe USB in general, maybe only HID) are > only loaded way after beastie. (If so, why?) > > > So... cool that you could solve this by using a Pi brand keyboard, but I don't > think this is actually what solved the issue. > > So, my questions stand: > > > Is this a known issue with USB keyboards on the Pi (or Pi4)? > (Never saw this on other hardware, also with USB keyboards) > > Is there a workaround (like a magic boot.conf setting)? > > If anybody has solved this with a generic keyboard...please... I'd really hate > going back to Linux on that thing. No workaround, but a couple of data points: - I don't have this problem on a 4 GB RPi 4 of the original revision, although the firmware has been updated. I tested with 13.2 and 14.0. - However. I do have the problem on an RPi 3B+ with either 13.2 or 14.0. btw, the loader doesn't use loadable drivers, so driver loading is not the problem. Mike