unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Timothy Sample <samplet@ngyro.com>
Cc: Eric Brown <brown@fastmail.com>, 32524@debbugs.gnu.org
Subject: bug#32524: guix system build bare-bones.scm fails with ahci shpchp
Date: Wed, 29 Aug 2018 23:13:37 +0200	[thread overview]
Message-ID: <8736uw7u66.fsf@gnu.org> (raw)
In-Reply-To: <871sam6zyt.fsf@ngyro.com> (Timothy Sample's message of "Sat, 25 Aug 2018 14:52:26 -0400")

Hi,

Timothy Sample <samplet@ngyro.com> skribis:

> Eric Brown <brown@fastmail.com> writes:
>
>> I am attempting to guix system reconfigure a GuixSD 0.15 (updated)
>> Macintosh laptop where reconfigure recommends and requires:
>>
>>   (initrd-modules (append (list "ahci" "shpchp")
>>                           %base-initrd-modules))
>>
>> However, the config file that I used at guix system init works
>> originally with this additional bit of lisp, but a reconfigure gives the
>> error below.
>>
>> In an attempt to narrow down, inserting this into bare-bones.scm gives a
>> similar error. Thanks to samplet for help and confirmation on #guixsd.
>
> Just to make things clear, the bare-bones config below works with
> Linux-Libre 4.17, but not with 4.18.  We no longer build the ”shpchp”
> module.  See commit 3004f1c69b258837b0e49a567787c97479ce6e71, which
> includes the following:
>
>     -CONFIG_HOTPLUG_PCI_SHPC=m
>     +# CONFIG_HOTPLUG_PCI_SHPC is not set
>
> I don’t know anything about this module or this change, so I don’t know
> if we should change the config file or not.  I will leave that to
> someone more knowledgeable.

I don’t know the rationale of this change, but I understand the problem:
it’s design issue with the module recommendation mechanism.  Basically
it looks at modules needed on the current kernel for, say,  your root
file system, and then it recommends adding those.

The problem occurs when you’re running on 4.17 and reconfiguring towards
4.18: on your system ‘shpchp’ is necessary, so ‘guix system’ recommends
it, but on the target system it’s not.  In that case ‘--skip-checks’ is
needed.

What we could do is determine that ‘shpchp.ko’ is not provided by the
target kernel, though that doesn’t tell us whether it’s needed.  Doing
that also has the disadvantage that we must build/download the target
kernel before we can emit the warning, as has been discussed before.

Thoughts?

Ludo’.

      reply	other threads:[~2018-08-29 21:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-25  3:13 bug#32524: guix system build bare-bones.scm fails with ahci shpchp Eric Brown
2018-08-25 18:52 ` Timothy Sample
2018-08-29 21:13   ` Ludovic Courtès [this message]

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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=8736uw7u66.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=32524@debbugs.gnu.org \
    --cc=brown@fastmail.com \
    --cc=samplet@ngyro.com \
    /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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).