Hi, Vagrant Cascadian <vagr...@debian.org> writes:
> After upgrading to linux-libre 4.20, and again tested with 4.20.3, an > aarch64 system failed to boot (using 4.19.10 worked fine): [...] > Workaround or fix was to add to config.scm: > > (initrd (append (list "crc32c_generic" ... ) %base-initrd-modules)) Here's a proposed (untested) patch. Would you like to test it and see if it eliminates the need for this workaround? Mark
>From 20a57e861cff4dce40c4eb6c7344f12d1f283cf8 Mon Sep 17 00:00:00 2001 From: Mark H Weaver <m...@netris.org> Date: Wed, 23 Jan 2019 01:20:30 -0500 Subject: [PATCH] gnu: linux-libre: Make CRYPTO_CRC32C a built-in on arm64. Fixes <https://bugs.gnu.org/34162> Reported by Vagrant Cascadian <vagr...@debian.org> Note that CRYPTO_CRC32C was already a built-in in our default configurations for other systems. * gnu/packages/aux-files/linux-libre/4.20-arm64.conf, gnu/packages/aux-files/linux-libre/4.19-arm64.conf (CONFIG_CRYPTO_CRC32C): Change from 'm' to 'y'. --- gnu/packages/aux-files/linux-libre/4.19-arm64.conf | 2 +- gnu/packages/aux-files/linux-libre/4.20-arm64.conf | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/gnu/packages/aux-files/linux-libre/4.19-arm64.conf b/gnu/packages/aux-files/linux-libre/4.19-arm64.conf index ba6fa177b..73cd300c1 100644 --- a/gnu/packages/aux-files/linux-libre/4.19-arm64.conf +++ b/gnu/packages/aux-files/linux-libre/4.19-arm64.conf @@ -7860,7 +7860,7 @@ CONFIG_CRYPTO_VMAC=m # # Digest # -CONFIG_CRYPTO_CRC32C=m +CONFIG_CRYPTO_CRC32C=y CONFIG_CRYPTO_CRC32=m CONFIG_CRYPTO_CRCT10DIF=y CONFIG_CRYPTO_GHASH=m diff --git a/gnu/packages/aux-files/linux-libre/4.20-arm64.conf b/gnu/packages/aux-files/linux-libre/4.20-arm64.conf index 9e71cadf0..3833e3e36 100644 --- a/gnu/packages/aux-files/linux-libre/4.20-arm64.conf +++ b/gnu/packages/aux-files/linux-libre/4.20-arm64.conf @@ -7932,7 +7932,7 @@ CONFIG_CRYPTO_VMAC=m # # Digest # -CONFIG_CRYPTO_CRC32C=m +CONFIG_CRYPTO_CRC32C=y CONFIG_CRYPTO_CRC32=m CONFIG_CRYPTO_CRCT10DIF=y CONFIG_CRYPTO_GHASH=m -- 2.20.1