Date: Thu, 23 Apr 2020 16:32:59 -0700 From: bob prohaska <fbsd@www.zefox.net> To: Mark Millard <marklmi@yahoo.com> Cc: freebsd-arm <freebsd-arm@freebsd.org>, bob prohaska <fbsd@www.zefox.net> Subject: Re: Booting from USB on RPI3 Message-ID: <20200423233259.GD3996@www.zefox.net> In-Reply-To: <328B7083-1119-43F1-A6E4-61F1FB9E922E@yahoo.com> References: <mailman.61.1587470402.80084.freebsd-arm@freebsd.org> <trinity-4938b1d4-f29f-4907-bedd-65be21112e48-1587489497227@3c-app-webde-bs65> <20200421181224.GC96994@www.zefox.net> <trinity-19081201-3024-4046-817a-48321c51a515-1587587309088@3c-app-webde-bap64> <20200423162124.GA3583@www.zefox.net> <CAJuc1zMHL6ke3LH67iV8%2BogKFO18xwW_v7bRAUsj8CbxD2EOTw@mail.gmail.com> <8D1F6A8D-4910-4C1E-8EB5-2F5F89E31120@yahoo.com> <CAJuc1zOTnoRmeaKXHMTH9po=6ipBYDxvxAoiVmow-sNgwUERVQ@mail.gmail.com> <20200423212614.GA3996@www.zefox.net> <328B7083-1119-43F1-A6E4-61F1FB9E922E@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Apr 23, 2020 at 03:24:57PM -0700, Mark Millard wrote:
>
>
>
> For USB-only or for microsd card also in use,
> have you tried the equivalent of:
>
> OK lsdev
>
Another surprise. First time I tried, after some time idle:
OK lsdev
unknown command
but a simple
ls
listed the contents of the root directory. Apparently the
drive was asleep after an idle timeout.
A second attempt at lsdev produced
OK lsdev
disk devices:
disk0: 250085377 X 512 blocks (removable)
disk0s1: DOS/Windows
disk0s2: FreeBSD
disk0s2a: FreeBSD UFS
disk0s2b: FreeBSD swap
disk1: 78140161 X 512 blocks
disk1s1: DOS/Windows
disk1s2: FreeBSD
disk1s2a: FreeBSD UFS
disk1s2b: FreeBSD swap
http: (unknown)
net devices:
net0:
> and then used the naming convention shown in
> the output for any loader commands/settings
> instead of using FreeBSD-stage da0 based naming?
> (You might want to report what lsdev shows.)
>
> Note: the disk0 and disk1 like prefixes are
> copied from the u-boot notations that the
> loader gets from u-boot, if I understand
> right.
>
> Does your loader.conf do anything to control
> what is booted?
Not in a way I recognize, but you might:
OK more /boot/loader.conf
*** FILE /boot/loader.conf BEGIN ***
# Configure USB OTG; see usb_template(4).
hw.usb.template=3
umodem_load="YES"
# Multiple console (serial+efi gop) enabled.
boot_multicons="YES"
boot_serial="YES"
# Disable the beastie menu and color
beastie_disable="YES"
loader_color="NO"
*** FILE /boot/loader.conf END ***
As Joanathan asked: what does
> your /etc/fstab have listed? (/etc/fstab should
> have FreeBSD notations, not loader device names.)
OK more /etc/fstab
*** FILE /etc/fstab BEGIN ***
# Custom /etc/fstab for FreeBSD embedded images
/dev/ufs/rootfs / ufs rw 1 1
/dev/msdosfs/MSDOSBOOT /boot/msdos msdosfs rw,noatime 0 0
tmpfs /tmp tmpfs rw,mode=1777,size=50m 0 0
*** FILE /etc/fstab END ***
OK
> Are there any other boot-contributing files that
> would be appropriate to show together in one
> message for review, including any on the
> msdos file system?
>
I don't know how to answer that question. Since the machine
has gotten to loader and it's looking at the USB drive it's
very tempting to think the msdos part is done. I'll admit
that names like /dev/ufs/rootfs seem rather obscure.
Are they required for RAID?
Thanks for reading, apologies for less-than-insightful questions!
bob prohaska
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20200423233259.GD3996>