From nobody Thu Nov 25 20:16:58 2021 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 5455F18BAA09 for ; Thu, 25 Nov 2021 20:17:10 +0000 (UTC) (envelope-from jdhurtado@orbiware.com) Received: from mail-ua1-x935.google.com (mail-ua1-x935.google.com [IPv6:2607:f8b0:4864:20::935]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4J0TgV1dFVz3kPX for ; Thu, 25 Nov 2021 20:17:10 +0000 (UTC) (envelope-from jdhurtado@orbiware.com) Received: by mail-ua1-x935.google.com with SMTP id l24so14599697uak.2 for ; Thu, 25 Nov 2021 12:17:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orbiware.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=I/kyBDGBjVBg+62VGhge3N97FfHQLDbVYe++5PTX7DE=; b=EmUanfr2L6lXBkYzEqGFH83I00KYmjPxf2ixfqp+cMralFVXuxBuZaANzYZRls7Uvk D4qIAtQEisH8lrBEnXwTR6n4OfhAygd8ihusPK4C07p8LN8DMIniN7xI4bRwJ8HZfx/l uKQKeyP3NSzc2tJmnRXDDTPAixq70ZFLum6dKrfJAI1sRDCqIyGMNoIGbQBJdYQ5l/gZ KtUb1HT5wQ+dNW8B9p7pamFMNPMcFJr7vdJP7oEwlm78euTLH2Gg6cXkKZnDLUOnXuvH KJfIK/y4bkYGpZNpC7BND61zoAOEHJrYGtCuxTYhZzSd4AVlfCFH/ReA/faQTUbLDRKe Vj4A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=I/kyBDGBjVBg+62VGhge3N97FfHQLDbVYe++5PTX7DE=; b=M2IDZPd9S8ORtrWyW38Kxf5yrafGId+vvCyY09Uppnok8kHFuiUtzlWnVptHFhHbtr MHzzcQd2cM3WBpd7TL6ViRILxIMd+pSBnEqYPBdliyEiMmeFcuJIMpepF5/63DEbF2hV HEAdWUFVPf+Utgr9JRmWaivMTSXdM3asWPRxqLt0pyi0q1lUJL9AHKipIcVdpPlfoxV9 ycSXkmoa+mXZNL7BQcXfu284ik/+M3//a8ODm/P4uSgkCSfj3s5f/6IP/LYeagxZ/iXV KGFp3wwF9ohVN245YgOrm6FY++RhnT6zeH9Ks89SM+C9DtydZQmmkuFveCArR2Bk9+py dMZA== X-Gm-Message-State: AOAM532GOB3s3l0JNOdSS5QIoQDpDNMviCSvrYzmjsDuPIagS7liMn9b WDOp+erj237hjngOAltiaUEHzhHXKWiHQ5o4LMWzN/rq1tfm X-Google-Smtp-Source: ABdhPJxKUNyfSbMx1VHWaGaQnI7lFoiAzZ7bxAZ4df+xux6BJyd9VvwXqnqP9/3mFGTgPUsIzoWQR0RE60CZ5S4xMVM= X-Received: by 2002:ab0:7095:: with SMTP id m21mr30602198ual.82.1637871429638; Thu, 25 Nov 2021 12:17:09 -0800 (PST) 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 References: <20211124155352.GA26072@www.zefox.net> <6CCD061E-DCDA-46E0-AE19-76EA1B30E56F@yahoo.com> <69E3CEF1-87D0-405B-B132-7D6A6A4EA056@yahoo.com> <1229E940-5DAB-4D49-AB14-E804296D10BC@yahoo.com> In-Reply-To: From: Juan David Hurtado G Date: Thu, 25 Nov 2021 15:16:58 -0500 Message-ID: Subject: Re: 13.0-RELEASE Poor performance on Raspberry pi 3 B+ To: Mark Millard Cc: Free BSD , bob prohaska Content-Type: multipart/alternative; boundary="000000000000c06f8405d1a2a881" X-Rspamd-Queue-Id: 4J0TgV1dFVz3kPX X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: Y --000000000000c06f8405d1a2a881 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Thanks, I've used `sysutils/u-boot-rpi3` (for the 3B+) and copied the u-boot.bin file to the sd card before the first boot. ``` root@generic:~ # strings /boot/msdos/u-boot.bin | grep "U-Boot 2" U-Boot 2021.07 (Nov 12 2021 - 01:50:18 +0000) ``` Now I'm U-Boot 2021.07 and at the same 0.4MHz :) I'll definitely wait for the new microSD to arrive hoping that it will work= . PS: Current card says HC I in its label and U3. Weird is that other systems do work well with it. El jue, 25 nov 2021 a las 14:29, Mark Millard () escribi=C3=B3: > On 2021-Nov-25, at 09:55, Juan David Hurtado G > wrote: > > > >> There are: v1.1, V1.2, and v1.4 revisions of that. > >> Which? > > > > Raspberry Pi 3 Model B Plus Rev 1.3 > > Raspberry Pi 4 Model B Rev 1.1 > > In a few days I likely will have access to a 4 GiByte RPi4B > Rev 1.1 . > > >> This is not what I've been using (2021.04) but I no > >> longer remember whatever I knew about the differences > >> in behavior. > > > > I've made a firmware update using `rpi-update` on the rpi 3 and > > `rpi-eeprom-update` on the rpi 4 (while on raspios). > > Same 0.4MHz so far on both of them when using FreeBSD. > > > > As for the label on the SoC... I have heat sinks in both of them :) > > I wonder if there is a command that I can use to get that information > > without removing the heat sinks. > > For the RPi4B: being an older variant (v1.1) would mean > 2711ZPKFSB06BOT . 2711ZPKFSB06COT only showed up more > recently. (I'm not aware of any software query equivalent > to the labeling on the SOC. But not being Rev 1.4 (or later), > finding the label explicitly should not matter.) > > For the RPi3B+: I'm not aware of ever needing to know any > labeling on the SOC. > > I focus on the RPi4B's as I at least have access to a variant > and should soon have access to a match. No RPi3's currently > and I've never had access to a RPi3B+. There haev been past > reports of RPi3B+ oddities on the lists as I remember. > > I normally do my own buildworld buildkernel and install > such. I build with tailoring, such as -mcpu-cortex-a72 > for targeting RPi4B's and other Cortex-A72 systems. Thus > my normal context would not match in an audit vs. your > context. And I've picked other things like RPi* firmware > versions based on experiments. (Various releases have > historically been problematical.) > > Other than running one USB related bug in FreeBSD via > my -mcpu=3Dcortex-a72 builds, I've not had mismatches > in behavior in general. > > When I've access to a 4 GiByte RPi4B Rev 1.1 I'll produce > a microsd card from an official 13.0-RELEASE image (so > no -p? at the time) and see what happens when using it to > boot the 4 GiByte RPi4B Rev 1.1 . > > I'll look up the eeprom version in use in the RPi4B Rev 1.1 > when I have access and report what it is. I definately > updated it in order to have the usb (no microsd card) style > of booting be possible. It will be another thing to compare. > (It is also something that an installed-files audit can > not cover.) > > So far the one notable difference in our context's is > your context's U-Boot 2020.10 vs. the 2021.04 in my > context. > > I can capture a binary byte sequence of the output of > a boot, such as verbose one. Looking for differences > in such might prove useful, given well matching contexts > if my results do not match yours for the frequency > involved. > > =3D=3D=3D > Mark Millard > marklmi at yahoo.com > ( dsl-only.net went > away in early 2018-Mar) > > --=20 Juan David Hurtado G (+57) 319 252 3773 www.orbiware.com --000000000000c06f8405d1a2a881--