From: "Tomáš Čech" <sleep_walker@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 30760@debbugs.gnu.org
Subject: bug#30760: guix system init broken on non GuixSD
Date: Mon, 12 Mar 2018 10:19:23 +0100 [thread overview]
Message-ID: <20180312091923.q47b3mrhzsl4vr75@doom> (raw)
In-Reply-To: <874llmuwc5.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1024 bytes --]
On Sun, Mar 11, 2018 at 10:38:18PM +0100, Ludovic Courtès wrote:
>Tomáš Čech <sleep_walker@gnu.org> skribis:
>
>> In ice-9/boot-9.scm:
>> 829:9 1 (catch system-error #<procedure 7fa004522f60 at gnu/sy…> …)
>> In gnu/system/linux-initrd.scm:
>> 361:6 0 (_)
>>
>> gnu/system/linux-initrd.scm:361:6: known-module-aliases: unbound variable
>
>My bad! Danny eventually fixed it in
>0803ddf2677ead5e9d8ef698316125e0c8b9c998.
I'm afraid this is still not correct.
# guix system init config.scm /mnt/mnt/
...
config.scm:64:9: error: you may need these modules in the initrd for /dev/nvme0n1p2: shpchp
hint: Try adding them to the `initrd-modules' field of your `operating-system' declaration, along these lines:
(operating-system
;; ...
(initrd-modules (append (list "shpchp")
%base-initrd-modules)))
I don't have `shpchp` as a module as I have it compiled into kernel
directly. Can I somehow disable the check?
Thanks.
S_W
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-03-12 9:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-09 17:35 bug#30760: guix system init broken on non GuixSD Tomáš Čech
2018-03-09 22:15 ` Danny Milosavljevic
2018-03-09 22:42 ` Ludovic Courtès
2018-03-09 22:52 ` Danny Milosavljevic
2018-03-09 23:19 ` Ludovic Courtès
2018-03-10 21:42 ` Tomáš Čech
2018-03-11 16:31 ` Danny Milosavljevic
[not found] ` <20180310063219.bxgl7bgspxu2o5ez@doom>
[not found] ` <874llmuwc5.fsf@gnu.org>
2018-03-12 9:19 ` Tomáš Čech [this message]
2018-03-12 12:24 ` Danny Milosavljevic
2018-03-12 12:38 ` Danny Milosavljevic
2018-03-12 12:57 ` Ludovic Courtès
2018-03-15 10:43 ` Ludovic Courtès
2018-03-12 15:27 ` Tomáš Čech
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=20180312091923.q47b3mrhzsl4vr75@doom \
--to=sleep_walker@gnu.org \
--cc=30760@debbugs.gnu.org \
--cc=ludo@gnu.org \
/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).