Date: Thu, 11 Apr 2024 10:57:31 -0700 From: Mark Millard <marklmi@yahoo.com> To: Johan Helsingius <julf@Julf.com> Cc: freebsd-arm@freebsd.org Subject: Re: Raspberry Pi 4 and M.2 SATA SSD recognized but not booting or available for install - unsupported interface Message-ID: <0E07E7CD-FFA7-411E-AF92-E79B7007E4C1@yahoo.com> In-Reply-To: <a87b47dc-1aca-4bc0-9b13-d3655c920bb6@Julf.com> References: <f0a303eb-a25c-4976-8d30-918c3e7b11f8@Julf.com> <3AA7F3FA-5CCC-401C-A638-DC5A65D707E4@yahoo.com> <a7ba45a8-8746-4a00-b0bc-a237bc661407@Julf.com> <F7126DB8-3FF0-483E-ADC7-BEA5DD73EF21@yahoo.com> <a87b47dc-1aca-4bc0-9b13-d3655c920bb6@Julf.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Apr 11, 2024, at 10:47, Johan Helsingius <julf@Julf.com> wrote: > On 11/04/2024 19:38, Mark Millard wrote: >> Which image(s)? >=20 > I think it was the memstick one. >=20 >> 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. >=20 > 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. >=20 >> 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. >=20 > 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=3DUSB_ERR_TIMEOUT # uhub_reattach_port: device problem (USB_ERR_TIMEOUT), disabling port = ? # WARNING, not sufficient for "boot -s": that needs the full = force_turbo=3D1 initial_turbo=3D60 END QUOTE =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?0E07E7CD-FFA7-411E-AF92-E79B7007E4C1>