l...@gnu.org (Ludovic Courtès) skribis:
> Duncan Keall <dun...@duncankeall.com> skribis:
>
>> Here are the configurations I have tested which all result in the errors
>> posted above:
>>
>> ("dm-crypt.ko" "aes-x86_64.ko" "crc32.ko" "pcbc.ko" "xcbc.ko"
>> "sha256-ssse3.ko")
>> ("dm-crypt.ko" "cryptd.ko" "aes-x86_64.ko" "crc32.ko" "pcbc.ko" "xcbc.ko"
>> "sha256-ssse3.ko")
>> ("dm-crypt.ko" "cryptd.ko" "crc32-pclmul.ko" "aes-x86_64.ko" "crc32.ko"
>> "pcbc.ko" "xcbc.ko" "sha256-ssse3.ko")
>>
>> I could also add "aesni-intel.ko" but it resulted in a different set of
>> kernel errors on boot:
>>
>> aesni_intel: Unknown symbol ablk_decrypt (err 0)
>> aesni_intel: Unknown symbol lrw_free_table (err 0)
>> aesni_intel: Unknown symbol ablk_set_key (err 0)
>> ...
>> ERROR: In procedure load-linux-module: Unknown error -1
>
> Presumably that’s because one of its prerequisites hasn’t been loaded
> yet.
>
> The difficulty is that modules need to be listed in topological order:
This particular problem was fixed in 0e704a2 a couple of weeks ago.
For testing, you would need to start from an image generated from
current master with:
./pre-inst-env \
guix system disk-image --image-size=800MiB gnu/system/install.scm
Let me know if anything else is needed.
Ludo’.
