Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 9 Feb 2020 18:32:55 -0800
From:      Bakul Shah <bakul@bitblocks.com>
To:        Mark Millard <marklmi@yahoo.com>
Cc:        freebsd-arm@freebsd.org
Subject:   Re: RPI4 Install r357606 test 09.02.2020 failed
Message-ID:  <D5F8A326-877A-42A4-B35B-7CD7B60CFF02@bitblocks.com>
In-Reply-To: <D11F4E71-FF1F-4C13-8F3C-A197AB372E3E@yahoo.com>
References:  <202002092026.019KQXLF021366@mail.karels.net> <4551CAE8-08DA-463F-876C-DD1BBAA5D7C5@bitblocks.com> <D11F4E71-FF1F-4C13-8F3C-A197AB372E3E@yahoo.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Feb 9, 2020, at 2:48 PM, Mark Millard via freebsd-arm =
<freebsd-arm@freebsd.org> wrote:
>=20
> If you want a build that works, use the kernel from head
> -r356767 . The next head version ( -r356776 ) is where
> the broken status starts for RPi4 and RPi3. RPi4B's with
> 4 GiBYTes of RAM fail to boot. As I understand, at least
> some forms of RPi3 boot but are messed up, such as only
> running 1 core. (Not surprising given the PSCI version
> problem which happens there as well.)

With this version I was able to boot it and log in as root.
Thanks!

I don't see any bcm2711 specific files in sys/arm/broadcom/bcm2835.
Is this intentional? pi3 (bcm2838) and pi4 (bcm2711) are rather
different.

[Aside: rebuilding with -DNO_CLEAN took 7 minutes on a $300
 Motile with an NVMe SSD!]








Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?D5F8A326-877A-42A4-B35B-7CD7B60CFF02>