Ludovic Courtès writes:
> David Thompson skribis:
>
>> From 2c9599720a8646a79fb3cb9517f7f0e6f1bfa25f Mon Sep 17 00:00:00 2001
>> From: David Thompson
>> Date: Fri, 18 Jul 2014 11:03:02 -0400
>> Subject: [PATCH] linux-initrd: Add AHCI modules.
>>
>>
"Jason Self" skribis:
> I would prefer to not maintain different kernel configurations (for
> Guix and non-Guix.)
This is an argument in favor of adding the modules to the initrd, rather
than changing the kernel config, right? (If yes, I agree.)
> If the initial ramdisk doesn't have enough stu
David Thompson skribis:
> From 2c9599720a8646a79fb3cb9517f7f0e6f1bfa25f Mon Sep 17 00:00:00 2001
> From: David Thompson
> Date: Fri, 18 Jul 2014 11:03:02 -0400
> Subject: [PATCH] linux-initrd: Add AHCI modules.
>
> * gnu/system/linux-initrd (linux-modules): Add them.
Ah yes, OK to push!
Ludo’.
I would prefer to not maintain different kernel configurations (for
Guix and non-Guix.)
If the initial ramdisk doesn't have enough stuff present to be able to
boot successfully, this seems to provide a good example of entire
directories of stuff to include:
http://www.linuxfromscratch.org/blfs/vi
David Thompson writes:
> One problem that Mark Weaver and I encountered when intalling the GNU
> system on our Thinkpad X60s was that initrd couldn't boot from our SATA
> hard disks without passing additional kernel modules in the
> operating-system declaration. I think it would make a lot of se
ep 17 00:00:00 2001
From: David Thompson
Date: Fri, 18 Jul 2014 11:03:02 -0400
Subject: [PATCH] linux-initrd: Add AHCI modules.
* gnu/system/linux-initrd (linux-modules): Add them.
---
gnu/system/linux-initrd.scm | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/gnu/syst
