Date: Wed, 11 Oct 2023 15:07:57 +0100 From: void <void@f-m.fm> To: freebsd-arm@freebsd.org Subject: Re: unable to boot latest 14-stable Message-ID: <ZSasPYs3jCZ7Si6U@int21h> In-Reply-To: <55C64D6A-2712-408A-B7A7-BA8081CA99FC@yahoo.com> References: <ZSXPnTXAdSJYrBDX@int21h> <841CA663-55E0-4EAD-B700-66DC884B50FA@yahoo.com> <ZSZotIDLHZE1SzwL@int21h> <ZSZ3vATEEGO3N8-T@int21h> <55C64D6A-2712-408A-B7A7-BA8081CA99FC@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Oct 11, 2023 at 06:01:05AM -0700, Mark Millard wrote: >You replaced the older EFI/boot/bootaa64.efi on the msdosfs >with a newer one. The newer one knows about and classifies >the zpool feature as known-to-be supported by itself. Or so >I expect: I've not tracked down the source code changes >between the specific versions in question. I can handle changes if I know about them, if there's somewhere to check where breaking changes like this and their consequence are always noted, in order to accomodate the change in any upgrade process. I've checked in https://cgit.freebsd.org/src/log/?h=stable%2F14&qt=grep&q=bootaa64.efi returns one entry from 2018. With the non-working efi: stat -f "%Sm %N" -t %Y%m%d%H%M%S bootaa64.efi 20220512075622 bootaa64.efi The working one: 20231006092102 bootaa64.efi How can I track breaking changes like this in future? --
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ZSasPYs3jCZ7Si6U>