Date: Thu, 13 Feb 2020 11:35:18 -0700 (MST) From: Ross Alexander <rwa@athabascau.ca> To: freebsd-arm@freebsd.org Subject: Re: freebsd-arm Digest, Vol 720, Issue 4 Message-ID: <alpine.BSF.2.22.395.2002131054010.60424@autopsy.pc.athabascau.ca> In-Reply-To: <mailman.67.1581422401.8606.freebsd-arm@freebsd.org> References: <mailman.67.1581422401.8606.freebsd-arm@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> Date: Tue, 11 Feb 2020 07:41:36 +0100
> From: freebsd@x86.ch
> To: bob prohaska <fbsd@www.zefox.net>
> Cc: freebsd-arm@freebsd.org
> Subject: Re: RPI4 Install r357606 test 09.02.2020 failed
> Message-ID:
> <20200211074136.Horde.uoO9uVx71HIGULsxJJY1f7a@webmail.x86.ch>
> Content-Type: text/plain; charset=3Dutf-8; format=3Dflowed; DelSp=3DYes
>
> hi bob
>
> for your information
>
> FreeBSD bsdrasp3 13.0-CURRENT FreeBSD 13.0-CURRENT r343104 GENERIC? arm64
>
> that runs perfectly on the rpi3b+
FWTIW,
Last login: Sat Feb 1 09:40:33 2020 from auwow2.bogons
FreeBSD 13.0-CURRENT (GENERIC-NODEBUG) #2 r356767: Tue Feb 11 13:27:57=
MST 2020
There seems to be general agreement on r356767 as the last
"sees all cpus, runs stably" kernel. My /boot contains,
in part,
rpi3:/u0/rwa > ls -ld /boot/kernel*
lrwxr-xr-x 1 root wheel 14 Feb 11 18:17 /boot/kernel -> kernel.r=
356767
drwxr-xr-x 2 root wheel 13312 Dec 11 09:28 /boot/kernel.r355553
drwxr-xr-x 2 root wheel 13312 Jan 11 14:18 /boot/kernel.r356595
drwxr-xr-x 2 root wheel 13312 Feb 11 18:14 /boot/kernel.r356767
drwxr-xr-x 2 root wheel 13312 Jan 20 04:56 /boot/kernel.r356904
drwxr-xr-x 2 root wheel 13312 Jan 31 16:23 /boot/kernel.r357318
drwxr-xr-x 2 root wheel 13312 Feb 1 19:12 /boot/kernel.r357356
drwxr-xr-x 2 root wheel 13312 Feb 9 13:03 /boot/kernel.r357644
As you can see, I've tried r356904, r357318, r357356, r357644 and no
solution yet - but I know some smart folk are working hard on it, they
will prevail :)
Having said that, here's my puzzle - I use crochet to build little
test images. I last pulled it down from github 14 Nov 2019 via
git clone https://github.com/freebsd/crochet.git
(and pulling it down today and doing a 'diff -r' says that nothing
has happened.) I've got pretty recent copies of the dependancies;
aubey2:/u0/cr-wk > pkg info -E -x rpi
rpi-firmware-1.20190925.g20200109
u-boot-rpi-2019.10
u-boot-rpi2-2019.10
u-boot-rpi3-2019.10
u-boot-rpi4-2019.10
BUT the mmscd images don't recognize the gpart partitions on
my rpi3's usb ssd any more.
I will provide better info when I get home and have a couple of hours
to collect boot listings. In short, what's broken in u-boot 2019.10,
or what config change does it need to see gpart partitions on a USB
device?
regards,
Ross
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D
Ross Alexander, (780) 675-6823 desk / (780) 689-0749 cell, rwa@athabascau.c=
a
54.71593 N 113.30835 W
"By the study of Boltzmann I have been unable to understand
him. He could not understand me on account of my shortness, and
his length was and is an equal stumbling block to me."
-- James Clerk Maxwell
--
This communication is intended for the use of the recipient to whom it is a=
ddressed, and may contain confidential, personal, and or privileged informa=
tion. Please contact us immediately if you are not the intended recipient o=
f this communication, and do not copy, distribute, or take action relying o=
n it. Any communications received in error, or subsequent reply, should be =
deleted or destroyed.
---
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.22.395.2002131054010.60424>