Date: Thu, 3 Sep 2020 10:16:26 +0300 From: Andriy Gapon <avg@FreeBSD.org> To: Dave Cottlehuber <dch@freebsd.org> Cc: freebsd-current@freebsd.org, freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: [openzfs] r365058 arm64 uefi boot fails with "unknown filesystem" after launching kernel Message-ID: <f0a4650b-c441-14c9-1b20-9a285430c67b@FreeBSD.org> In-Reply-To: <f9e6928d-d560-410f-ab98-205d40b8f541@www.fastmail.com> References: <c2c0eff7-18dc-4d50-97f0-4417684608f1@www.fastmail.com> <a13cabae-c99e-6dc7-f779-a503f5004873@gmail.com> <d4008e58-0c0c-6b70-61d6-0354eeae3ddd@FreeBSD.org> <f9e6928d-d560-410f-ab98-205d40b8f541@www.fastmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 03/09/2020 10:01, Dave Cottlehuber wrote: > On Thu, 3 Sep 2020, at 06:48, Andriy Gapon wrote: >> On 03/09/2020 00:01, Navdeep Parhar wrote: >>> Load cryptodev manually from the loader to boot and then add >>> cryptodev_load="YES" to your loader.conf. >> >> I think that this shouldn't be needed *if* zfs module has a dependency on >> cryptodev module (MODULE_DEPEND in the code). >> The loader knows how to load dependencies. > > emaste mentioned that this dependency walking doesn't work on aarch64 yet, > until after loader stage is complete. Sorry for the noise then! I didn't know about that bug. -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?f0a4650b-c441-14c9-1b20-9a285430c67b>