From nobody Wed Dec 07 19:21:43 2022 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 4NS6bh6DMBz4jcYr for ; Wed, 7 Dec 2022 19:21:52 +0000 (UTC) (envelope-from adr@SDF.ORG) Received: from mx.sdf.org (mx.sdf.org [205.166.94.24]) (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 "mx.sdf.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4NS6bh0Qrsz3JvP for ; Wed, 7 Dec 2022 19:21:51 +0000 (UTC) (envelope-from adr@SDF.ORG) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of adr@SDF.ORG designates 205.166.94.24 as permitted sender) smtp.mailfrom=adr@SDF.ORG; dmarc=pass (policy=none) header.from=sdf.org Received: from sdf.org (IDENT:adr@sdf.org [205.166.94.16]) by mx.sdf.org (8.15.2/8.14.5) with ESMTPS id 2B7JLhx7003133 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256 bits) verified NO); Wed, 7 Dec 2022 19:21:44 GMT Received: from localhost (adr@localhost) by sdf.org (8.15.2/8.12.8/Submit) with ESMTP id 2B7JLhsL011249; Wed, 7 Dec 2022 19:21:43 GMT Date: Wed, 7 Dec 2022 19:21:43 +0000 (UTC) From: adr To: Mark Millard cc: freebsd-arm@freebsd.org Subject: Re: FreeBSD on RPI4 B 8G rev 1.4 In-Reply-To: <3ebd7048-213e-8920-dfe5-44f6a1e5f3ac@SDF.ORG> Message-ID: <5f1ba830-60e-407d-c09f-d75ab0946ca6@SDF.ORG> References: <9c587c3-b6e5-fbe2-7dcc-f7d98dd47ace@SDF.ORG> <047DB634-2D87-402D-A65C-A4F517E042BD@yahoo.com> <3ebd7048-213e-8920-dfe5-44f6a1e5f3ac@SDF.ORG> 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; charset=US-ASCII; format=flowed X-Spamd-Result: default: False [-3.80 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.998]; DMARC_POLICY_ALLOW(-0.50)[sdf.org,none]; R_SPF_ALLOW(-0.20)[+ip4:205.166.94.0/24]; MIME_GOOD(-0.10)[text/plain]; FREEMAIL_TO(0.00)[yahoo.com]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org]; ASN(0.00)[asn:14361, ipnet:205.166.94.0/24, country:US]; MIME_TRACE(0.00)[0:+]; ARC_NA(0.00)[]; RCVD_TLS_LAST(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; TO_DN_SOME(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; MID_RHS_MATCH_FROM(0.00)[] X-Rspamd-Queue-Id: 4NS6bh0Qrsz3JvP X-Spamd-Bar: --- X-ThisMailContainsUnwantedMimeParts: N On Tue, 6 Dec 2022, adr wrote: > Yes, I could be more specific. When I said "the only way > I can run..." I mean the official images don't even boot. > > The errors differ but they were related to xhci I think. I'll make > some test with the u-boot in ports, but after reading your experience > with other rev 1.4 boards I wonder if this could be related with > the eeprom firmware, if this is even possible. It was a usb hub with sd card reader. There was no card there, u-boot choked trying to read it. Yes, how silly of me. I would appreciate if someone share his/her experience with 13.1 release, stable and current. It's there any advantage of using stable|current at this moment? Regards, adr.