Date: Wed, 29 Nov 2017 17:42:52 -0700 From: Warner Losh <imp@bsdimp.com> To: Shawn Webb <shawn.webb@hardenedbsd.org> Cc: "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org>, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: Booting UEFI ZFS is broken on arm64 Message-ID: <CANCZdfqgco6gp-ccph3hSgJg81=%2BEfW2DJp0DOx2xgCdgH7UkQ@mail.gmail.com> In-Reply-To: <20171130003458.bnltotlgfdbke5ue@mutt-hbsd> References: <20171130002135.q7p27hh6qkog4slr@mutt-hbsd> <CANCZdfrjKkR-Lr4FKVyCBBnYy8k-n6rgz6ES6=_K6SeXtFOtMg@mail.gmail.com> <20171130003458.bnltotlgfdbke5ue@mutt-hbsd>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Nov 29, 2017 at 5:34 PM, Shawn Webb <shawn.webb@hardenedbsd.org> wrote: > On Wed, Nov 29, 2017 at 05:33:46PM -0700, Warner Losh wrote: > > On Wed, Nov 29, 2017 at 5:21 PM, Shawn Webb <shawn.webb@hardenedbsd.org> > > wrote: > > > > > It appears that in the latest FreeBSD 12-CURRENT/arm64 snapshot, > > > booting UEFI GPT ZFS on my OverDrive 1000 is broken. It boots up to > > > this line: > > > > > > Using DTB provided by EFI at 0x801fe00000. > > > > > > Which snapshot is that? Boot1 was broken until recently. > > FreeBSD-12.0-CURRENT-arm64-aarch64-20171121-r326056-memstick.img > > It also happens on latest HEAD, so it would appear to still be broken. Is this boot1.efi producing the output, or loader.efi? I'm guessing the latter, but wanted to make sure. If so, then we're past the point where boot1.efi would have failed (besides, it was fixed before that snapshot). Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfqgco6gp-ccph3hSgJg81=%2BEfW2DJp0DOx2xgCdgH7UkQ>