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: Sat, 10 Mar 2018 22:42:28 +0100 [thread overview]
Message-ID: <20180310214228.uie2qxbiihaukpz5@doom> (raw)
In-Reply-To: <87woykx2ef.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 2014 bytes --]
On Sat, Mar 10, 2018 at 12:19:52AM +0100, Ludovic Courtès wrote:
>Danny Milosavljevic <dannym@scratchpost.org> skribis:
>
>> [huge build]
>>> The current tradeoff is to make that diagnostic based on the running
>>> kernel, even if it’s an approximation.
>>
>> Ah, good point.
>>
>>> If that’s fine with you I’d like to fix this bug with the conservative
>>> patch below.
>>
>> Sure, looks good.
>
>Pushed as 8d5c14edf5a6d01f859b1aa00c836ffdb5ddecf4.
I'm afraid that now it leads to:
Backtrace:
12 (primitive-load "/usr/bin/guix")
In guix/ui.scm:
1501:12 11 (run-guix-command _ . _)
In ice-9/boot-9.scm:
829:9 10 (catch _ _ #<procedure 7fa007c66420 at guix/ui.scm:552…> …)
829:9 9 (catch _ _ #<procedure 7fa007c66438 at guix/ui.scm:660…> …)
In guix/scripts/system.scm:
1180:8 8 (_)
1052:6 7 (process-action _ _ _)
In guix/store.scm:
1443:24 6 (run-with-store _ _ #:guile-for-build _ #:system _ # _)
In guix/scripts/system.scm:
1065:13 5 (_ _)
764:4 4 (perform-action init #<<operating-system> kernel: #<pa…> …)
In srfi/srfi-1.scm:
640:9 3 (for-each #<procedure 55b8f874b9c0 at guix/scripts/sys…> …)
In gnu/system/linux-initrd.scm:
360:4 2 (check-device-initrd-modules "/dev/nvme0n1p2" ("ahci" …) …)
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
This is part of my config:
(initrd (lambda (file-system . rest)
(raw-initrd file-systems
#:linux linux-x1-sw1
#:linux-modules '()
#:helper-packages '(linux-firmware-initrd-x1-sw1)
#:mapped-devices mapped-devices)))
I don't have any modules to be loaded in initrd, kernel is compiled
using my configuration which fits my needs and follows the HW it will run on.
S_W
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-03-10 21:43 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180310214228.uie2qxbiihaukpz5@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 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.