Date: Sat, 8 Feb 2025 07:24:51 -0800 From: Mark Millard <marklmi@yahoo.com> To: Dennis Clarke <dclarke@blastwave.org>, freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: Trying an install to a Raspberry PI5 unit Message-ID: <6EDF888D-5F45-4667-BE0A-CB414CA073C3@yahoo.com> References: <6EDF888D-5F45-4667-BE0A-CB414CA073C3.ref@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Dennis Clarke <dclarke_at_blastwave.org> wrote on Date: Fri, 07 Feb 2025 22:33:58 UTC : > On 2/7/25 16:09, Dennis Clarke wrote: > >=20 > > All : > >=20 > > Today I will be trying to follow the instructions at : > >=20 > > https://wiki.freebsd.org/arm/Raspberry%20Pi%205 > >=20 > > Instantly the instructions are not clear. Not at all. > >=20 > > I will try to follow along but expect many problems for someone > > that has zero experience with the arm platform. Almost zero. > >=20 >=20 > Copy the unzipped contents to the root of the USB stick. ?? >=20 > What the heck does that mean? There needs to be a partition > table on a USB stick and then a filesystem and what filesystem > here? UFS ? ZFS ? ext4 for Linux? Limiting this reply to the above paragraphs for the most part . . . The: = https://download.freebsd.org/ftp/*/ISO-IMAGES/*/*-arm64-aarch64-RPI*.img.x= z are compressed image files that you can fetch listing a specific name, not a pattern. The uncompressed naming would normally match the pattern: *-arm64-aarch64-RPI*.img So, for example, # fetch = https://download.freebsd.org/ftp/releases/ISO-IMAGES/14.2/FreeBSD-14.2-REL= EASE-arm64-aarch64-RPI.img.xz # unxz FreeBSD-14.2-RELEASE-arm64-aarch64-RPI.img.xz produces a: FreeBSD-14.2-RELEASE-arm64-aarch64-RPI.img Such a *.img file contains multiple partitions (if GPT) or slices (if MBR). It already has the file systems needed, although the first boot may grow a partition/slice/file-system and/or create a swap partition/slice. It can be dd'd to media directly (microsd cards, USB drives), replacing the prior content (partitions or slices). A USB example is: # dd if=3DFreeBSD-14.2-RELEASE-arm64-aarch64-RPI.img of=3D/dev/da0 bs=3D1M= conv=3Dsync A microsd card example is: # dd if=3DFreeBSD-14.2-RELEASE-arm64-aarch64-RPI.img of=3D/dev/mmcsd0 = bs=3D1M conv=3Dsync Nothing about the above notes is specific to the RPi5 context. It applies to other aarch64 RPi* as well, including ones that FreeBSD does claim to support. Other than the version numbers that appear, it is nothing new for its general structure. The *-arm64-aarch64-RPI*.img.xz references do make that content aarch64 RPi* specific. Other appropriate name patterns that involve *.img.xz names would be for some non-aarch64-RPi* context. >=20 > These instructions are madness. My notes above do not deal with then updating the msdosfs with the EDK2 files from: = https://github.com/worproject/rpi5-uefi/releases/download/v0.3/RPi5_UEFI_R= elease_v0.3.zip (The first and only version to avoid causing USB DMA corruption issues: do not use older versions.) This activity would be RPi5 specific. =3D=3D=3D Mark Millard marklmi at yahoo.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6EDF888D-5F45-4667-BE0A-CB414CA073C3>