Hi!
l...@gnu.org (Ludovic Courtès) skribis:
> Nevertheless, the risk of false-positives obviously exists, hence the
> need for an escape hatch.
>
> What about the attached patch?
Pushed as 61b1dbbdcd87f6b37d6b87715a9a4da4e63485ab.
Thanks,
Ludo’.
On Mon, Mar 12, 2018 at 01:24:37PM +0100, Danny Milosavljevic wrote:
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
Hello,
Danny Milosavljevic skribis:
>> 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
>>
Or maybe to this:
> > # guix system init config.scm /mnt/mnt/
> > ...
> > config.scm:64:9: WARNING: you may need these modules in the initrd for
> > /dev/nvme0n1p2: shpchp
>^^^ not error
> > hint: Try adding them to the `initrd-modules' field of your
> > `operating-system'
> 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 li
On Sun, Mar 11, 2018 at 10:38:18PM +0100, Ludovic Courtès wrote:
Tomáš Čech skribis:
In ice-9/boot-9.scm:
829:9 1 (catch system-error # …)
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
Hi Ludo,
> BTW, we should add a ‘--skip-checks’ option to ‘guix system’ so that
> users can skip those checks. That’d provide an escape hatch in case
> ‘check-device-initrd-modules’ makes the wrong diagnostic.
Yeah, good idea!
pgpBUFlRA1b_T.pgp
Description: OpenPGP digital signature
On Sat, Mar 10, 2018 at 12:19:52AM +0100, Ludovic Courtès wrote:
Danny Milosavljevic 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
Danny Milosavljevic 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.
Push
[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.
While we are approximating we could also in a la
Hello,
Danny Milosavljevic skribis:
> there's a problem with check-device-initrd-modules: on "guix system init"
> it doesn't get linux-module-directory and doesn't pass it on to
> matching-modules.
> matching-modules then eventually defaults to (current-alias-file) - which is
> not
> found on
Hi Ludo,
there's a problem with check-device-initrd-modules: on "guix system init"
it doesn't get linux-module-directory and doesn't pass it on to
matching-modules.
matching-modules then eventually defaults to (current-alias-file) - which is not
found on a non-GuixSD system.
Would it be possible
`guix system init` seems to be broken for non GuixSD distirbutions:
When I tried it on openSUSE:
# guix system --no-bootloader init /Devel/git/guix-config/config.scm /mnt/mnt/
;;; note: source file /Devel/extra/gnu/packages/connman.scm
;;; newer than compiled /root/.config/guix/latest/gnu/p
13 matches
Mail list logo
