all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Marius Bakke <mbakke@fastmail.com>
To: t_w_@freenet.de, help-guix <help-guix@gnu.org>
Subject: Re: Custom kernel module woes
Date: Thu, 22 Mar 2018 18:51:49 +0100	[thread overview]
Message-ID: <87k1u4kngq.fsf@fastmail.com> (raw)
In-Reply-To: <770cd26b-86dd-0e04-5079-532801f228b8@freenet.de>

[-- Attachment #1: Type: text/plain, Size: 1030 bytes --]

Thorsten Wilms <t_w_@freenet.de> 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.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  reply	other threads:[~2018-03-22 17:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-21 10:48 Custom kernel module woes Thorsten Wilms
2018-03-22 17:51 ` Marius Bakke [this message]
2018-03-22 19:22   ` Thorsten Wilms
2018-04-08 20:47 ` Marius Bakke

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87k1u4kngq.fsf@fastmail.com \
    --to=mbakke@fastmail.com \
    --cc=help-guix@gnu.org \
    --cc=t_w_@freenet.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.