From owner-freebsd-arm@freebsd.org Tue Dec 17 02:33:21 2019 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 042711D86DC for ; Tue, 17 Dec 2019 02:33:21 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 47cMdD6MRDz3C8m for ; Tue, 17 Dec 2019 02:33:20 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from mail-qk1-f181.google.com (mail-qk1-f181.google.com [209.85.222.181]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) (Authenticated sender: kevans) by smtp.freebsd.org (Postfix) with ESMTPSA id C7AF640D7 for ; Tue, 17 Dec 2019 02:33:20 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: by mail-qk1-f181.google.com with SMTP id w127so7055255qkb.11 for ; Mon, 16 Dec 2019 18:33:20 -0800 (PST) X-Gm-Message-State: APjAAAXVIXALuAEZ4tjlTUkE4I+kfoM93/ZF0aQ1BPvJEMvqIDXCgDPv A+sbyov2Ic+nWydz+GbQnMwhKdpdMJDHM8M5pf8= X-Google-Smtp-Source: APXvYqzp+6ex0GxpOyZBmaTZv+A5RcKUGp3/50CPI9dMt5Cw+/FFPyfUnNBhdpXMvWMrnAOMMXmqNiJdi5drMLiDvZk= X-Received: by 2002:ae9:e10e:: with SMTP id g14mr2848891qkm.430.1576550000218; Mon, 16 Dec 2019 18:33:20 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Kyle Evans Date: Mon, 16 Dec 2019 20:33:08 -0600 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: How to boot freebsd on rpi4b? To: ykla Cc: "freebsd-arm@freebsd.org" Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Dec 2019 02:33:21 -0000 On Mon, Dec 16, 2019 at 8:30 PM ykla wrote: > ykla =E4=BA=8E 2019=E5=B9=B412=E6=9C=8817=E6=97=A5=E5= =91=A8=E4=BA=8C =E4=B8=8A=E5=8D=8810:27=E5=86=99=E9=81=93=EF=BC=9A >> Kyle Evans =E4=BA=8E 2019=E5=B9=B412=E6=9C=8817=E6= =97=A5=E5=91=A8=E4=BA=8C =E4=B8=8A=E5=8D=8810:04=E5=86=99=E9=81=93=EF=BC=9A >>> >>> On Mon, Dec 16, 2019 at 7:50 PM ykla wrote: >>> > >>> > Hi, I download latest version 12.12 current 13 img and write in TF ca= rd. >>> > Then I download rpi-firmware(2019-12-05 16:15:16) and extract and co= py it >>> > in BOOT partition. And look at my screen shows me that stop boot on l= o0 >>> > state. I know it can't support USB/PCI/ethernet and I just want to in= stall >>> > it. Thanks. >>> >>> That's a most curious failure mode... if you got to the point where >>> we're bringing up lo0, it should have either been fine or blown up >>> terribly in an obvious way -- I'll reimage tomorrow-ish based on the >>> latest snapshot and see if I can reproduce. >>> >>> In the meantime, can you post a transcript of the boot? >>> >>> Thanks, >>> >>> Kyle Evans >> >> New error: stopped at >> Warning: no time-of-day clock registered. system time will not be set ac= curately. > > I just reboot and bugs show: > lo0 :link state change to UP. > Can you scroll up to just above that sdhci output and take another picture? (above the =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D) Thanks, Kyle Evans