Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 9 Oct 2020 17:21:52 -0700
From:      Mark Millard <marklmi@yahoo.com>
To:        Klaus Cucinauomo <maciphone2@googlemail.com>
Cc:        Robert Crowston <crowston@protonmail.com>, Kyle Evans <kevans@freebsd.org>, freebsd-arm@freebsd.org
Subject:   Re: RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting)
Message-ID:  <B4AF1099-0049-4E5E-A951-6615E950A965@yahoo.com>
In-Reply-To: <83BA1DDB-C725-470C-B382-9D229860E2F1@googlemail.com>
References:  <D8BDF95A-D6A8-4E95-A0CE-D53068E8355B.ref@yahoo.com> <D8BDF95A-D6A8-4E95-A0CE-D53068E8355B@yahoo.com> <ABE16EA6-49F1-461F-9B8A-6DAA7ED6A18D@googlemail.com> <98BC985D-EAAB-4AFB-AA8F-7391A45C4EBF@yahoo.com> <91324D35-B66A-4674-AE37-45F3DDB736FD@yahoo.com> <2B3F0409-88F2-4EBD-9C39-37929F973C77@yahoo.com> <B3133D77-FA24-4F42-B529-D0B56F48E790@yahoo.com> <CCEEC0AD-B874-4753-AAA1-B3B5B302A30C@googlemail.com> <E82AE086-837C-4CEA-92D5-78A39412F964@yahoo.com> <803EF261-1407-4331-AC56-1D49E05F8382@googlemail.com> <2FAA304E-045B-4B10-AA14-1E869FB6FD00@yahoo.com> <ABEE9729-353C-473D-8670-271395A697C8@googlemail.com> <36A6B0E4-7578-4EFF-8095-9030DA36214B@yahoo.com> <83BA1DDB-C725-470C-B382-9D229860E2F1@googlemail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On 2020-Oct-9, at 16:20, Klaus Cucinauomo <maciphone2 at googlemail.com> =
wrote:

>> Am 10.10.2020 um 00:48 schrieb Mark Millard <marklmi at yahoo.com>:
>> =E2=80=A6. Sorry for the noise. =E2=80=A6...
>=20
> the more noise, the more we find out ;-)..=20
> and of course also for me , probably all of us, that=E2=80=99s all =
really confusing stuff from raspberrypi.org=20
> because very strange that ubuntu`msdos is compatible with 2020.10=20
> while their GitHub-stuff isn=E2=80=99t (in our msdos-part) .

Does not go so well for FreeBSD in my context . . .

My FreeBSD USB3 SSD is partitioned as:

# gpart show -p
. . .
=3D>       40  468862048    da0  GPT  (224G)
         40       2008         - free -  (1.0M)
       2048  413138944  da0p1  freebsd-ufs  (197G)
  413140992    9437184  da0p2  freebsd-swap  (4.5G)
  422578176     204800  da0p3  ms-basic-data  (100M)
  422782976   46079112         - free -  (22G)
# gpart show -pl
. . .
=3D>       40  468862048    da0  GPT  (224G)
         40       2008         - free -  (1.0M)
       2048  413138944  da0p1  RPi4Broot  (197G)
  413140992    9437184  da0p2  RPi4Bswap  (4.5G)
  422578176     204800  da0p3  RPi4BEFI  (100M)
  422782976   46079112         - free -  (22G)

So it is the 3rd partition that has the msdos file system.
Turns out that the start4.elf / fixup4.dat vintage in the
ubuntu materials assumes the msdos file system to be the
first one instead of looking for it.

So, attempting to use the ubuntu vintage start4.elf / fixup4.dat,
I end up with:

QUOTE
Device 0: Vendor: OWC      Rev: 0    Prod: Envoy Pro mini =20
            Type: Hard Disk
            Capacity: 228936.5 MB =3D 223.5 GB (468862128 x 512)
... is now current device
** Unrecognized filesystem type **
END QUOTE

After that it tries to boot from ethernet (which was
not connected).

This is not true of the start4.elf / fixup4.dat vintage used by
the uefi/ACPI v1.20 materials. That start4.elf / fixup4.dat
pair finds and uses the 3rd partition for the msdos file
system based material just fine.=20

So using older materials than the 2020-Aug-20 RaspiOS related
ones does have tradeoffs.

>> =E2=80=A6=E2=80=A6
>> .
>> FYI for the u-boot vintage/variant involved for ubuntu:
>>=20
>> # strings /boot/firmware/uboot_rpi_4.bin | grep 2020
>> gcc (Ubuntu 9.2.1-28ubuntu1) 9.2.1 20200203
>> 02/11/2020
>> U-Boot 2019.07+dfsg-1ubuntu6 (Feb 11 2020 - 10:43:57 +0000)
> =E2=80=A6..
> I even didn=E2=80=99t boot it, just copied the msdos-part=E2=80=A6=20
> all files in ubuntu server msdos are of date  /31st of July 2020 /

That well predates 2020-Aug-20. /boot/firmware/ is the
mounted msdos file system under ubuntu. uboot_rpi_4.bin is
one of the things in that file system.

> , the only reason why I used that distro is really because it seems to =
be a raspberrypi.org official image =20

https://www.raspberrypi.org/downloads/ lists the following
"Third Party Operating System Images" (down a ways on the
page), saying:

QUOTE
Third-party operating system images for Raspberry Pi are also available:

Ubuntu MATE
Ubuntu Core
Ubuntu Server
OSMC
LibreELEC
Mozilla WebThings
PiNet
RISC OS
Weather Station
IchigoJam RPi
END QUOTE

Clicking on the image for one of those takes you
to the third party's web site for it, such as
https://ubuntu.com/download/raspberry-pi/ for
"Ubuntu Server".

The RaspberryPi-imager apparently gives access to
some of those 3rd party operating systems images
as well.

> And I GUESSED(!;-) it has to boot up 2020.10 , and that was right=E2=80=A6=

> But puuuh, all strange stuff

What I report about finding and using the msdos file system
is from before u-boot would have been started.

=3D=3D=3D
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?B4AF1099-0049-4E5E-A951-6615E950A965>