Deutsch English Français Italiano |
<vs6el4$3054c$1@dont-email.me> View for Bookmarking (what is this?) Look up another Usenet article |
Path: news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail From: bp@www.zefox.net Newsgroups: comp.sys.raspberry-pi Subject: Re: Pi2 bootcode.bin puzzle Date: Fri, 28 Mar 2025 15:19:00 -0000 (UTC) Organization: A noiseless patient Spider Lines: 26 Message-ID: <vs6el4$3054c$1@dont-email.me> References: <vrufnd$3hlnn$1@dont-email.me> <buh*PEl+z@news.chiark.greenend.org.uk> <vrvei8$cssq$1@dont-email.me> <cuh*Acn+z@news.chiark.greenend.org.uk> Injection-Date: Fri, 28 Mar 2025 16:19:01 +0100 (CET) Injection-Info: dont-email.me; posting-host="6c52340899b957e359a99bdccf5a0f27"; logging-data="3150988"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX197F794BQfYwnEsgC3eRCLI2wOtyuClQ7s=" User-Agent: tin/2.6.4-20241224 ("Helmsdale") (FreeBSD/14.2-STABLE (arm64)) Cancel-Lock: sha1:YoJPdQ1prbgdIR8ch7EDA3R58H4= Theo <theom+news@chiark.greenend.org.uk> wrote: > > I believe that config.txt is consumed by the GPU-side firmware, which is > start*.elf. bootcode.bin is just enough to be able to load start.elf > and config.txt from storage. I'd guess that if that storage is USB, it's > too early to have read config.txt. It looks like the path of least resistance is to let FreeBSD boot from microSD, mount that as root and then mount the USB disk as /usr, with /var/, /tmp/ and swap mounted from the USB device, either as links to /usr or maybe as hard partitions. That worked fine in the very early days of FreeBSD on the Pi2. There isn't much write activity to the root filesystem in a "production" environment, only during OS upgrades. If the microSD is sufficiently oversized it'll last long enough. I'd hoped bootcode.bin could be upgraded/tuned to boot from a USB3 disk on a Pi2, but apparently not. Thanks to everyone for writing! bob prohaska