Date: Thu, 5 Mar 2020 22:57:45 -0800 From: bob prohaska <fbsd@www.zefox.net> To: Mark Millard <marklmi@yahoo.com> Cc: freebsd-arm@freebsd.org, bob prohaska <fbsd@www.zefox.net> Subject: Re: Adding a swap partition to the March 5 snapshot image Message-ID: <20200306065745.GA19280@www.zefox.net> In-Reply-To: <5C66F8DD-F97B-4A44-8E84-1E48B920B8FA@yahoo.com> References: <20200306045443.GA19058@www.zefox.net> <58BB6CC3-34C7-413F-9ED4-D84E63FBCD2D@yahoo.com> <5C66F8DD-F97B-4A44-8E84-1E48B920B8FA@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Mar 05, 2020 at 09:42:01PM -0800, Mark Millard wrote: > > > On 2020-Mar-5, at 21:26, Mark Millard <marklmi at yahoo.com> wrote: > > > > > On 2020-Mar-5, at 20:54, bob prohaska <fbsd at www.zefox.net> wrote: > >> > >> I've been trying for a while to set up an armv7 RPI2 with a single > >> root partition plus a swap partition at the end of mmcsd0. Letting > >> firstboot invoke growfs seems not to help, since growfs leaves no > >> space for swap. > >> > >> Attempts using gpart in single-user give the appearance of > >> working, but on reboot the machine stops at the mountroot prompt. > >> This method worked well in July of 2018. Seemingly, no more. > >> > >> Has something changed? > >> > >> Mounting the armv7 card on a second Freebsd box and making the changes > >> appears to work also, but on the initial boot (firstboot disabled) the > >> machine stops at the mountroot prompt on initial boot. > >> > >> If there's a better way to pursue the same end I'd be grateful for > >> a hint. Perhaps giving a swap size parameter to firstboot? > > > > You have not reported what shows if you enter a "?" command at the > > mountroot prompt. (As I remember that lists what mount root > > classifies as available.) > > > > That might prove to be useful information. > > > > Ahh, "March 5 snapshot image"? The only head 20200305 images are > for amd64: everything else failed to build for head -r358658 . > > Are you using stable/12 images? Those built ( 12.1-STABLE -r358659 ), > including for RPI2. > FreeBSD-12.1-STABLE-arm-armv7-RPI2-20200305-r358659.img Same trouble with the Feb 27 image. > All stable/11 builds failed. > > (You seem to usually use head but did not comment on using > stable/12. So I'm just checking the context here.) > Only on the Pi3. My intent was to set up production 8-) machines on new media, which are early Pi2 v 1.1 boards. I'll repeat the exercise in the morning and try to keep a transcript. Thanks for replying! bob prohaska
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20200306065745.GA19280>