Re: FYI: FreeBSD-14.0-CURRENT-arm-armv7-GENERICSD-20220930-42dc8696df5-258315.img is broken for RPi2 v1.1 (so: armv7)g
- Reply: Mark Millard : "How to armv7 boot both RPi2B v1.1 (bcm2709 --real armv7) and RPi3B (bcm2710 aarch64), but not RPI4B (bcm2711 aarch64)"
- In reply to: Mark Millard : "Re: FYI: FreeBSD-14.0-CURRENT-arm-armv7-GENERICSD-20220930-42dc8696df5-258315.img is broken for RPi2 v1.1 (so: armv7)g"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Tue, 11 Oct 2022 23:33:27 UTC
On Tue, Oct 11, 2022 at 11:37:25AM -0700, Mark Millard wrote: [snip] > Actually the below is confusing. /boot/msdos > is supposed to be a mount point (empty directory) > at which the msdosfs can be mounted to make those > files show up there, despite being from a different > file system. Apologies for the ambiguity! /dev/da0s1 on /boot/msdos (msdosfs, local, noatime) is the normal dos filesystem on the root USB device. Normally it is mounted, IME. /dev/mmcsd0s1 on /mnt (msdosfs, local) was where I mounted the microSD DOS partition so the contents could be listed. This is a Pi2 so a DOS microSD card is required to boot from USB. Normally /dev/mmcsd0s1 is not mounted when root is booted from USB. Mostly I wondered if files placed in an "unused" DOS subdirectory could be hidden from the boot software. It was a poor way to pose the question. At the moment the armv7 PATA disk is updating. If it boots the Pi2 successfully I'll try it on Pi3 and Pi4. If that works I'll set up a SATA armv7 disk and test the troublesome disk enclosures. Thank you! bob prohaska