Subject: Re: [bug#30629] [PATCH 0/5] Detect missing modules in the initrd

From: Danny Milosavljevic <[email-masked]>
Date: Fri, 2 Mar 2018 19:16:52 +0100

Hmm...

$ make TESTS=iso-image-installer check-system
...
   592:29  2 (map1 _)
   592:17  1 (map1 ("iso9660" "isofs" "overlay"))
In unknown file:
           0 (scm-error misc-error #f "~A ~S ~S" ("module not fo?" ?) ?)

ERROR: In procedure scm-error:
module not found "iso9660.ko" "/gnu/store/lzmq94d47pcgr38kwdmy67x6cd1f9ip4-linux-libre-4.15.7/lib/modules"
note: keeping build directory `/tmp/guix-build-linux-modules.drv-0'
builder for `/gnu/store/minvqnpizvasga2gc68ph488y69vw9w2-linux-modules.drv' failed with exit code 1
@ build-failed /gnu/store/minvqnpizvasga2gc68ph488y69vw9w2-linux-modules.drv - 1 builder for `/gnu/store/minvqnpizvasga2gc68ph488y69vw9w2-linux-modules.drv' failed with exit code 1
cannot build derivation `/gnu/store/cic83a4mlg3kvp3iygmm721rk5lz44ks-init.drv': 1 dependencies couldn't be built

(It's called "isofs" but there are aliases in modules.alias: fs-iso9660, iso9960)

I think now we need to take care about the module key resolution order with modules.alias, modules.builtin and modules.dep.