Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 21 Jan 2023 17:12:22 -0800
From:      Mark Millard <marklmi@yahoo.com>
To:        Fred Finster <fred@thegalacticzoo.com>
Cc:        freebsd-arm@freebsd.org
Subject:   Re: Raspberry Pi 4B not booting single user mode on FreeBSD 14.0 aarch64. Does it work for you?
Message-ID:  <BB195C81-3978-49B6-9A3E-CCC0598D102D@yahoo.com>
In-Reply-To: <e86d8396-e545-e726-7509-7736054e41df@thegalacticzoo.com>
References:  <e86d8396-e545-e726-7509-7736054e41df@thegalacticzoo.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Jan 20, 2023, at 06:22, Fred Finster <fred@thegalacticzoo.com> wrote:

> was just trying to boot into single user mode from this documentation =
below:
> https://people.freebsd.org/~rodrigc/doc/handbook/makeworld.html
> Once in single-user mode, run these commands if the system is =
formatted with UFS:
>=20
> |#|  *|mount -u /|*
> |#|  *|mount -a -t ufs|*
> |#|  *|swapon -a|*
>=20
> example I created this blog post: =
https://ghostbsd-arm64.blogspot.com/2023/01/time-make-j4-buildworld.html
> I could boot into multi-user mode but not into Single User Mode on =
this Raspberry Pi 4B.
> What do you suggest and how to trouble shoot?  I turned on verbose =
mode and saw that it hung after starting /sbin/init
> but do not know why  this aarch64 ARM64 BCM2711 cpu hangs on FreeBSD =
14.0 going into "single user mode".
>=20
> This Version:
>=20
> root@Fred_RasPi4B:~ # uname -Kmnopr
> FreeBSD Fred_RasPi4B 14.0-CURRENT arm64 aarch64 1400077
> root@Fred_RasPi4B:~ # uname -a
> FreeBSD Fred_RasPi4B 14.0-CURRENT FreeBSD 14.0-CURRENT #6 =
main-n259952-7e2600ea7be2-dirty: Sun Jan 15 18:14:05 PST 2023 =
root@Fred_RasPi4B:/usr/obj/usr/src/arm64.aarch64/sys/GENERIC-VCHIQ arm64
. . .

I've never tried GENERIC-VCHIQ.

Have you tried testing a standard build on some
media, such as trying a dd of an uncompressed:

=
http://ftp3.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/14.0/FreeBSD-14.0=
-CURRENT-arm64-aarch64-RPI-20230120-43703bc489ec-260163.img.xz

and seeing if the problem replicates for that in
your context? If it replicates, then at least you
know it is not something more specific to your
context and other folks would be able to test
similarly with a sufficiently analogous context.

But, if it does not replicate when you try such a
test, then folks likely would have to try to
reproduce your context to have a sufficiently
analogous context to test.

=3D=3D=3D
Mark Millard
marklmi at yahoo.com




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BB195C81-3978-49B6-9A3E-CCC0598D102D>