Date: Sat, 1 Feb 2020 21:45:07 +0100 From: =?utf-8?Q?Klaus_K=C3=BCchemann?= <maciphone2@googlemail.com> To: Mark Millard <marklmi@yahoo.com>, freebsd-arm@freebsd.org Subject: Re: head -r357356: fails to boot RPi4 but boots Rock64 (same media, moved between machines); -r356426 booted both Message-ID: <0908ECCA-4776-4662-9C78-309C20445BE5@googlemail.com> In-Reply-To: <E3D981E8-D6D3-4CFA-BA80-4A9BBFBB7E80@yahoo.com> References: <63205335-8E8A-4CCB-BC80-E4EC767FBC09.ref@yahoo.com> <63205335-8E8A-4CCB-BC80-E4EC767FBC09@yahoo.com> <EF8A3BE3-DF0A-4544-9BD6-3071E6516202@googlemail.com> <E3D981E8-D6D3-4CFA-BA80-4A9BBFBB7E80@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> Am 01.02.2020 um 20:02 schrieb Mark Millard <marklmi@yahoo.com>: >=20 > I described the original sequence that made the originally > -r356426 based Rock64 microSD card also bootable on the > RPi4 in: >=20 > = https://lists.freebsd.org/pipermail/freebsd-arm/2020-January/021117.html >=20 Thanks for posting (I also =E2=80=99ve both boards available),=20 so we can assume that=E2=80=99s an (known) RPI4-only issue, which I also = encounter when compiling to=20 GENERIC-NODEBUG(or whatever kernel) to r357335 yesterday. I discussed that with Kyle Evans in :=20 https://reviews.freebsd.org/D15955 >=20 >> which kernel did you boot from (e.g. GENERIC) ? >=20 > This question was repeated twice. Answered earlier. >>=20 That was a copy/paste-issue because I was watching football the same = time I wrote :-) > But I also have a glabel label assigned so there is > /dev/label/RPi4root for the partition that has the > ufs file system as well. When the card was at > -r357426 that worked fine in the RPi4 and its still > works fine with the microSD card put in the Rock64. >=20 > For reference (done on the Rock64): >=20 > # gpart show -p > =3D> 63 249737153 mmcsd0 MBR (119G) > 63 32705 - free - (16M) > 32768 102312 mmcsd0s1 fat32lba [active] (50M) > 135080 28760 - free - (14M) > 163840 241172480 mmcsd0s2 freebsd (115G) > 241336320 8400896 - free - (4.0G) >=20 > =3D> 0 241172480 mmcsd0s2 BSD (115G) > 0 230686720 mmcsd0s2a freebsd-ufs (110G) > 230686720 7340032 mmcsd0s2b freebsd-swap (3.5G) > 238026752 2097152 mmcsd0s2d freebsd-swap (1.0G) > 240123904 1048576 - free - (512M) >=20 >=20 >=20 >=20 > =3D=3D=3D > Mark Millard > marklmi at yahoo.com > ( dsl-only.net went > away in early 2018-Mar) >=20 The rescan seems to fail... so that if you were on mountroot > -prompt = it probably wouldn=E2=80=99t be help to mount=20 by ufs:/=E2=80=A6. =20 But I=E2=80=99ve read somewhere that 1 user had success by mounting = mmc/uSD by typing ufs:/=E2=80=A6 @mountroot When I waited a moment after the mount-crash it gave me the mountroot> = prompt on RPI4 but with me no way to mount manually at the moment, so = this issue has to be fixed =E2=80=A6. I have updated the Wiki a little( and will add more today) : https://wiki.freebsd.org/arm/Raspberry%20Pi .. welcome there if you have interesting news=20 Regards Klaus=20
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0908ECCA-4776-4662-9C78-309C20445BE5>