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 sense to
have these modules loaded by default, given the widespread use of SATA
disks.
I doubt that hardcoding the AHCI module names into linux-modules is the
preferred way to do this, but I wanted to propose something simple to
get the discussion started. :)
Thoughts?
>From 2c9599720a8646a79fb3cb9517f7f0e6f1bfa25f Mon Sep 17 00:00:00 2001
From: David Thompson <dthomps...@worcester.edu>
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/system/linux-initrd.scm b/gnu/system/linux-initrd.scm
index 9e39f2d..62f95c5 100644
--- a/gnu/system/linux-initrd.scm
+++ b/gnu/system/linux-initrd.scm
@@ -249,7 +249,8 @@ exception and backtrace!)."
(define linux-modules
;; Modules added to the initrd and loaded from the initrd.
- `(,@(if (or virtio? qemu-networking?)
+ `("libahci.ko" "ahci.ko" ; modules for SATA controllers
+ ,@(if (or virtio? qemu-networking?)
virtio-modules
'())
,@(if (find (file-system-type-predicate "cifs") file-systems)
--
2.0.0
--
David Thompson
Web Developer - Free Software Foundation - http://fsf.org
GPG Key: 0FF1D807
Support the FSF: https://fsf.org/donate
