Re: Custom kernel module woes

Thorsten Wilms writes: > 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

Re: Custom kernel module woes

On 22.03.2018 18:51, Marius Bakke wrote: Can you post the .config that requires CONFIG_CRYPTO_XTS=y? I attached the result of `make menuconfig` in linux-libre-4.15.12, as that shows the issue and is as neutral as it gets. I remember having to turn on "expert" configuration in order to

Re: Custom kernel module woes

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

Custom kernel module woes

Hi! My mentionable reasons for a custom kernel are optimizations for audio work (CONFIG_HZ=1000 and "Preemptible Kernel (Low-Latency Desktop)"), the specific CPU and reducing time and energy costs of building by selecting only the necessary drivers. I added the package definition to my