Thorsten Wilms writes: > Things were going well until I got to XTS support. With either my custom > configuration, or a default one, XTS is stuck on -*-, i.e. mandatory > built-in. The after-build phase will fail if there's no xts.ko module! > > I tried to figure out the dependencies and failed. Finally, I took the > guix kernel configuration, replaced the entire segment device-drivers up > to file-systems with one from my custom version and did the few other > changes. It works! > > Now if anyone knows or can figure out how *exactly* to turn XTS's -*- > into a {M}, that would still be good to know. A script that turns any > kernel configuration into a guix-sd-safe one, or changes to make these > gymnastics unnecessary would be great! Can you post the .config that requires CONFIG_CRYPTO_XTS=y? I remember having to turn on "expert" configuration in order to change some of the default builtins. If this is the case, perhaps we should make it a built-in on GuixSD too.