Re: Raspberry Pi 4 and M.2 SATA SSD recognized but not booting or available for install - unsupported interface

On Apr 11, 2024, at 10:47, Johan Helsingius <[email protected]> wrote:

> On 11/04/2024 19:38, Mark Millard wrote:
>> Which image(s)?
> 
> I think it was the memstick one.
> 
>> Only the likes of, say,
>> FreeBSD-14.0-STABLE-arm64-aarch64-RPI-20240404-72c3d91294c4-267114.img.xz
>> and:
>> FreeBSD-15.0-CURRENT-arm64-aarch64-RPI-20240404-112783ebbc31-269103.img.xz
>> and:
>> FreeBSD-14.0-RELEASE-arm64-aarch64-RPI.img.xz
>> are set up with the extra materials that I referenced for the RPi*'s. Note:
>> Those are UFS based, not ZFS based.
> 
> Ah! I see! Bummer that none of them are ZFS based, but I guess I can
> live with UFS on a RPi - it just means I have to have yet another
> backup procedure.
> 
>> What did you put in da1p1 (efiboot0) ? That area you have
>> to deal with for bsdinstall usage. Some folks extract and
>> copy over what is in the msdosfs in a:
>> *-arm64-aarch64-RPI-*.img.xz
>> as a means of getting an officially-built set of such
>> materials when they want to customize other aspects.
> 
> Would that make it possible to do a ZFS-based environment?

As far as I know, the absence of sufficient material in
da1p1 (efiboot0) could be your only problem. So, likely, up
to . . .

QUOTE
The config.txt may need the likes of the following added:

#
# Local addition that avoids USB3 SSD boot failures that look like:
#   uhub_reattach_port: port ? reset failed, error=USB_ERR_TIMEOUT
#   uhub_reattach_port: device problem (USB_ERR_TIMEOUT), disabling port ?
# WARNING, not sufficient for "boot -s": that needs the full force_turbo=1
initial_turbo=60
END QUOTE


===
Mark Millard
marklmi at yahoo.com